Description of problem: Login cluster console with cluster admin, click "Workloads -> Pods", and select one project from drop-down list, eg: openshift-kube-apiserver, then select one pod, in the "Pod Overview" section, the "Memory Usage" uses "pod_name:container_memory_usage_bytes:sum{pod_name='kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal',namespace='openshift-kube-apiserver'}" to calculate "Memory Usage" search in prometheus UI **************************************************************** pod_name:container_memory_usage_bytes:sum{pod_name='kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal',namespace='openshift-kube-apiserver'} / 1024 /1024 Element Value {namespace="openshift-kube-apiserver",pod_name="kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal"} 1833.5234375 **************************************************************** whereas **************************************************************** # oc -n openshift-kube-apiserver adm top pod kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal NAME CPU(cores) MEMORY(bytes) kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal 206m 867Mi **************************************************************** Although we know `oc -n openshift-kube-apiserver adm top pod kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal` uses the following expression **************************************************************** sum(container_memory_working_set_bytes{container_name!="POD",container_name!="",pod_name!="", pod_name="kube-apiserver-ip-10-0-139-94.us-east-2.compute.internal"}) / 1024 /1024 Element Value {} 867.28515625 **************************************************************** I think "Memory Usage" under "Workloads -> Pods" should be the same with "oc adm top pod" Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-18-050636 How reproducible: Always Steps to Reproduce: 1. See the description part 2. 3. Actual results: "Memory Usage" under "Workloads -> Pods" is not the same with "oc adm top pod" Expected results: "Memory Usage" under "Workloads -> Pods" should be the same with "oc adm top pod" Additional info:
Similar issue with CPU metrics: https://bugzilla.redhat.com/show_bug.cgi?id=1709176
Created attachment 1611369 [details] console screenshot
*** Bug 1709176 has been marked as a duplicate of this bug. ***
fix is not in 4.2.0-0.nightly-2019-09-04-142146