Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7224

Include Maximum CPU Usage Visualization in the "Kubernetes / Compute Resources / Pod" Observe Dashboard

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • openshift-4.16.z
    • User Interface
    • None
    • None
    • Future Sustainability
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request: Include Maximum CPU Usage Visualization in the "Kubernetes / Compute Resources / Pod" Observe Dashboard
      2. What is the nature and description of the request? The current "CPU usage" diagram in the Openshift Observe page (Developer view, Dashboard "Kubernetes / Compute Resources / Pod") only shows the average CPU usage. Especially over longer timeframes (e.g., 2 weeks) this visualization erases peaks, making it difficult for users to accurately set CPU limits for their containers. The request is to enhance the current "CPU usage" panel to include both the average CPU usage and the maximum CPU usage, or to add an additional panel that shows the maximum CPU usage.
      3. Why does the customer need this? (List the business requirements here) Users need to see the maximum CPU usage to correctly rightsize their application deployments. The current average-only view can mislead users, causing them to set inappropriate CPU limits, leading to resource wastage, unneccesary application throttling and ultimatively application outages. By including maximum CPU usage in the default dashboard, users can make informed decisions about extending CPU limits, ensuring efficient resource utilization and preventing unnecessary throttling.
      4. List any affected packages or components:

              rh-ee-vmartini Vanessa Martini
              rhn-support-ydandge Yash Dandge
              None
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                None
                None