-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metrics: Report a gauge for when cluster operator conditions change #107
metrics: Report a gauge for when cluster operator conditions change #107
Conversation
/retest |
/retest |
/assign @abhinavdahiya |
Cluster operators may "flap" - have conditions that periodically move from true to false (or appear and disappear). The CVO can record all transitions as they occur and report it to prometheus, allowing us to get fine grained reports of transitions. Since most operators should be stable, treat Unknown -> False and <missing> -> Unknown as just as valid, on the assumption that transitions are important. Will allow us to identify flapping operators and fix them.
af8851a
to
648d27c
Compare
Resolved, also cleaned up the naming to be slightly more concise. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Cluster operators may "flap" - have conditions that periodically
move from true to false (or appear and disappear). The CVO can record
all transitions as they occur and report it to prometheus, allowing
us to get fine grained reports of transitions. Since most operators
should be stable, treat Unknown -> False and -> Unknown
as just as valid, on the assumption that transitions are important.
Will allow us to identify flapping operators and fix them.