Description of problem: The marketplace operator is configured to expose metrics when it attempts to connect to a default AppRegisrty. Given that each http response code can create a new time series, the telemeter team has requested that we limit the potential number of time series by using a recording rule and exposing that metric to telemter instead. Version-Release number of selected component (if applicable): 4.3.x How reproducible: Always Steps to Reproduce: 1. Create an OpenShift 4.3.x cluster 2. Visit the /metrics endpoint on the marketplace-operator Actual results: Each time series tracks a response code and are not grouped by a recording rule. Example: app_registry_request_total{code="200",opsrc="community-operators"} 1 Expected results: app_registry_request_total{code="200",opsrc="community-operators"} 1 app_registry:community_operators:1xx_response 0 app_registry:community_operators:2xx_response 1 app_registry:community_operators:3xx_response 0 app_registry:community_operators:4xx_response 0 app_registry:community_operators:5xx_response 0 Additional info:
There is an open PR for this bug here: https://github.com/operator-framework/operator-marketplace/pull/259
(In reply to Alexander Greene from comment #1) > There is an open PR for this bug here: > https://github.com/operator-framework/operator-marketplace/pull/259 This was incorrect, the referenced PR was meant for https://bugzilla.redhat.com/show_bug.cgi?id=1768483
*** This bug has been marked as a duplicate of bug 1768483 ***