Upgrade prom and alert manager to 2.7.1 and 0.16.1 #1098
Merged
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
alert
label in the scale-up alertfunction_name
label instead ofthe
instance
label that was removed.https://groups.google.com/d/msg/prometheus-users/7Ul6ngc7Ogs/j_YDszV5BwAJ
the alert value should not be included in the alert labels otherwise
each calculation of the alert is treated like a new alert and then the
use of
for 5s
will not behave as expected.Motivation and Context
Resolves #1095
How Has This Been Tested?
Tested manually on my Mac
hey
http://localhost:9090/graph?g0.range_input=15m&g0.expr=rate(gateway_function_invocation_total%5B10s%5D)&g0.tab=0&g1.range_input=15m&g1.expr=ALERTS%7Balertname%3D%22APIHighInvocationRate%22%7D&g1.tab=0&g2.range_input=15m&g2.expr=gateway_service_count&g2.tab=0
Types of changes
Checklist:
git commit -s