Bug 1717255 - No monitoring rules report when cloud-credential pod is failing
Summary: No monitoring rules report when cloud-credential pod is failing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Credential Operator
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Joel Diaz
QA Contact: Oleg Nesterov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-05 02:16 UTC by Justin Pierce
Modified: 2020-01-08 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-08 13:33:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cloud-credential-operator pull 132 0 'None' closed Bug 1717255: add alert for when operator is down 2020-07-03 08:04:47 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.