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

[Dev Preview] MCOA Metrics Collection

XMLWordPrintable

    • [Dev Preview] MCOA Metrics Collection
    • False
    • None
    • False
    • Not Selected
    • To Do
    • ACM-12063 - Multi-signal Observability Storage, Collection and Query Support in ACM
    • ACM-12063Multi-signal Observability Storage, Collection and Query Support in ACM
    • 75% To Do, 8% In Progress, 17% Done
    • XL

      DDR Doc

      https://docs.google.com/document/d/1zuH32s-pmnbw8cuTC5pFeMGb0uCP0vCBDt42djoAXSg/edit?usp=sharing

      Epic Goal

      ...

      Why is this important?

      Metrics collection is the current feature of ACM-Observability, the new addon needs to consider existing features

      Scenarios

      ...

      Acceptance Criteria

      • MUST Users can specify downsampling for metrics collection (from raw scrape up to 5 mins)
      • MUST Users can view and modify the allowlist of metrics sent from spokes to the hub Thanos
      • MUST Users can add recording rules that are evaluated in the spoke metrics stack
      • MUST Users get a k8s native metrics collection stack if the spoke is non-OCP (prometheus-operator, kube-state metrics, node-exporter)
      • MUST Users can configure the CMO OCP stack if the spoke is OCP  
      • COULD support dynamic collection of metrics based on CPU/Memory triggers in the spoke cluster (telco) 
      • The metrics-collection stack deployed to the spoke reports its addon status to the hub correctly
      • Users are able to configure metrics-collection via a top-level CRD in MCOA

      Alert-forwarding is not in-scope for this epic, that is being tracked through ACM-12472 

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      1. Could this be derived from the CMO CRD for how it is configured? https://drive.google.com/file/d/1o6wpi99zU4mqbQEPzDlEH94GWrDv6z1p/view 

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

              mzardab@redhat.com Moad Zardab
              mzardab@redhat.com Moad Zardab
              Xiang Yin Xiang Yin
              Christian Stark Christian Stark
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: