# Backport
This will backport the following commits from `main` to `8.12`:
- [[Ent Search] Connector client copy cleanup
(#176290)](https://github.com/elastic/kibana/pull/176290)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Liam
Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-06T17:31:55Z","message":"[Ent
Search] Connector client copy cleanup (#176290)\n\nAdditional fixes
missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The
deployment first paragraph was outdated and irrelevant to the
user\r\nworkflow\r\n- Some of step headings were
vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.13.0","v8.12.2"],"title":"[Ent
Search] Connector client copy
cleanup","number":176290,"url":"https://github.com/elastic/kibana/pull/176290","mergeCommit":{"message":"[Ent
Search] Connector client copy cleanup (#176290)\n\nAdditional fixes
missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The
deployment first paragraph was outdated and irrelevant to the
user\r\nworkflow\r\n- Some of step headings were
vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176290","number":176290,"mergeCommit":{"message":"[Ent
Search] Connector client copy cleanup (#176290)\n\nAdditional fixes
missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The
deployment first paragraph was outdated and irrelevant to the
user\r\nworkflow\r\n- Some of step headings were
vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Integrating latest translations extracted from 8.12 branch.
Skipping backports from main to target branches since the `i18n_check`
might trim unused translations that are still used in different
branches. Integration script is ran against each target branch
separately.
# Backport
This will backport the following commits from `main` to `8.12`:
- [[Fleet] adding upgrade details UPG_FAILED check to stuck in updating
(#173628)](https://github.com/elastic/kibana/pull/173628)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-21T08:06:02Z","message":"[Fleet]
adding upgrade details UPG_FAILED check to stuck in updating
(#173628)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/171419\r\n\r\nAdded upgrade
details check to restart upgrade callout when agent is\r\nstuck in
updating.\r\nChanged the copy slightly when the agent has failed upgrade
state.\r\n\r\n<img width=\"653\"
alt=\"image\"\r\nsrc=\"50061732-aa92-495b-b683-4d96114a1d5a\">\r\n\r\nExisting
copy when there is no upgrade details (stuck in updating for\r\nmore
than 2 hours):\r\n<img width=\"609\"
alt=\"image\"\r\nsrc=\"14413c4a-ce51-49fa-a217-68993c4378fd\">\r\n\r\nAdjusted
Agent list tooltip as well if upgrade details state is
failed.\r\n\r\n<img width=\"513\"
alt=\"image\"\r\nsrc=\"6836e02e-2c30-4c0a-91ea-8baddb0ccf03\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1f3d3eaaa703ddc470ebe3e2e6140cd068434f14","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.12.0","v8.13.0"],"number":173628,"url":"https://github.com/elastic/kibana/pull/173628","mergeCommit":{"message":"[Fleet]
adding upgrade details UPG_FAILED check to stuck in updating
(#173628)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/171419\r\n\r\nAdded upgrade
details check to restart upgrade callout when agent is\r\nstuck in
updating.\r\nChanged the copy slightly when the agent has failed upgrade
state.\r\n\r\n<img width=\"653\"
alt=\"image\"\r\nsrc=\"50061732-aa92-495b-b683-4d96114a1d5a\">\r\n\r\nExisting
copy when there is no upgrade details (stuck in updating for\r\nmore
than 2 hours):\r\n<img width=\"609\"
alt=\"image\"\r\nsrc=\"14413c4a-ce51-49fa-a217-68993c4378fd\">\r\n\r\nAdjusted
Agent list tooltip as well if upgrade details state is
failed.\r\n\r\n<img width=\"513\"
alt=\"image\"\r\nsrc=\"6836e02e-2c30-4c0a-91ea-8baddb0ccf03\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1f3d3eaaa703ddc470ebe3e2e6140cd068434f14"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173628","number":173628,"mergeCommit":{"message":"[Fleet]
adding upgrade details UPG_FAILED check to stuck in updating
(#173628)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/171419\r\n\r\nAdded upgrade
details check to restart upgrade callout when agent is\r\nstuck in
updating.\r\nChanged the copy slightly when the agent has failed upgrade
state.\r\n\r\n<img width=\"653\"
alt=\"image\"\r\nsrc=\"50061732-aa92-495b-b683-4d96114a1d5a\">\r\n\r\nExisting
copy when there is no upgrade details (stuck in updating for\r\nmore
than 2 hours):\r\n<img width=\"609\"
alt=\"image\"\r\nsrc=\"14413c4a-ce51-49fa-a217-68993c4378fd\">\r\n\r\nAdjusted
Agent list tooltip as well if upgrade details state is
failed.\r\n\r\n<img width=\"513\"
alt=\"image\"\r\nsrc=\"6836e02e-2c30-4c0a-91ea-8baddb0ccf03\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"1f3d3eaaa703ddc470ebe3e2e6140cd068434f14"}}]}]
BACKPORT-->
Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[Lens] Fix context formula functions
(#172710)](https://github.com/elastic/kibana/pull/172710)
<!--- Backport version: 8.9.8 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"drew.tate@elastic.co"},"sourceCommit":{"committedDate":"2023-12-19T15:32:31Z","message":"[Lens]
Fix context formula functions (#172710)\n\n## Summary\r\nFix
f5b50ffa-4a03-45ee-bc7a-2f2aca7fa3bd\r\n\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"99763dc61647c817384019f6603de7ad258eea01","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:ExpressionLanguage","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.13.0"],"number":172710,"url":"https://github.com/elastic/kibana/pull/172710","mergeCommit":{"message":"[Lens]
Fix context formula functions (#172710)\n\n## Summary\r\nFix
f5b50ffa-4a03-45ee-bc7a-2f2aca7fa3bd\r\n\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"99763dc61647c817384019f6603de7ad258eea01"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172710","number":172710,"mergeCommit":{"message":"[Lens]
Fix context formula functions (#172710)\n\n## Summary\r\nFix
f5b50ffa-4a03-45ee-bc7a-2f2aca7fa3bd\r\n\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"99763dc61647c817384019f6603de7ad258eea01"}}]}]
BACKPORT-->
# Backport
This will backport the following commits from `main` to `8.12`:
- [Update design of Prompt Editor
(#173571)](https://github.com/elastic/kibana/pull/173571)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Coen
Warmer","email":"coen.warmer@gmail.com"},"sourceCommit":{"committedDate":"2023-12-19T14:14:16Z","message":"Update
design of Prompt Editor
(#173571)","sha":"3ea5865a0ab485782ddd62562890e7ac618768bf","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.12.0","v8.13.0"],"number":173571,"url":"https://github.com/elastic/kibana/pull/173571","mergeCommit":{"message":"Update
design of Prompt Editor
(#173571)","sha":"3ea5865a0ab485782ddd62562890e7ac618768bf"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173571","number":173571,"mergeCommit":{"message":"Update
design of Prompt Editor
(#173571)","sha":"3ea5865a0ab485782ddd62562890e7ac618768bf"}}]}]
BACKPORT-->
Co-authored-by: Coen Warmer <coen.warmer@gmail.com>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[ML] Remove beta badge from ML alerting rules
(#173545)](https://github.com/elastic/kibana/pull/173545)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dima
Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2023-12-19T13:13:02Z","message":"[ML]
Remove beta badge from ML alerting rules (#173545)\n\n##
Summary\r\n\r\n- Removes the beta badge from Anomaly detection and
Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly
detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly
detection\") for consistency with the other rules in the
list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly
Detection","Feature:Alerting/RuleTypes","Team:ML","v8.12.0","v8.13.0"],"number":173545,"url":"https://github.com/elastic/kibana/pull/173545","mergeCommit":{"message":"[ML]
Remove beta badge from ML alerting rules (#173545)\n\n##
Summary\r\n\r\n- Removes the beta badge from Anomaly detection and
Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly
detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly
detection\") for consistency with the other rules in the
list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173545","number":173545,"mergeCommit":{"message":"[ML]
Remove beta badge from ML alerting rules (#173545)\n\n##
Summary\r\n\r\n- Removes the beta badge from Anomaly detection and
Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly
detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly
detection\") for consistency with the other rules in the
list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb"}}]}] BACKPORT-->
Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[SLOs] Fix cloning SLO by opening pre filled form
(#172927)](https://github.com/elastic/kibana/pull/172927)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-12-18T10:52:32Z","message":"[SLOs]
Fix cloning SLO by opening pre filled form
(#172927)","sha":"3419469e39e0bb4443267bc80fb2500629c772ba","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-management","v8.13.0"],"number":172927,"url":"https://github.com/elastic/kibana/pull/172927","mergeCommit":{"message":"[SLOs]
Fix cloning SLO by opening pre filled form
(#172927)","sha":"3419469e39e0bb4443267bc80fb2500629c772ba"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172927","number":172927,"mergeCommit":{"message":"[SLOs]
Fix cloning SLO by opening pre filled form
(#172927)","sha":"3419469e39e0bb4443267bc80fb2500629c772ba"}}]}]
BACKPORT-->
Co-authored-by: Shahzad <shahzad31comp@gmail.com>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[SLO] Rename Partition by to Group by
(#173239)](https://github.com/elastic/kibana/pull/173239)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Bena
Kansara","email":"69037875+benakansara@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-13T08:44:48Z","message":"[SLO]
Rename Partition by to Group by (#173239)\n\nResolves
https://github.com/elastic/kibana/issues/172210","sha":"43b48adbc427416e0d9bd0bc656d0265c7719869","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","auto-backport","v8.12.0","Team:obs-ux-management","v8.13.0"],"number":173239,"url":"https://github.com/elastic/kibana/pull/173239","mergeCommit":{"message":"[SLO]
Rename Partition by to Group by (#173239)\n\nResolves
https://github.com/elastic/kibana/issues/172210","sha":"43b48adbc427416e0d9bd0bc656d0265c7719869"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173239","number":173239,"mergeCommit":{"message":"[SLO]
Rename Partition by to Group by (#173239)\n\nResolves
https://github.com/elastic/kibana/issues/172210","sha":"43b48adbc427416e0d9bd0bc656d0265c7719869"}}]}]
BACKPORT-->
Co-authored-by: Bena Kansara <69037875+benakansara@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[Lens] Fixes wrong tooltip
(#172929)](https://github.com/elastic/kibana/pull/172929)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2023-12-11T07:26:54Z","message":"[Lens]
Fixes wrong tooltip (#172929)\n\n## Summary\r\n\r\nBecause the
perfection is in the details, this PR fixes a minor bug in\r\nthe inline
editing of **dataview** mode charts. The tooltip mentions\r\nES|QL while
it
shouldn't","sha":"08693ff1b73f76ed1ab352147c2e36b22e57fd49","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","v8.12.0","v8.13.0"],"number":172929,"url":"https://github.com/elastic/kibana/pull/172929","mergeCommit":{"message":"[Lens]
Fixes wrong tooltip (#172929)\n\n## Summary\r\n\r\nBecause the
perfection is in the details, this PR fixes a minor bug in\r\nthe inline
editing of **dataview** mode charts. The tooltip mentions\r\nES|QL while
it
shouldn't","sha":"08693ff1b73f76ed1ab352147c2e36b22e57fd49"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172929","number":172929,"mergeCommit":{"message":"[Lens]
Fixes wrong tooltip (#172929)\n\n## Summary\r\n\r\nBecause the
perfection is in the details, this PR fixes a minor bug in\r\nthe inline
editing of **dataview** mode charts. The tooltip mentions\r\nES|QL while
it shouldn't","sha":"08693ff1b73f76ed1ab352147c2e36b22e57fd49"}}]}]
BACKPORT-->
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [Language client getting started dedicated
(#172869)](https://github.com/elastic/kibana/pull/172869)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-08T18:48:56Z","message":"Language
client getting started dedicated (#172869)\n\n## Summary\r\n\r\nThis
adds the getting started page from Serverless Elasticsearch
to\r\nDedicated.","sha":"8b9ce1848ca59291a759396e61389a76e0d17133","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.12.0","v8.13.0"],"number":172869,"url":"https://github.com/elastic/kibana/pull/172869","mergeCommit":{"message":"Language
client getting started dedicated (#172869)\n\n## Summary\r\n\r\nThis
adds the getting started page from Serverless Elasticsearch
to\r\nDedicated.","sha":"8b9ce1848ca59291a759396e61389a76e0d17133"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172869","number":172869,"mergeCommit":{"message":"Language
client getting started dedicated (#172869)\n\n## Summary\r\n\r\nThis
adds the getting started page from Serverless Elasticsearch
to\r\nDedicated.","sha":"8b9ce1848ca59291a759396e61389a76e0d17133"}}]}]
BACKPORT-->
Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[monitoring] Revert CPU Usage rule changes
(#172913)](https://github.com/elastic/kibana/pull/172913)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Milton
Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2023-12-08T15:25:23Z","message":"[monitoring]
Revert CPU Usage rule changes (#172913)\n\nReverts
https://github.com/elastic/kibana/pull/159351\r\nRevertshttps://github.com/elastic/kibana/pull/167244\r\n\r\nDue to the many
unexpected issues that these changes introduced we've\r\ndecided to
revert these changes until we have better solutions for the\r\nproblems
we've learnt about.\r\n\r\nProblems:\r\n- Gaps in data cause alerts to
fire (see next point)\r\n- Normal CPU rescaling causes alerts to
fire\r\nhttps://github.com/elastic/kibana/issues/160905\r\n- Any error
fires an alert (since there is no other way to inform the\r\nuser about
the problems faced by the rule executor)\r\n- Many assumptions about
cgroups only being for container users are\r\nwrong\r\n\r\nTo address
some of these issues we also need more functionality in the\r\nalerting
framework to be able to register secondary actions so that we\r\nmay
trigger non-oncall workflows for when a rule faces issues
with\r\nevaluating the stats.\r\n\r\nOriginal issue
https://github.com/elastic/kibana/issues/116128","sha":"55bc6d505977e8831633cc76e0f46b2ca66ef559","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","v8.12.0","v8.13.0"],"number":172913,"url":"https://github.com/elastic/kibana/pull/172913","mergeCommit":{"message":"[monitoring]
Revert CPU Usage rule changes (#172913)\n\nReverts
https://github.com/elastic/kibana/pull/159351\r\nRevertshttps://github.com/elastic/kibana/pull/167244\r\n\r\nDue to the many
unexpected issues that these changes introduced we've\r\ndecided to
revert these changes until we have better solutions for the\r\nproblems
we've learnt about.\r\n\r\nProblems:\r\n- Gaps in data cause alerts to
fire (see next point)\r\n- Normal CPU rescaling causes alerts to
fire\r\nhttps://github.com/elastic/kibana/issues/160905\r\n- Any error
fires an alert (since there is no other way to inform the\r\nuser about
the problems faced by the rule executor)\r\n- Many assumptions about
cgroups only being for container users are\r\nwrong\r\n\r\nTo address
some of these issues we also need more functionality in the\r\nalerting
framework to be able to register secondary actions so that we\r\nmay
trigger non-oncall workflows for when a rule faces issues
with\r\nevaluating the stats.\r\n\r\nOriginal issue
https://github.com/elastic/kibana/issues/116128","sha":"55bc6d505977e8831633cc76e0f46b2ca66ef559"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172913","number":172913,"mergeCommit":{"message":"[monitoring]
Revert CPU Usage rule changes (#172913)\n\nReverts
https://github.com/elastic/kibana/pull/159351\r\nRevertshttps://github.com/elastic/kibana/pull/167244\r\n\r\nDue to the many
unexpected issues that these changes introduced we've\r\ndecided to
revert these changes until we have better solutions for the\r\nproblems
we've learnt about.\r\n\r\nProblems:\r\n- Gaps in data cause alerts to
fire (see next point)\r\n- Normal CPU rescaling causes alerts to
fire\r\nhttps://github.com/elastic/kibana/issues/160905\r\n- Any error
fires an alert (since there is no other way to inform the\r\nuser about
the problems faced by the rule executor)\r\n- Many assumptions about
cgroups only being for container users are\r\nwrong\r\n\r\nTo address
some of these issues we also need more functionality in the\r\nalerting
framework to be able to register secondary actions so that we\r\nmay
trigger non-oncall workflows for when a rule faces issues
with\r\nevaluating the stats.\r\n\r\nOriginal issue
https://github.com/elastic/kibana/issues/116128","sha":"55bc6d505977e8831633cc76e0f46b2ca66ef559"}}]}]
BACKPORT-->
Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[Obs AI Assistant] Perform functions etc on the server
(#172590)](https://github.com/elastic/kibana/pull/172590)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Dario
Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2023-12-07T14:18:41Z","message":"[Obs
AI Assistant] Perform functions etc on the server
(#172590)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56b36b9042b42c702a57568f1612af3d433d2df1","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:APM","v8.12.0","apm:review","v8.13.0"],"number":172590,"url":"https://github.com/elastic/kibana/pull/172590","mergeCommit":{"message":"[Obs
AI Assistant] Perform functions etc on the server
(#172590)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56b36b9042b42c702a57568f1612af3d433d2df1"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172590","number":172590,"mergeCommit":{"message":"[Obs
AI Assistant] Perform functions etc on the server
(#172590)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56b36b9042b42c702a57568f1612af3d433d2df1"}}]}]
BACKPORT-->
Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
# Backport
This will backport the following commits from `main` to `8.12`:
- [[Cloud Security] Remove manual-manual from azure integration
(#172669)](https://github.com/elastic/kibana/pull/172669)
<!--- Backport version: 8.9.7 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Jordan","email":"51442161+JordanSh@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-12-07T09:12:51Z","message":"[Cloud
Security] Remove manual-manual from azure integration
(#172669)","sha":"ef5305d47f3daaefe6f2bee858d94770a4a86f71","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud
Security","v8.12.0","v8.13.0"],"number":172669,"url":"https://github.com/elastic/kibana/pull/172669","mergeCommit":{"message":"[Cloud
Security] Remove manual-manual from azure integration
(#172669)","sha":"ef5305d47f3daaefe6f2bee858d94770a4a86f71"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172669","number":172669,"mergeCommit":{"message":"[Cloud
Security] Remove manual-manual from azure integration
(#172669)","sha":"ef5305d47f3daaefe6f2bee858d94770a4a86f71"}}]}]
BACKPORT-->
Co-authored-by: Jordan <51442161+JordanSh@users.noreply.github.com>
## Summary
This PR adds a bunch of plugins to help manage AI Assistant Management
settings.
It offers a 'selection' plugin inside Stack Management where a user can
select which AI Assistant she wants to manage.
The Security team can hook into this one, so settings for both AI
Assistants can be accessed from inside one place inside Stack
Management.
This PR also adds the plugin to manage settings for the AI Assistant for
Observability, including Knowledge Base management. This plugin is
available both in Stack Management (stateful) and Project Settings
(serverless).
## What it looks like
51392ec5-05c9-4947-9bf2-810d8d0b7525
## Detailed
1. **Adds a Stack Management plugin**
(`/src/plugins/ai_assistant_management/selection`). Its primary function
is to render a selection screen to help users navigate to the settings
plugin for the AI Assistant for a specific solution. This plugin is
displayed in Stack Management, which is only available in stateful
versions of Kibana.
2. **Adds a AI Assistant for Observability Settings plugin**
(`/src/plugins/ai_assistant_management/observability`). This plugin
allows management of specific Observability AI Assistant settings. It is
available in stateful versions of Kibana (via the aforementioned Stack
Management plugin) or in serverless versions via Project Management.
3. **Knowledge Base management for Observability AI Assistant**: The AI
Assistant for Observability Settings plugin has a Knowledge Base tab,
which allows users to add / read / update / delete and bulk import
entries into the Knowledge Base of the Observability AI Assistant.
4. **Moving of KB endpoints in Observability AI Assistant plugin**: KB
endpoints and functions were located in the same folder. As this PR adds
new endpoints for the KB for CRUD operations, it also moves the existing
ones from the function folder into a dedicated one so there's a clearer
distinction between kb and functions.
5. **Adding of GenAI Connector inside Chat Flyout**: If the user has
admin rights, it is possible to set up a GenAI connector from within the
Observability AI Assistant Chat Flyout. This provides a faster and more
seamless onboarding experience. If the user does not, she will be
redirected to the Settings page.
## Bug fixes
* Fixes chat item styling issues (padding, background color).
## How to test
* Check if the Stack Management plugin works on stateful
* Check if the AI Assistant Settings plugin works on stateful +
serverless
* Check if CRUD operations on KB work
* Check if searching on KB entries work
* Check if its possible to navigate to KB tab directly
(`app/management/kibana/aiAssistantManagementObservability?tab=knowledge_base`)
## Todo
- [x] Add sorting to getEntries
- [x] Add params for tab routing
- [x] Add unit tests
- [ ] Add API tests
- [ ] Add fallback for already indexed entries when searching
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR updates the callouts in the Endpoint Policy where we mention the
detection rules associated with Endpoint. This makes it more current and
provides a docs link with more details.
- Banner is added to the top of the Policy page
- Individual banners are removed from the individual cards
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
b749781c-1941-40d5-8dc8-094659fba9e5
<img width="674" alt="Screenshot 2023-12-05 at 10 31 10"
src="dc0dc39e-6ac1-47e6-b608-ec6667be251b">
* Remove the `firstLastSeen` call from managed user data because it can
be inferred from the event timestamp.
* Updated the managed data API to return Okta and Azure data.
* Create a Flyout asset document details panel
* Create a cell action that add/remove fields from the asset table
* Persist selected field on the redux store
* Persist the selected fields on local storage
* [] TODO update query match to use e-mail field
### How to test it?
* Enable the experimental flag
`xpack.securitySolution.enableExperimental: ['newUserDetailsFlyout']`
* Start an elastic cluster with fleet and elastic agent
* Follow this steps to setup a cluster with elastic-package
* Install https://github.com/elastic/elastic-package
* `elastic-package stack up -vd --version 8.12.0-SNAPSHOT`
* connect your local kibana instance to the cluster ES instance
* configured `server.port`, `elasticsearch.hosts`,
`elasticsearch.ssl.certificateAuthorities`,
`elasticsearch.serviceAccountToken`
* Install Okta and Entra integrations (ask @machadoum for credentials)
* Create a rule that generates alerts for every event
* Go to the alerts table and click on the username to open the flyout
**Tip:** You can open your Docker application and explore the files to
copy the token and the certificate.
<img width="1420" alt="Screenshot 2023-12-04 at 16 29 53"
src="60032e34-6f50-4316-ad88-2a13109a5622">
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [x] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
## Summary
Closes#136391
Uses a description of the anomaly for the alert message for anomaly
detection alerting rules with the `record` result type. This messages is
used for example in the `Reason` field in the alert table and details
flyout.
<img width="753" alt="image"
src="072fe833-204b-4d38-bd3d-50d00015a43f">
### Checklist
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
## Summary
Add a mute/unmute action component to be used in alerts table row
actions, move all common alerts table row actions to triggersActionsUI
and re-export them for consumers to compose their table actions.
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
---------
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This PR:
* extracts `enterprise_search` index documents component to common
package.
* Uses EUI pagination, converting Elasticsearch`from` & `size` to EUI
pagination standard for documents list
### Screen Recording
f585d9cc-f92c-44f4-aead-23c75c107a0f
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Relates https://github.com/elastic/fleet-server/issues/3116
Relates https://github.com/elastic/kibana/issues/104986
Reading latest output health state from
`logs-fleet_server.output_health-default` data stream by output id, and
displaying error state on UI - Edit Output flyout.
Steps to verify:
- enable feature flag `remoteESOutput`
- add `remote_elasticsearch` output, can be a non-existent host for this
test
- add the output as monitoring output of an agent policy
- run fleet-server with the changes
[here](https://github.com/elastic/fleet-server/issues/3116)
- enroll an agent
- wait until fleet-server starts reporting degraded state in the output
health data stream
- open edit output flyout on UI and verify that the error state is
visible
- when the connection is back again (update host to a valid one, or
remote es was temporarily down), the error state goes away
<img width="568" alt="image"
src="46d0cf95-6aa4-4f7c-8608-4362ada4eb6c">
The UI was suggested in the design doc:
https://docs.google.com/document/d/19D0bX7oURf0yms4qemfqDyisw_IYB-OVw4oU-t4lf18/edit#bookmark=id.595r8l91kaq8
### Notes/suggestions:
- We might want to add the output state to the output list as well
(maybe as badges like agent health?) as it's not too visible in the
flyout (have to scroll down).
- Also the error state will be reported earliest when an agent is
enrolled and fleet-server can't create api key, so not immediately when
the output is added. It would be good to show the time of the last state
(e.g. how we display on agents last checkin x minutes ago)
- I think it would be beneficial to display the healthy state too.
Added badges to output list:
<img width="1233" alt="image"
src="07ff06ec-b778-4420-975b-b46a0a18c7cc">
Added healthy state UI to Edit output:
<img width="627" alt="image"
src="4222d849-c957-41d7-9606-b58493264115">
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
## Summary
[Test
env](https://p.elstc.co/paste/Y83spa-G#0BRN87aMZxLJfbVok3W0U-7D/sss9OGfH9IIqw4oHL6)
1. When landing on the page the first time, all the tasks are collapsed.
If visited before, it keeps the last expanded task.
2. When clicking on the task, the url has the task id appended as
`#{taskId}`
3. When visiting the page, if url has `#{taskId}`, the relevant task
should be expanded. If no `#{taskId}` in the url, it expands the last
expanded task according to **local storage**.
4. Tasks completion are checked automatically, users are not able to
undo any tasks unless the **local storage** is cleanned.
5. Task completion criteria:
https://github.com/elastic/security-team/issues/8032 `Onboarding tasks
with success criteria`:
- [x] "create first project" -> ~unexpandable~, already complete when
user arrives
- [x] "watch overview video" -> user clicks to expand (success == users
opens section/clicks "Start")
- [x] "add integrations" -> users clicks to expand and goes to
integration page (success == query fleet to confirm an agent exists with
an integration) `Update we use **indicesExist** from sourcerer to
replace fleet api as some performance issue found when running locally,
not sure how it will affect the production.`
- [x] - after user clicks "Start" and expands, if success criteria is
already met (e.g. agent is installed with an integration), notify user
agent is installed and mark step as complete.
- [x] "view and analyze dashboards" -> users clicks to expand (success
== click action)
- [x] "enable prebuilt rules" -> clicks to expand (success == at least
one rule **enabled**, show enabled rules like integrations above)
- [x] "view alerts" -> user clicks to expand (success == click action)
6. Design:
https://github.com/elastic/kibana/pull/171078#issuecomment-1828562066https://github.com/elastic/kibana/issues/170643
<img width="2556" alt="Screenshot 2023-12-04 at 16 47 48"
src="c98eb2f5-6b31-43f9-9db5-0829e78bb3c2">
<img width="2548" alt="Screenshot 2023-12-04 at 16 29 50"
src="41cb329c-417f-4b95-b19b-67663380a9a3">
<img width="2546" alt="Screenshot 2023-12-04 at 16 30 47"
src="daa3cf3b-9d2e-4c69-83f1-fcc4817f6b8f">
- Integration added:
1f9aefe4-c20b-4d46-b8b0-1aabf8bd7091
- Integration not added:
8b0d6c6b-0bae-4857-aeb1-715f9f4080b8
29432bfe-f270-4e5e-a1c9-86ad806ea5bb
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>
## Summary
Partially resolves: https://github.com/elastic/kibana/issues/164255,
this is 2/3 of the scoped query changes.
Maintenance window scoped query frontend changes. Adds the ability to
add and edit scoped query for maintenance windows. Due to limitations
with the alerts search bar and each solution fetches AAD fields, we only
allow users to associate scoped query with 1 category (manangement,
o11y, or security solution). The intended usage in this case is for the
user to create multiple maintenance windows if they wish to apply scoped
queries to multiple solutions.
### To test:
go to
`x-pack/plugins/alerting/public/pages/maintenance_windows/constants.ts`
and set `IS_SCOPED_QUERY_ENABLED` to `true`
### Scoped query off, multiple category allowed:
### Scoped query on, multiple category disallowed:
### Checklist
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
In the "Add inference pipeline" flyout, change the existing pipeline
selector dropdown to a selection list with search. Also re-organize the
option layout to more closely match the layout implemented for ML
pipeline cards in #172209.
- Removes old flamegraph code replacing it with the ES Flamegraph API
- Creates new user settings
- Adds a feature flag to use the kibana CO2/Cost calculations instead of
the new version
- Reads CO2 and Cost from /Stacktraces and /Flamegraph APIs
Where do we show the CO2 and Cost values?
- Flamegraph toolip
- Flamegraph Frame information flyout
- Diff Flamegraph Summary
- Functions table
- Function information flyout
- Diff Functions Summary
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Reorganizes the ML Pipeline card on the Indices Pipelines view.
Note: Displaying source fields within this card is out of scope of this
PR.
Before:
<img width="506" alt="pipeline-card-before"
src="9b41e4c0-cb19-4bc8-b33a-31c85797b6e2">
After:
<img width="517" alt="image"
src="2a15df6c-3564-4957-a847-cf1859c8bd65">
Example of multiple pipeline cards:
<img width="520" alt="image"
src="ff6dfc1a-c45c-4bd3-b456-c633b3794175">
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Summarize your PR. If it involves visual changes include a screenshot or
gif.
- Add benchmarks to Compliance Dashboard API.
- Add `score_by_benchmark_id` to the Benchmark Scores Index this will
show posture stats for each benchmark id
- Add benchmark aggregation query using benchmark id and version
- Add BWC API versioning
- STATS API V1 should show clusters
- STATS API V2 should show benchmarks
- Add unit tests
- Added integration tests with API versioning test cases.
To test PR with API versioning, in Kibana client -
`x-pack/plugins/cloud_security_posture/public/common/api/use_stats_api.ts`
- Change version value to 1 to see clusters
```
http.get<ComplianceDashboardData>(getStatsRoute(CSPM_POLICY_TEMPLATE), { version: '1' }),
```
- Change version value to 2 to see versions
```
http.get<ComplianceDashboardData>(getStatsRoute(CSPM_POLICY_TEMPLATE), { version: '2' })
```
<img width="1721" alt="image"
src="7fb53dec-c405-49e5-aa22-7788b4d1d5c0">
Uploading Untitled 2.mov…
## Summary
This PR moves formulas and charts developed for the Hosts View and Asset
Details into the Inventory Models existing structure.
### `metrics_data_access` plugin
This is where the inventory models are found. All charts and formulas
have been moved from `infra` plugin into this plugin Most of the changes
are just about that. I've refactored a few things to help with the
reusability of these charts/dashboards
### `infra` plugin
Changes made here were a consequence of the refactors in the
charts/dashboards config.
### `@kbn/lens-embaddable-utils` package
Just added new types
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Consolidates UI elements and backend code to create/delete data views
and destination indices related to transforms and data frame analytics.
We ended up with two different approaches for creating data views in the
wizards for transforms and data frame analytics, the original reason was
we were not aware of the `allowNoIndex: true` setting and worked around
that in different ways.
This PR aligns UI workflows and moves related code to a new package
`@kbn/ml-data-view-utils` for data views and
`@kbn/ml-creation-wizard-utils` for the destination index form. The
latter might be used for other shared components across wizard..
In Data Frame Analytics, the checkbox to create a data view was removed
from the last "Create" step, instead the option to create a data view
was moved to the "Details" step.
In Transforms, the UI component to create the destination index was
brought over from DFA where there is a switch option to automatically
use the job ID as the name for the destination index by default.
Split Configure step’s components in pipeline creation into two tabs:
- Create new: pipeline name, model selection
- Use existing: pipeline selection
Keep the split components' content as-is, they are out of scope for this
task.
Remove the left hand side panels (“Create or select a pipeline”, “Select
a trained ML Model” and blurbs underneath), and make the tab full width.
Also remove the ELSER text expansion callout from the flyout.
## Summary
This amends the Getting Started page in Search and turns it into the
Search Hub.
<img width="1907" alt="Screenshot 2023-11-27 at 19 14 05"
src="0634d0de-4d6c-43d1-ac16-7d6ad81b0071">
<img width="1385" alt="Screenshot 2023-11-27 at 19 14 13"
src="3fdb40dd-7984-48d3-a1f2-2b21c42fe109">
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
