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-drainsToday 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

Three Ways to Aggregate Metrics on Heroku


Integrations


Three Ways to Aggregate Metrics on Heroku

We're honored to share this guest post by Mathias Meyer, founder of Travis CI.  Mathias outlines the challenges of collecting metrics as you scale out your operations on Heroku.  He highlights a few select ways to collect and aggregate that help work around these challenges, with a focus on Librato Metrics. The general means, though, are applicable to any aggregation service or tool.

Read More

Service-Side Filtering with Collectd



Our new collectd integration has been hugely popular with users that want an easy way to gather all of their application and system metrics. Precisely because it's so easy to collect a wealth of new data, we also wanted to give users the tools to store only the collectd metrics that they find personally useful. This is why we developed our Service-Side Filtering for collectd.

Read More