[Response Ops][POC] Adding is_improving
to alert document for conditional actions.
#183543
+433
−73
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.
In this POC:
kibana.alert.is_improving
flag to alert documentAlso for the purposes of testing this POC, I added another action group to the metric threshold rule type. This way, we can mimic the same action group changes that the SLO burn rate rule moves through.
With these changes, we can create a metric threshold rule with a
triggered
,warning
andlow
condition and add the following actions:triggered
Critical
severitywarning
Warning
severitylow
kibana.alert.is_improving: false
low
kibana.alert.is_improving: true
low
kibana.alert.is_improving: true
recovered
Action Group definition
For a SLO burn rate rule with the same configuration, this is the behavior we would expect:
No alert -> Medium -> slack message
Medium -> High -> PD incident opened at Warning severity
High -> Critical -> Same PD incident changed to Critical severity
Critical -> High -> Same PD incident change to Warning severity
High -> Medium -> PD incident resolved, "improving" slack message for Medium action group sent
Medium -> Recovered -> slack recovery message sent