-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
-
OCPSTRAT-316 - HyperShift Consumption Models
-
Hypershift Sprint 10, Hypershift Sprint 11, Hypershift Sprint 12, Hypershift Sprint 13, Hypershift Sprint 15, Hypershift Sprint 16, Hypershift Sprint 17, Hypershift Sprint 18, Hypershift Sprint 19, Hypershift Sprint 20, Hypershift Sprint 21
-
0
-
0
-
0
For a default installation of HyperShift standalone via MCE, we still want to make sure that telemetry metrics produced by hosted control planes can be forwarded to Red Hat. In order to not require large amounts of cpu/memory on UWM to scrape default metrics, we want to make it possible to only produce the metrics needed for telemetry. If the customer wants more metrics, they can update the setting to produce a larger set of metrics. This makes it possible to at least collect what we need for telemetry without imposing a big burden on our customers' infrastructure at the start.
Ref: https://docs.google.com/document/d/1tS_agjnvVKbq_SVKNZEYCPetkTtGh30fIzwXtoCCyeI/edit?usp=sharing
- is blocked by
-
MON-2655 Hypershift control plane telemetry metrics are not showing up in Telemeter
- Closed
- links to