Skip to content

Commit

Permalink
Clear up 'Open questions' section
Browse files Browse the repository at this point in the history
  • Loading branch information
simonpasquier committed Mar 15, 2022
1 parent 78d6ddb commit f556b83
Showing 1 changed file with 1 addition and 11 deletions.
12 changes: 1 addition & 11 deletions enhancements/monitoring/multi-tenant-alerting.md
Original file line number Diff line number Diff line change
Expand Up @@ -535,17 +535,7 @@ Mitigation

### Open Questions

1. How can the Dev Console support the UWM Alertmanager?

Users are able to silence alerts from the Dev Console and the console backend
assumes that the API is served by the
`alertmanager-main.openshift-monitoring.svc` service. To support the UWM
Alertmanager configuration, CMO should provide to the console operator the name
of the Alertmanager service managing the user alerts (either
`alertmanager-main.openshift-monitoring.svc` or
`alertmanager.openshift-user-workload-monitoring.svc`). Based on the presence
of the `openshift_io_alert_source` label, the console backend can decide which
Alertmanager service should be queried.
None.

### Test Plan

Expand Down

0 comments on commit f556b83

Please sign in to comment.