Archives Puppet

by Jeff Barlam, LogicMonitor’s Financial Controller

As LogicMonitor’s Financial Controller, I’m proud to share some exciting news from the LogicMonitor finance department. I know, I know … “exciting” and “finance” rarely go together … but if you’re adventurous enough to read on, you’ll hear about how we’re bringing accuracy and efficiency to our accounting operations using two leading technologies: Zuora and LogicMonitor.

As hopefully you already know, LogicMonitor is the automated IT performance monitoring platform. We’re fortunate to have a rapidly expanding customer base and an ever-growing number of devices being monitored by our customers around the globe. Even better, the LogicMonitor solution allows customers to easily add devices to monitoring and scale up or down depending on their needs. But with that comes complexity in the accounting world. Read more »

Do you use Puppet? Hear from Alanna Brown of PuppetLabs about the power of integrating LogicMonitor with Puppet.

Want to learn more? Visit our Puppet integration page.

This post, written by LogicMonitor’s Director of Tech Ops, Jesse Aukeman, originally appeared on HighScalability.com on February 19, 2013

If you are like us, you are running some type of linux configuration management tool. The value of centralized configuration and deployment is well known and hard to overstate. Puppet is our tool of choice. It is powerful and works well for us, except when things don’t go as planned. Failures of puppet can be innocuous and cosmetic, or they can cause production issues, for example when crucial updates do not get properly propagated.


In the most innocuous cases, the puppet agent craps out (we run puppet agent via cron). As nice as puppet is, we still need to goose it from time to time to get past some sort of network or host resource issue. A more dangerous case is when an administrator temporarily disables puppet runs on a host in order to perform some test or administrative task and then forgets to reenable it. In either case it’s easy to see how a host may stop receiving new puppet updates. The danger here is that this may not be noticed until that crucial update doesn’t get pushed, production is impacted, and it’s the client who notices.

How to implement monitoring?

Monitoring is clearly necessary in order to keep on top of this. Rather than just monitoring the status of the puppet server (a necessary, but not sufficient, state), we would like to monitor the success or failure of actual puppet runs on the end nodes themselves. For that purpose, puppet has a built in feature to export status info Read more »


Popular Posts
Subscribe to our blog.