|
|
|
|
|
|
Digg |
|
|
|
Well-used services write reams of log information to disk, which is not only bothersome from a storage perspective but also pushes grep and the usual group of statistics tools to their limits. Will hitching the syslog daemon up to a database help?
Who said length doesn’t matter? My spam filters alone give me a 3GB logfile daily, which would be fine if I just needed the beast to check up on the occasional error. Because I need to extract a whole bunch of statistics about spam and virus threats from the file, grepping such enormous files takes ages, besides creating far too much I/ O overhead.
RSyslog took me a giant leap closerm to finding a solution – it logs directly to a MySQL or PostgreSQL database, meaning that I can replace my grep commands with fast SQL statements. RSyslog is included with many distributions and is the default application in Fedora 8, for example. By default, my Ubuntu lab environment runs sysklogd, making it easy for me to switch to RSyslog. For the time being, I can even keep my old syslog.conf. For the most part, RSyslog’s configuration file is the same as the legacy format, although it does support a couple of additional options for linking up with the database.
|
|
|
| Related Articles | |
|---|---|
| APP WATCH | Application performance monitoring with Hyperic HQ |
| KDE COOKING | Create a KDE-based recipe database |
| When Geeks Cruise | Linux Lunacy, Perl Whirl,MySQL Swell: Open Source technologists on board |
| BOOK REVIEWS | |
| BOOK REVIEWS | |
| BOOK REVIEWS | |
| Special Linux Magazine 3 for 1 Offer |
|---|
|
Get 3 Issues + 3 DVDs for the price of a single issue! Let Linux Magazine's hands-on, technical articles guide you in your daily Linux use. Check out bonus DVDs like Ubuntu, SUSE, or Fedora and save the download. Only available for a limited time. Don't miss out! |
Comments