Bug 1712912 - Cluster console shows double container ram used in OCP 3.11
Summary: Cluster console shows double container ram used in OCP 3.11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
: 1703414 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-22 13:10 UTC by hgomes
Modified: 2023-10-06 18:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:29:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Cluster console double (107.75 KB, image/jpeg)
2019-05-22 13:10 UTC, hgomes
no flags Details
Prometheus view (298.17 KB, image/jpeg)
2019-05-22 13:12 UTC, hgomes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 441 0 'None' closed Bug 1712912: jsonnet/rules: fix double accounting of metrics 2021-02-17 14:23:28 UTC
Red Hat Knowledge Base (Solution) 4177321 0 Performance tune None Pod metrics in the cluster console show duplicate data in OCP 3.11 2019-05-28 16:20:47 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:29:33 UTC

Description hgomes 2019-05-22 13:10:57 UTC
Created attachment 1571989 [details]
Cluster console double

Description of problem:

Pod metrics in the cluster console show duplicate data for container_memory_usage_bytes, resulting in usage shown to be double the actual usage.


Version-Release number of selected component (if applicable):

3.11.88

How reproducible:


Steps to Reproduce:
1. Open Prometheus dashboard, apply a metric
Eg. container_memory_usage_bytes{pod_name='logging-fluentd-p5f2q',namespace='openshift-logging'}
2. Observe multiple results.

3.Check on OpenShift UI Metrics for pods. It will show the total amount of 2 values from the Prometheus results.

Actual results:


Expected results:

I would expect the cluster console to have a filter similar to the one used in the prometheus alert rules: e.g.  container_memory_usage_bytes{container_name!=""} 
https://github.com/openshift/cluster-monitoring-operator/blob/master/assets/prometheus-k8s/rules.yaml#L22

Additional info:

Comment 1 hgomes 2019-05-22 13:12:24 UTC
Created attachment 1571990 [details]
Prometheus view

Comment 2 Frederic Branczyk 2019-05-28 11:24:08 UTC
We have three related BZs in total in this area, I'd suggest we fix all of them at once, by introducing a recording rule for memory/cpu that is used universally across the stack, that way we can have consistency:

* https://bugzilla.redhat.com/show_bug.cgi?id=1712912
* https://bugzilla.redhat.com/show_bug.cgi?id=1703414
* https://bugzilla.redhat.com/show_bug.cgi?id=1701856

I'd expect this to be solved in the 4.2 time frame.

Comment 6 Sergiusz Urbaniak 2019-08-26 09:26:38 UTC
*** Bug 1703414 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2019-10-16 06:29:13 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922


Note You need to log in before you can comment on or make changes to this bug.