Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8032

Provide an ability to silence all alerts of the same kind within a namespace in a single action in RHOCP 4

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Provide the ability to silence all alerts of the same kind within a namespace in a single action

       

      2. What is the nature and description of the request?

      The current alerting behavior in OpenShift, managed via Alertmanager, requires each alert to be silenced individually. This becomes inefficient and error-prone in scenarios where multiple alerts of the same type (e.g., PodDisruptionBudgetAtLimit) are triggered across resources within a single namespace.

      In the reported case, the customer has defined 15+ PodDisruptionBudget (PDB) objects, each triggering the same alert. Since these alerts are considered informational and expected (as per KCS 6968768), they do not require active remediation and can be safely silenced.

      The request is to enhance the Alertmanager interface to allow users to silence all alerts of the same kind within a specific namespace at once. For example, by applying a silence using label-based selectors like `alertname=PodDisruptionBudgetAtLimit` and `namespace=<value>` or an option/filter in the OCP Web Console.

       

      3. Why does the customer need this? (List the business requirements here)

      The customer is receiving repetitive PodDisruptionBudgetAtLimit alerts across 15+ PDBs in a single namespace.

      These alerts are expected, as confirmed by Red Hat in KCS 6968768.

      Silencing each alert manually introduces unnecessary operational overhead and is error-prone, especially during time-sensitive activities like upgrades or deployments.

      The customer wants a more scalable way to suppress such alerts in bulk for a namespace, rather than having to create multiple silences manually.

      A feature to silence same-kind alerts in a namespace with a single action would:

        • Reduce alert fatigue and noise
        • Improve operational efficiency for platform and DevOps teams
        • Lower the risk of accidental misconfiguration of alert rules or silences
        • Align with alert best practices during planned maintenance windows

       

      4. List any affected packages or components.

      Alertmanager
      OCP Web Console
      Prometheus Alerting Rules
      Monitoring stack components

              rh-ee-rfloren Roger Florén
              rhn-support-sdharma Suruchi Dharma
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                None
                None