http://mberkay.disqus.com/enTue, 29 Jun 2010 17:56:41 -0000http://www.mberkay.com/2010/06/29/impact-of-infrastructure-automation-tools-on-monitoring/#comment-59906035<p>Hi Matt, <br>The demo you had sounds very good. As you've also mentioned there are number of potential integration points between monitoring and infrastructure automation tools that would significantly increase the value of both sets of tools. I'm just beginning to explore them, and possibilities are indeed exciting. </p> <p>Looking forward to learn more about your Chef integration when it becomes available!</p> <p>Berkay</p>berkayTue, 29 Jun 2010 17:56:41 -0000http://www.mberkay.com/2010/06/29/impact-of-infrastructure-automation-tools-on-monitoring/#comment-59902683<p>Excellent post, some Zenoss users are already on this track. We've got integrations for Puppet (<a href="http://community.zenoss.org/docs/DOC-5818)" rel="nofollow">http://community.zenoss.org/do...</a> and Cfengine (<a href="http://community.zenoss.org/docs/DOC-5897)" rel="nofollow">http://community.zenoss.org/do...</a> and I'm working on the Chef integration (should have code available soon). Eventually the Zenoss cookbook for Chef should deploy a Zenoss server and automatically monitor the devices managed by Chef. One of the really exciting applications of tighter integration between infrastructure automation and monitoring is using the monitoring application to dynamically allocate or replace nodes in response to events (outages, heavy load, etc.). We demoed a bit of this at Velocity (Zenoss/Chef/Dyn) and should have another demo at OSCON. </p> <p>Thanks,<br>Matt Ray<br>Zenoss Community Manager<br></p>Matt RayTue, 29 Jun 2010 17:28:53 -0000