+++ This bug was initially created as a clone of Bug #2038406 +++
+++ This bug was initially created as a clone of Bug #2038404 +++
Description of problem:
To help prioritize future features for NTO, we want to better understand how it is being used. One way we can do this is by sending metrics through telemetry to see how often NTO is being used to manage custom TuneD profiles on nodes. This is available on 4.10 but not older versions
Version-Release number of selected component (if applicable):
See NTO metric nto_custom_profiles:count on 4.8 and 4.9
--- Additional comment from on 2022-01-07 20:34:43 UTC ---
Closing as this is already fixed on 4.10.0. Will create a clone with target release 4.9.z.
Moving back POST as a PR is still needed on the cluster-monitoring-operator side.
Verified on the version
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.8.0-0.nightly-2022-03-02-003355 True False 37m Cluster version is 4.8.0-0.nightly-2022-03-02-003355
There is nto_custom_profile:count metric on monitoring/metric
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.8.34 bug fix 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.