For some usage / verification metrics that might point out configuration issues but may only live for as short time, having to change the whitelist of telemetry is very expensive in human and backport logic, hindering our ability to do quick iteration on data around a customer problem set. In addition, teams may need to do this and monitoring quickly bottlenecks the problem. Allow a whitelist rule for usage in telemetry to allow this behavior. An e2e test will be added that ensures we don't have excessive cardinality, and we will audit and review all metrics of this form periodically to ensure users are following the rules.
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