Background

n order for ACM to reuse the monitoring plugin, the plugin needs to connect to a different alert manager. It needs to also contain a new column in alerts to show the source cluster these alerts are generated from

Check the ACM documentation around alerts for reference: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/observability/observing-environments-intro#observability-arch

Outcomes

• The monitoring plugin can discover alert managers present in the cluster
• If multiple alert managers are discovered, the plugin should display a dropdown to select an alert manager to connect to, if no alert manager is discovered the plugin should fallback to the in-cluster one
• The monitoring plugin can connect to a specific alert manager, to create silences
• The monitoring plugin can connect to a specific Prometheus rules endpoint, to read alerts
• Add a new column that can display from which cluster the alert is coming from

UX Goal

Surface an Alert Manager selection component on 4 pages so that users can easily switch between alert managers and know which manager they're currently using. The alert manager will be surfaced on the following pages:

• Alerts page
• Silences page
  • Create silence page (In Silences, when the user clicks on the "Create silences" button)
• Alerting rules page

Adding a new column to the table to display which Cluster name the alert is coming from.

Designs

• Figma designs