[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999)#241100
Merged
kibanamachine merged 1 commit intoelastic:9.2from Oct 29, 2025
Merged
[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999)#241100kibanamachine merged 1 commit intoelastic:9.2from
kibanamachine merged 1 commit intoelastic:9.2from
Conversation
## Summary Another attempt to fix the flaky tests with the embeddable alerts panel. The issue is that alerts are not being generated. I made the rules more sensitive so they will always produce alerts and use the event log to check the rules' execution status. I run the flaky test runner 3 x 200 without any issues. Fixes: elastic#227748 Fixes: elastic#220807 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 3cb9979)
1 task
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
cnasikas
added a commit
that referenced
this pull request
Nov 3, 2025
…#241154) # Backport This will backport the following commits from `main` to `9.1`: - [[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)](#227999) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-10-29T10:17:04Z","message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Team:obs-ux-management","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps] Fix embeddable alerts panel flaky tests","number":227999,"url":"https://github.com/elastic/kibana/pull/227999","mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227999","number":227999,"mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/241100","number":241100,"state":"MERGED","mergeCommit":{"sha":"0679d9c9347d54986cd26c8c6e79914e6cfa7f93","message":"[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999) (#241100)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps] Fix embeddable alerts panel flaky tests\n(#227999)](https://github.com/elastic/kibana/pull/227999)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Christos Nasikas <christos.nasikas@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
cnasikas
added a commit
that referenced
this pull request
Nov 3, 2025
#241155) # Backport This will backport the following commits from `main` to `8.19`: - [[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)](#227999) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-10-29T10:17:04Z","message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Team:obs-ux-management","backport:version","v9.3.0","v8.19.7","v9.1.7","v9.2.1"],"title":"[ResponseOps] Fix embeddable alerts panel flaky tests","number":227999,"url":"https://github.com/elastic/kibana/pull/227999","mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},"sourceBranch":"main","suggestedTargetBranches":["8.19","9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/227999","number":227999,"mergeCommit":{"message":"[ResponseOps] Fix embeddable alerts panel flaky tests (#227999)\n\n## Summary\n\nAnother attempt to fix the flaky tests with the embeddable alerts panel.\nThe issue is that alerts are not being generated. I made the rules more\nsensitive so they will always produce alerts and use the event log to\ncheck the rules' execution status. I run the flaky test runner 3 x 200\nwithout any issues.\n\nFixes: https://github.com/elastic/kibana/issues/227748\nFixes: https://github.com/elastic/kibana/issues/220807\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"3cb997977f9fe132c44de0216455852e8340f42e"}},{"branch":"8.19","label":"v8.19.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/241100","number":241100,"state":"MERGED","mergeCommit":{"sha":"0679d9c9347d54986cd26c8c6e79914e6cfa7f93","message":"[9.2] [ResponseOps] Fix embeddable alerts panel flaky tests (#227999) (#241100)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [[ResponseOps] Fix embeddable alerts panel flaky tests\n(#227999)](https://github.com/elastic/kibana/pull/227999)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Christos Nasikas <christos.nasikas@elastic.co>"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport
This will backport the following commits from
mainto9.2:Questions ?
Please refer to the Backport tool documentation