-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
False
-
Undefined
-
-
1. Proposed title of this feature request
Runbooks for Resolving the Default Alerts Configured in OCP 4.x
2. What is the nature and description of the request?
Over time the customer created alerts to identify issues within our 3.x clusters. It seems many of those alerts (plus new additional alerts) are included in OpenShift v4. The customer is now trying to understand what the new alerts mean and how to go about resolving them when they fire. If Redhat configures these alerts out of the box, the customer figure there is a good reason. The customer also believes that if there are known conditions to alert on, they should have a known solution. This is a request to have the alert solutions (runbooks) published somewhere (preferably as a link to a KB or solution document) so that our alerts can reference the URL by way of an annotation.
3. Why does the customer need this? (List the business requirements here)
This provides the customer's support teams a quick point of reference and saves them time from having to understand the alert, identify the problem, come up with a solution, and document said solution.
4. List any affected packages or components.
Prometheus
- is related to
-
LOG-915 Move Logging Operator from Operator maturity level 3 to 4
- Closed
-
LOG-860 Move Elasticsearch Operator from Operator maturity level 3 to 4
- Closed
-
OCPPLAN-6068 Increase the overall quality for OpenShift's OOTB alerting rules
- Closed