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

Alerts with a non-standard severity label should be filtered out from Telemetry

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.12
    • Monitoring
    • None
    • Moderate
    • None
    • MON Sprint 259
    • 1
    • False
    • Hide

      None

      Show
      None
    • NA
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-41908. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-39246. The following is the description of the original issue:

      Description of problem:

          Alerts with non-standard severity labels are sent to Telemeter.

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

          All supported versions

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create an always firing alerting rule with severity=foo.
          2. Make sure that telemetry is enabled for the cluster.
          3.
          

      Actual results:

          The alert can be seen on the telemeter server side.

      Expected results:

          The alert is dropped by the telemeter allow-list.

      Additional info:

      Red Hat operators should use standard severities: https://github.com/openshift/enhancements/blob/master/enhancements/monitoring/alerting-consistency.md#style-guide
      Looking at the current data, it looks like ~2% of the alerts reported to Telemter have an invalid severity.

              spasquie@redhat.com Simon Pasquier
              openshift-crt-jira-prow OpenShift Prow Bot
              Junqi Zhao Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: