Skip to content

[8.19] [Observability] [Alert] Add context.grouping action variable in SLO Burn rate and ES Query rules (#213550)#220055

Merged
benakansara merged 3 commits intoelastic:8.19from
benakansara:backport/8.19/pr-213550
May 5, 2025
Merged

[8.19] [Observability] [Alert] Add context.grouping action variable in SLO Burn rate and ES Query rules (#213550)#220055
benakansara merged 3 commits intoelastic:8.19from
benakansara:backport/8.19/pr-213550

Conversation

@benakansara
Copy link
Contributor

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

benakansara and others added 2 commits May 5, 2025 12:55
…urn rate and ES Query rules (elastic#213550)

Part of elastic#180709

Adds `context.grouping` action variable in the following rules:
- SLO Burn rate rule
- ES Query rule
1. Create each rule with group by fields, and with "active" and
"recovered" actions
- for SLO Burn rate rule, group by fields are derived from the SLO so
you need to create SLO with group by fields
- for ES Query rule, use "Grouped over"
2. In "active" and "recovered" action message, use `context.grouping`
variable
3. Ensure that both "active" and "recovered" alert notifications contain
correct information
4. Ensure that the action variables UI in rule form shows
`context.grouping` action variable

Example of action message:

```
{
  "grouping": "{{context.grouping}}",
  "host.name": "{{context.grouping.host.name}}",
  "container.id": "{{context.grouping.container.id}}"
}
```

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
(cherry picked from commit 3c1b882)
@benakansara benakansara requested a review from kibanamachine as a code owner May 5, 2025 10:56
@benakansara benakansara added the backport This PR is a backport of another PR label May 5, 2025
@benakansara benakansara enabled auto-merge (squash) May 5, 2025 10:56
@botelastic botelastic bot added Team:obs-ux-infra_services - DEPRECATED DEPRECATED - Use Team:obs-presentation. Team:actionable-obs Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics. labels May 5, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
@kbn/alerting-rule-utils 5 13 +8
triggersActionsUi 533 534 +1
total +9

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
triggersActionsUi 101.0KB 101.1KB +101.0B
Unknown metric groups

API count

id before after diff
@kbn/alerting-rule-utils 5 13 +8
triggersActionsUi 539 540 +1
total +9

Copy link
Contributor

@kdelemme kdelemme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@benakansara benakansara merged commit 66a1b0f into elastic:8.19 May 5, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR Team:actionable-obs Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics. Team:obs-ux-infra_services - DEPRECATED DEPRECATED - Use Team:obs-presentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants