Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-5625

(ACM 2.7) ACM Observability alert "ViolatedPolicyReport" does not return cluster name

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • No
    • Observability Sprint 2023-11
    • Moderate

      Description of problem:

      When querying for the ALERTS metric that is generated for the alert rule "ViolatedPolicyReport", there isn't a "cluster" label available to filter the alert by cluster. The user will need to know the cluster ID in order for them to filter for the correct cluster.

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

      2.7+

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy ACM 2.7+ on cluster.
      2. Enable Observability.
      3. View ALERTS metric in Observability Grafana.
      4. Filter for alertname="ViolatedPolicyReport"
      5. Verify that the "cluster" label is not available. (Only clusterID and managedClusterID)

      Actual results:

      The "cluster" label is missing within the ALERTS{alertname="ViolatedPolicyReport"} time series; however, the label is available for the other alerts.

      Expected results:

      The "ViolatedPolicyReport" alert should contain the "cluster" label.

      Additional info:

      Screenshots are available to show the missing labels.

        1. Screenshot 2023-05-01 at 11.59.52 AM.png
          249 kB
          Disaiah Bennett
        2. Screenshot 2023-05-01 at 12.00.10 PM.png
          254 kB
          Disaiah Bennett
        3. image-2023-06-14-20-26-55-843.png
          148 kB
          ChangLiang Qu
        4. image-2023-06-14-20-27-13-073.png
          290 kB
          ChangLiang Qu
        5. image-2023-06-14-20-28-45-970.png
          318 kB
          ChangLiang Qu

            dbennett@redhat.com Disaiah Bennett
            dbennett@redhat.com Disaiah Bennett
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: