If your applications are restarting regularly, whether due to segfaults or OOMs, it'd be nice to know.
Reliable Insights
A blog on monitoring, scale and operational Sanity
Worried that your application metrics might suddenly explode in cardinality? sample_limit can save you.
So you have just discovered Prometheus and want to try it out or use it to replace your old monitoring system but have run into a part of your stack that you cannot instrument with a client library and for which there are no officially supported exporters. What do you do?
Jobs of an ephemeral nature are often not around long enough to have their metrics scraped by Prometheus. In order to remedy this the Pushgateway was developed to allow for these types of jobs to push their metrics to a metrics cache in order to be scraped by Prometheus long after the original jobs have gone away. This blogpost discusses some of the common pitfalls users tend to fall into when adding the Pushgateway to their monitoring stack.
One of the major changes introduced in Prometheus 2.0 was that of staleness handling. Previously for instant vectors, Prometheus would return a point up to 5 minutes in the past which caused a number of different issues.
Have you ever wondered what percentage of time a given service or application spends up or down?
Having previously discussed why the Prometheus project does not support SSL and user authentication out of the box and detailing how to add basic authentication with Nginx, we will now demonstrate how to do the same with Apache.
In this blogpost we'll run you through a quick 'hello world' example instrumenting a Rails application with the Prometheus ruby client.
