As PromQL has evolved, there are some functions that should no longer be used.
While the irate() function is useful for granular graphs, it is not suitable for alerting.
When relabelling is suggested for selecting targets with service discovery there’s sometimes a misunderstanding that relabelling can only change labels. That’s not the case.
Continuing in our exploration of the ongoing epic saga of push vs. pull where the very future of humanity is at stake, let’s look at two general classes of push that are often conflated.
We’re often asked how to call set() on a Counter. So how do you do that?
The Prometheus instrumentation best practices say to “Avoid missing metrics”. Let’s look at why, and how to deal with it.
Prometheus is architected for reliability of alerting, how do you set it up?
If you’ve determined a metric should be tested, how do you go about that?
Should you unit test every bit of instrumentation you add? Not always.
If you’ve an existing instrumentation library in use, it’s not always practical to immediately switch to a Prometheus instrumentation library. There are a multitude of integrations available to aid your transition.