Description of problem: Telemeter does not whitelist `csv_succeeded` and `csv_abnormal` metrics. Version-Release number of selected component (if applicable): 4.3.0 How reproducible: Always Steps to Reproduce: 1. Visit Telemeter: https://telemeter-lts-dashboards.datahub.redhat.com/explore 2. Make a query for `csv_succeeded` or `csv_abnormal` Actual results: No results. Expected results: Lots of results.
Tested on 4.3.0-0.nightly-2019-11-21-122827, but as shown on http://pics.osci.redhat.com/7s2wpw.png , cluster metrics are not being collected. Talked with Alex and he told me that there are some steps to whitelist these metrics collect at telemeter that is being worked at openshift/cluster-monitoring-operator/pull/561 PR.
> The metric is whitelisted in 4.4 (https://github.com/openshift/cluster-monitoring-operator/pull/563) and 4.4 (https://github.com/openshift/cluster-monitoring-operator/pull/570) on client-side. I guess what is missing is whitelisting them on server-side which is not tracked in Bugzilla. Please follow steps 7. and 8. of the Telemetry guide: https://docs.google.com/document/d/1a6n5iBGM2QaIQRg9Lw4-Npj6QY9--Hpx3XYut-BrUSY I am pushing these changes through - I will update the ticket once it is ready to test.
Installed an Operator with a wrong OperatorGroup and after that did a correction to Operator installation succeed. I was able to see this behavior metrics by querying telemeter: csv_abnormal{_id="6724cdfd-e9e7-49fb-99f7-a3b1dc09981b",endpoint="https-metrics",exported_namespace="test-operators",instance="10.130.0.18:8081",job="olm-operator-metrics",name="etcdoperator.v0.9.2",namespace="openshift-operator-lifecycle-manager",phase="Failed",pod="olm-operator-7d9d75f4f9-6vt46",prometheus="openshift-monitoring/k8s",reason="UnsupportedOperatorGroup",receive="true",service="olm-operator-metrics",version="0.9.2"} csv_succeeded{_id="6724cdfd-e9e7-49fb-99f7-a3b1dc09981b",endpoint="https-metrics",exported_namespace="test-operators",instance="10.130.0.18:8081",job="olm-operator-metrics",name="etcdoperator.v0.9.2",namespace="openshift-operator-lifecycle-manager",pod="olm-operator-7d9d75f4f9-6vt46",prometheus="openshift-monitoring/k8s",receive="true",service="olm-operator-metrics",version="0.9.2"} Considering that, marking as VERIFIED. Cluster Version: 4.4.0-0.nightly-2019-12-11-234322
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, 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:0581