fix!: backend orchestration failure alarm should be SEV2.5 (medium severity) #1767
Conversation
This file contains hidden or 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
iankhou
changed the title
|
Nice, I'm actually working something that would allow this in a more configurable way. Closing in favor of #1768 |
auto-merge was automatically disabled
July 21, 2025 07:33
Pull request was closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backend orchestration failure does not necessarily mean a violation of our SLA, but it is an emergent issue. It currently triggers a
highSeverityAlarm. Here, we reduce the severity to cut amediumSeverityAlarm.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license