Prometheus 2.4.0 is now out, following on from 2.3.0 back in June with many fixes and improvements.
Reliable Insights
A blog on monitoring, scale and operational Sanity
The textfile collector is handy for monitoring machine-level cronjobs. How would you go about that?
If a misconfiguration leads to unwanted time series, it'd good to know how to remove them.
While not a problem specific to Prometheus, being affected by the open files ulimit is something you're likely to run into at some point.
While the Java client library uses pom.xml and Maven, there's nothing stopping you from using other tools such as Gradle
The standard way to use metrics in Prometheus is to declare them at file level, before using them. Why?
For counting how many times a thing has happened you can use a counter and rate(), but that doesn't work across batch jobs.
After many months of work, Prometheus: Up&Running is now available for purchase!
In the previous post we looked at dealing with when all the targets for a job had disappeared. What if you wanted to alert on specific metrics from one target disappearing?
Alerting on numbers being too big or small is easy with Prometheus. But what if the numbers go missing?
