Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.11] [SLO] Fix SLO burn rate rule to call alertWithLifecycle before getAlertUuid (#169004) #169026

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.11:

Questions ?

Please refer to the Backport tool documentation

…AlertUuid` (elastic#169004)

## Summary

This PR fixes elastic#168962 by calling `alertWithLifecycle` before
`getAlertUuid`. When `getAlertUuid` is called first it will generate a
UUID which is not associated with the actual alert. When you call
`alertWithLifecycle`, it generates the Alert then stores the `alertUuid`
that maps the `alertId` to the `alertUuid`; `getAlertUuid` tries to
recall this association but falls back to generating a UUID. I had to
change the way the test worked by modifying mock's behavior to match the
implementation; once I had a test that failed similarly to what we see
in the real world, I fixed the issue by changing the implementation to
call `alertWithLifecycle` first

Co-authored-by: Kibana Machine <[email protected]>
(cherry picked from commit 48bb5ae)
@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #51 / dashboard app - group 3 dashboard state "after all" hook for "Saved search will update when the query is changed in the URL"
  • [job] [logs] FTR Configs #51 / dashboard app - group 3 dashboard state Directly modifying url updates dashboard state when removing a panel

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @simianhacker

@kibanamachine kibanamachine merged commit eb2a11f into elastic:8.11 Oct 16, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants