Description of problem: In relation with the bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1669718 the usage of CPU is seen doubled in the cluster console as comparison with the metrics shown on the Grafana and top command. As per the outputs from oc adm top pod and grafana, metrics for pod matches. But cluster console shows doubled usage. Version-Release number of selected component (if applicable): OCP v3.11 Actual results: # oc adm top pod router-6-9b664 4m 46Mi Attaching the screenshots for the cluster console and Grafana (K8s / Compute Resources / Pod dashboard for same pod) and metrics. Expected results: Cluster console output should match according to the console outputs from Grafana, metrics.
Created attachment 1559029 [details] cluster-console pod overview
Created attachment 1559030 [details] grafana K8S compute resources pod dashborad
Created attachment 1559031 [details] metrics
Do you see this consistently for the router pod and other pods? If you click on the chart, it should take you to the Prometheus UI with the same query. Do you see the same data as console there?
Yes. I can see this consistently for router and other pods. Also, the query behind the chart is taking me to the prometheus console and showing the wrong data. This query is addressed actually in https://bugzilla.redhat.com/show_bug.cgi?id=1669410. I already asked on that and opened a separate bug according to the engineer. I will also update this information on the Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1669410 and ask for the wrong CPU usage as well.
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.
*** This bug has been marked as a duplicate of bug 1712912 ***