The standard way to use metrics in Prometheus is to declare them at file level, before using them. Why?
Reliable Insights
A blog on monitoring, scale and operational Sanity
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?
The Blackbox exporter can perform ICMP probes. Let's see how.
In a previous post I looked at setting the external URL. What if the reverse proxy is sending a different path than the user is using?
Sometimes users will not access Prometheus's UI directly, instead using another URL. How do you make this work?
Shutting down Prometheus properly helps reduce the risk of delays at startup. So how do you do that?
