-
Epic
-
Resolution: Done
-
Critical
-
None
-
Enhance acm_managed_cluster_info metric to include the installed operator information
-
False
-
None
-
False
-
Green
-
To Do
-
ACM-1037 - Drive OPP product investment from telemetry data
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Include a new field in the acm_managed_cluster_info metric that indicates which operator is installed.
Why is this important?
The acm_managed_cluster_info metric is now associated to the following operators:
- Red Hat Advanced Cluster Management
- multicluster engine for Kubernetes
- Stolostron
- Stolostron Engine
In order to accurately report product utilization, we need to be able to discern if the metric is coming from the product or community operators. As an additional benefit, it would be good to know if the metric is coming from the associated "engine" standalone operator, or the fuller ACM/Stolostron operator.
Scenarios
- User is using RHACM
- Each metric entry associated to this RHACM installation would indicate ACM
- The metric would not say MCE
- User is using MCE standalone
- Each metric entry associated to this RHACM installation would indicate MCE
- The metric would not say ACM
- User is using Stolostron
- Each metric entry associated to this Stolostron installation would indicate Stolostron
- The metric would not say Stolostron Engine
- User is using MCE standalone
- Each metric entry associated to this Stolostron Engine installation would indicate Stolostron Engine
- The metric would not say Stolostron
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
ACM Epic Done Checklist
See presentation and details.
Update with "Y" if Epic meets the requirement, "N" if it does not, or "N/A" if not applicable.
- _ FIPS Readiness - N/A
- _ Works in Disconnected - N/A
- _ Global Proxy Support - N/A
- _ Installable to Infrastructure Nodes - N/A
- _ No impacts to Performance and Scalability - N
- _ Backup and Restorable - N/A