At what point should you consider an alert resolved?
A blog on monitoring, scale and operational Sanity
At what point should you consider an alert resolved?
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.
The Prometheus instrumentation best practices say to "Avoid missing metrics". Let's look at why, and how to deal with it.
Should you unit test every bit of instrumentation you add? Not always.
You may have noticed that most PromQL functions and operators remove the metric name in their result. Let's look at why.
It's often claimed that an advantage of push-based monitoring systems is that, compared to pull-based systems like Prometheus, they don't need service discovery. This isn't true, and I'm going to explain why.
The Prometheus client library guidelines recommend having a Child
be returned via labels()
. Why?