On 2010-05-25 at 07:31 -0400, Joe McDonagh wrote: > I just finished integrating puppet with nagios so that nagios configs > are automagically built by puppet. It's a little different than what > you're saying but cool nonetheless. If I include an apache class, an > apache service checks gets setup on my nagios master, stuff like that.
So, if service Foo gets droped from your puppet configs somehow, through misconfiguration, your monitoring will stop and the service can go down without you knowing about it? There's an argument for "belt and braces" -- certainly, some of what you monitor can and should be autogenerated from the canonical definition of what should exist; eg, machines, etc. But you want some level of monitoring based on a separate and simpler list of "these are the services we expect to exist". You can then have a separate audit tool, perhaps invoked at VCS commit time, which notifies you of inconsistencies. This may just be a difference of opinion with no right or wrong answer, but your approach scares me a little. -Phil _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
