Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-4219

Add runbook link to PrometheusRuleFailures

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.12
    • Monitoring
    • None
    • Low
    • None
    • MON Sprint 229
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Before the fix, the alert PrometheusRuleFailure did not have a link to a runbook.
      After the fix, the alert PrometheusRuleFailure now has a link to the runbook to help troubleshoot the alert.
      Show
      Before the fix, the alert PrometheusRuleFailure did not have a link to a runbook. After the fix, the alert PrometheusRuleFailure now has a link to the runbook to help troubleshoot the alert.
    • Enhancement

      Description of problem:

      The current "description" annotation of the PrometheusRuleFailures alert doesn't provide much context about what's happening and what to do next.

      Version-Release number of selected component (if applicable):

      4.12

      How reproducible:

      always

      Steps to Reproduce:

      1. Deploy a PrometheusRule object in the openshift-monitoring namespace that fails to evaluate (annotation with invalid Go template for instance).
2.
3.

      Actual results:

      PrometheusRuleFailures but the description's annotation doesn't provide lots of information about what to do next.

      Expected results:

      Detailed instructions.

      Additional info:

      https://coreos.slack.com/archives/C0VMT03S5/p1669658109764129

       

       

              jmarcal@redhat.com Joao Marcal
              spasquie@redhat.com Simon Pasquier
              Tai Gao Tai Gao
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: