+++ This bug was initially created as a clone of Bug #1955462 +++
+++ This bug was initially created as a clone of Bug #1955457 +++
Description of problem:
The container_memory_failures_total metric is in the top 10 of metrics with high cardinality. It isn't used in any rule or dashboard. Storing the metric in Prometheus increases memory usage for no benefit.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open the Prometheus UI, go to the Status > TSDB status page and look at the "Top 10 series count by metric names" section.
container_memory_failures_total is listed.
container_memory_failures_total isn't present.
checked with 4.6.0-0.nightly-2021-05-27-033913, no container_memory_failures_total metrics now
# token=`oc sa get-token prometheus-k8s -n openshift-monitoring`
# oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep container_memory_failures_total
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 (OpenShift Container Platform 4.6.32 bug fix 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.