The sys admin’s daily grind: phpLogCon

MILKING MACHINE 2.0

Author(s):

Using SQL to sift syslog data out of a database is an admittedly universal, but also fairly convoluted approach. phpLogCon, with its web interface, gives admins an easier option.

In last month’s issue, I talked about RSyslog, a replacement for the syslog daemons. Instead of referencing the standard logfiles in /var/log, RSyslog works with one or multiple databases in which it logs local results or data supplied by remote servers. I always use one database, Maillog, for the mail facility, and a second database, syslog, for all other messages.
A couple of scripts extract statistics on spam filter performance from the Maillog DB.

Read full article as PDF:

069-069_charly.pdf  (262.88 kB)

Related content

  • Charly's Column

    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?

  • Security Lessons: Rsyslog

    Might as well do it properly – rsyslog.

  • Charly's Column: lsof

    The shorter a command, the longer the list of support parameters. This rule applies to lsof, one of Charly’s favorite commands.

  • Charly's Column: Snoopy

    Sometimes sys admin Charly needs to know when exactly he did something ingenious on one of his servers. Finding an infallible memory aid is difficult, you might think. "Peanuts!" says Charly.

  • Charly's Column

    It would be great if every MySQL database enjoyed perfect health 24 by 7, but unfortunately, trouble sometimes strikes. A logfile isn’t much help if you are investigating why a database is flooded with requests. Mtop to the rescue.

comments powered by Disqus

Direct Download

Read full article as PDF:

069-069_charly.pdf  (262.88 kB)

News