-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.18.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
MON Sprint 271
-
1
-
Done
-
None
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-56732. The following is the description of the original issue:
—
Description of problem:
When using promtool to check high cardinality mterics, it reports 0 as the value. $ oc -n openshift-monitoring -c prometheus prometheus-k8s-1 -- promtool tsdb analyze /prometheus --limit=10 --- Highest cardinality metric names: 0 :node_memory_MemAvailable_bytes:sum 0 ALERTS 0 ALERTS_FOR_STATE 0 aggregator_discovery_aggregation_count_total 0 aggregator_unavailable_apiservice 0 aggregator_unavailable_apiservice_total 0 alertmanager_alerts 0 alertmanager_alerts_invalid_total 0 alertmanager_alerts_received_total 0 alertmanager_build_info
Version-Release number of selected component (if applicable):
RHOCP 4.18.z
How reproducible:
100%
Steps to Reproduce:
1. Run command "oc -n openshift-monitoring -c prometheus prometheus-k8s-1 -- promtool tsdb analyze /prometheus --limit=10"
2. Check "Highest cardinality metric names" section in the output.
3.
Actual results:
"Highest cardinality metric names" reports list of metrics but value is 0
Expected results:
It should report the actual value of the high cardinality metrics.
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:8280
OpenShift Container Platform 4.17.32 bug fix update
