[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Central Reporting/Monitoring
From: |
David Douthitt |
Subject: |
Re: Central Reporting/Monitoring |
Date: |
Thu, 12 Jun 2003 14:42:20 -0500 |
On Thursday, June 12, 2003, at 10:32 AM, Chip Seraphine wrote:
Syslog seems pretty reasonable, although not everything you might want
goes thru there.
In my environment, I patched cfengine to use the "local1" facility (to
seperate cfengine messages from other noise) and dump local1 to a
specific file (/var/log/cfengine.log). I then run swatch against that
log file and have swatch report certain strings or any message that
went at the .err priority or higher.
You could also use syslog-ng to sort based on the name or source or a
pattern in the syslog message.
I think that sounds like a good idea... I'm going to try it myself :-)
I already use syslog-ng to sort syslog messages nicely...
- Central Reporting/Monitoring, Dennis, Richard, 2003/06/12
- RE: Central Reporting/Monitoring, Steve Bergeon, 2003/06/12
- Re: Central Reporting/Monitoring, Chip Seraphine, 2003/06/12
- Re: Central Reporting/Monitoring, Nate Campi, 2003/06/12
- Re: Central Reporting/Monitoring,
David Douthitt <=
- Re: Central Reporting/Monitoring, Will Lowe, 2003/06/12
- pass arguments to cfagent via cfexecd?, Will Lowe, 2003/06/13
- Re: pass arguments to cfagent via cfexecd?, Mark . Burgess, 2003/06/13
- Re: pass arguments to cfagent via cfexecd?, Will Lowe, 2003/06/13
- Re: pass arguments to cfagent via cfexecd?, Will Lowe, 2003/06/13