A common question around Prometheus client libraries is how much RAM they'll use on a busy process. There tends to be disbelief when we say it's the same as an inactive server. Let's look deeper.
Reliable Insights
A blog on monitoring, scale and operational Sanity
Python is one of the four languages that has an official Prometheus client. Let's take a quick look at how to use it.
The Prometheus instrumentation guidelines say to use seconds, and the timing functions in client libraries follow this. Why?
I've previously mentioned that you shouldn't have the version of your software as either a target label, or exposed via a label on all metrics of your server as it'll make using the metrics more challenging. What should you do instead?
How you choose to name metrics is important. If everyone choose different schemes it'd lead to confusion, irritation and prevent us from sharing and reusing each others' work. I'd like to share some guidelines to help keep things sane for everyone.
Prometheus monitoring is usually against on long-lived daemons, but what if you've a batch job that you want to monitor?
