XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Observability
    • None
    • False
    • None
    • False
    • Hide

      Provide the required acceptance criteria using this template.
      * ...
      Show
      Provide the required acceptance criteria using this template. * ...
    • ACM-12063 - Multi-signal Observability Storage, Collection and Query Support in ACM
    • None

      For improved stability, scalability and maintainability, we want to spike the deployment of the Prometheus Agent as a daemonset with one instance on each node of the spoke.
      Each instance is in charge of scraping itself the metrics from the targets located on its own node.
      This enables:

      • Scaling naturally with the number of endpoints, no need to tune resources requirements.
      • Independence from the spoke monitoring solution

      This requires mounting the needed secrets and permissions for accessing platform metrics endpoints to scrape, access the service monitors.

              Unassigned Unassigned
              rh-ee-tmange Thibault Mange
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: