Case Study: LogicMonitor achieves better Puppet run visibility with Puppet

How to Monitor the Success or Failure of Puppet Runs

LogicMonitor used Puppet for Linux configuration management, but needed a way to detect when Puppet agent runs failed or stopped altogether on end nodes. Because missed runs could leave critical updates unapplied and cause production issues, LogicMonitor looked for a way to monitor the success, failure, and recency of Puppet runs rather than only the Puppet server itself.

Puppet’s last-run summary data was collected through MCollective and stored in MongoDB, then pulled into LogicMonitor for graphing and alerting. Puppet and LogicMonitor together enabled tracking of time since last run, events success/failure, and run performance, with alerts configured for delayed updates; in one example, administrators were notified when Puppet runs stopped around 18:00, helping the team catch problems before they impacted production.

LogicMonitor

Jesse Aukeman

Director of Tech Ops