Bug 1877816

Summary: Categorize clusters in telemetry by hardware type, cloud type, and install type
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MonitoringAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: high    
Version: 4.6CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: telemeter-metric
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:39:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Clayton Coleman 2020-09-10 13:58:03 UTC 
Key dimensions for understanding clusters are cloud provider type, how the cluster was installed, and what the dominant hardware or virtualization type underpinning the cluster is.  Also, as we have added tracking metrics for these over time some clusters do not report these metrics which is a common gotcha when querying and complicates other queries.

We should create telemetry recording rules that summarize each of these dimensions, then fold them into the cluster_subscribed rule (which will not increase cardinality of that rule) so that we can more effectively subdivide on our key dimensions.
Comment 2 Junqi Zhao 2020-09-15 08:46:24 UTC 
tested with 4.6.0-0.nightly-2020-09-14-181123, the metrics could be found in telemeter-server
Comment 5 errata-xmlrpc 2020-10-27 16:39:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196