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 explosion.
tested with 4.7.0-0.nightly-2020-11-25-114114, "cluster:usage:resources:sum" record rule is as below and the metric works well # oc -n openshift-monitoring get cm prometheus-k8s-rulefiles-0 -oyaml ... - expr: topk(500, max(etcd_object_counts) by (resource)) record: cluster:usage:resources:sum ...
*** Bug 1869910 has been marked as a duplicate of this bug. ***
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.7.0 security, bug fix, and enhancement 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. https://access.redhat.com/errata/RHSA-2020:5633