Good afternoon (morning|night) all, I've just posted an article on how I manage automatic monitoring with Puppet http://www.example42.com/?q=Test_Driven_Puppet_Infrastructures_deployment and besides the shameless spam on this list I'd like to take this occasion to raise again a topic discussed with Nigel, Dan and others in the last Puppetcamp, in this list and somewhere else in the past.
We all think, I suppose, that Puppet should somehow manage automatically the monitoring of the resources it provides. How this is done is a whole universe of complexity, alternative approaches and design decisions. What I've done is an attempt to use standard naming to define what to monitor in an abstract way (without reference to the tool actually used for monitoring) and a (working in different productions) implementation entirely based on Puppet DSL that prefers linearity and extendability over performance and optimization of resources. I think it would be interesting to know how people are dealing with this topic and how/when this will eventually implemented directly in Puppet code. All the best Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
