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.

Sign up for GitHub

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

Jump to bottom

[8.18] [UA] Remove 7->8 multitype check #203835

Closed
wants to merge 2,748 commits into from
Closed

[8.18] [UA] Remove 7->8 multitype check #203835

wants to merge 2,748 commits into from

Conversation

jloleysens
Copy link
Contributor

@jloleysens jloleysens commented Dec 11, 2024 •
edited
Loading

Summary

Removes the 7->8.x logic for detecting and warning users about custom types. Specifically, we had a GET index call with include_type_name that is no longer supported and would return mappings in the following, deprecated, multitype form:

{
  "mappings": {
    "<type_name>": { "properties": /* properties */ }
    }
}

Now you can only get:

{
  "mappings": {
    "properties": { /* properties */ }
}

...including include_type_name is causing a 400 response from ES, blocking UA's ability to reindex. Existing code already handles both of these forms bc it had to for 7.last, this PR just removes logic targeting the former (and removes our outdated user-facing warning).

TODO

  • Once merged, forward port to main

Resources

darnautov and others added 30 commits December 5, 2024 07:55
@darnautov
[8.x] [ML] Trained Models: Optimize trained models Kibana API (elasti…
1f61f5b 
…c#200977) (elastic#203087)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ML] Trained Models: Optimize trained models Kibana API
(elastic#200977)](elastic#200977)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dima
Arnautov","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T18:50:18Z","message":"[ML]
Trained Models: Optimize trained models Kibana API (elastic#200977)\n\n##
Summary\r\n\r\nCloses elastic#191939 \r\nCloses
https://github.com/elastic/kibana/issues/175220\r\n\r\nAdds various
optimizations for the Trained Models page:\r\n\r\n---\r\n\r\n- Creates a
new Kibana `/trained_models_list` endpoint responsible for\r\nfetching
complete data for the Trained Model UI page, including\r\npipelines,
indices and stats.\r\n\r\nBefore the Trained Models page required 3
endpoints. The new\r\n`trained_models_list` replaces them, reducing the
overall latency.\r\n\r\n<img width=\"715\" alt=\"Screenshot 2024-12-02
at 16 18
32\"\r\nsrc=\"https://github.com/user-attachments/assets/34bebbdc-ae80-4e08-8512-199c57cb5b54\">\r\n\r\n\r\n---\r\n\r\n-
Optimized fetching of pipelines, indices and stats, reducing
the\r\nnumber of API calls to ES\r\n\r\nSeveral issues with the old
endpoint stemmed from the with_indices flag.\r\nThis flag triggered a
method designed for the Model Map feature, which\r\ninvolved fetching a
complete list of pipelines, iterating over each\r\nmodel, retrieving
index settings multiple times, and obtaining both\r\nindex content and a
full list of transforms.\r\n\r\nThe new endpoint solves these issues by
fetching only the necessary\r\ninformation for the Trained Model page
with minimal calls to\r\nElasticsearch.\r\n\r\n#### APM transaction with
a new endpoint \r\n<img width=\"1822\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/55e4a5f0-e571-46a2-b7ad-5b5a6fc44ceb\">\r\n\r\n####
APM transaction with an old
endpoint\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c9d62ddb-5e13-4ac1-9cbf-d685fbed7808\r\n\r\n---\r\n\r\n-
Improves type definitions for different model types\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":"e067fa239de670123c4f7d6aaba3d6001796babe","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Data
Frame Analytics","v9.0.0","Feature:3rd Party
Models","Team:ML","backport:version","v8.17.0","v8.18.0"],"number":200977,"url":"https://github.com/elastic/kibana/pull/200977","mergeCommit":{"message":"[ML]
Trained Models: Optimize trained models Kibana API (elastic#200977)\n\n##
Summary\r\n\r\nCloses elastic#191939 \r\nCloses
https://github.com/elastic/kibana/issues/175220\r\n\r\nAdds various
optimizations for the Trained Models page:\r\n\r\n---\r\n\r\n- Creates a
new Kibana `/trained_models_list` endpoint responsible for\r\nfetching
complete data for the Trained Model UI page, including\r\npipelines,
indices and stats.\r\n\r\nBefore the Trained Models page required 3
endpoints. The new\r\n`trained_models_list` replaces them, reducing the
overall latency.\r\n\r\n<img width=\"715\" alt=\"Screenshot 2024-12-02
at 16 18
32\"\r\nsrc=\"https://github.com/user-attachments/assets/34bebbdc-ae80-4e08-8512-199c57cb5b54\">\r\n\r\n\r\n---\r\n\r\n-
Optimized fetching of pipelines, indices and stats, reducing
the\r\nnumber of API calls to ES\r\n\r\nSeveral issues with the old
endpoint stemmed from the with_indices flag.\r\nThis flag triggered a
method designed for the Model Map feature, which\r\ninvolved fetching a
complete list of pipelines, iterating over each\r\nmodel, retrieving
index settings multiple times, and obtaining both\r\nindex content and a
full list of transforms.\r\n\r\nThe new endpoint solves these issues by
fetching only the necessary\r\ninformation for the Trained Model page
with minimal calls to\r\nElasticsearch.\r\n\r\n#### APM transaction with
a new endpoint \r\n<img width=\"1822\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/55e4a5f0-e571-46a2-b7ad-5b5a6fc44ceb\">\r\n\r\n####
APM transaction with an old
endpoint\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c9d62ddb-5e13-4ac1-9cbf-d685fbed7808\r\n\r\n---\r\n\r\n-
Improves type definitions for different model types\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":"e067fa239de670123c4f7d6aaba3d6001796babe"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200977","number":200977,"mergeCommit":{"message":"[ML]
Trained Models: Optimize trained models Kibana API (elastic#200977)\n\n##
Summary\r\n\r\nCloses elastic#191939 \r\nCloses
https://github.com/elastic/kibana/issues/175220\r\n\r\nAdds various
optimizations for the Trained Models page:\r\n\r\n---\r\n\r\n- Creates a
new Kibana `/trained_models_list` endpoint responsible for\r\nfetching
complete data for the Trained Model UI page, including\r\npipelines,
indices and stats.\r\n\r\nBefore the Trained Models page required 3
endpoints. The new\r\n`trained_models_list` replaces them, reducing the
overall latency.\r\n\r\n<img width=\"715\" alt=\"Screenshot 2024-12-02
at 16 18
32\"\r\nsrc=\"https://github.com/user-attachments/assets/34bebbdc-ae80-4e08-8512-199c57cb5b54\">\r\n\r\n\r\n---\r\n\r\n-
Optimized fetching of pipelines, indices and stats, reducing
the\r\nnumber of API calls to ES\r\n\r\nSeveral issues with the old
endpoint stemmed from the with_indices flag.\r\nThis flag triggered a
method designed for the Model Map feature, which\r\ninvolved fetching a
complete list of pipelines, iterating over each\r\nmodel, retrieving
index settings multiple times, and obtaining both\r\nindex content and a
full list of transforms.\r\n\r\nThe new endpoint solves these issues by
fetching only the necessary\r\ninformation for the Trained Model page
with minimal calls to\r\nElasticsearch.\r\n\r\n#### APM transaction with
a new endpoint \r\n<img width=\"1822\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/55e4a5f0-e571-46a2-b7ad-5b5a6fc44ceb\">\r\n\r\n####
APM transaction with an old
endpoint\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c9d62ddb-5e13-4ac1-9cbf-d685fbed7808\r\n\r\n---\r\n\r\n-
Improves type definitions for different model types\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":"e067fa239de670123c4f7d6aaba3d6001796babe"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
@kibanamachine @shahzad31
[8.x] [Synthetics] Fix overview trends for read-only user !! (elastic…
c585b53 
…#202914) (elastic#202990)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Synthetics] Fix overview trends for read-only user !!
(elastic#202914)](elastic#202914)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T17:24:07Z","message":"[Synthetics]
Fix overview trends for read-only user !! (elastic#202914)\n\n##
Summary\r\n\r\nFix overview trends for read-only user , we wrongly
assume that this\r\n`POST` route needs write
permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.17.0","v8.18.0","v8.16.3"],"title":"[Synthetics]
Fix overview trends for read-only user
!!","number":202914,"url":"https://github.com/elastic/kibana/pull/202914","mergeCommit":{"message":"[Synthetics]
Fix overview trends for read-only user !! (elastic#202914)\n\n##
Summary\r\n\r\nFix overview trends for read-only user , we wrongly
assume that this\r\n`POST` route needs write
permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202914","number":202914,"mergeCommit":{"message":"[Synthetics]
Fix overview trends for read-only user !! (elastic#202914)\n\n##
Summary\r\n\r\nFix overview trends for read-only user , we wrongly
assume that this\r\n`POST` route needs write
permission.","sha":"16817cc44dd02fbb9b7e10e7d03871c299267dfb"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Shahzad <[email protected]>
@kibanamachine @viduni94
[8.x] [Obs AI Assistant] Update AI Assistant icon for Serverless (ela…
886fffe 
…stic#202861) (elastic#203094)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Obs AI Assistant] Update AI Assistant icon for Serverless
(elastic#202861)](elastic#202861)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Viduni
Wickramarachchi","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T12:38:33Z","message":"[Obs
AI Assistant] Update AI Assistant icon for Serverless (elastic#202861)\n\n##
Summary\r\n\r\n### Problem\r\nThe Obs AI Assistant icon doesn't look as
expected in serverless top\r\nnavigation.\r\n\r\n### Solution\r\nUpdate
button CSS for Obs AI Assistant top nav icon for serverless.
No\r\nchanges to the classic navigation.\r\n\r\n### Checklist\r\n\r\n-
[x] The PR description includes the appropriate Release Notes
section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a73528ab10acb5e10d86ac9e60a3a42d1e11f89","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Obs
AI
Assistant","ci:project-deploy-observability","backport:version","v8.18.0"],"title":"[Obs
AI Assistant] Update AI Assistant icon for
Serverless","number":202861,"url":"https://github.com/elastic/kibana/pull/202861","mergeCommit":{"message":"[Obs
AI Assistant] Update AI Assistant icon for Serverless (elastic#202861)\n\n##
Summary\r\n\r\n### Problem\r\nThe Obs AI Assistant icon doesn't look as
expected in serverless top\r\nnavigation.\r\n\r\n### Solution\r\nUpdate
button CSS for Obs AI Assistant top nav icon for serverless.
No\r\nchanges to the classic navigation.\r\n\r\n### Checklist\r\n\r\n-
[x] The PR description includes the appropriate Release Notes
section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a73528ab10acb5e10d86ac9e60a3a42d1e11f89"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202861","number":202861,"mergeCommit":{"message":"[Obs
AI Assistant] Update AI Assistant icon for Serverless (elastic#202861)\n\n##
Summary\r\n\r\n### Problem\r\nThe Obs AI Assistant icon doesn't look as
expected in serverless top\r\nnavigation.\r\n\r\n### Solution\r\nUpdate
button CSS for Obs AI Assistant top nav icon for serverless.
No\r\nchanges to the classic navigation.\r\n\r\n### Checklist\r\n\r\n-
[x] The PR description includes the appropriate Release Notes
section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8a73528ab10acb5e10d86ac9e60a3a42d1e11f89"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Viduni Wickramarachchi <[email protected]>
@stratoula @kibanamachine
[8.x] [ES|QL] Update function metadata (elastic#200480) (elastic#200501)
1ef9cbe 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Update function metadata
(elastic#200480)](elastic#200480)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kibana
Machine","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-18T07:13:25Z","message":"[ES|QL]
Update function metadata (elastic#200480)\n\nThis PR updates the function
definitions and inline docs based on the\r\nlatest metadata from
Elasticsearch.","sha":"be183bb09dcf03fef605ebe2f938dfe98947bf16","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport:skip","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.17.0"],"number":200480,"url":"https://github.com/elastic/kibana/pull/200480","mergeCommit":{"message":"[ES|QL]
Update function metadata (elastic#200480)\n\nThis PR updates the function
definitions and inline docs based on the\r\nlatest metadata from
Elasticsearch.","sha":"be183bb09dcf03fef605ebe2f938dfe98947bf16"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200480","number":200480,"mergeCommit":{"message":"[ES|QL]
Update function metadata (elastic#200480)\n\nThis PR updates the function
definitions and inline docs based on the\r\nlatest metadata from
Elasticsearch.","sha":"be183bb09dcf03fef605ebe2f938dfe98947bf16"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Kibana Machine <[email protected]>
@kibanamachine @xcrzx
[8.x] [Security Solution] Add rule upgrade review cache invalidation (e…
f0eb7fc 
…lastic#202969) (elastic#203102)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution] Add rule upgrade review cache invalidation
(elastic#202969)](elastic#202969)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dmitrii
Shevchenko","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T13:25:35Z","message":"[Security
Solution] Add rule upgrade review cache invalidation
(elastic#202969)\n\n**Resolves:
https://github.com/elastic/kibana/issues/202779**\r\n\r\n##
Summary\r\n\r\nImplemented proper cache invalidation after rule CRUD
operations to\r\nprevent displaying stale data in rule upgrade flyouts.
See the linked\r\nissue for more details.\r\n\r\n### How to
Test\r\n\r\n1. Ensure rule customization is enabled\r\n2. Navigate to
the Rule Updates page \r\n3. Locate any rule with updates\r\n4. Make
changes to the rule:\r\n - Edit the rule via the Rule Editing page\r\n -
Use bulk actions\r\n - Delete the rule\r\n5. Return to the Rule Updates
page\r\n - All introduced changes should be reflected:\r\n -
Modifications should be visible\r\n - If the rule was deleted, it should
no longer appear on the
page","sha":"94c561436644d3a97e01a2d762a368c6965d0ac1","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection Rule
Management","backport:version","v8.18.0"],"title":"[Security Solution]
Add rule upgrade review cache
invalidation","number":202969,"url":"https://github.com/elastic/kibana/pull/202969","mergeCommit":{"message":"[Security
Solution] Add rule upgrade review cache invalidation
(elastic#202969)\n\n**Resolves:
https://github.com/elastic/kibana/issues/202779**\r\n\r\n##
Summary\r\n\r\nImplemented proper cache invalidation after rule CRUD
operations to\r\nprevent displaying stale data in rule upgrade flyouts.
See the linked\r\nissue for more details.\r\n\r\n### How to
Test\r\n\r\n1. Ensure rule customization is enabled\r\n2. Navigate to
the Rule Updates page \r\n3. Locate any rule with updates\r\n4. Make
changes to the rule:\r\n - Edit the rule via the Rule Editing page\r\n -
Use bulk actions\r\n - Delete the rule\r\n5. Return to the Rule Updates
page\r\n - All introduced changes should be reflected:\r\n -
Modifications should be visible\r\n - If the rule was deleted, it should
no longer appear on the
page","sha":"94c561436644d3a97e01a2d762a368c6965d0ac1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202969","number":202969,"mergeCommit":{"message":"[Security
Solution] Add rule upgrade review cache invalidation
(elastic#202969)\n\n**Resolves:
https://github.com/elastic/kibana/issues/202779**\r\n\r\n##
Summary\r\n\r\nImplemented proper cache invalidation after rule CRUD
operations to\r\nprevent displaying stale data in rule upgrade flyouts.
See the linked\r\nissue for more details.\r\n\r\n### How to
Test\r\n\r\n1. Ensure rule customization is enabled\r\n2. Navigate to
the Rule Updates page \r\n3. Locate any rule with updates\r\n4. Make
changes to the rule:\r\n - Edit the rule via the Rule Editing page\r\n -
Use bulk actions\r\n - Delete the rule\r\n5. Return to the Rule Updates
page\r\n - All introduced changes should be reflected:\r\n -
Modifications should be visible\r\n - If the rule was deleted, it should
no longer appear on the
page","sha":"94c561436644d3a97e01a2d762a368c6965d0ac1"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dmitrii Shevchenko <[email protected]>
@kibanamachine @iblancof
[8.x] [Infra] Send Host View Total Host Count Retrieved event on ever…
92950c1 
…y query submission in hosts inventory (elastic#202691) (elastic#202900)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Infra] Send Host View Total Host Count Retrieved event on every
query submission in hosts inventory
(elastic#202691)](elastic#202691)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Irene
Blanco","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T11:41:44Z","message":"[Infra]
Send Host View Total Host Count Retrieved event on every query
submission in hosts inventory (elastic#202691)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/202441\r\n\r\nThis PR
reintroduces the `Host View Total Host Count Retrieved` event,\r\nwhich
was unintentionally removed in the past. It has been added back
to\r\nthe same position in the code as
previously\r\n\r\n|Scenario|Event|\r\n|-|-|\r\n|Page load|![Screenshot
2024-12-03 at 12
37\r\n28](https://github.com/user-attachments/assets/8a12d713-219b-4c1f-a08e-7b475634b4fc)|\r\n|Query|![Screenshot
2024-12-03 at 12
40\r\n12](https://github.com/user-attachments/assets/501a8a81-b0b0-46a6-a470-dceeba791c01)|\r\n|Filter|![Screenshot
2024-12-03 at 12
40\r\n56](https://github.com/user-attachments/assets/586f2176-b05b-4571-b3d8-f3f9cb803249)|","sha":"51ef0e7034e4aa4c3515e3e863221bed08e118a8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.18.0"],"title":"[Infra]
Send Host View Total Host Count Retrieved event on every query
submission in hosts
inventory","number":202691,"url":"https://github.com/elastic/kibana/pull/202691","mergeCommit":{"message":"[Infra]
Send Host View Total Host Count Retrieved event on every query
submission in hosts inventory (elastic#202691)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/202441\r\n\r\nThis PR
reintroduces the `Host View Total Host Count Retrieved` event,\r\nwhich
was unintentionally removed in the past. It has been added back
to\r\nthe same position in the code as
previously\r\n\r\n|Scenario|Event|\r\n|-|-|\r\n|Page load|![Screenshot
2024-12-03 at 12
37\r\n28](https://github.com/user-attachments/assets/8a12d713-219b-4c1f-a08e-7b475634b4fc)|\r\n|Query|![Screenshot
2024-12-03 at 12
40\r\n12](https://github.com/user-attachments/assets/501a8a81-b0b0-46a6-a470-dceeba791c01)|\r\n|Filter|![Screenshot
2024-12-03 at 12
40\r\n56](https://github.com/user-attachments/assets/586f2176-b05b-4571-b3d8-f3f9cb803249)|","sha":"51ef0e7034e4aa4c3515e3e863221bed08e118a8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202691","number":202691,"mergeCommit":{"message":"[Infra]
Send Host View Total Host Count Retrieved event on every query
submission in hosts inventory (elastic#202691)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/202441\r\n\r\nThis PR
reintroduces the `Host View Total Host Count Retrieved` event,\r\nwhich
was unintentionally removed in the past. It has been added back
to\r\nthe same position in the code as
previously\r\n\r\n|Scenario|Event|\r\n|-|-|\r\n|Page load|![Screenshot
2024-12-03 at 12
37\r\n28](https://github.com/user-attachments/assets/8a12d713-219b-4c1f-a08e-7b475634b4fc)|\r\n|Query|![Screenshot
2024-12-03 at 12
40\r\n12](https://github.com/user-attachments/assets/501a8a81-b0b0-46a6-a470-dceeba791c01)|\r\n|Filter|![Screenshot
2024-12-03 at 12
40\r\n56](https://github.com/user-attachments/assets/586f2176-b05b-4571-b3d8-f3f9cb803249)|","sha":"51ef0e7034e4aa4c3515e3e863221bed08e118a8"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Irene Blanco <[email protected]>
@kibanamachine @simianhacker
[8.x] 🌊 Add type safety to Painless conditions (elastic#202603) (elas…
f6f28fd 
…tic#203104)

# Backport

This will backport the following commits from `main` to `8.x`:
- [🌊 Add type safety to Painless conditions
(elastic#202603)](elastic#202603)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Chris
Cowan","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T13:58:36Z","message":"🌊
Add type safety to Painless conditions (elastic#202603)\n\n## 🍒
Summary\r\n\r\nThis PR closes
elastic/streams-program#18 by\r\nadding some
basic type checking to the painless output for the Stream\r\nconditions.
The new code will check to ensure that none of the fields\r\nused in the
condition are `Map` objects. Then it wraps the if statement\r\nin a
`try/catch`.\r\n\r\n### Condition\r\n```Typescript\r\n{\r\n and: [\r\n {
field: 'log.logger', operator: 'eq' as const, value: 'nginx_proxy'
},\r\n {\r\n or: [\r\n { field: 'log.level', operator: 'eq' as const,
value: 'error' },\r\n { field: 'log.level', operator: 'eq' as const,
value: 'ERROR' },\r\n ],\r\n },\r\n ],\r\n}\r\n```\r\n\r\n###
Before\r\n\r\n```\r\n(ctx.log?.logger !== null && ctx.log?.logger ==
\"nginx_proxy\") && ((ctx.log?.level !== null && ctx.log?.level ==
\"error\") || (ctx.log?.level !== null && ctx.log?.level ==
\"ERROR\"))\r\n```\r\n\r\n### After\r\n\r\n```\r\nif (ctx.log?.logger
instanceof Map || ctx.log?.level instanceof Map) {\r\n return
false;\r\n}\r\ntry {\r\n if ((ctx.log?.logger !== null &&
ctx.log?.logger == \"nginx_proxy\") && ((ctx.log?.level !== null &&
ctx.log?.level == \"error\") || (ctx.log?.level !== null &&
ctx.log?.level == \"ERROR\"))) {\r\n return true;\r\n }\r\n return
false;\r\n} catch (Exception e) {\r\n return
false;\r\n}\r\n```","sha":"fe56d6d90af45b971ff82731c1ec7eb4c4c0eff3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","v8.18.0","Feature:Streams"],"title":"🌊
Add type safety to Painless
conditions","number":202603,"url":"https://github.com/elastic/kibana/pull/202603","mergeCommit":{"message":"🌊
Add type safety to Painless conditions (elastic#202603)\n\n## 🍒
Summary\r\n\r\nThis PR closes
elastic/streams-program#18 by\r\nadding some
basic type checking to the painless output for the Stream\r\nconditions.
The new code will check to ensure that none of the fields\r\nused in the
condition are `Map` objects. Then it wraps the if statement\r\nin a
`try/catch`.\r\n\r\n### Condition\r\n```Typescript\r\n{\r\n and: [\r\n {
field: 'log.logger', operator: 'eq' as const, value: 'nginx_proxy'
},\r\n {\r\n or: [\r\n { field: 'log.level', operator: 'eq' as const,
value: 'error' },\r\n { field: 'log.level', operator: 'eq' as const,
value: 'ERROR' },\r\n ],\r\n },\r\n ],\r\n}\r\n```\r\n\r\n###
Before\r\n\r\n```\r\n(ctx.log?.logger !== null && ctx.log?.logger ==
\"nginx_proxy\") && ((ctx.log?.level !== null && ctx.log?.level ==
\"error\") || (ctx.log?.level !== null && ctx.log?.level ==
\"ERROR\"))\r\n```\r\n\r\n### After\r\n\r\n```\r\nif (ctx.log?.logger
instanceof Map || ctx.log?.level instanceof Map) {\r\n return
false;\r\n}\r\ntry {\r\n if ((ctx.log?.logger !== null &&
ctx.log?.logger == \"nginx_proxy\") && ((ctx.log?.level !== null &&
ctx.log?.level == \"error\") || (ctx.log?.level !== null &&
ctx.log?.level == \"ERROR\"))) {\r\n return true;\r\n }\r\n return
false;\r\n} catch (Exception e) {\r\n return
false;\r\n}\r\n```","sha":"fe56d6d90af45b971ff82731c1ec7eb4c4c0eff3"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202603","number":202603,"mergeCommit":{"message":"🌊
Add type safety to Painless conditions (elastic#202603)\n\n## 🍒
Summary\r\n\r\nThis PR closes
elastic/streams-program#18 by\r\nadding some
basic type checking to the painless output for the Stream\r\nconditions.
The new code will check to ensure that none of the fields\r\nused in the
condition are `Map` objects. Then it wraps the if statement\r\nin a
`try/catch`.\r\n\r\n### Condition\r\n```Typescript\r\n{\r\n and: [\r\n {
field: 'log.logger', operator: 'eq' as const, value: 'nginx_proxy'
},\r\n {\r\n or: [\r\n { field: 'log.level', operator: 'eq' as const,
value: 'error' },\r\n { field: 'log.level', operator: 'eq' as const,
value: 'ERROR' },\r\n ],\r\n },\r\n ],\r\n}\r\n```\r\n\r\n###
Before\r\n\r\n```\r\n(ctx.log?.logger !== null && ctx.log?.logger ==
\"nginx_proxy\") && ((ctx.log?.level !== null && ctx.log?.level ==
\"error\") || (ctx.log?.level !== null && ctx.log?.level ==
\"ERROR\"))\r\n```\r\n\r\n### After\r\n\r\n```\r\nif (ctx.log?.logger
instanceof Map || ctx.log?.level instanceof Map) {\r\n return
false;\r\n}\r\ntry {\r\n if ((ctx.log?.logger !== null &&
ctx.log?.logger == \"nginx_proxy\") && ((ctx.log?.level !== null &&
ctx.log?.level == \"error\") || (ctx.log?.level !== null &&
ctx.log?.level == \"ERROR\"))) {\r\n return true;\r\n }\r\n return
false;\r\n} catch (Exception e) {\r\n return
false;\r\n}\r\n```","sha":"fe56d6d90af45b971ff82731c1ec7eb4c4c0eff3"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Chris Cowan <[email protected]>
@kibanamachine @nchaulet
[8.x] [Fleet] Handle when an agent policy is removed from the current…
8aa7419 
… space (elastic#202991) (elastic#203111)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Fleet] Handle when an agent policy is removed from the current space
(elastic#202991)](elastic#202991)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Nicolas
Chaulet","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T14:13:53Z","message":"[Fleet]
Handle when an agent policy is removed from the current space
(elastic#202991)","sha":"5061174117dddb3a7334ded196541105a53f4f3e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-major"],"title":"[Fleet]
Handle when an agent policy is removed from the current
space","number":202991,"url":"https://github.com/elastic/kibana/pull/202991","mergeCommit":{"message":"[Fleet]
Handle when an agent policy is removed from the current space
(elastic#202991)","sha":"5061174117dddb3a7334ded196541105a53f4f3e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202991","number":202991,"mergeCommit":{"message":"[Fleet]
Handle when an agent policy is removed from the current space
(elastic#202991)","sha":"5061174117dddb3a7334ded196541105a53f4f3e"}}]}]
BACKPORT-->

Co-authored-by: Nicolas Chaulet <[email protected]>
@kibanamachine @miltonhultgren
[8.x] [EEM] Add create and read APIs for v2 type and source definitio…
c9e60df 
…ns (elastic#201470) (elastic#202928)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[EEM] Add create and read APIs for v2 type and source definitions
(elastic#201470)](elastic#201470)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Milton
Hultgren","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T13:53:57Z","message":"[EEM]
Add create and read APIs for v2 type and source definitions
(elastic#201470)\n\n## Summary\r\n\r\nThis PR adds:\r\n* Some basic features
and privileges for the EEM app\r\n* A function that sets up an index
with a template for the new\r\ndefinitions\r\n* 4 API endpoints to read
and create entity types and sources\r\n * `POST
/internal/entities/v2/definitions/types`\r\n * `GET
/internal/entities/v2/definitions/types`\r\n * `POST
/internal/entities/v2/definitions/sources`\r\n * `GET
/internal/entities/v2/definitions/sources`\r\n* Some v2 shuffling around
of code\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Maxim Palenov
<[email protected]>","sha":"26de7a85ba8dfcfca082a463a67de58ba376ce13","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:all-open","ci:project-deploy-observability","Feature:EEM"],"title":"[EEM]
Add create and read APIs for v2 type and source
definitions","number":201470,"url":"https://github.com/elastic/kibana/pull/201470","mergeCommit":{"message":"[EEM]
Add create and read APIs for v2 type and source definitions
(elastic#201470)\n\n## Summary\r\n\r\nThis PR adds:\r\n* Some basic features
and privileges for the EEM app\r\n* A function that sets up an index
with a template for the new\r\ndefinitions\r\n* 4 API endpoints to read
and create entity types and sources\r\n * `POST
/internal/entities/v2/definitions/types`\r\n * `GET
/internal/entities/v2/definitions/types`\r\n * `POST
/internal/entities/v2/definitions/sources`\r\n * `GET
/internal/entities/v2/definitions/sources`\r\n* Some v2 shuffling around
of code\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Maxim Palenov
<[email protected]>","sha":"26de7a85ba8dfcfca082a463a67de58ba376ce13"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201470","number":201470,"mergeCommit":{"message":"[EEM]
Add create and read APIs for v2 type and source definitions
(elastic#201470)\n\n## Summary\r\n\r\nThis PR adds:\r\n* Some basic features
and privileges for the EEM app\r\n* A function that sets up an index
with a template for the new\r\ndefinitions\r\n* 4 API endpoints to read
and create entity types and sources\r\n * `POST
/internal/entities/v2/definitions/types`\r\n * `GET
/internal/entities/v2/definitions/types`\r\n * `POST
/internal/entities/v2/definitions/sources`\r\n * `GET
/internal/entities/v2/definitions/sources`\r\n* Some v2 shuffling around
of code\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Maxim Palenov
<[email protected]>","sha":"26de7a85ba8dfcfca082a463a67de58ba376ce13"}}]}]
BACKPORT-->

Co-authored-by: Milton Hultgren <[email protected]>
@kibanamachine @jloleysens
[8.x] [UA] Ensure that old indices are detected for reindexing (elast…
2c22b24 
…ic#203082) (elastic#203119)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[UA] Ensure that old indices are detected for reindexing
(elastic#203082)](elastic#203082)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jean-Louis
Leysens","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T14:47:32Z","message":"[UA]
Ensure that old indices are detected for reindexing (elastic#203082)\n\n##
Summary\r\n\r\nWe need to handle the following response shape from
`GET\r\n_migration/deprecations`\r\n\r\n```jsonc\r\n \"myindex\": [\r\n
{\r\n \"level\": \"critical\",\r\n \"message\": \"Old index with a
compatibility version < 8.0\", // specifically this message\r\n \"url\":
\"https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-9.0.html\",\r\n
\"details\": \"This index has version: 7.17.25\",\r\n
\"resolve_during_rolling_upgrade\": false\r\n }\r\n ]\r\n```\r\n\r\n<img
width=\"1142\" alt=\"Screenshot 2024-12-05 at 12 44
59\"\r\nsrc=\"https://github.com/user-attachments/assets/723e19ab-dd9d-4b6a-bcda-26a5c8bffa0b\">\r\n\r\n\r\n##
To reviewers\r\n\r\nThese changes were developed/tested on `8.x` and
must be backported.\r\n\r\nRelated\r\n*
https://github.com/elastic/kibana/issues/202669\r\n*
https://github.com/elastic/elasticsearch/issues/118062","sha":"3579425d77caeb59bdb101a2f3c88fe111f8e65e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Feature:Upgrade
Assistant","v9.0.0","backport:version","v8.17.0","v8.18.0"],"title":"[UA]
Ensure that old indices are detected for
reindexing","number":203082,"url":"https://github.com/elastic/kibana/pull/203082","mergeCommit":{"message":"[UA]
Ensure that old indices are detected for reindexing (elastic#203082)\n\n##
Summary\r\n\r\nWe need to handle the following response shape from
`GET\r\n_migration/deprecations`\r\n\r\n```jsonc\r\n \"myindex\": [\r\n
{\r\n \"level\": \"critical\",\r\n \"message\": \"Old index with a
compatibility version < 8.0\", // specifically this message\r\n \"url\":
\"https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-9.0.html\",\r\n
\"details\": \"This index has version: 7.17.25\",\r\n
\"resolve_during_rolling_upgrade\": false\r\n }\r\n ]\r\n```\r\n\r\n<img
width=\"1142\" alt=\"Screenshot 2024-12-05 at 12 44
59\"\r\nsrc=\"https://github.com/user-attachments/assets/723e19ab-dd9d-4b6a-bcda-26a5c8bffa0b\">\r\n\r\n\r\n##
To reviewers\r\n\r\nThese changes were developed/tested on `8.x` and
must be backported.\r\n\r\nRelated\r\n*
https://github.com/elastic/kibana/issues/202669\r\n*
https://github.com/elastic/elasticsearch/issues/118062","sha":"3579425d77caeb59bdb101a2f3c88fe111f8e65e"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203082","number":203082,"mergeCommit":{"message":"[UA]
Ensure that old indices are detected for reindexing (elastic#203082)\n\n##
Summary\r\n\r\nWe need to handle the following response shape from
`GET\r\n_migration/deprecations`\r\n\r\n```jsonc\r\n \"myindex\": [\r\n
{\r\n \"level\": \"critical\",\r\n \"message\": \"Old index with a
compatibility version < 8.0\", // specifically this message\r\n \"url\":
\"https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-9.0.html\",\r\n
\"details\": \"This index has version: 7.17.25\",\r\n
\"resolve_during_rolling_upgrade\": false\r\n }\r\n ]\r\n```\r\n\r\n<img
width=\"1142\" alt=\"Screenshot 2024-12-05 at 12 44
59\"\r\nsrc=\"https://github.com/user-attachments/assets/723e19ab-dd9d-4b6a-bcda-26a5c8bffa0b\">\r\n\r\n\r\n##
To reviewers\r\n\r\nThese changes were developed/tested on `8.x` and
must be backported.\r\n\r\nRelated\r\n*
https://github.com/elastic/kibana/issues/202669\r\n*
https://github.com/elastic/elasticsearch/issues/118062","sha":"3579425d77caeb59bdb101a2f3c88fe111f8e65e"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Jean-Louis Leysens <[email protected]>
@kibanamachine @artem-shelkovnikov
[8.x] Add prompt for connector configuration being in editable mode (e…
6d4ec53 
…lastic#202463) (elastic#203117)

# Backport

This will backport the following commits from `main` to `8.x`:
- [Add prompt for connector configuration being in editable mode
(elastic#202463)](elastic#202463)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Artem
Shelkovnikov","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T14:44:16Z","message":"Add
prompt for connector configuration being in editable mode
(elastic#202463)\n\n### Closes
https://github.com/elastic/search-team/issues/8547\r\n##
Summary\r\n\r\nUser creates connectors following a set of steps. During
configuration\r\nstep they are able to open configuration form and then
click \"Next\" -\r\nconfiguration will not be saved and user will not be
prompted about it.\r\n\r\nThis change adds a prompt for this step - if
the configuration is in\r\neditable state, the prompt will be shown. It
does not check that the\r\nform was edited, however, and it's on
purpose. I'm open to changing it\r\nto only prompt if any value changed,
but I feel that it's important to\r\nprompt even if no values were
entered, just to confirm with the user\r\nthat they want to move on
without specifying any
values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n###
Checklist\r\n\r\nCheck the PR satisfies following conditions.
\r\n\r\nReviewers should verify this PR satisfies this list as
well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-major"],"title":"Add
prompt for connector configuration being in editable
mode","number":202463,"url":"https://github.com/elastic/kibana/pull/202463","mergeCommit":{"message":"Add
prompt for connector configuration being in editable mode
(elastic#202463)\n\n### Closes
https://github.com/elastic/search-team/issues/8547\r\n##
Summary\r\n\r\nUser creates connectors following a set of steps. During
configuration\r\nstep they are able to open configuration form and then
click \"Next\" -\r\nconfiguration will not be saved and user will not be
prompted about it.\r\n\r\nThis change adds a prompt for this step - if
the configuration is in\r\neditable state, the prompt will be shown. It
does not check that the\r\nform was edited, however, and it's on
purpose. I'm open to changing it\r\nto only prompt if any value changed,
but I feel that it's important to\r\nprompt even if no values were
entered, just to confirm with the user\r\nthat they want to move on
without specifying any
values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n###
Checklist\r\n\r\nCheck the PR satisfies following conditions.
\r\n\r\nReviewers should verify this PR satisfies this list as
well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202463","number":202463,"mergeCommit":{"message":"Add
prompt for connector configuration being in editable mode
(elastic#202463)\n\n### Closes
https://github.com/elastic/search-team/issues/8547\r\n##
Summary\r\n\r\nUser creates connectors following a set of steps. During
configuration\r\nstep they are able to open configuration form and then
click \"Next\" -\r\nconfiguration will not be saved and user will not be
prompted about it.\r\n\r\nThis change adds a prompt for this step - if
the configuration is in\r\neditable state, the prompt will be shown. It
does not check that the\r\nform was edited, however, and it's on
purpose. I'm open to changing it\r\nto only prompt if any value changed,
but I feel that it's important to\r\nprompt even if no values were
entered, just to confirm with the user\r\nthat they want to move on
without specifying any
values.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/af768d6d-282d-4f67-a1d0-c54bcf1cb2d0\r\n\r\n###
Checklist\r\n\r\nCheck the PR satisfies following conditions.
\r\n\r\nReviewers should verify this PR satisfies this list as
well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b8a41013ca6f13bea26dd78eaed990104741dc40"}}]}]
BACKPORT-->

Co-authored-by: Artem Shelkovnikov <[email protected]>
@kibanamachine @iblancof
[8.x] [APM] Update alert rule producer terms in getServicesAlerts que…
967baa1 
…ry (elastic#203100) (elastic#203123)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[APM] Update alert rule producer terms in getServicesAlerts query
(elastic#203100)](elastic#203100)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Irene
Blanco","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T15:35:15Z","message":"[APM]
Update alert rule producer terms in getServicesAlerts query
(elastic#203100)\n\n## Summary\r\n\r\nThis PR continues the work
from\r\nhttps://github.com/elastic/issues/201565.\r\nWe missed
updating the alert rules in the `getServicesAlerts` function,\r\nso this
fixes that.\r\n\r\nThere's an
ongoing\r\n[issue](elastic#202415) to
test the\r\nalert counts across solutions and ensure it works as
expected in all\r\nscenarios.\r\n\r\n---------\r\n\r\nCo-authored-by:
Cauê Marcondes
<[email protected]>","sha":"b210a3e6aaac2c82afd817075922ffbeb265ad0b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.18.0"],"title":"[APM]
Update alert rule producer terms in getServicesAlerts
query","number":203100,"url":"https://github.com/elastic/kibana/pull/203100","mergeCommit":{"message":"[APM]
Update alert rule producer terms in getServicesAlerts query
(elastic#203100)\n\n## Summary\r\n\r\nThis PR continues the work
from\r\nhttps://github.com/elastic/issues/201565.\r\nWe missed
updating the alert rules in the `getServicesAlerts` function,\r\nso this
fixes that.\r\n\r\nThere's an
ongoing\r\n[issue](elastic#202415) to
test the\r\nalert counts across solutions and ensure it works as
expected in all\r\nscenarios.\r\n\r\n---------\r\n\r\nCo-authored-by:
Cauê Marcondes
<[email protected]>","sha":"b210a3e6aaac2c82afd817075922ffbeb265ad0b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203100","number":203100,"mergeCommit":{"message":"[APM]
Update alert rule producer terms in getServicesAlerts query
(elastic#203100)\n\n## Summary\r\n\r\nThis PR continues the work
from\r\nhttps://github.com/elastic/issues/201565.\r\nWe missed
updating the alert rules in the `getServicesAlerts` function,\r\nso this
fixes that.\r\n\r\nThere's an
ongoing\r\n[issue](elastic#202415) to
test the\r\nalert counts across solutions and ensure it works as
expected in all\r\nscenarios.\r\n\r\n---------\r\n\r\nCo-authored-by:
Cauê Marcondes
<[email protected]>","sha":"b210a3e6aaac2c82afd817075922ffbeb265ad0b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Irene Blanco <[email protected]>
@kibanamachine @alexwizp
[8.x] fix: [Search:Stateful:EnterpriseSearch:WorkplaceSearch:Usersand…
13dc356 
…Roles]Assign to specific groups input combobox is missing form label (elastic#202462) (elastic#203125)

# Backport

This will backport the following commits from `main` to `8.x`:
- [fix:
[Search:Stateful:EnterpriseSearch:WorkplaceSearch:UsersandRoles]Assign
to specific groups input combobox is missing form label
(elastic#202462)](elastic#202462)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T15:48:18Z","message":"fix:
[Search:Stateful:EnterpriseSearch:WorkplaceSearch:UsersandRoles]Assign
to specific groups input combobox is missing form label
(elastic#202462)\n\nCloses: elastic#202234\r\n\r\n## Description\r\nAssign to specific
groups input combobox on create a role mapping panel\r\non users and
roles page should have a label so assistive technology can\r\nhelp the
user figure out which input they would want to select.\r\n\r\n## Changes
made:\r\n1. required `aria-*` attribute was set for
`EuiComboBox`\r\n\r\n## Screen: \r\n\r\n<img width=\"1438\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b167aafd-b881-4a38-aedc-953858c13dcc\">","sha":"589a6eee000cf1694516b845ba9b72e8ad7e2fb2","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","v9.0.0","Team:Search","backport:prev-minor"],"title":"fix:
[Search:Stateful:EnterpriseSearch:WorkplaceSearch:UsersandRoles]Assign
to specific groups input combobox is missing form
label","number":202462,"url":"https://github.com/elastic/kibana/pull/202462","mergeCommit":{"message":"fix:
[Search:Stateful:EnterpriseSearch:WorkplaceSearch:UsersandRoles]Assign
to specific groups input combobox is missing form label
(elastic#202462)\n\nCloses: elastic#202234\r\n\r\n## Description\r\nAssign to specific
groups input combobox on create a role mapping panel\r\non users and
roles page should have a label so assistive technology can\r\nhelp the
user figure out which input they would want to select.\r\n\r\n## Changes
made:\r\n1. required `aria-*` attribute was set for
`EuiComboBox`\r\n\r\n## Screen: \r\n\r\n<img width=\"1438\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b167aafd-b881-4a38-aedc-953858c13dcc\">","sha":"589a6eee000cf1694516b845ba9b72e8ad7e2fb2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202462","number":202462,"mergeCommit":{"message":"fix:
[Search:Stateful:EnterpriseSearch:WorkplaceSearch:UsersandRoles]Assign
to specific groups input combobox is missing form label
(elastic#202462)\n\nCloses: elastic#202234\r\n\r\n## Description\r\nAssign to specific
groups input combobox on create a role mapping panel\r\non users and
roles page should have a label so assistive technology can\r\nhelp the
user figure out which input they would want to select.\r\n\r\n## Changes
made:\r\n1. required `aria-*` attribute was set for
`EuiComboBox`\r\n\r\n## Screen: \r\n\r\n<img width=\"1438\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b167aafd-b881-4a38-aedc-953858c13dcc\">","sha":"589a6eee000cf1694516b845ba9b72e8ad7e2fb2"}}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <[email protected]>
@kibanamachine @benakansara
[8.x] [RCA] [Events timeline] Show all events (elastic#202235) (elast…
67e7073 
…ic#202956)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[RCA] [Events timeline] Show all events
(elastic#202235)](elastic#202235)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Bena
Kansara","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T14:57:05Z","message":"[RCA]
[Events timeline] Show all events (elastic#202235)\n\nAs part of
elastic#200799, this PR\r\nremoves
filter (previously the filter was based on any group by field,\r\nwhich
was changed to focus only on `service.name` for kubecon demo) so\r\nthat
all events are shown on events
timeline.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Faisal Kanout
<[email protected]>","sha":"2a7689e693424679c6e870b772e8510d9a25dbd0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[RCA]
[Events timeline] Show all
events","number":202235,"url":"https://github.com/elastic/kibana/pull/202235","mergeCommit":{"message":"[RCA]
[Events timeline] Show all events (elastic#202235)\n\nAs part of
elastic#200799, this PR\r\nremoves
filter (previously the filter was based on any group by field,\r\nwhich
was changed to focus only on `service.name` for kubecon demo) so\r\nthat
all events are shown on events
timeline.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Faisal Kanout
<[email protected]>","sha":"2a7689e693424679c6e870b772e8510d9a25dbd0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202235","number":202235,"mergeCommit":{"message":"[RCA]
[Events timeline] Show all events (elastic#202235)\n\nAs part of
elastic#200799, this PR\r\nremoves
filter (previously the filter was based on any group by field,\r\nwhich
was changed to focus only on `service.name` for kubecon demo) so\r\nthat
all events are shown on events
timeline.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Faisal Kanout
<[email protected]>","sha":"2a7689e693424679c6e870b772e8510d9a25dbd0"}}]}]
BACKPORT-->

Co-authored-by: Bena Kansara <[email protected]>
@kibanamachine @walterra
[8.x] [ML] Transform: Fix &lt;DefinePivotSummary /&gt; jest test. (el…
627d84b 
…astic#195998) (elastic#203129)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ML] Transform: Fix &lt;DefinePivotSummary /&gt; jest test.
(elastic#195998)](elastic#195998)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T15:59:00Z","message":"[ML]
Transform: Fix <DefinePivotSummary /> jest test. (elastic#195998)\n\n##
Summary\r\n\r\nFixes elastic#195992 (failing test).\r\n\r\nUpdates the mock for
the preview endpoint to make the test pass again.\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\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#_add_your_labels)","sha":"c4d64039b3c23433eb643f3a772357407695d024","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:Transforms","v9.0.0","backport:version","v8.18.0"],"title":"[ML]
Transform: Fix <DefinePivotSummary /> jest
test.","number":195998,"url":"https://github.com/elastic/kibana/pull/195998","mergeCommit":{"message":"[ML]
Transform: Fix <DefinePivotSummary /> jest test. (elastic#195998)\n\n##
Summary\r\n\r\nFixes elastic#195992 (failing test).\r\n\r\nUpdates the mock for
the preview endpoint to make the test pass again.\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\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#_add_your_labels)","sha":"c4d64039b3c23433eb643f3a772357407695d024"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195998","number":195998,"mergeCommit":{"message":"[ML]
Transform: Fix <DefinePivotSummary /> jest test. (elastic#195998)\n\n##
Summary\r\n\r\nFixes elastic#195992 (failing test).\r\n\r\nUpdates the mock for
the preview endpoint to make the test pass again.\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\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#_add_your_labels)","sha":"c4d64039b3c23433eb643f3a772357407695d024"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Walter Rafelsberger <[email protected]>
@kibanamachine @fkanout
[8.x] [OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter …
a70bdf0 
…is invalid (elastic#203096) (elastic#203134)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[OBX-UX-MGMT][ALERTING] Fix APM rule error msg when KQL filter is
invalid (elastic#203096)](elastic#203096)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Faisal
Kanout","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T16:07:58Z","message":"[OBX-UX-MGMT][ALERTING]
Fix APM rule error msg when KQL filter is invalid (elastic#203096)\n\n##
Summary\r\n\r\nIt fixes elastic#199273
by validating\r\nthe query before passing it to the preview
chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management"],"title":"[OBX-UX-MGMT][ALERTING]
Fix APM rule error msg when KQL filter is
invalid","number":203096,"url":"https://github.com/elastic/kibana/pull/203096","mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING]
Fix APM rule error msg when KQL filter is invalid (elastic#203096)\n\n##
Summary\r\n\r\nIt fixes elastic#199273
by validating\r\nthe query before passing it to the preview
chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203096","number":203096,"mergeCommit":{"message":"[OBX-UX-MGMT][ALERTING]
Fix APM rule error msg when KQL filter is invalid (elastic#203096)\n\n##
Summary\r\n\r\nIt fixes elastic#199273
by validating\r\nthe query before passing it to the preview
chart","sha":"f1109cfccedfd386263a00207df81c766cfaf6e4"}}]}] BACKPORT-->

Co-authored-by: Faisal Kanout <[email protected]>
@animehart
[8.x] [Cloud Security][Bug] Fix for Page Crashing (elastic#203028) (e…
ba5086b 
…lastic#203139)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Cloud Security][Bug] Fix for Page Crashing
(elastic#203028)](elastic#203028)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rickyanto
Ang","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T14:35:42Z","message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud
Security","backport:prev-minor","backport:version","v8.17.0"],"number":203028,"url":"https://github.com/elastic/kibana/pull/203028","mergeCommit":{"message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203028","number":203028,"mergeCommit":{"message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6"}},{"branch":"8.17","label":"v8.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/203135","number":203135,"branch":"8.x","state":"OPEN"}]}]
BACKPORT-->
@kibanamachine @semd
[8.x] [SecuritySolution][Onboarding] Siem migration start card and fl…
6445464 
…yout - Part 1 (elastic#202886) (elastic#203141)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[SecuritySolution][Onboarding] Siem migration start card and flyout -
Part 1 (elastic#202886)](elastic#202886)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T16:29:51Z","message":"[SecuritySolution][Onboarding]
Siem migration start card and flyout - Part 1 (elastic#202886)\n\n##
Summary\r\n\r\nPart of:
https://github.com/elastic/security-team/issues/10667\r\n\r\nImplementation
of the Onboarding card to create migrations using the\r\nflyout\r\n\r\n>
[!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental
flag enabled\r\nto work. Otherwise only the default topic will be
available and the\r\ntopic selector won't be displayed.\r\n\r\n<img
width=\"1547\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f43c60a0-0631-44d8-ba82-7f16971ecc24\">\r\n\r\n####
To do in part 2:\r\n- Complete implementation of migration finished
panel: chart and stats\r\n- Improve implementation of migration ready
panel: should only allow\r\nopen the flyout\r\n- Implement missing steps
in the flyout: Macros and Lookups\r\n\r\n### Test \r\nEnable
experimental flag\r\nUse
file:\r\n[1733135547_1420.json](https://github.com/user-attachments/files/18010116/1733135547_1420.json)\r\n\r\n---------\r\n\r\nCo-authored-by:
Elastic Machine
<[email protected]>\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b5c119496ace2c56da6752c7e9ab26ef963fec95","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting","Team:
SecuritySolution","backport:version","v8.18.0"],"title":"[SecuritySolution][Onboarding]
Siem migration start card and flyout - Part
1","number":202886,"url":"https://github.com/elastic/kibana/pull/202886","mergeCommit":{"message":"[SecuritySolution][Onboarding]
Siem migration start card and flyout - Part 1 (elastic#202886)\n\n##
Summary\r\n\r\nPart of:
https://github.com/elastic/security-team/issues/10667\r\n\r\nImplementation
of the Onboarding card to create migrations using the\r\nflyout\r\n\r\n>
[!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental
flag enabled\r\nto work. Otherwise only the default topic will be
available and the\r\ntopic selector won't be displayed.\r\n\r\n<img
width=\"1547\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f43c60a0-0631-44d8-ba82-7f16971ecc24\">\r\n\r\n####
To do in part 2:\r\n- Complete implementation of migration finished
panel: chart and stats\r\n- Improve implementation of migration ready
panel: should only allow\r\nopen the flyout\r\n- Implement missing steps
in the flyout: Macros and Lookups\r\n\r\n### Test \r\nEnable
experimental flag\r\nUse
file:\r\n[1733135547_1420.json](https://github.com/user-attachments/files/18010116/1733135547_1420.json)\r\n\r\n---------\r\n\r\nCo-authored-by:
Elastic Machine
<[email protected]>\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b5c119496ace2c56da6752c7e9ab26ef963fec95"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202886","number":202886,"mergeCommit":{"message":"[SecuritySolution][Onboarding]
Siem migration start card and flyout - Part 1 (elastic#202886)\n\n##
Summary\r\n\r\nPart of:
https://github.com/elastic/security-team/issues/10667\r\n\r\nImplementation
of the Onboarding card to create migrations using the\r\nflyout\r\n\r\n>
[!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental
flag enabled\r\nto work. Otherwise only the default topic will be
available and the\r\ntopic selector won't be displayed.\r\n\r\n<img
width=\"1547\"
alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f43c60a0-0631-44d8-ba82-7f16971ecc24\">\r\n\r\n####
To do in part 2:\r\n- Complete implementation of migration finished
panel: chart and stats\r\n- Improve implementation of migration ready
panel: should only allow\r\nopen the flyout\r\n- Implement missing steps
in the flyout: Macros and Lookups\r\n\r\n### Test \r\nEnable
experimental flag\r\nUse
file:\r\n[1733135547_1420.json](https://github.com/user-attachments/files/18010116/1733135547_1420.json)\r\n\r\n---------\r\n\r\nCo-authored-by:
Elastic Machine
<[email protected]>\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"b5c119496ace2c56da6752c7e9ab26ef963fec95"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Massaneda <[email protected]>
@eokoneyo
[8.x] [React18] Migrate test suites to account for testing library up…
62f28c4 
…grades security-threat-hunting-investigations (elastic#201145) (elastic#201859)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[React18] Migrate test suites to account for testing library upgrades
security-threat-hunting-investigations
(elastic#201145)](elastic#201145)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Eyo O.
Eyo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-22T10:54:41Z","message":"[React18]
Migrate test suites to account for testing library upgrades
security-threat-hunting-investigations (elastic#201145)\n\nThis PR migrates
test suites that use `renderHook` from the
library\r\n`@testing-library/react-hooks` to adopt the equivalent and
replacement\r\nof `renderHook` from the export that is now available
from\r\n`@testing-library/react`. This work is required for the
planned\r\nmigration to react18.\r\n\r\n## Context\r\n\r\nIn this PR,
usages of `waitForNextUpdate` that previously could have\r\nbeen
destructured from `renderHook` are now been replaced with
`waitFor`\r\nexported from `@testing-library/react`, furthermore
`waitFor`\r\nthat would also have been destructured from the same
renderHook result\r\nis now been replaced with `waitFor` from the export
of\r\n`@testing-library/react`.\r\n\r\n***Why is `waitFor` a sufficient
enough replacement for\r\n`waitForNextUpdate`, and better for testing
values subject to async\r\ncomputations?***\r\n\r\nWaitFor will retry
the provided callback if an error is returned, till\r\nthe configured
timeout elapses. By default the retry interval is `50ms`\r\nwith a
timeout value of `1000ms` that\r\neffectively translates to at least 20
retries for assertions placed\r\nwithin waitFor.
See\r\nhttps://testing-library.com/docs/dom-testing-library/api-async/#waitfor\r\nfor
more information.\r\nThis however means that for person's writing tests,
said person has to\r\nbe explicit about expectations that describe the
internal state of the\r\nhook being tested.\r\nThis implies checking for
instance when a react query hook is being\r\nrendered, there's an
assertion that said hook isn't loading anymore.\r\n\r\nIn this PR you'd
notice that this pattern has been adopted, with most\r\nexisting
assertions following an invocation of `waitForNextUpdate`
being\r\nplaced within a `waitFor`\r\ninvocation. In some cases the
replacement is simply a `waitFor(() => new\r\nPromise((resolve) =>
resolve(null)))` (many thanks to @kapral18, for\r\npoint out exactly why
this works),\r\nwhere this suffices the assertions that follow aren't
placed within a\r\nwaitFor so this PR doesn't get larger than it needs
to be.\r\n\r\nIt's also worth pointing out this PR might also contain
changes to test\r\nand application code to improve said existing
test.\r\n\r\n### What to do next?\r\n1. Review the changes in this
PR.\r\n2. If you think the changes are correct, approve the
PR.\r\n\r\n## Any questions?\r\nIf you have any questions or need help
with this PR, please leave\r\ncomments in this
PR.","sha":"06de5f3f51961df174ae109a200a8ae1e4acfaff","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","v9.0.0","Team:Threat
Hunting:Investigations","backport:prev-minor","React@18"],"number":201145,"url":"https://github.com/elastic/kibana/pull/201145","mergeCommit":{"message":"[React18]
Migrate test suites to account for testing library upgrades
security-threat-hunting-investigations (elastic#201145)\n\nThis PR migrates
test suites that use `renderHook` from the
library\r\n`@testing-library/react-hooks` to adopt the equivalent and
replacement\r\nof `renderHook` from the export that is now available
from\r\n`@testing-library/react`. This work is required for the
planned\r\nmigration to react18.\r\n\r\n## Context\r\n\r\nIn this PR,
usages of `waitForNextUpdate` that previously could have\r\nbeen
destructured from `renderHook` are now been replaced with
`waitFor`\r\nexported from `@testing-library/react`, furthermore
`waitFor`\r\nthat would also have been destructured from the same
renderHook result\r\nis now been replaced with `waitFor` from the export
of\r\n`@testing-library/react`.\r\n\r\n***Why is `waitFor` a sufficient
enough replacement for\r\n`waitForNextUpdate`, and better for testing
values subject to async\r\ncomputations?***\r\n\r\nWaitFor will retry
the provided callback if an error is returned, till\r\nthe configured
timeout elapses. By default the retry interval is `50ms`\r\nwith a
timeout value of `1000ms` that\r\neffectively translates to at least 20
retries for assertions placed\r\nwithin waitFor.
See\r\nhttps://testing-library.com/docs/dom-testing-library/api-async/#waitfor\r\nfor
more information.\r\nThis however means that for person's writing tests,
said person has to\r\nbe explicit about expectations that describe the
internal state of the\r\nhook being tested.\r\nThis implies checking for
instance when a react query hook is being\r\nrendered, there's an
assertion that said hook isn't loading anymore.\r\n\r\nIn this PR you'd
notice that this pattern has been adopted, with most\r\nexisting
assertions following an invocation of `waitForNextUpdate`
being\r\nplaced within a `waitFor`\r\ninvocation. In some cases the
replacement is simply a `waitFor(() => new\r\nPromise((resolve) =>
resolve(null)))` (many thanks to @kapral18, for\r\npoint out exactly why
this works),\r\nwhere this suffices the assertions that follow aren't
placed within a\r\nwaitFor so this PR doesn't get larger than it needs
to be.\r\n\r\nIt's also worth pointing out this PR might also contain
changes to test\r\nand application code to improve said existing
test.\r\n\r\n### What to do next?\r\n1. Review the changes in this
PR.\r\n2. If you think the changes are correct, approve the
PR.\r\n\r\n## Any questions?\r\nIf you have any questions or need help
with this PR, please leave\r\ncomments in this
PR.","sha":"06de5f3f51961df174ae109a200a8ae1e4acfaff"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201145","number":201145,"mergeCommit":{"message":"[React18]
Migrate test suites to account for testing library upgrades
security-threat-hunting-investigations (elastic#201145)\n\nThis PR migrates
test suites that use `renderHook` from the
library\r\n`@testing-library/react-hooks` to adopt the equivalent and
replacement\r\nof `renderHook` from the export that is now available
from\r\n`@testing-library/react`. This work is required for the
planned\r\nmigration to react18.\r\n\r\n## Context\r\n\r\nIn this PR,
usages of `waitForNextUpdate` that previously could have\r\nbeen
destructured from `renderHook` are now been replaced with
`waitFor`\r\nexported from `@testing-library/react`, furthermore
`waitFor`\r\nthat would also have been destructured from the same
renderHook result\r\nis now been replaced with `waitFor` from the export
of\r\n`@testing-library/react`.\r\n\r\n***Why is `waitFor` a sufficient
enough replacement for\r\n`waitForNextUpdate`, and better for testing
values subject to async\r\ncomputations?***\r\n\r\nWaitFor will retry
the provided callback if an error is returned, till\r\nthe configured
timeout elapses. By default the retry interval is `50ms`\r\nwith a
timeout value of `1000ms` that\r\neffectively translates to at least 20
retries for assertions placed\r\nwithin waitFor.
See\r\nhttps://testing-library.com/docs/dom-testing-library/api-async/#waitfor\r\nfor
more information.\r\nThis however means that for person's writing tests,
said person has to\r\nbe explicit about expectations that describe the
internal state of the\r\nhook being tested.\r\nThis implies checking for
instance when a react query hook is being\r\nrendered, there's an
assertion that said hook isn't loading anymore.\r\n\r\nIn this PR you'd
notice that this pattern has been adopted, with most\r\nexisting
assertions following an invocation of `waitForNextUpdate`
being\r\nplaced within a `waitFor`\r\ninvocation. In some cases the
replacement is simply a `waitFor(() => new\r\nPromise((resolve) =>
resolve(null)))` (many thanks to @kapral18, for\r\npoint out exactly why
this works),\r\nwhere this suffices the assertions that follow aren't
placed within a\r\nwaitFor so this PR doesn't get larger than it needs
to be.\r\n\r\nIt's also worth pointing out this PR might also contain
changes to test\r\nand application code to improve said existing
test.\r\n\r\n### What to do next?\r\n1. Review the changes in this
PR.\r\n2. If you think the changes are correct, approve the
PR.\r\n\r\n## Any questions?\r\nIf you have any questions or need help
with this PR, please leave\r\ncomments in this
PR.","sha":"06de5f3f51961df174ae109a200a8ae1e4acfaff"}}]}] BACKPORT-->
@kibanamachine @animehart
[8.x] [Cloud Security][Bug] Fix for Page Crashing (elastic#203028) (e…
0d4df88 
…lastic#203140)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Cloud Security][Bug] Fix for Page Crashing
(elastic#203028)](elastic#203028)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rickyanto
Ang","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T14:35:42Z","message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud
Security","backport:prev-minor","backport:version","v8.17.0"],"title":"[Cloud
Security][Bug] Fix for Page
Crashing","number":203028,"url":"https://github.com/elastic/kibana/pull/203028","mergeCommit":{"message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203028","number":203028,"mergeCommit":{"message":"[Cloud
Security][Bug] Fix for Page Crashing (elastic#203028)\n\n## Summary\r\n\r\nThis
PR is for quick fix to address issue with Page crashing when
user\r\nclicks on user name or host name on preview flyout for Alerts
Contextual\r\nFlyout","sha":"06b774e78886bf914cc51a2d99497427a8c2a9e6"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"url":"https://github.com/elastic/kibana/pull/203135","number":203135,"branch":"8.x","state":"OPEN"}]}]
BACKPORT-->

Co-authored-by: Rickyanto Ang <[email protected]>
@paul-tavares
[8.x] [Security Solution][Endpoint] Fix Cypress test to work with ref…
e9cb539 
…actored Roles page (elastic#202770) (elastic#203131)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Solution][Endpoint] Fix Cypress test to work with
refactored Roles page
(elastic#202770)](elastic#202770)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Paul
Tavares","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T15:56:53Z","message":"[Security
Solution][Endpoint] Fix Cypress test to work with refactored Roles page
(elastic#202770)\n\n## Summary\r\n\r\n- Fixes cypress tests for space awareness
RBAC checks to work with the\r\nrecent changes to the core Role page\r\n
- Fixes elastic#200962\r\n - Fixes elastic#200967\r\n- Enables test file for runs on
Serverless MKI
environments","sha":"5262902a86a6b2b549e61b81037ce77933e2d484","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend
Workflows","backport:prev-minor","v8.18.0"],"number":202770,"url":"https://github.com/elastic/kibana/pull/202770","mergeCommit":{"message":"[Security
Solution][Endpoint] Fix Cypress test to work with refactored Roles page
(elastic#202770)\n\n## Summary\r\n\r\n- Fixes cypress tests for space awareness
RBAC checks to work with the\r\nrecent changes to the core Role page\r\n
- Fixes elastic#200962\r\n - Fixes elastic#200967\r\n- Enables test file for runs on
Serverless MKI
environments","sha":"5262902a86a6b2b549e61b81037ce77933e2d484"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202770","number":202770,"mergeCommit":{"message":"[Security
Solution][Endpoint] Fix Cypress test to work with refactored Roles page
(elastic#202770)\n\n## Summary\r\n\r\n- Fixes cypress tests for space awareness
RBAC checks to work with the\r\nrecent changes to the core Role page\r\n
- Fixes elastic#200962\r\n - Fixes elastic#200967\r\n- Enables test file for runs on
Serverless MKI
environments","sha":"5262902a86a6b2b549e61b81037ce77933e2d484"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
@kibanamachine @eokoneyo
[8.x] make emotion typing global (elastic#200958) (elastic#203162)
c4c00af 
# Backport

This will backport the following commits from `main` to `8.x`:
- [make emotion typing global
(elastic#200958)](elastic#200958)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Eyo O.
Eyo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T18:20:43Z","message":"make
emotion typing global (elastic#200958)\n\n## Summary\r\n\r\nInformed
by\r\nhttps://github.com/elastic/eui/discussions/6828#discussioncomment-11247425,\r\ncloses
https://github.com/elastic/kibana-team/issues/1299\r\n\r\nThis PR
consolidates typings to provide adequate typing for the `css`\r\nprop
EUI components accept. Placing the required typing file in the\r\ntyping
directory means that all other plugins that already reference\r\nthis
directory in their `tsconfig.json` would get this improvement
by\r\ndefault.\r\n\r\n<!--\r\n### Checklist\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_node:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\n\r\n-->","sha":"c5cc1532d74e8d733f57329959253e698105b447","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management"],"title":"make
emotion typing
global","number":200958,"url":"https://github.com/elastic/kibana/pull/200958","mergeCommit":{"message":"make
emotion typing global (elastic#200958)\n\n## Summary\r\n\r\nInformed
by\r\nhttps://github.com/elastic/eui/discussions/6828#discussioncomment-11247425,\r\ncloses
https://github.com/elastic/kibana-team/issues/1299\r\n\r\nThis PR
consolidates typings to provide adequate typing for the `css`\r\nprop
EUI components accept. Placing the required typing file in the\r\ntyping
directory means that all other plugins that already reference\r\nthis
directory in their `tsconfig.json` would get this improvement
by\r\ndefault.\r\n\r\n<!--\r\n### Checklist\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_node:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\n\r\n-->","sha":"c5cc1532d74e8d733f57329959253e698105b447"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200958","number":200958,"mergeCommit":{"message":"make
emotion typing global (elastic#200958)\n\n## Summary\r\n\r\nInformed
by\r\nhttps://github.com/elastic/eui/discussions/6828#discussioncomment-11247425,\r\ncloses
https://github.com/elastic/kibana-team/issues/1299\r\n\r\nThis PR
consolidates typings to provide adequate typing for the `css`\r\nprop
EUI components accept. Placing the required typing file in the\r\ntyping
directory means that all other plugins that already reference\r\nthis
directory in their `tsconfig.json` would get this improvement
by\r\ndefault.\r\n\r\n<!--\r\n### Checklist\r\n\r\nCheck the PR
satisfies following conditions. \r\n\r\nReviewers should verify this PR
satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [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- [ ] If a plugin
configuration key changed, check if it needs to be\r\nallowlisted in the
cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [ ] [Flaky
Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\r\nused on any tests changed\r\n- [ ] The PR description includes
the appropriate Release Notes section,\r\nand the correct
`release_node:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nDoes this PR introduce any risks? For example,
consider risks like hard\r\nto test bugs, performance regression,
potential of data loss.\r\n\r\nDescribe the risk, its severity, and
mitigation for each identified\r\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\r\n\r\n- [ ] [See some
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n-
[ ]
...\r\n\r\n\r\n-->","sha":"c5cc1532d74e8d733f57329959253e698105b447"}}]}]
BACKPORT-->

Co-authored-by: Eyo O. Eyo <[email protected]>
@kibanamachine @bhapas
[8.x] [Automatic Import] Restrict unsupported log formats (elastic#20…
aae390d 
…2994) (elastic#203176)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Automatic Import] Restrict unsupported log formats
(elastic#202994)](elastic#202994)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Bharat
Pasupula","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T19:18:08Z","message":"[Automatic
Import] Restrict unsupported log formats
(elastic#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport"],"title":"[Automatic
Import] Restrict unsupported log
formats","number":202994,"url":"https://github.com/elastic/kibana/pull/202994","mergeCommit":{"message":"[Automatic
Import] Restrict unsupported log formats
(elastic#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202994","number":202994,"mergeCommit":{"message":"[Automatic
Import] Restrict unsupported log formats
(elastic#202994)","sha":"178baa8468b3252bbebb6074baf0e59c9916d1a3"}}]}]
BACKPORT-->

Co-authored-by: Bharat Pasupula <[email protected]>
@kibanamachine @kdelemme
[8.x] feat(slo): SLO grouping values selector (elastic#202364) (elast…
f6d3809 
…ic#203168)

# Backport

This will backport the following commits from `main` to `8.x`:
- [feat(slo): SLO grouping values selector
(elastic#202364)](elastic#202364)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kevin
Delemme","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T18:51:03Z","message":"feat(slo):
SLO grouping values selector
(elastic#202364)","sha":"7806861c5fc742cc09156655413d3d5c2ab87fda","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.18.0"],"title":"feat(slo):
SLO grouping values
selector","number":202364,"url":"https://github.com/elastic/kibana/pull/202364","mergeCommit":{"message":"feat(slo):
SLO grouping values selector
(elastic#202364)","sha":"7806861c5fc742cc09156655413d3d5c2ab87fda"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202364","number":202364,"mergeCommit":{"message":"feat(slo):
SLO grouping values selector
(elastic#202364)","sha":"7806861c5fc742cc09156655413d3d5c2ab87fda"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Kevin Delemme <[email protected]>
@kibanamachine @nreese
[8.x] [embeddable] remove legacy embeddable factories from &#x27;Add …
8bce480 
…from library&#x27; flyout (elastic#202823) (elastic#203181)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[embeddable] remove legacy embeddable factories from &#x27;Add from
library&#x27; flyout
(elastic#202823)](elastic#202823)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T19:55:40Z","message":"[embeddable]
remove legacy embeddable factories from 'Add from library' flyout
(elastic#202823)\n\nPart of
https://github.com/elastic/kibana/issues/180059\r\n\r\nPR removes legacy
embeddable factory support from Canvas and Dashboard\r\n`Add from
library` flyout\r\n\r\nPR also does the following clean-ups\r\n1)
Renames folder, files, and component from `add_panel_flyout`
to\r\n`add_from_library_flyout`. When component was originally
created,\r\ndashboard `Add panel` button did not exist, and `Add from
library`\r\nbutton was called `Add panel`. Now that dashboard contains
`Add panel`\r\nand `Add from library` buttons, the old naming convention
is super\r\nconfusing and not longer lines up with the current UI.\r\n2)
moves registry to `add_from_library` folder so that the registry
is\r\nin closer proximity to its usage.\r\n2) Renames
`registerReactEmbeddableSavedObject` to\r\n`registerAddFromLibraryType`
because\r\n`registerReactEmbeddableSavedObject` does not clearly
specifying what\r\nthe registry
enables.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"d508b5da9ce4664565c1594d23688663eff66522","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","v9.0.0","ci:project-deploy-observability","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[embeddable]
remove legacy embeddable factories from 'Add from library'
flyout","number":202823,"url":"https://github.com/elastic/kibana/pull/202823","mergeCommit":{"message":"[embeddable]
remove legacy embeddable factories from 'Add from library' flyout
(elastic#202823)\n\nPart of
https://github.com/elastic/kibana/issues/180059\r\n\r\nPR removes legacy
embeddable factory support from Canvas and Dashboard\r\n`Add from
library` flyout\r\n\r\nPR also does the following clean-ups\r\n1)
Renames folder, files, and component from `add_panel_flyout`
to\r\n`add_from_library_flyout`. When component was originally
created,\r\ndashboard `Add panel` button did not exist, and `Add from
library`\r\nbutton was called `Add panel`. Now that dashboard contains
`Add panel`\r\nand `Add from library` buttons, the old naming convention
is super\r\nconfusing and not longer lines up with the current UI.\r\n2)
moves registry to `add_from_library` folder so that the registry
is\r\nin closer proximity to its usage.\r\n2) Renames
`registerReactEmbeddableSavedObject` to\r\n`registerAddFromLibraryType`
because\r\n`registerReactEmbeddableSavedObject` does not clearly
specifying what\r\nthe registry
enables.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"d508b5da9ce4664565c1594d23688663eff66522"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202823","number":202823,"mergeCommit":{"message":"[embeddable]
remove legacy embeddable factories from 'Add from library' flyout
(elastic#202823)\n\nPart of
https://github.com/elastic/kibana/issues/180059\r\n\r\nPR removes legacy
embeddable factory support from Canvas and Dashboard\r\n`Add from
library` flyout\r\n\r\nPR also does the following clean-ups\r\n1)
Renames folder, files, and component from `add_panel_flyout`
to\r\n`add_from_library_flyout`. When component was originally
created,\r\ndashboard `Add panel` button did not exist, and `Add from
library`\r\nbutton was called `Add panel`. Now that dashboard contains
`Add panel`\r\nand `Add from library` buttons, the old naming convention
is super\r\nconfusing and not longer lines up with the current UI.\r\n2)
moves registry to `add_from_library` folder so that the registry
is\r\nin closer proximity to its usage.\r\n2) Renames
`registerReactEmbeddableSavedObject` to\r\n`registerAddFromLibraryType`
because\r\n`registerReactEmbeddableSavedObject` does not clearly
specifying what\r\nthe registry
enables.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>\r\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"d508b5da9ce4664565c1594d23688663eff66522"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <[email protected]>
@jeramysoucy @kibanamachine
[8.x] Upgrade axios 1.7.4 → 1.7.9 (elastic#202774) (elastic#203036)
e67edef 
# Backport

This will backport the following commits from `main` to `8.x`:
- [Upgrade axios 1.7.4 → 1.7.9
(elastic#202774)](elastic#202774)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-04T22:13:35Z","message":"Upgrade
axios 1.7.4 → 1.7.9 (elastic#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from
v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Security","release_note:skip","v9.0.0","backport:all-open","v8.18.0"],"number":202774,"url":"https://github.com/elastic/kibana/pull/202774","mergeCommit":{"message":"Upgrade
axios 1.7.4 → 1.7.9 (elastic#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from
v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202774","number":202774,"mergeCommit":{"message":"Upgrade
axios 1.7.4 → 1.7.9 (elastic#202774)\n\n## Summary\r\n\r\nUpgrades `axios` from
v1.7.4 to v1.7.9.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<[email protected]>","sha":"52e021ff7fa289fcba42e090aa12e9de1f868ee0"}},{"branch":"8.x","label":"v8.18.0","labelRegex":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <[email protected]>
@kibanamachine @Ikuni17
[8.x] [CI] Upgrade buildkite deps (elastic#203160) (elastic#203189)
e3f51cd 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[CI] Upgrade buildkite deps
(elastic#203160)](elastic#203160)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Brad
White","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T21:34:50Z","message":"[CI]
Upgrade buildkite deps (elastic#203160)\n\n-
[Mocha\r\nChangelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md#changelog)\r\n
- Only breaking change seems to be min Node
version","sha":"9c635a2b25307efe1b33916b190da3894272414e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","v9.0.0","backport:prev-major"],"title":"[CI]
Upgrade buildkite
deps","number":203160,"url":"https://github.com/elastic/kibana/pull/203160","mergeCommit":{"message":"[CI]
Upgrade buildkite deps (elastic#203160)\n\n-
[Mocha\r\nChangelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md#changelog)\r\n
- Only breaking change seems to be min Node
version","sha":"9c635a2b25307efe1b33916b190da3894272414e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203160","number":203160,"mergeCommit":{"message":"[CI]
Upgrade buildkite deps (elastic#203160)\n\n-
[Mocha\r\nChangelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md#changelog)\r\n
- Only breaking change seems to be min Node
version","sha":"9c635a2b25307efe1b33916b190da3894272414e"}}]}]
BACKPORT-->

Co-authored-by: Brad White <[email protected]>
@kibanamachine @pickypg
[8.x] [DataUsage][Serverless] Fix AutoOps error message to drop &quot…
e128dfc 
…;agent&quot; reference (elastic#202996) (elastic#203190)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[DataUsage][Serverless] Fix AutoOps error message to drop
&quot;agent&quot; reference
(elastic#202996)](elastic#202996)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Chris
Earle","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T21:43:29Z","message":"[DataUsage][Serverless]
Fix AutoOps error message to drop \"agent\" reference (elastic#202996)\n\n##
Summary\r\n\r\nThis removes the references to \"autoops agent\" in the
error message if\r\nthe request fails, as it has nothing to do with any
agent.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following
conditions. \r\n\r\nReviewers should verify this PR satisfies this list
as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] The PR description includes the appropriate Release
Notes section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nNo. None of the error messages are exported, so
they cannot be misused\r\nin other
places.","sha":"82301e7454c43392d3aac04f9f3d8f64d52c6622","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:build-serverless-image","backport:version","v8.18.0"],"title":"[DataUsage][Serverless]
Fix AutoOps error message to drop \"agent\" reference
","number":202996,"url":"https://github.com/elastic/kibana/pull/202996","mergeCommit":{"message":"[DataUsage][Serverless]
Fix AutoOps error message to drop \"agent\" reference (elastic#202996)\n\n##
Summary\r\n\r\nThis removes the references to \"autoops agent\" in the
error message if\r\nthe request fails, as it has nothing to do with any
agent.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following
conditions. \r\n\r\nReviewers should verify this PR satisfies this list
as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] The PR description includes the appropriate Release
Notes section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nNo. None of the error messages are exported, so
they cannot be misused\r\nin other
places.","sha":"82301e7454c43392d3aac04f9f3d8f64d52c6622"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202996","number":202996,"mergeCommit":{"message":"[DataUsage][Serverless]
Fix AutoOps error message to drop \"agent\" reference (elastic#202996)\n\n##
Summary\r\n\r\nThis removes the references to \"autoops agent\" in the
error message if\r\nthe request fails, as it has nothing to do with any
agent.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following
conditions. \r\n\r\nReviewers should verify this PR satisfies this list
as well.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] This was checked for breaking HTTP API changes, and any
breaking\r\nchanges have been approved by the breaking-change committee.
The\r\n`release_note:breaking` label should be applied in these
situations.\r\n- [x] The PR description includes the appropriate Release
Notes section,\r\nand the correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Identify risks\r\n\r\nNo. None of the error messages are exported, so
they cannot be misused\r\nin other
places.","sha":"82301e7454c43392d3aac04f9f3d8f64d52c6622"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Chris Earle <[email protected]>
@kibanamachine @stephmilovic
[8.x] [Security Assistant] Abort signal fix (elastic#203041) (elastic…
619a64f 
…#203187)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[Security Assistant] Abort signal fix
(elastic#203041)](elastic#203041)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T21:27:29Z","message":"[Security
Assistant] Abort signal fix
(elastic#203041)","sha":"b3b2c1745ac846b377d8e234526aa965196e4de9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:
SecuritySolution","backport:prev-major","Team:Security Generative
AI"],"title":"[Security Assistant] Abort signal
fix","number":203041,"url":"https://github.com/elastic/kibana/pull/203041","mergeCommit":{"message":"[Security
Assistant] Abort signal fix
(elastic#203041)","sha":"b3b2c1745ac846b377d8e234526aa965196e4de9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203041","number":203041,"mergeCommit":{"message":"[Security
Assistant] Abort signal fix
(elastic#203041)","sha":"b3b2c1745ac846b377d8e234526aa965196e4de9"}}]}]
BACKPORT-->

Co-authored-by: Steph Milovic <[email protected]>
@tsullivan
[8.x] Preparation for High Contrast Mode, Core/SharedUX domains (elas…
d2a78a9 
…tic#202606) (elastic#203147)

# Backport

This will backport the following commits from `main` to `8.x`:
- [Preparation for High Contrast Mode, Core/SharedUX domains
(elastic#202606)](elastic#202606)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tim
Sullivan","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-05T15:26:41Z","message":"Preparation
for High Contrast Mode, Core/SharedUX domains (elastic#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\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- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor"],"number":202606,"url":"https://github.com/elastic/kibana/pull/202606","mergeCommit":{"message":"Preparation
for High Contrast Mode, Core/SharedUX domains (elastic#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\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- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/202606","number":202606,"mergeCommit":{"message":"Preparation
for High Contrast Mode, Core/SharedUX domains (elastic#202606)\n\n##
Summary\r\n\r\n**Reviewers: Please test the code paths affected by this
PR. See the\r\n\"Risks\" section below.**\r\n\r\nPart of work for
enabling \"high contrast mode\" in Kibana.
See\r\nhttps://github.com/elastic/issues/176219.\r\n\r\n**Background:**\r\nKibana
will soon have a user profile setting to allow users to enable\r\n\"high
contrast mode.\" This setting will activate a flag
with\r\n`<EuiProvider>` that causes EUI components to render with
higher\r\ncontrast visual elements. Consumer plugins and packages need
to be\r\nupdated selected places where `<EuiProvider>` is wrapped, to
pass the\r\n`UserProfileService` service dependency from the CoreStart
contract.\r\n\r\n**NOTE:** **EUI currently does not yet support the
high-contrast mode\r\nflag**, but support for that is expected to come
in around 2 weeks.\r\nThese first PRs are simply preparing the code by
wiring up the\r\n`UserProvideService`.\r\n\r\n### Checklist\r\n\r\nCheck
the PR satisfies following conditions. \r\n\r\nReviewers should verify
this PR satisfies this list as well.\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- [X] The PR
description includes the appropriate Release Notes section,\r\nand the
correct `release_note:*` label is applied per
the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n###
Risks\r\n\r\nDoes this PR introduce any risks? For example, consider
risks like hard\r\nto test bugs, performance regression, potential of
data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for
each identified\r\nrisk. Invite stakeholders and evaluate how to proceed
before merging.\r\n\r\n- [ ] [medium/high] The implementor of this
change did not manually test\r\nthe affected code paths and relied on
type-checking and functional tests\r\nto drive the changes. Code owners
for this PR need to manually test the\r\naffected code paths.\r\n- [ ]
[medium] The `UserProfileService` dependency comes from the\r\nCoreStart
contract. If acquiring the service causes synchronous code to\r\nbecome
asynchronous, check for race conditions or errors in rendering\r\nReact
components. Code owners for this PR need to manually test
the\r\naffected code paths.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<[email protected]>","sha":"6178e8295dc35343ab1847416a6d40432a35e4a5"}}]}]
BACKPORT-->
@jloleysens jloleysens closed this Dec 12, 2024
auto-merge was automatically disabled December 12, 2024 10:31

Pull request was closed

@jloleysens jloleysens deleted the ua/remove-custom-type-warning-logic branch December 12, 2024 10:33
@jloleysens
Copy link
Contributor Author

Superseded by #203995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rudolf rudolf Awaiting requested review from rudolf

@Bamieh Bamieh Awaiting requested review from Bamieh

@kibanamachine kibanamachine Awaiting requested review from kibanamachine

@dgieselaar dgieselaar Awaiting requested review from dgieselaar dgieselaar is a code owner

@vigneshshanmugam vigneshshanmugam Awaiting requested review from vigneshshanmugam vigneshshanmugam is a code owner

@nikitaindik nikitaindik Awaiting requested review from nikitaindik nikitaindik is a code owner automatically assigned from elastic/security-detection-rule-management

@rylnd rylnd Awaiting requested review from rylnd rylnd is a code owner automatically assigned from elastic/security-detection-engine

@gergoabraham gergoabraham Awaiting requested review from gergoabraham gergoabraham was automatically assigned from elastic/security-defend-workflows

@paul-tavares paul-tavares Awaiting requested review from paul-tavares paul-tavares was automatically assigned from elastic/security-defend-workflows

Assignees

@jloleysens jloleysens

Labels
backport:skip This commit does not require backporting Feature:Upgrade Assistant release_note:skip Skip the PR/issue when compiling release notes v8.18.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.