Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-17079

observabilityclient should discover prometheus or aetos from keystone endpoints

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • observabilityclient should discover prometheus or aetos from keystone endpoints
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-625Implement multi-tenancy telemetry control
    • Not Selected
    • Proposed
    • Proposed
    • To Do
    • RHOSSTRAT-625 - Implement multi-tenancy telemetry control
    • Proposed
    • rhos-conplat-observability
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done

      Goal:

      • Aetos when installed through the devstack plugin creates a keystone endpoint labeled "prometheus". Admins can register a plain prometheus into keystone with a single command too. The observabilityclient should be able to use that to discover the prometheus / aetos endpoint. The current options (/etc/openstack/prometheus.yaml file and env variables) should stay and since they seem a bit more explicit, they should have higher priority (so when a keystone endpoint exists and a /etc/openstack/prometheus.yaml exists as well, the file will be used. When env variable is defined, it'll get used instead of any of the previous two).

      Acceptance Criteria:

      • A patch to enable observabilityclient discover prometheus or aetos from keystone endpoints exists and is merged.

              rh-ee-jwysogla Jaromir Wysoglad
              rh-ee-jwysogla Jaromir Wysoglad
              rhos-conplat-observability
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: