Re: Central Reporting/Monitoring

[Chip Seraphine]

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?
>
> TIA
>
> -Rick
>
> ------------------------------------------------------------------------------
> This message is intended only for the personal and confidential use of the 
> designated recipient(s) named above.  If you are not the intended recipient of 
> this message you are hereby notified that any review, dissemination, 
> distribution or copying of this message is strictly prohibited.  This 
> communication is for information purposes only and should not be regarded as an 
> offer to sell or as a solicitation of an offer to buy any financial product, an 
> official confirmation of any transaction, or as an official statement of Lehman 
> Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
> Therefore, we do not represent that this information is complete or accurate 
> and it should not be relied upon as such.  All information is subject to change 
> without notice.
>
>
>
>
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-cfengine
>
>
>