-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.13.z
-
None
-
-
-
Moderate
-
No
-
MON Sprint 240
-
1
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
These alerts fire without a namespace label: * KubeStateMetricsListErrors * KubeStateMetricsWatchErrors * KubeletPlegDurationHigh * KubeletTooManyPods * KubeNodeReadinessFlapping * KubeletPodStartUpLatencyHigh Alerting rules without a namespace label make it harder for cluster admins to route the alerts.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Always
Steps to Reproduce:
1. Check the definitions of the said alerting rules.
Actual results:
The PromQL expressions aggregate away the namespace label and there's no static namespace label either.
Expected results:
Static namespace label in the rule definition.
Additional info:
https://github.com/openshift/enhancements/blob/master/enhancements/monitoring/alerting-consistency.md#style-guide Alerts SHOULD include a namespace label indicating the source of the alert. Many alerts will include this by virtue of the fact that their PromQL expressions result in a namespace label. Others may require a static namespace label
- is cloned by
-
OCPBUGS-17197 Missing namespace label for HighOverallControlPlaneMemory alerting rule
- Closed
- is depended on by
-
MON-3266 Report alerting rules without namespace label
- Closed
- links to
-
RHEA-2023:5006 rpm