Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-1671

[R&D] Determine CPU and memory usage when all metrics are dropped

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • False
    • NEW
    • TELCOSTRAT-87 - Single Core CPU CaaS Budget for DU Deployment w/ Single-Node OpenShift on Sapphire Rapids Platform
    • NEW
    • Undefined
    • Monitoring - Sprint 203, Monitoring - Sprint 204

      To decrease resource usage of Prometheus, we'll continue to drop more metrics. Having said that, even when metrics aren't stored, Prometheus still needs to parse and process the metrics. We need to evaluate what's the fixed cost to get an idea of the lower bounds.

      We could run a cloned instance of prometheus-k8s (same targets and rules) but dropping all metrics at collection time.

      DoD

      • Compare CPU & RAM usage of the cloned Prometheus with the regular Prometheus.

              hasun@redhat.com Haoyu Sun
              spasquie@redhat.com Simon Pasquier
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: