Ever wanted to use Prometheus for monitoring and alerting on the OpenShift platform?
Reliable Insights
A blog on monitoring, scale and operational Sanity
We've looked at the full Life of a Label. Let's focus on one of the most common confusions around relabelling.
Prometheus alerts use the same powerful PromQL expressions as queries and graphs. This can be used to produce sophisticated alerts.
Prometheus 1.3.0 contained a small change that makes it possible to extract arbitrary labels from systems like Consul that only normally support one-dimensional tags.
Usually the Prometheus Alertmanager will send a given notification to only one destination. What if you want it to go to both Slack and Pagerduty though?
Prometheus doesn't have an explicit boolean type or functionality. However there is a convention and enough power in PromQL to work with booleans.
The Prometheus client library guidelines recommend having a Child be returned via labels(). Why?
There's so many monitoring systems out there these days that it's difficult to figure out what's actually different, and what just has a different name or falls under a different concept. Let's look at the Graphite, InfluxDB and Prometheus query languages and see how the same ideas are represented in each.
A handy feature of the Alertmanager is that almost all notification fields are templatable. This can be used to route emails based on labels.
