Uploaded image for project: 'Observability UI'
  1. Observability UI
  2. OU-396

DP: Monitoring plugin in ACM

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • COO 1.0.0 RC
    • 2024Q4
    • None
    • None
    • DP: Monitoring plugin in ACM
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • NEW
    • To Do
    • OBSDA-565 - Multicluster Alerting UI / ACM
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • OBSDA-565Multicluster Alerting UI / ACM
    • NEW
    • 0% To Do, 0% In Progress, 100% Done

      Description

      "In order to provide ACM with the same monitoring capabilities OCP has, we as the Observability UI Team need to allow the monitoring plugin to be installed and work in ACM environments."

      Goals & Outcomes

      Product Requirements:

      • Be able to install the monitoring plugin without CMO, use COO
      • Allow the monitoring plugin to use a different backend endpoint to fetch alerts, ACM has is own alert manager
      • Add a column to the alerts list to display the cluster that originated the alert
      • Include only the alerting parts which include the alerts list, alert detail and silences

      UX Requirements:

      • Align UX text and patterns between ACM concepts (hub cluster, spoke cluster, core operators) and current the monitoring plugin

      Open Questions

      • Do the current monitoring plugin and the ACM monitoring plugin need to coexist in a cluster?
      • Do we need to connect to a different prometheus/thanos or is just a different alert manager?

              gbernal@redhat.com Gabriel Bernal
              gbernal@redhat.com Gabriel Bernal
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: