After 1.7.0 back in June, Prometheus 1.8.0 is now out. Let’s look at what has changed.
While doing research for implementing exporters, I’ve noticed some confusion around ratios and percentages that I’d like to clear up.
If you have to choose one of push or pull in your core, which should it be?
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?