Bug 1900792

Summary: Track all resource counts via telemetry
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: TelemeterAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, juzhao
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1900790 Environment:
Last Closed: 2021-01-18 17:59:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1900790    
Bug Blocks:    

Description Clayton Coleman 2020-11-23 17:44:10 UTC
+++ This bug was initially created as a clone of Bug #1900790 +++

Transcribe all etcd_object_counts (number of all objects) into
cluster resource usage for reporting in cluster telemetry.

The data about how many instances of a CRD are in use on the cluster
is a key question for analyzing the success and health of a cluster
as well as for understanding how a cluster can be more successful.
From a configuration perspective, it indicates use of core platform
features. From an operator perspective, it shows adoption and usage
in a way that installation stats alone do not capture. From a support
perspective it highlights interactions between operators that may
help problem resolution.

On an average cluster this increases the series gathered by ~130
series (18 gathered today, 155 after this change, + 280 on average).
While this is a 50% increase in gathered series, it drives significant
value in all of the domains mentioned above and we believe we have
the budget to perform this increase and that using the budget on these
series specifically will deliver significant value.

In order to defend telemetry against clusters that may have thousands
of resource types, cap the cluster:usage:resources:sum series to 500.
Most have 150, and of those a large number are single or zero instance
counts, so we anticipate for the vast majority of clusters 500 is
enough to get reasonable workload and prevent a full cardinality

Backporting now that we have verified in 4.7

Comment 6 errata-xmlrpc 2021-01-18 17:59:29 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 (Moderate: OpenShift Container Platform 4.6.12 bug fix and security update), and where to find the updated
files, follow the link below.

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