Bug 1779912

Summary: Allow some telemetry metrics to be added without changes to whitelist
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: MonitoringAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1779913 (view as bug list) Environment:
Last Closed: 2020-05-04 11:18:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1779913    

Description Clayton Coleman 2019-12-05 00:34:43 UTC 
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.
Comment 4 errata-xmlrpc 2020-05-04 11:18:31 UTC 
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