-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
Current documentation about scraping Quay metrics and exposing them to Prometheus are missing steps or a link to existing documentation on how to integrate Prometheus to read the exposed Quay metrics. Currently, the docs show how to set up Quay to expose metrics and then in this document section 13.1.3 it states merely:
"Prometheus needs a way to access all Red Hat Quay instances running in a cluster. In the typical setup, this is done by listing all the Red Hat Quay instances in a single named DNS entry, which is then given to Prometheus."
I recommend we add a link to the existing monitoring documentation which explains how to set up a ServiceMonitor to scrape user workload metrics, here.