Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3364

[CEE.neXT]UserWorkLoad components failures leading to CMO degradation/unavailability should be easy to identify

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • UWM components failures identification
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW
    • 0% To Do, 0% In Progress, 100% Done

      1. Proposed title of this feature request

      UserWorkLoad monitoring pods having any problem should not degrade ClusterMonitoringOperator(CMO)

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

      Currently when customer has enabled UserWorkloadMonitoring(UWM) if any pods under UWM project goes down that inturn degraded CMO which should not happen as Core Monitoring is working totally fine

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

      IF the pods under UWM are having problem CMO degrades this creates panic for CU as one of the core CO is degrade and CU raise a high sev cases which is not at all needed as cluster monitoring is totally fine

      4. List any affected packages or components.

      Cluster Monitoring Operator

      —

      *This was the first idea but isn't what was implemented at the end, check the comments below and the document linked to https://issues.redhat.com/browse/MON-3421.*

       

          There are no Sub-Tasks for this issue.

              rh-ee-amrini Ayoub Mrini
              rhn-support-ssonigra Sonigra Saurab
              Tai Gao Tai Gao
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: