Re: Central Reporting/Monitoring

[Nate Campi]

I chose to kill two birds with one stone, and verify cfengine and
MTA/null mailer config together by using cfrun to trigger a mail message
on all hosts. The script running cfrun knows if it couldn't connect to a
box, and the script that accepts the mail on the mail server can easily
compare the received mail against a "all cfengine hosts" list.

The downside is that I need to make sure I keep the host list up to
date, but whatever automated methods you use to deploy/retire hosts can
do this as well.

On Thu, Jun 12, 2003 at 10:32:02AM -0500, 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.
> 
> I also have certain classes that, when defined, kick off shell commands 
> that generate emails to system admins (and sometimes their pagers).   
> This is useful for situations that might not show up in the syslogs, or 
> as a 'just to be sure' notification for really dire situations.
> 
> Dennis, Richard wrote:
> 
> >How do people keep track of monitoring how cfengine is running on all their
> >boxes? 
> >
> >What is the best way to do this?  Send data via some method back to a
> >reporting server?

-- 
Nate Campi    http://www.campin.net