Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-15942

MCO Thanos Resource and Rate Limits on the Ingest Path

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Observability
    • None
    • MCO Thanos Resource and Rate Limits on the Ingest Path
    • Not Selected
    • 100% To Do, 0% In Progress, 0% Done

      Problem statement:

      As an ACM Observability User I am able to determine the exact memory and CPU requirement needed for the default Multi-cluster Observability Operator needs to schedule receiver pods for a given number of active series by default

      As an ACM Observability User I have confidence in the base performance of a default installation of ACM Multi-cluster Observability Operator component in my Hub Cluster with respect to Max Active Series on ingest 

      OCP Example https://docs.openshift.com/container-platform/4.13/scalability_and_performance/planning-your-environment-according-to-object-maximums.html

      Mimir example https://grafana.com/docs/mimir/latest/manage/run-production-environment/planning-capacity/#:~:text=Estimated%20required%20CPU%2C%20memory%2C%20and,every%20300%2C000%20series%20in%20memory 

              rh-ee-rfloren Roger Florén
              mzardab@redhat.com Moad Zardab
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: