# Backport
This will backport the following commits from `main` to `8.8`:
- [[infra] remove firefox tag in metrics_explorer tests
(#158945)](https://github.com/elastic/kibana/pull/158945)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-06-28T13:21:22Z","message":"[infra]
remove firefox tag in metrics_explorer tests (#158945)\n\n##
Summary\r\n\r\nAfter update to Firefox 113 FTR tests became ~2-3x slower
on CI and as\r\nresult, flaky. It is probably related to FF consuming a
lot resources in\r\nheadless mode while running on our spot instances in
CI.\r\n\r\nWe did investigation and tried few things to improve FTR
runtime with\r\nFF, but without any luck.\r\nSince these tests are
failing constantly on CI with Firefox, but ok with\r\nChrome our general
approach is to remove the flaky test suite from\r\nfirefox
run.","sha":"67312abd2d4b04cf7ee9a0103ff093f18ed80919","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.1","v8.10.0"],"number":158945,"url":"https://github.com/elastic/kibana/pull/158945","mergeCommit":{"message":"[infra]
remove firefox tag in metrics_explorer tests (#158945)\n\n##
Summary\r\n\r\nAfter update to Firefox 113 FTR tests became ~2-3x slower
on CI and as\r\nresult, flaky. It is probably related to FF consuming a
lot resources in\r\nheadless mode while running on our spot instances in
CI.\r\n\r\nWe did investigation and tried few things to improve FTR
runtime with\r\nFF, but without any luck.\r\nSince these tests are
failing constantly on CI with Firefox, but ok with\r\nChrome our general
approach is to remove the flaky test suite from\r\nfirefox
run.","sha":"67312abd2d4b04cf7ee9a0103ff093f18ed80919"}},"sourceBranch":"main","suggestedTargetBranches":["8.9","8.8"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158945","number":158945,"mergeCommit":{"message":"[infra]
remove firefox tag in metrics_explorer tests (#158945)\n\n##
Summary\r\n\r\nAfter update to Firefox 113 FTR tests became ~2-3x slower
on CI and as\r\nresult, flaky. It is probably related to FF consuming a
lot resources in\r\nheadless mode while running on our spot instances in
CI.\r\n\r\nWe did investigation and tried few things to improve FTR
runtime with\r\nFF, but without any luck.\r\nSince these tests are
failing constantly on CI with Firefox, but ok with\r\nChrome our general
approach is to remove the flaky test suite from\r\nfirefox
run.","sha":"67312abd2d4b04cf7ee9a0103ff093f18ed80919"}}]}] BACKPORT-->
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [FTR: delete .kibana mappings from archives to avoid recreating SO
indexes (#159957)](https://github.com/elastic/kibana/pull/159957)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-06-23T16:04:11Z","message":"FTR:
delete .kibana mappings from archives to avoid recreating SO indexes
(#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better
understand the PR, we need to have a look at
`esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n-
It processes the file and if it finds saved object index
(e.g.\r\n`.kibana`), it will delete all SO indexes
(.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created
on Kibana\r\nstart. Then esArchiver will re-create all indexes according
to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to
the latest code changes, it is\r\ngood to avoid re-creating SO indexes
and use \"official\" ones whenever it\r\nis possible. This PR
removes/cleans `mappings.json` files where it seems\r\nreasonable. I
also deleted few not used archives:\r\n-
es_archiver/saved_objects/ui_counters\r\n-
es_archiver/saved_objects/usage_counters\r\n-
security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.2","v8.10.0"],"number":159957,"url":"https://github.com/elastic/kibana/pull/159957","mergeCommit":{"message":"FTR:
delete .kibana mappings from archives to avoid recreating SO indexes
(#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better
understand the PR, we need to have a look at
`esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n-
It processes the file and if it finds saved object index
(e.g.\r\n`.kibana`), it will delete all SO indexes
(.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created
on Kibana\r\nstart. Then esArchiver will re-create all indexes according
to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to
the latest code changes, it is\r\ngood to avoid re-creating SO indexes
and use \"official\" ones whenever it\r\nis possible. This PR
removes/cleans `mappings.json` files where it seems\r\nreasonable. I
also deleted few not used archives:\r\n-
es_archiver/saved_objects/ui_counters\r\n-
es_archiver/saved_objects/usage_counters\r\n-
security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777"}},"sourceBranch":"main","suggestedTargetBranches":["8.9","8.8"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159957","number":159957,"mergeCommit":{"message":"FTR:
delete .kibana mappings from archives to avoid recreating SO indexes
(#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better
understand the PR, we need to have a look at
`esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n-
It processes the file and if it finds saved object index
(e.g.\r\n`.kibana`), it will delete all SO indexes
(.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created
on Kibana\r\nstart. Then esArchiver will re-create all indexes according
to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to
the latest code changes, it is\r\ngood to avoid re-creating SO indexes
and use \"official\" ones whenever it\r\nis possible. This PR
removes/cleans `mappings.json` files where it seems\r\nreasonable. I
also deleted few not used archives:\r\n-
es_archiver/saved_objects/ui_counters\r\n-
es_archiver/saved_objects/usage_counters\r\n-
security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777"}}]}]
BACKPORT-->
Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Failing Tests] Skips and comments tests failing with
no_shard_available_action
(#159039)](https://github.com/elastic/kibana/pull/159039)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-06-06T07:11:22Z","message":"[Failing
Tests] Skips and comments tests failing with no_shard_available_action
(#159039)\n\n## Summary\r\n\r\nSkips several tests failing with
the\r\n`no_shard_available_action_exception`. Also adds comments noting
the\r\nrelated test failure issues and the [master issue
being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee
issue #158918 and PR
#159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Saved
Objects","Feature:Security/Spaces","skipped-test","release_note:skip","backport:prev-minor","v8.9.0"],"number":159039,"url":"https://github.com/elastic/kibana/pull/159039","mergeCommit":{"message":"[Failing
Tests] Skips and comments tests failing with no_shard_available_action
(#159039)\n\n## Summary\r\n\r\nSkips several tests failing with
the\r\n`no_shard_available_action_exception`. Also adds comments noting
the\r\nrelated test failure issues and the [master issue
being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee
issue #158918 and PR
#159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159039","number":159039,"mergeCommit":{"message":"[Failing
Tests] Skips and comments tests failing with no_shard_available_action
(#159039)\n\n## Summary\r\n\r\nSkips several tests failing with
the\r\n`no_shard_available_action_exception`. Also adds comments noting
the\r\nrelated test failure issues and the [master issue
being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee
issue #158918 and PR
#159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa"}}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Testing] Improve policy related endpoint
regression test coverage
(#157412)](https://github.com/elastic/kibana/pull/157412)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Gergő
Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2023-05-30T09:21:14Z","message":"[Security
Solution][Testing] Improve policy related endpoint regression test
coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage
for Policy Detail page related manual\r\ntests. See linked issue for
test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test
cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases
will be added in a\r\nseparate
PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:Defend
Workflows","v8.9.0"],"number":157412,"url":"https://github.com/elastic/kibana/pull/157412","mergeCommit":{"message":"[Security
Solution][Testing] Improve policy related endpoint regression test
coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage
for Policy Detail page related manual\r\ntests. See linked issue for
test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test
cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases
will be added in a\r\nseparate
PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157412","number":157412,"mergeCommit":{"message":"[Security
Solution][Testing] Improve policy related endpoint regression test
coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage
for Policy Detail page related manual\r\ntests. See linked issue for
test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test
cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases
will be added in a\r\nseparate
PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11"}}]}] BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [[RO] Incorrect Deletion of Webhook Actions in Kibana Rules
(#159204)](https://github.com/elastic/kibana/pull/159204)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Julian
Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-12T08:19:20Z","message":"[RO]
Incorrect Deletion of Webhook Actions in Kibana Rules (#159204)\n\n##
Summary\r\n\r\nFixes #158167\r\n\r\nThe issue occurred because we were
using a number called \"index\" as the\r\nReact key prop. When we
removed the first element, the second one took\r\nits place, but React
still showed the removed element.\r\n\r\nTo fix this problem, we found a
solution by using the uuid field that\r\neach action item has. We now
generate it for each new action we create\r\nin the action form and use
that as key\r\n\r\nI was told to add @pmuellr as you might know if we
are missing something\r\n🙇\r\n\r\n### Test: why xpath selector?\r\n\r\nI
had to use the xpath selector to fix a problem we had. The problem
was\r\nbetween two actions we set up. They look the same, but the body
content\r\nis the only different (I've attached a screenshot for more
details).\r\n\r\nWe use a third party component for these actions. This
component doesn't\r\nhave any \"value\" attribute and doesn't add
anything besides the HTML\r\ntext. I tried to find other useful details
but couldn't find any.\r\n\r\nThe problem comes up when we try to delete
one of the actions. To fix\r\nit, we needed to check if that component
was missing. We already have\r\ntools that can look for missing
components, but they don't work with the\r\nxpath selector. So, I added
a new function that can do this. Now, we can\r\nuse the xpath selector
to look for missing components and fix the\r\nproblem\r\n
\r\n<details>\r\n<summary>See
Screenshot</summary>\r\n<img\r\nsrc=\"5447795d-0281-4847-aa85-76d0e5fdec3d\"/>\r\n</details>\r\n\r\n```[tasklist]\r\n-
[x] Make sure that it's ok to generate the uuid\r\n- [x] Test\r\n- [x]
Do we need to backport?
Versions?\r\n```","sha":"55bc8cf567a437581d37e6e7d1380216667f34cd","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v8.8.0","v8.9.0"],"number":159204,"url":"https://github.com/elastic/kibana/pull/159204","mergeCommit":{"message":"[RO]
Incorrect Deletion of Webhook Actions in Kibana Rules (#159204)\n\n##
Summary\r\n\r\nFixes #158167\r\n\r\nThe issue occurred because we were
using a number called \"index\" as the\r\nReact key prop. When we
removed the first element, the second one took\r\nits place, but React
still showed the removed element.\r\n\r\nTo fix this problem, we found a
solution by using the uuid field that\r\neach action item has. We now
generate it for each new action we create\r\nin the action form and use
that as key\r\n\r\nI was told to add @pmuellr as you might know if we
are missing something\r\n🙇\r\n\r\n### Test: why xpath selector?\r\n\r\nI
had to use the xpath selector to fix a problem we had. The problem
was\r\nbetween two actions we set up. They look the same, but the body
content\r\nis the only different (I've attached a screenshot for more
details).\r\n\r\nWe use a third party component for these actions. This
component doesn't\r\nhave any \"value\" attribute and doesn't add
anything besides the HTML\r\ntext. I tried to find other useful details
but couldn't find any.\r\n\r\nThe problem comes up when we try to delete
one of the actions. To fix\r\nit, we needed to check if that component
was missing. We already have\r\ntools that can look for missing
components, but they don't work with the\r\nxpath selector. So, I added
a new function that can do this. Now, we can\r\nuse the xpath selector
to look for missing components and fix the\r\nproblem\r\n
\r\n<details>\r\n<summary>See
Screenshot</summary>\r\n<img\r\nsrc=\"5447795d-0281-4847-aa85-76d0e5fdec3d\"/>\r\n</details>\r\n\r\n```[tasklist]\r\n-
[x] Make sure that it's ok to generate the uuid\r\n- [x] Test\r\n- [x]
Do we need to backport?
Versions?\r\n```","sha":"55bc8cf567a437581d37e6e7d1380216667f34cd"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159204","number":159204,"mergeCommit":{"message":"[RO]
Incorrect Deletion of Webhook Actions in Kibana Rules (#159204)\n\n##
Summary\r\n\r\nFixes #158167\r\n\r\nThe issue occurred because we were
using a number called \"index\" as the\r\nReact key prop. When we
removed the first element, the second one took\r\nits place, but React
still showed the removed element.\r\n\r\nTo fix this problem, we found a
solution by using the uuid field that\r\neach action item has. We now
generate it for each new action we create\r\nin the action form and use
that as key\r\n\r\nI was told to add @pmuellr as you might know if we
are missing something\r\n🙇\r\n\r\n### Test: why xpath selector?\r\n\r\nI
had to use the xpath selector to fix a problem we had. The problem
was\r\nbetween two actions we set up. They look the same, but the body
content\r\nis the only different (I've attached a screenshot for more
details).\r\n\r\nWe use a third party component for these actions. This
component doesn't\r\nhave any \"value\" attribute and doesn't add
anything besides the HTML\r\ntext. I tried to find other useful details
but couldn't find any.\r\n\r\nThe problem comes up when we try to delete
one of the actions. To fix\r\nit, we needed to check if that component
was missing. We already have\r\ntools that can look for missing
components, but they don't work with the\r\nxpath selector. So, I added
a new function that can do this. Now, we can\r\nuse the xpath selector
to look for missing components and fix the\r\nproblem\r\n
\r\n<details>\r\n<summary>See
Screenshot</summary>\r\n<img\r\nsrc=\"5447795d-0281-4847-aa85-76d0e5fdec3d\"/>\r\n</details>\r\n\r\n```[tasklist]\r\n-
[x] Make sure that it's ok to generate the uuid\r\n- [x] Test\r\n- [x]
Do we need to backport?
Versions?\r\n```","sha":"55bc8cf567a437581d37e6e7d1380216667f34cd"}}]}]
BACKPORT-->
Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Security solution] Generative AI Connector
(#157228)](https://github.com/elastic/kibana/pull/157228)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2023-05-24T22:47:35Z","message":"[Security
solution] Generative AI Connector
(#157228)","sha":"029eb3104ae878f8178bb1d936183f7488a8f1f2","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Explore","ui-copy","v8.9.0"],"number":157228,"url":"https://github.com/elastic/kibana/pull/157228","mergeCommit":{"message":"[Security
solution] Generative AI Connector
(#157228)","sha":"029eb3104ae878f8178bb1d936183f7488a8f1f2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157228","number":157228,"mergeCommit":{"message":"[Security
solution] Generative AI Connector
(#157228)","sha":"029eb3104ae878f8178bb1d936183f7488a8f1f2"}}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [[ML] Reenable data visualizer tests
(#158568)](https://github.com/elastic/kibana/pull/158568)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-06-01T15:25:11Z","message":"[ML]
Reenable data visualizer tests (#158568)\n\n## Summary\r\n\r\nThis PR
stabilizes the data visualizer tests by making sure global\r\nloading is
done around time picker and sampler selections. It also\r\nre-enables
the index data visualizer test
suite.","sha":"d4b20ab4c85cf1a12535bbfec9697338f31e35ed","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158568,"url":"https://github.com/elastic/kibana/pull/158568","mergeCommit":{"message":"[ML]
Reenable data visualizer tests (#158568)\n\n## Summary\r\n\r\nThis PR
stabilizes the data visualizer tests by making sure global\r\nloading is
done around time picker and sampler selections. It also\r\nre-enables
the index data visualizer test
suite.","sha":"d4b20ab4c85cf1a12535bbfec9697338f31e35ed"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158568","number":158568,"mergeCommit":{"message":"[ML]
Reenable data visualizer tests (#158568)\n\n## Summary\r\n\r\nThis PR
stabilizes the data visualizer tests by making sure global\r\nloading is
done around time picker and sampler selections. It also\r\nre-enables
the index data visualizer test
suite.","sha":"d4b20ab4c85cf1a12535bbfec9697338f31e35ed"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Infrastructure UI] Hosts View flaky test - Remove async from
describe (#158752)](https://github.com/elastic/kibana/pull/158752)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-01T10:47:37Z","message":"[Infrastructure
UI] Hosts View flaky test - Remove async from describe
(#158752)\n\nfixes:
[#157721](https://github.com/elastic/kibana/issues/157721)\r\n##
Summary\r\n\r\nThis PR aims to fix a flaky, my main suspicion is the
existence of an\r\nasync `describe`, that could influence the execution
of other tests. The\r\ntest `describe` itself contained a test that
wasn't really relevant for\r\nthe Host View test suite because it
validated the Processes tab summary\r\nfield titles. I decided to remove
it
altogether","sha":"81b9bd2d906ac4db3c156f21a7696764c016e1a6","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra
Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":158752,"url":"https://github.com/elastic/kibana/pull/158752","mergeCommit":{"message":"[Infrastructure
UI] Hosts View flaky test - Remove async from describe
(#158752)\n\nfixes:
[#157721](https://github.com/elastic/kibana/issues/157721)\r\n##
Summary\r\n\r\nThis PR aims to fix a flaky, my main suspicion is the
existence of an\r\nasync `describe`, that could influence the execution
of other tests. The\r\ntest `describe` itself contained a test that
wasn't really relevant for\r\nthe Host View test suite because it
validated the Processes tab summary\r\nfield titles. I decided to remove
it
altogether","sha":"81b9bd2d906ac4db3c156f21a7696764c016e1a6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158752","number":158752,"mergeCommit":{"message":"[Infrastructure
UI] Hosts View flaky test - Remove async from describe
(#158752)\n\nfixes:
[#157721](https://github.com/elastic/kibana/issues/157721)\r\n##
Summary\r\n\r\nThis PR aims to fix a flaky, my main suspicion is the
existence of an\r\nasync `describe`, that could influence the execution
of other tests. The\r\ntest `describe` itself contained a test that
wasn't really relevant for\r\nthe Host View test suite because it
validated the Processes tab summary\r\nfield titles. I decided to remove
it altogether","sha":"81b9bd2d906ac4db3c156f21a7696764c016e1a6"}}]}]
BACKPORT-->
Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.8`:
- [Unskips spaces nav test for Chrome, skips spaces selection suite for
Firefox only (#158700)](https://github.com/elastic/kibana/pull/158700)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-05-31T15:20:45Z","message":"Unskips
spaces nav test for Chrome, skips spaces selection suite for Firefox
only (#158700)\n\n## Summary\r\n\r\nThe Firefox update to v113 has
resulted in slower test execution time\r\nand ultimately some timeout
failures. Auto-skip functionality skips the\r\ntest suite completely.
This PR removes Firefox testing for the spaces\r\nselection suite and
unskips the spaces nav test.\r\n\r\nFlaky Test Runner (just for good
measure):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2337","sha":"208e359aad16f6962cd1b125602b9010ae138c40","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158700,"url":"https://github.com/elastic/kibana/pull/158700","mergeCommit":{"message":"Unskips
spaces nav test for Chrome, skips spaces selection suite for Firefox
only (#158700)\n\n## Summary\r\n\r\nThe Firefox update to v113 has
resulted in slower test execution time\r\nand ultimately some timeout
failures. Auto-skip functionality skips the\r\ntest suite completely.
This PR removes Firefox testing for the spaces\r\nselection suite and
unskips the spaces nav test.\r\n\r\nFlaky Test Runner (just for good
measure):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2337","sha":"208e359aad16f6962cd1b125602b9010ae138c40"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158700","number":158700,"mergeCommit":{"message":"Unskips
spaces nav test for Chrome, skips spaces selection suite for Firefox
only (#158700)\n\n## Summary\r\n\r\nThe Firefox update to v113 has
resulted in slower test execution time\r\nand ultimately some timeout
failures. Auto-skip functionality skips the\r\ntest suite completely.
This PR removes Firefox testing for the spaces\r\nselection suite and
unskips the spaces nav test.\r\n\r\nFlaky Test Runner (just for good
measure):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2337","sha":"208e359aad16f6962cd1b125602b9010ae138c40"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Fleet] Include hidden data streams in package upgrade
(#158654)](https://github.com/elastic/kibana/pull/158654)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-31T07:50:42Z","message":"[Fleet]
Include hidden data streams in package upgrade (#158654)\n\n##
Summary\r\n\r\nAPM team reported an issue in 8.8 where some of their
newer data streams\r\nwere not rolled over as expected.\r\nIt turned out
these are hidden data streams and those were not updated\r\nin Fleet
when a new version of a package is installed.\r\n\r\nTo test:\r\n- Start
up a kibana\r\n- Install apm 8.7.0
package\r\n[apm-8.7.0.zip](11600335/apm-8.7.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.7.0.zip\r\n```\r\n- Index a doc to apm
datastream\r\n```\r\nPOST
metrics-apm.service_summary.10m-default/_doc\r\n {\r\n \"@timestamp\":
\"2023-05-30T07:50:00.000Z\",\r\n \"agent\": {\r\n \"name\": \"go\"\r\n
},\r\n \"data_stream\": {\r\n \"dataset\":
\"apm.service_summary.10m\",\r\n \"namespace\": \"default\",\r\n
\"type\": \"metrics\"\r\n },\r\n \"ecs\": {\r\n \"version\":
\"8.6.0-dev\"\r\n },\r\n \"event\": {\r\n \"agent_id_status\":
\"missing\",\r\n \"ingested\": \"2023-05-30T07:57:12Z\"\r\n },\r\n
\"metricset\": {\r\n \"interval\": \"10m\",\r\n \"name\":
\"service_summary\"\r\n },\r\n \"observer\": {\r\n \"hostname\":
\"047e282994fb\",\r\n \"type\": \"apm-server\",\r\n \"version\":
\"8.7.0\"\r\n },\r\n \"processor\": {\r\n \"event\": \"metric\",\r\n
\"name\": \"metric\"\r\n },\r\n \"service\": {\r\n \"language\": {\r\n
\"name\": \"go\"\r\n },\r\n \"name\":
\"___main_elastic_cloud_87_ilm_fix\"\r\n }\r\n }\r\n```\r\n- Install apm
8.8.0
package\r\n[apm-8.8.0.zip](11599946/apm-8.8.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.8.0.zip\r\n```\r\n- Expect that the hidden
datastream is updated and rolls over
on\r\nfailures.\r\n\r\n```\r\n[2023-05-30T15:23:21.666+02:00][DEBUG][plugins.fleet]
Updating mappings for
metrics-apm.service_summary.10m-default\r\n[2023-05-30T15:23:21.670+02:00][ERROR][plugins.fleet]
Mappings update for metrics-apm.service_summary.10m-default
failed\r\n[2023-05-30T15:23:21.671+02:00][ERROR][plugins.fleet]
ResponseError: illegal_argument_exception\r\n Root causes:\r\n
illegal_argument_exception: Mapper for [processor.name] conflicts with
existing mapper:\r\n Cannot update parameter [value] from [metric] to
[null]\r\n```\r\n\r\n<img width=\"995\"
alt=\"image\"\r\nsrc=\"6a5a1abc-30f2-4b2f-a949-5b727cc91f57\">\r\n<img
width=\"1175\"
alt=\"image\"\r\nsrc=\"8e18c40f-6b7f-4810-a9e4-9685a7fa5d0c\">\r\n\r\nAdded
integration test.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"58e0fdf096df0af53e5902ee9da9cc5c63d77847","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","v8.9.0","v8.8.1"],"number":158654,"url":"https://github.com/elastic/kibana/pull/158654","mergeCommit":{"message":"[Fleet]
Include hidden data streams in package upgrade (#158654)\n\n##
Summary\r\n\r\nAPM team reported an issue in 8.8 where some of their
newer data streams\r\nwere not rolled over as expected.\r\nIt turned out
these are hidden data streams and those were not updated\r\nin Fleet
when a new version of a package is installed.\r\n\r\nTo test:\r\n- Start
up a kibana\r\n- Install apm 8.7.0
package\r\n[apm-8.7.0.zip](11600335/apm-8.7.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.7.0.zip\r\n```\r\n- Index a doc to apm
datastream\r\n```\r\nPOST
metrics-apm.service_summary.10m-default/_doc\r\n {\r\n \"@timestamp\":
\"2023-05-30T07:50:00.000Z\",\r\n \"agent\": {\r\n \"name\": \"go\"\r\n
},\r\n \"data_stream\": {\r\n \"dataset\":
\"apm.service_summary.10m\",\r\n \"namespace\": \"default\",\r\n
\"type\": \"metrics\"\r\n },\r\n \"ecs\": {\r\n \"version\":
\"8.6.0-dev\"\r\n },\r\n \"event\": {\r\n \"agent_id_status\":
\"missing\",\r\n \"ingested\": \"2023-05-30T07:57:12Z\"\r\n },\r\n
\"metricset\": {\r\n \"interval\": \"10m\",\r\n \"name\":
\"service_summary\"\r\n },\r\n \"observer\": {\r\n \"hostname\":
\"047e282994fb\",\r\n \"type\": \"apm-server\",\r\n \"version\":
\"8.7.0\"\r\n },\r\n \"processor\": {\r\n \"event\": \"metric\",\r\n
\"name\": \"metric\"\r\n },\r\n \"service\": {\r\n \"language\": {\r\n
\"name\": \"go\"\r\n },\r\n \"name\":
\"___main_elastic_cloud_87_ilm_fix\"\r\n }\r\n }\r\n```\r\n- Install apm
8.8.0
package\r\n[apm-8.8.0.zip](11599946/apm-8.8.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.8.0.zip\r\n```\r\n- Expect that the hidden
datastream is updated and rolls over
on\r\nfailures.\r\n\r\n```\r\n[2023-05-30T15:23:21.666+02:00][DEBUG][plugins.fleet]
Updating mappings for
metrics-apm.service_summary.10m-default\r\n[2023-05-30T15:23:21.670+02:00][ERROR][plugins.fleet]
Mappings update for metrics-apm.service_summary.10m-default
failed\r\n[2023-05-30T15:23:21.671+02:00][ERROR][plugins.fleet]
ResponseError: illegal_argument_exception\r\n Root causes:\r\n
illegal_argument_exception: Mapper for [processor.name] conflicts with
existing mapper:\r\n Cannot update parameter [value] from [metric] to
[null]\r\n```\r\n\r\n<img width=\"995\"
alt=\"image\"\r\nsrc=\"6a5a1abc-30f2-4b2f-a949-5b727cc91f57\">\r\n<img
width=\"1175\"
alt=\"image\"\r\nsrc=\"8e18c40f-6b7f-4810-a9e4-9685a7fa5d0c\">\r\n\r\nAdded
integration test.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"58e0fdf096df0af53e5902ee9da9cc5c63d77847"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158654","number":158654,"mergeCommit":{"message":"[Fleet]
Include hidden data streams in package upgrade (#158654)\n\n##
Summary\r\n\r\nAPM team reported an issue in 8.8 where some of their
newer data streams\r\nwere not rolled over as expected.\r\nIt turned out
these are hidden data streams and those were not updated\r\nin Fleet
when a new version of a package is installed.\r\n\r\nTo test:\r\n- Start
up a kibana\r\n- Install apm 8.7.0
package\r\n[apm-8.7.0.zip](11600335/apm-8.7.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.7.0.zip\r\n```\r\n- Index a doc to apm
datastream\r\n```\r\nPOST
metrics-apm.service_summary.10m-default/_doc\r\n {\r\n \"@timestamp\":
\"2023-05-30T07:50:00.000Z\",\r\n \"agent\": {\r\n \"name\": \"go\"\r\n
},\r\n \"data_stream\": {\r\n \"dataset\":
\"apm.service_summary.10m\",\r\n \"namespace\": \"default\",\r\n
\"type\": \"metrics\"\r\n },\r\n \"ecs\": {\r\n \"version\":
\"8.6.0-dev\"\r\n },\r\n \"event\": {\r\n \"agent_id_status\":
\"missing\",\r\n \"ingested\": \"2023-05-30T07:57:12Z\"\r\n },\r\n
\"metricset\": {\r\n \"interval\": \"10m\",\r\n \"name\":
\"service_summary\"\r\n },\r\n \"observer\": {\r\n \"hostname\":
\"047e282994fb\",\r\n \"type\": \"apm-server\",\r\n \"version\":
\"8.7.0\"\r\n },\r\n \"processor\": {\r\n \"event\": \"metric\",\r\n
\"name\": \"metric\"\r\n },\r\n \"service\": {\r\n \"language\": {\r\n
\"name\": \"go\"\r\n },\r\n \"name\":
\"___main_elastic_cloud_87_ilm_fix\"\r\n }\r\n }\r\n```\r\n- Install apm
8.8.0
package\r\n[apm-8.8.0.zip](11599946/apm-8.8.0.zip)\r\n```\r\nurl
-XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true'
http://localhost:5601/julia/api/fleet/epm/packages -u elastic:changeme
--data-binary @apm-8.8.0.zip\r\n```\r\n- Expect that the hidden
datastream is updated and rolls over
on\r\nfailures.\r\n\r\n```\r\n[2023-05-30T15:23:21.666+02:00][DEBUG][plugins.fleet]
Updating mappings for
metrics-apm.service_summary.10m-default\r\n[2023-05-30T15:23:21.670+02:00][ERROR][plugins.fleet]
Mappings update for metrics-apm.service_summary.10m-default
failed\r\n[2023-05-30T15:23:21.671+02:00][ERROR][plugins.fleet]
ResponseError: illegal_argument_exception\r\n Root causes:\r\n
illegal_argument_exception: Mapper for [processor.name] conflicts with
existing mapper:\r\n Cannot update parameter [value] from [metric] to
[null]\r\n```\r\n\r\n<img width=\"995\"
alt=\"image\"\r\nsrc=\"6a5a1abc-30f2-4b2f-a949-5b727cc91f57\">\r\n<img
width=\"1175\"
alt=\"image\"\r\nsrc=\"8e18c40f-6b7f-4810-a9e4-9685a7fa5d0c\">\r\n\r\nAdded
integration test.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"58e0fdf096df0af53e5902ee9da9cc5c63d77847"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
---------
Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[ML] Stabilize and reenable classification tests
(#158555)](https://github.com/elastic/kibana/pull/158555)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T15:31:57Z","message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158555,"url":"https://github.com/elastic/kibana/pull/158555","mergeCommit":{"message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158555","number":158555,"mergeCommit":{"message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[ML] Stabilize and reenable notifications tests
(#158546)](https://github.com/elastic/kibana/pull/158546)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T15:31:10Z","message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158546,"url":"https://github.com/elastic/kibana/pull/158546","mergeCommit":{"message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158546","number":158546,"mergeCommit":{"message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Cases] Fix bug with registered attachmets memoization
(#158441)](https://github.com/elastic/kibana/pull/158441)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Christos
Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T12:43:43Z","message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","Feature:Cases","v8.9.0","v8.8.1"],"number":158441,"url":"https://github.com/elastic/kibana/pull/158441","mergeCommit":{"message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158441","number":158441,"mergeCommit":{"message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [unskip tests for chrome, fix tags
(#158405)](https://github.com/elastic/kibana/pull/158405)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T08:19:53Z","message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.1"],"number":158405,"url":"https://github.com/elastic/kibana/pull/158405","mergeCommit":{"message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158405","number":158405,"mergeCommit":{"message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Detection Engine] fixes wildcard in field names
issue for query language in detection rules
(#157981)](https://github.com/elastic/kibana/pull/157981)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T09:12:21Z","message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","backport:prev-minor","v8.9.0","v8.8.1","Team:Detection
Engine"],"number":157981,"url":"https://github.com/elastic/kibana/pull/157981","mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157981","number":157981,"mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.8`:
- [Add multi-instance tests for the .kibana split
(#156756)](https://github.com/elastic/kibana/pull/156756)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2023-05-12T14:47:21Z","message":"Add
multi-instance tests for the .kibana split (#156756)\n\nImprove _dot
kibana split_ integration tests, take into
account\nhttps://github.com/elastic/kibana/pull/157356
fix.","sha":"612064aa8baa4aa321cc3f08405e95c789c02016","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Team:Fleet","Feature:Migrations","backport:prev-minor","v8.8.0","v8.9.0","v8.8.1"],"number":156756,"url":"https://github.com/elastic/kibana/pull/156756","mergeCommit":{"message":"Add
multi-instance tests for the .kibana split (#156756)\n\nImprove _dot
kibana split_ integration tests, take into
account\nhttps://github.com/elastic/kibana/pull/157356
fix.","sha":"612064aa8baa4aa321cc3f08405e95c789c02016"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156756","number":156756,"mergeCommit":{"message":"Add
multi-instance tests for the .kibana split (#156756)\n\nImprove _dot
kibana split_ integration tests, take into
account\nhttps://github.com/elastic/kibana/pull/157356
fix.","sha":"612064aa8baa4aa321cc3f08405e95c789c02016"}}]}] BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.8`:
- [[RAM] Fix updates also updating createdAt/createdBy for maintenance
window and rules settings
(#158028)](https://github.com/elastic/kibana/pull/158028)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Jiawei
Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-18T14:13:15Z","message":"[RAM]
Fix updates also updating createdAt/createdBy for maintenance window and
rules settings (#158028)\n\n## Summary\r\n\r\nFix a small bug where our
update functions were also updating the\r\n`createdBy/createdAt` fields
for some of our saved objects, we should\r\njust be updating the
`updatedBy/updatedAt` fields\r\n\r\n### Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"833ece60d7cd77cb58f694215aef9c289f0fd284","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Alerting/RulesFramework","v8.9.0","v8.8.1"],"number":158028,"url":"https://github.com/elastic/kibana/pull/158028","mergeCommit":{"message":"[RAM]
Fix updates also updating createdAt/createdBy for maintenance window and
rules settings (#158028)\n\n## Summary\r\n\r\nFix a small bug where our
update functions were also updating the\r\n`createdBy/createdAt` fields
for some of our saved objects, we should\r\njust be updating the
`updatedBy/updatedAt` fields\r\n\r\n### Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"833ece60d7cd77cb58f694215aef9c289f0fd284"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158028","number":158028,"mergeCommit":{"message":"[RAM]
Fix updates also updating createdAt/createdBy for maintenance window and
rules settings (#158028)\n\n## Summary\r\n\r\nFix a small bug where our
update functions were also updating the\r\n`createdBy/createdAt` fields
for some of our saved objects, we should\r\njust be updating the
`updatedBy/updatedAt` fields\r\n\r\n### Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"833ece60d7cd77cb58f694215aef9c289f0fd284"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Fleet] Rollover data streams when package w/ TSDB setting changed is
installed (#157869)](https://github.com/elastic/kibana/pull/157869)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Kyle
Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2023-05-16T18:16:14Z","message":"[Fleet]
Rollover data streams when package w/ TSDB setting changed is installed
(#157869)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157345\r\n\r\nWhen a package
with a changed `index.mode` or `source.mode` setting is\r\ninstalled,
Fleet will now automatically perform a rollover to ensure the\r\ncorrect
setting is present on the resulting backing index.\r\n\r\nThere is an
issue with Elasticsearch wherein toggling these settings\r\nback and
forth will incur a backing index range overlap error.
See\r\nhttps://github.com/elastic/elasticsearch/issues/96163.\r\n\r\nTo
test\r\n1. Install the `system` integration at version `1.28.0`\r\n2.
Create an integration policy for the `system` integration (a
standard\r\ndefault agent policy will do)\r\n3. Enroll an agent in this
policy, and allow it to ingest some data\r\n4. Confirm that there are
documents present in the\r\n`metrics-system.cpu-default` data stream,
and note its backing index via\r\nStack Management\r\n5. Create a new
`1.28.1` version of the `system` integration
where\r\n`elasticsearch.index_mode: time_series` is set and install it
via\r\n`elastic-package install --zip`\r\n6. Confirm that a rollover
occurs and the backing index for the\r\n`metrics-system.cpu-default`
data stream has been updated\r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"22e38472f6f05f9e72d97e74ff8328565da4d53b","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.9.0"],"number":157869,"url":"https://github.com/elastic/kibana/pull/157869","mergeCommit":{"message":"[Fleet]
Rollover data streams when package w/ TSDB setting changed is installed
(#157869)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157345\r\n\r\nWhen a package
with a changed `index.mode` or `source.mode` setting is\r\ninstalled,
Fleet will now automatically perform a rollover to ensure the\r\ncorrect
setting is present on the resulting backing index.\r\n\r\nThere is an
issue with Elasticsearch wherein toggling these settings\r\nback and
forth will incur a backing index range overlap error.
See\r\nhttps://github.com/elastic/elasticsearch/issues/96163.\r\n\r\nTo
test\r\n1. Install the `system` integration at version `1.28.0`\r\n2.
Create an integration policy for the `system` integration (a
standard\r\ndefault agent policy will do)\r\n3. Enroll an agent in this
policy, and allow it to ingest some data\r\n4. Confirm that there are
documents present in the\r\n`metrics-system.cpu-default` data stream,
and note its backing index via\r\nStack Management\r\n5. Create a new
`1.28.1` version of the `system` integration
where\r\n`elasticsearch.index_mode: time_series` is set and install it
via\r\n`elastic-package install --zip`\r\n6. Confirm that a rollover
occurs and the backing index for the\r\n`metrics-system.cpu-default`
data stream has been updated\r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"22e38472f6f05f9e72d97e74ff8328565da4d53b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157869","number":157869,"mergeCommit":{"message":"[Fleet]
Rollover data streams when package w/ TSDB setting changed is installed
(#157869)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157345\r\n\r\nWhen a package
with a changed `index.mode` or `source.mode` setting is\r\ninstalled,
Fleet will now automatically perform a rollover to ensure the\r\ncorrect
setting is present on the resulting backing index.\r\n\r\nThere is an
issue with Elasticsearch wherein toggling these settings\r\nback and
forth will incur a backing index range overlap error.
See\r\nhttps://github.com/elastic/elasticsearch/issues/96163.\r\n\r\nTo
test\r\n1. Install the `system` integration at version `1.28.0`\r\n2.
Create an integration policy for the `system` integration (a
standard\r\ndefault agent policy will do)\r\n3. Enroll an agent in this
policy, and allow it to ingest some data\r\n4. Confirm that there are
documents present in the\r\n`metrics-system.cpu-default` data stream,
and note its backing index via\r\nStack Management\r\n5. Create a new
`1.28.1` version of the `system` integration
where\r\n`elasticsearch.index_mode: time_series` is set and install it
via\r\n`elastic-package install --zip`\r\n6. Confirm that a rollover
occurs and the backing index for the\r\n`metrics-system.cpu-default`
data stream has been updated\r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"22e38472f6f05f9e72d97e74ff8328565da4d53b"}}]}]
BACKPORT-->
Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co>
# Backport
This will backport the following commits from `main` to `8.8`:
- [[ResponseOps] es query rule params not compatible between 8.6 and 8.7
(#157710)](https://github.com/elastic/kibana/pull/157710)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Alexi
Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-15T17:08:30Z","message":"[ResponseOps]
es query rule params not compatible between 8.6 and 8.7
(#157710)\n\nResolves
https://github.com/elastic/kibana/issues/156856\r\n\r\n##
Summary\r\n\r\nAdds a default value to `aggType` and `groupBy` fields
\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"8ecd2d67a02f9de2a0e4f8778dcca3781dceaa90","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v8.8.0","v8.9.0"],"number":157710,"url":"https://github.com/elastic/kibana/pull/157710","mergeCommit":{"message":"[ResponseOps]
es query rule params not compatible between 8.6 and 8.7
(#157710)\n\nResolves
https://github.com/elastic/kibana/issues/156856\r\n\r\n##
Summary\r\n\r\nAdds a default value to `aggType` and `groupBy` fields
\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"8ecd2d67a02f9de2a0e4f8778dcca3781dceaa90"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157710","number":157710,"mergeCommit":{"message":"[ResponseOps]
es query rule params not compatible between 8.6 and 8.7
(#157710)\n\nResolves
https://github.com/elastic/kibana/issues/156856\r\n\r\n##
Summary\r\n\r\nAdds a default value to `aggType` and `groupBy` fields
\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"8ecd2d67a02f9de2a0e4f8778dcca3781dceaa90"}}]}]
BACKPORT-->
Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
Reverts elastic/kibana#157121
We need to revert because after talking to @kobelb, we are introducing a
new bug where user always need to be a super user to access the fields
from the alert index since only only super user can access the kibana
index.
# Backport
This will backport the following commits from `main` to `8.8`:
- [[Infrastructure UI] Hosts view handle invalid KQL error
(#156989)](https://github.com/elastic/kibana/pull/156989)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-11T16:59:23Z","message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics
UI","Team:Infra Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":156989,"url":"https://github.com/elastic/kibana/pull/156989","mergeCommit":{"message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156989","number":156989,"mergeCommit":{"message":"[Infrastructure
UI] Hosts view handle invalid KQL error (#156989)\n\ncloses
[#987](https://github.com/elastic/obs-infraobs-team/issues/987)\r\n\r\n##
Summary\r\n\r\nThis PR changes the hosts view to graciously handle
exceptions caused by\r\ninvalid KQL submissions\r\n\r\n<img
width=\"1451\"
alt=\"image\"\r\nsrc=\"5bafc987-9a14-4b03-9038-53179f7b6735\">\r\n\r\n\r\nBesides,
it changes the way it was handling a fatal error that can\r\nhappen if
something wrong happens while creating an ad-hoc data-view -\r\nthis is
highly unlike to happen, but we're standardizing how we
display\r\nerrors on the hosts view\r\n\r\n_Previously:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236833673-c994512f-cb73-441b-9783-506bab67ff4b.png\">\r\n\r\n_Now:_\r\n<img
width=\"1439\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/2767137/236862216-fada9f50-5d27-45b9-a6f3-8ac497a3e048.png\">\r\n\r\n###
How to test\r\n- Go to hosts view\r\n- Type invalid KQL expressions on
the search bar\r\n\r\n### For reviewer\r\n\r\nIf the page is loaded with
a querystring containing an invalid
`query`\r\n(e.g:\r\n`_a=(dateRange:(from:now-15m,to:now),filters:!(),limit:20,panelFilters:!(),query:(language:kuery,query:%27%7D%27)`),\r\nthe
Control components will show an error. However, they can't
recover\r\nfrom fatal errors. So even after the user corrects the
mistake in the\r\nquery, the controls will remain in the error
state.\r\n\r\nA ticket has been opened to address this
problem:\r\nhttps://github.com/elastic/kibana/issues/156430\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8baff25966d45c1b351e96a5cc524372b4dbdb29"}}]}]
BACKPORT-->
Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
