Background

In 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 incluster 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

Steps

1. Use the backend API to list the alert managers that are different from the in-cluster one
2. If there is only one alert manager, we need to make sure to inform the user which one is selected
3. On Selecting an alert manager, all the requests for creating and silencing alerts should be targeted to the selected alert manager