HiWe have an automatic Jenkins job that runs early every morning. If the job is failed, i.e. red, it is not a big problem.
But if it is red 2 times in a row, an alert has to be triggered and a human has to look at it.
Here what I have done:
---
XXX-Job-Status (1 active)
name: XXX-Job-Status
expr: default_jenkins_builds_last_build_result{jenkins_job=~".+zedf"} != 1
for: 1d1h
labels:
channel: mail
severity: critical
annotations:
description: The Jenkins Job (cron schedule) zedf failed twice in a row
---
Doesn't work, the alert is always in pending state, even though it
failed about 8 times in a row.
The metric is updated only once a day (in the morning). kind regards Evelyn -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/d3c04591-61b2-87a9-a958-b7eb50b0b424%40disroot.org.
OpenPGP_0x61776FA8E38403FB.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
