-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: notification
variable is encoded as a string, fix alert thresholds
#231
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
Show Plan
Action: |
chris13524
approved these changes
Oct 2, 2023
xav
approved these changes
Oct 4, 2023
arein
approved these changes
Oct 16, 2023
chris13524
reviewed
Oct 18, 2023
geekbrother
force-pushed
the
max/fix/graphana_alerts
branch
from
October 18, 2023 21:03
decd0e4
to
42754db
Compare
Show Plan
Action: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Description
This PR fixes firing alerts for 5xx errors by making the following changes:
jsonencode
from the localnotifications
variable that causes encoding json array as a string.no data state
from:no_data
to keep the last state to provide consistent alarm firing in case the threshold was met and then no data was provided.Resolves #210
How Has This Been Tested?
Deployed from the PR branch to the staging environment, the alert was fired successfully and delivered to the opsgenie and slack channel when the 500 error count was > 1 for 5 minutes.
Due Diligence