monitoring: change api prober alert #892
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Hector Fernandez <[email protected]>
haydentherapper
approved these changes
Dec 6, 2023
bobcallaway
approved these changes
Dec 6, 2023
cpanato
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I got paged again by the alert testing the creation of a rekor entry and verifying it. (
Policy: API Prober: Rekor write correctness verifier returned 'false' within the last 60s)I decided to change the alert to check the counter metric and also add
EVALUATION_MISSING_DATA_NO_OPcondition.With this new change the metric resets once the alert has been fired as you can see below:
Release Note
Documentation