Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-29410

Prometheus enabled namespaces

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • No

      The Subscription Watch application pulls event data from Telemeter to meter and bill Pay-As-You-Go subscriptions.  Our QE team wants to be able to create a Prometheus instance that they can then push mock data to so that they can test our consumption of these (make sure the promql is correct, etc).  I have a rough procedure for doing this, but it's pretty laborious.

      I saw in the docs that Prometheus isn't enabled by default in the EEs but I was wondering about the feasibility of creating a namespace pool for Prometheus enabled environments so that our QE folks don't have to deploy a custom ClowdEnv each time.

      prometheus.md Is the procedure I've been using but it requires a lot of fiddling with various YAML to get the prometheus instance up and going.  Anything that could eliminate some of these steps would be very helpful.

              gburges@redhat.com Gabor Burges (Inactive)
              awood1@redhat.com Alex Wood
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: