Bug 2001566
| Summary: | Enable alerts for prometheus operator in UWM | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Prashant Balachandran <pnair> |
| Component: | Monitoring | Assignee: | Prashant Balachandran <pnair> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | Brian Burt <bburt> |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | amuller, anpicker, aos-bugs, bburt, erooth, spasquie |
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, alerts for the Prometheus Operator component did not apply to the Prometheus Operator that runs the `openshift-user-workload-monitoring` namespace when user-defined monitoring is enabled.
Consequently, no alerts fired when the Prometheus Operator that manages the `openshift-user-workload-monitoring` namespace encountered issues.
With this release, alerts have been modified to monitor both the `openshift-monitoring` and `openshift-user-workload-monitoring` namespaces.
As a result, cluster adminisrators receive alert notifications when the Prometheus Operator that manages user-defined monitoring encounters issues.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:07:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Prashant Balachandran
2021-09-06 12:24:16 UTC
checked with 4.10.0-0.nightly-2021-09-17-190348, prometheus operator alerts include UWM Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056 |