+++ This bug was initially created as a clone of Bug #2059843 +++ Description of problem: SRO telemetry metric have issue, missing sro_used_nodes metrics in SRO4.10 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy SRO from source code git clone https://github.com/openshift/special-resource-operator.git cd special-resource-operator export CONTAINER_COMMAND=podman make local-image-build TAG=master make deploy 2.Login OCP console, check observe=>metrics, search sro_, only three metrics, expect 4 sro_* metrics --- Additional comment from on 2022-03-02 07:52:46 UTC --- Expected Metrics sro_used_nodes Returns the nodes that are running pods created by a SRO custom resource (CR). This metric is available for DaemonSet and Deployment objects only. sro_kind_completed_info Represents whether a kind of an object defined by the Helm Charts in a SRO CR has been successfully uploaded in the cluster (value 1) or not (value 0). Examples of objects are DaemonSet, Deployment or BuildConfig. sro_states_completed_info Represents whether the SRO has finished processing a CR successfully (value 1) or the SRO has not processed the CR yet (value 0). sro_managed_resources_total Returns the number of SRO CRs in the cluster, regardless of their state.
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 (Important: OpenShift Container Platform 4.11.0 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. https://access.redhat.com/errata/RHSA-2022:5069