Bug 1964716

Summary:	CSV metrics emitted by OLM are not persistent across pod restarts
Product:	OpenShift Container Platform	Reporter:	Anik <anbhatta>
Component:	OLM	Assignee:	Kevin Rizza <krizza>
OLM sub component:	OLM	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	htariq
Version:	4.8
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-07 15:37:49 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:

Description Anik 2021-05-25 22:06:45 UTC

Description of problem:

OLM emits the `csv_succeeded` and `csv_abnormal` metrics, that are used in various telemeter dashboards to answer numerous questions using data aggregated from all live openshift clusters. 

When the olm pod restarts, the `csv_succeeded` and `csv_abnormal` metrics are not persisted, which means the data being displayed across the org is inaccurate.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install an operator
2. Inspect metrics emitted by olm operator pod to see the `csv_succeeded` (or csv_abnormal metric for the installed operator
3. Delete the olm pod and let a new pod get created 
4. Inspect metrics emitted by the new olm operator pod

Actual results:

No `csv_succeeded` or `csv_abnormal` metrics

Expected results:

Metrics related to CSVs are persisted across pod restart. 

Additional info:

Comment 1 Anik 2021-06-07 15:37:49 UTC

Looks like this issue was already reported in 1952576. Closing this as duplicate

*** This bug has been marked as a duplicate of bug 1952576 ***