-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
5
-
False
-
False
-
RHDP-286 - Drive metrics needs to allow us to properly target our workload and developer-focused adoption efforts
-
-
AppSvc Sprint 207, AppSvc Sprint 208, AppSvc Sprint 210, AppSvc Sprint 211, AppSvc Sprint 212, AppSvc Sprint 218, AppSvc Sprint 219, AppSvc Sprint 220
Owner: Architect:
Story (Required)
As an OpenShift PM, I will like to see console_helm_chart_installs metric on Thanos, so that I can make priority decisions based on customer data
Background (Required)
Each OpenShift component expose their own metrics in Prometheus. Some of those are moved forward to a fleet level Prometheus setup (Thanos). There is a process to promote metrics to be visible in OpenShift Thanos.
Glossary
Thanos: https://thanos.io/
Out of scope
NA
In Scope
Metric console_helm_chart_installs
Approach(Required)
This story should take care of following that process. See documentation so far here: https://source.redhat.com/groups/public/appservices/wiki/adding_new_openshift_metrics
Dependencies
Edge Case
NA
Acceptance Criteria
The console_helm_chart_installs metric can be seen here in our Thanos Service
Documentation is updated as needed to reflex the current procedure.
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied