Fix: aws alb latency thresholds seem inverted #394
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
rsicart
requested review from
xp-1000,
Shr3ps,
BzSpi,
cvauvarin and
tchernomax
as code owners
rsicart
force-pushed
the
rsi/fix-aws-alb-latency-levels
branch
from
560022a
to
8b88ea8
Compare
xp-1000
added
bug
xp-1000
approved these changes
Feb 28, 2022
This was referenced Feb 28, 2022
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.
AWS alb latency detector thresholds seem inverted.
Major severity is less important than Critical severity, according to docs.
Is that right?
Thanks in advance.