Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1717255

Summary:	No monitoring rules report when cloud-credential pod is failing
Product:	OpenShift Container Platform	Reporter:	Justin Pierce <jupierce>
Component:	Cloud Credential Operator	Assignee:	Joel Diaz <jdiaz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Oleg Nesterov <olnester>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0
Target Milestone:	---
Target Release:	4.3.0
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:	2020-01-08 13:33:20 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 Justin Pierce 2019-06-05 02:16:41 UTC

Description of problem:
When diagnosing https://bugzilla.redhat.com/show_bug.cgi?id=1717244 I found that no prometheus alerts were firing when the operator pod was stuck.

Version-Release number of selected component (if applicable):
4.1.0-rc.4 


How reproducible:
100%

Steps to Reproduce:
1. Prevent the cloud-credential-operator pod from running
2.
3.

Actual results:
No prometheus alerts are raised.

Expected results:
A prometheus alert should be raised.

Additional info:
If a service monitor is created for this pod, a absent(up{job=..) rule would have helped to detect the issue.

Comment 1 Devan Goodwin 2019-08-02 12:27:40 UTC

Going to propose adding metrics for CCO in 4.3.

Comment 2 Devan Goodwin 2019-10-28 12:01:07 UTC

CCO metrics coming in 4.3, Joel has led the work, lets get this absent rule in as well as I don't think we had that on the list.