Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-15899

Difference in metric between workload view and observe dashboard

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • 4.13, 4.12
    • Monitoring
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • MON Sprint 240
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      sDescription of problem:

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

       

      How reproducible:

      always

      Steps to Reproduce:

      when viewing dashboard panels within observe -> dashboards 
      the dashboards that contain a value for "memory usage" and that query be against `container_memory_working_set_bytes`
      the query also contains - "container!=''" 
      
      if you navigate to workloads -> pods -> click pod name -> metrics -> memory usage the query does not contain - container!='' 
      
      it contains container="" 

      Actual results:

       

      Expected results:

      should these values not match? 

      Additional info:

      I understand the difference to be: 
      
      sum(container_memory_working_set_bytes{pod=~'POD_NAME',container!=''})  
      would usually be expected to be  smaller than container_memory_working_set_bytes{pod=~'POD_NAME',container=''}.  
      
      The former sums up the memory usage of all the managed containers in the pod, the latter reprensents the memory usage of the parent cgroup of the pod, that includes additional resources to manage the pod. 

              janantha@redhat.com Jayapriya Pai
              rhn-support-nigsmith Nigel Smith
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: