+++ 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): 4.8 Expected results: 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.
Switching back to POST as we also need the PR to cluster-monitoring-operator.
Hi David, (In reply to dagray from comment #2) > Switching back to POST as we also need the PR to cluster-monitoring-operator. Do we have that PR now? Links? Thank you.
PR is LGTM, we can see the nto_custom_profiles:count metrics both in the telemeter client and server side
Verified Result: Create a NTO profile, there is a nto_custom_profiles:count was updated.
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 (Low: OpenShift Container Platform 4.9.23 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:0655