-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.10
-
Moderate
-
No
-
MON Sprint 238
-
1
-
False
-
-
This enhancement adds some context when the PrometheusRemoteStorageFailures is triggered, providing a link to the runbook on how to fix it and a link to https://github.com/openshift/runbooks.
-
Enhancement
Description of problem:
When the PrometheusRemoteStorageFailures alert fires, it's not clear for cluster admins what is the impact and how they can resolve it.
Version-Release number of selected component (if applicable):
4.10
How reproducible:
Steps to Reproduce:
1. Configure CMO with an invalid remote-write endpoint (e.g. invalid URL or authentication). 2. 3.
Actual results:
The PrometheusRemoteStorageFailures alert fires but it provides little information about what's the issue and how to remediate.
Expected results:
The PrometheusRemoteStorageFailures alert fires and there's a link to a runbook in https://github.com/openshift/runbooks.
Additional info:
Reported via the internal OpenShift SME mailing list.
- is documented by
-
OBSDOCS-358 Content for new PrometheusRemoteStorageFailures runbook
- Closed
- links to