Metrics-Driven Development - Part II



Metrics-Driven Development - Part II


In this second installment on Metrics-Driven Development (MDD), we dive past the abstract and into the realm of real-life adventure.  Read along as we document Librato's own use of MDD during a recent production outage, and discover how MDD can help you detect, identify, troubleshoot, debug and recover from production problems.

Read More

Automatic Clearing of Triggered Alerts


New Features, Alerting


Today we are are happy to announce the next big step in our alerting platform: Automatic Clearing of Triggered Alerts. With alert clearing you will now receive a clear notification when the alert is no longer in a triggered state. For threshold and windowed alert conditions, any measurement that has returned to normal levels for a source will clear the alert. For absent alert conditions, any measurement that reappears for the source will clear the alert.

Read More

Heroku Status Codes and Release Annotations



Our Heroku users know how awesome the Librato Add-On is for tracking application performance and customer metrics on our favorite Platform-As-A-Service. It was already super easy to monitor Router metrics and Postgres metrics with our support for Heroku log-drains. Today we're pleased to announce that our Librato Add-on for Heroku is now able to record Router status codes and release events as annotations!

Read More

Unified CPU Metrics in Collectd


Integrations


One of the things that makes collectd such an effective collector is all of the metrics it gives you with a minimal amount of effort. As I touched on in a previous blog post, we took extra steps by adding Service-Side Filtering to help our customers filter the collectd metrics we store on your behalf. However, there are still a number of "noisy" metrics where it might be desirable to condense them before publishing them to Librato.

Read More