mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
2504 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
|
a67b352c42
|
[8.16] fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831) (#218271)
# Backport This will backport the following commits from `main` to `8.16`: - [fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)](https://github.com/elastic/kibana/pull/217831) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T13:38:48Z","message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","Feature:Anomaly Detection","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement","number":217831,"url":"https://github.com/elastic/kibana/pull/217831","mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217831","number":217831,"mergeCommit":{"message":"fix: [Analytics:MachineLearning:AnomalyDetection:Jobs page] Edit model snapshot flyout missing title from announcement (#217831)\n\nCloses: #216147\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n\n1. Added` aria-labelledby={flyoutTitleId} `for mentioned places","sha":"d47e77627ac594883969066205a0888bb5034efb"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
cf4d918a62
|
[8.16] fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666) (#218256)
# Backport This will backport the following commits from `main` to `8.16`: - [fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)](https://github.com/elastic/kibana/pull/217666) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-04-15T12:17:20Z","message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility",":ml","release_note:skip","Feature:Data Frame Analytics","backport:prev-major","v9.1.0"],"title":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement","number":217666,"url":"https://github.com/elastic/kibana/pull/217666","mergeCommit":{"message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/217666","number":217666,"mergeCommit":{"message":"fix: [ML] Data Frame Analytics: Analytics selection flyout missing title from announcement (#217666)\n\nCloses: https://github.com/elastic/kibana/issues/217511\n\n**Description**\nDialog modal, flyout, field visible title should be announced for the\nusers, especially using assistive technology to know what dialog modal,\nflyout opened, what field is active and what is needed to enter in it.\n\n**Changes made:**\n1. Set correct value for `aria-labelledby` attr.","sha":"4399248cf013552902af726e61b0da5b2ed23b2e"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
30f212a3e4
|
[8.16] Update @elastic/ml-ui dependencies (main) (#204210) (#207798)
# Backport This will backport the following commits from `main` to `8.16`: - [Update @elastic/ml-ui dependencies (main) (#204210)](https://github.com/elastic/kibana/pull/204210) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
030bac4924
|
[8.16] [APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651) (#207224)
# Backport This will backport the following commits from `main` to `8.16`: - [[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)](https://github.com/elastic/kibana/pull/206651) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T13:36:22Z","message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5","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","Team:obs-ux-infra_services"],"title":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues","number":206651,"url":"https://github.com/elastic/kibana/pull/206651","mergeCommit":{"message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5"}},"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/206651","number":206651,"mergeCommit":{"message":"[APM][ML] Update cytoscape with new index.d.ts def, fix typing issues (#206651)\n\n## Summary\r\n\r\n`cytoscape` released yet another semver breaking change, affecting\r\ntyping once more in a couple of places. They now have their own\r\n`index.d.ts` file for Typescript support, but this causes some issues as\r\nthey don't always have the same type name as the `@types` version. Had\r\nto fix in a couple of places, both in APM and in ML codebases.\r\n\r\nSupersedes #206498\r\n\r\n## How to test\r\n\r\n* This PR passes the CI with no typing issues, or failed tests\r\n* Going to APM or ML pages with cytoscape being loaded shows no\r\nregressions.","sha":"a0bdc1968456f0db02a18becefdc19bdcc5469f5"}}]}] BACKPORT--> |
||
|
2e63133937
|
[8.16] [ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726) (#205854)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)](https://github.com/elastic/kibana/pull/205726) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2025-01-08T09:16:17Z","message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69","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","Team:obs-ux-infra_services"],"title":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions","number":205726,"url":"https://github.com/elastic/kibana/pull/205726","mergeCommit":{"message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69"}},"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/205726","number":205726,"mergeCommit":{"message":"[ML][APM] Fix Cytoscape listener typing, Update Cytoscape versions (#205726)\n\n## Summary\r\n\r\nUpdates Cytoscape to newer versions, requiring one change with some\r\n`removeListener` usage no longer being valid typing.\r\n\r\nSupersedes #205444\r\n\r\n## How to test\r\n\r\n- Passes CI with no type errors or failed CI jobs for ML\r\n- Job Map or wherever cytoscape is being used on ML doesn't leak event\r\nlisteners.\r\n- Usages in APM also do not break.","sha":"7363f03d81835f70f39caa27e7096b8a0361ae69"}}]}] BACKPORT--> |
||
|
7e0ea54b45
|
[8.16] [ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712) (#202742)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)](https://github.com/elastic/kibana/pull/202712) <!--- Backport version: 9.4.3 --> ### 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":"2024-12-03T14:29:28Z","message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\r\n\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","sha":"ded18eeaac82787ea57d4991bad28b983d43ad0c","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models","number":202712,"url":"https://github.com/elastic/kibana/pull/202712","mergeCommit":{"message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\r\n\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","sha":"ded18eeaac82787ea57d4991bad28b983d43ad0c"}},"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/202712","number":202712,"mergeCommit":{"message":"[ML] Trained Models: Fixes spaces sync to retrieve 10000 models (#202712)\n\n## Summary\r\n\r\nThe default page size for the /trained_models API is 100. As a result,\r\nthe spaces sync task only fetched the first 100 models, leaving the rest\r\nunassigned to spaces and therefore invisible in the ML UI.\r\n\r\nThis PR increases the page size to 10,000 to ensure all models are\r\nproperly assigned to Kibana spaces.\r\n\r\n### Checklist\r\n\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","sha":"ded18eeaac82787ea57d4991bad28b983d43ad0c"}},{"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.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
2e1ed36c0a
|
[8.16] [ML] Trained Models: Show deployment stats for unallocated deployments (#202005) (#202166)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)](https://github.com/elastic/kibana/pull/202005) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-28T13:22:31Z","message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","ci:cloud-deploy","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Models: Show deployment stats for unallocated deployments ","number":202005,"url":"https://github.com/elastic/kibana/pull/202005","mergeCommit":{"message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0"}},"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/202005","number":202005,"mergeCommit":{"message":"[ML] Trained Models: Show deployment stats for unallocated deployments (#202005)\n\n## Summary\r\n\r\nFixes #201930 \r\n\r\nShow deployment on the Deployent stats table even if it hasn't been\r\nallocated to any node yet.\r\n\r\n\r\n<img width=\"875\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/858041fd-16d4-44f3-8d13-1ad45550452e\">","sha":"c06adbc8ec55cb211aba6a154f8d740b25c2b9c0"}},{"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.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
e15914eb44
|
[8.16] [ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes (#201256) (#201746)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes (#201256)](https://github.com/elastic/kibana/pull/201256) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-26T10:33:04Z","message":"[ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes (#201256)\n\n## Summary\r\n\r\nDuring my testing, I used the current user with all required privileges\r\nbut failed to notice that, after switching to the internal`\r\nkibana_system` user, it lacked the manage_autoscaling privilege required\r\nfor the `GET /_autoscaling/policy` API.\r\n\r\nAs a result, the `isMlAutoscalingEnabled` flag, which we rely on in the\r\nStart Deployment modal, was always set to false. This caused a bug in\r\nscenarios with zero active ML nodes, where falling back to deriving\r\navailable processors from ML limits was not possible.\r\n\r\n\r\nYou can check the created deployment, it correctly identifies ML\r\nautoscaling:\r\n\r\n<img width=\"670\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ff1f835e-2b90-4b73-bea8-a49da8846fbd\">\r\n\r\n\r\nAlso fixes restoring vCPU levels from the API deployment params.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \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":"9827a07b5891d643a61a53e09350ff6e4ab25889","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","ci:cloud-deploy","ci:cloud-redeploy","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes ","number":201256,"url":"https://github.com/elastic/kibana/pull/201256","mergeCommit":{"message":"[ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes (#201256)\n\n## Summary\r\n\r\nDuring my testing, I used the current user with all required privileges\r\nbut failed to notice that, after switching to the internal`\r\nkibana_system` user, it lacked the manage_autoscaling privilege required\r\nfor the `GET /_autoscaling/policy` API.\r\n\r\nAs a result, the `isMlAutoscalingEnabled` flag, which we rely on in the\r\nStart Deployment modal, was always set to false. This caused a bug in\r\nscenarios with zero active ML nodes, where falling back to deriving\r\navailable processors from ML limits was not possible.\r\n\r\n\r\nYou can check the created deployment, it correctly identifies ML\r\nautoscaling:\r\n\r\n<img width=\"670\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ff1f835e-2b90-4b73-bea8-a49da8846fbd\">\r\n\r\n\r\nAlso fixes restoring vCPU levels from the API deployment params.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \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":"9827a07b5891d643a61a53e09350ff6e4ab25889"}},"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/201256","number":201256,"mergeCommit":{"message":"[ML] Trained Model: Fix start deployment with ML autoscaling and 0 active nodes (#201256)\n\n## Summary\r\n\r\nDuring my testing, I used the current user with all required privileges\r\nbut failed to notice that, after switching to the internal`\r\nkibana_system` user, it lacked the manage_autoscaling privilege required\r\nfor the `GET /_autoscaling/policy` API.\r\n\r\nAs a result, the `isMlAutoscalingEnabled` flag, which we rely on in the\r\nStart Deployment modal, was always set to false. This caused a bug in\r\nscenarios with zero active ML nodes, where falling back to deriving\r\navailable processors from ML limits was not possible.\r\n\r\n\r\nYou can check the created deployment, it correctly identifies ML\r\nautoscaling:\r\n\r\n<img width=\"670\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/ff1f835e-2b90-4b73-bea8-a49da8846fbd\">\r\n\r\n\r\nAlso fixes restoring vCPU levels from the API deployment params.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \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":"9827a07b5891d643a61a53e09350ff6e4ab25889"}},{"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.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
e76d4830df
|
[8.16] [ML] Trained Models: fix NaN in a progress bar during the download task initialization (#201221) (#201341)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained Models: fix `NaN` in a progress bar during the download task initialization (#201221)](https://github.com/elastic/kibana/pull/201221) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-22T10:26:56Z","message":"[ML] Trained Models: fix `NaN` in a progress bar during the download task initialization (#201221)\n\n## Summary\r\n\r\nWhen we request a status of the download task right after initializing a\r\ndownload, `total_parts` might be returned with a `0` value, hence\r\ndividing by 0 for the progress bar causing in `NaN%` value rendered.\r\nThis PR adds a fallback to `-1` for that, to make sure we render 0%.\r\n\r\n### Checklist\r\n\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","sha":"639c9b7505020baf5dc5d31122d8924b301a77fc","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","backport:version","v8.17.0","v8.18.0","v8.16.2"],"title":"[ML] Trained Models: fix `NaN` in a progress bar during the download task initialization ","number":201221,"url":"https://github.com/elastic/kibana/pull/201221","mergeCommit":{"message":"[ML] Trained Models: fix `NaN` in a progress bar during the download task initialization (#201221)\n\n## Summary\r\n\r\nWhen we request a status of the download task right after initializing a\r\ndownload, `total_parts` might be returned with a `0` value, hence\r\ndividing by 0 for the progress bar causing in `NaN%` value rendered.\r\nThis PR adds a fallback to `-1` for that, to make sure we render 0%.\r\n\r\n### Checklist\r\n\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","sha":"639c9b7505020baf5dc5d31122d8924b301a77fc"}},"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/201221","number":201221,"mergeCommit":{"message":"[ML] Trained Models: fix `NaN` in a progress bar during the download task initialization (#201221)\n\n## Summary\r\n\r\nWhen we request a status of the download task right after initializing a\r\ndownload, `total_parts` might be returned with a `0` value, hence\r\ndividing by 0 for the progress bar causing in `NaN%` value rendered.\r\nThis PR adds a fallback to `-1` for that, to make sure we render 0%.\r\n\r\n### Checklist\r\n\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","sha":"639c9b7505020baf5dc5d31122d8924b301a77fc"}},{"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.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
d2fc28cf92
|
[8.16] [ML] Single Metric Viewer embeddable: fix job refetch on error (#199726) (#200766)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Single Metric Viewer embeddable: fix job refetch on error (#199726)](https://github.com/elastic/kibana/pull/199726) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2024-11-19T15:57:56Z","message":"[ML] Single Metric Viewer embeddable: fix job refetch on error (#199726)\n\n## Summary\r\n\r\nThis PR ensures that the job fetch is not reattempted continuously when\r\nerrors are encountered.\r\n\r\nTo test, add a Single Metric Viewer panel to a dashboard, then delete\r\nthe job the panel depends on. You can then refresh the browser and see\r\nthe error message about the job not being found.\r\n\r\nError panel for generic error and for no known job error: \r\n<img width=\"1308\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6d6d6972-ac1a-479c-a5dc-8d770026ca4e\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ddf324a9a055bf9ab5a6ba3e9a5f7c36d1e7f9ae","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v9.0.0","Feature:Embeddables","backport:version","v8.17.0","v8.16.1"],"title":"[ML] Single Metric Viewer embeddable: fix job refetch on error","number":199726,"url":"https://github.com/elastic/kibana/pull/199726","mergeCommit":{"message":"[ML] Single Metric Viewer embeddable: fix job refetch on error (#199726)\n\n## Summary\r\n\r\nThis PR ensures that the job fetch is not reattempted continuously when\r\nerrors are encountered.\r\n\r\nTo test, add a Single Metric Viewer panel to a dashboard, then delete\r\nthe job the panel depends on. You can then refresh the browser and see\r\nthe error message about the job not being found.\r\n\r\nError panel for generic error and for no known job error: \r\n<img width=\"1308\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6d6d6972-ac1a-479c-a5dc-8d770026ca4e\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ddf324a9a055bf9ab5a6ba3e9a5f7c36d1e7f9ae"}},"sourceBranch":"main","suggestedTargetBranches":["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/199726","number":199726,"mergeCommit":{"message":"[ML] Single Metric Viewer embeddable: fix job refetch on error (#199726)\n\n## Summary\r\n\r\nThis PR ensures that the job fetch is not reattempted continuously when\r\nerrors are encountered.\r\n\r\nTo test, add a Single Metric Viewer panel to a dashboard, then delete\r\nthe job the panel depends on. You can then refresh the browser and see\r\nthe error message about the job not being found.\r\n\r\nError panel for generic error and for no known job error: \r\n<img width=\"1308\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6d6d6972-ac1a-479c-a5dc-8d770026ca4e\">\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ddf324a9a055bf9ab5a6ba3e9a5f7c36d1e7f9ae"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co> |
||
|
6d6852dcd9
|
[8.16] [ML] Fix Trained model deletion with expanded row (#198530) (#198567)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Fix Trained model deletion with expanded row (#198530)](https://github.com/elastic/kibana/pull/198530) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-31T15:33:17Z","message":"[ML] Fix Trained model deletion with expanded row (#198530)\n\n## Summary\r\n\r\nFixes #198408.\r\n\r\nFixes trained model item deletion with expanded row.\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":"bd21496b3c0af2167918bd385bd259b05c8e765d","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Team:ML","v8.16.0","backport:version","v8.17.0"],"title":"[ML] Fix Trained model deletion with expanded row","number":198530,"url":"https://github.com/elastic/kibana/pull/198530","mergeCommit":{"message":"[ML] Fix Trained model deletion with expanded row (#198530)\n\n## Summary\r\n\r\nFixes #198408.\r\n\r\nFixes trained model item deletion with expanded row.\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":"bd21496b3c0af2167918bd385bd259b05c8e765d"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198530","number":198530,"mergeCommit":{"message":"[ML] Fix Trained model deletion with expanded row (#198530)\n\n## Summary\r\n\r\nFixes #198408.\r\n\r\nFixes trained model item deletion with expanded row.\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":"bd21496b3c0af2167918bd385bd259b05c8e765d"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
ee3af60985
|
[8.16] [ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group (#198256) (#198513)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group (#198256)](https://github.com/elastic/kibana/pull/198256) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-31T11:56:50Z","message":"[ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group (#198256)\n\n## Summary\r\n\r\nFix for: [#196509](https://github.com/elastic/kibana/issues/196509)\r\n\r\nAfter fix:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/9d731676-fd47-41fe-8843-8b8e6c6e153d","sha":"9eb8b885148ba8fb5f22a1c64c02452eba5dfca9","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v9.0.0","Team:ML","v8.16.0","backport:version","v8.17.0"],"title":"[ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group","number":198256,"url":"https://github.com/elastic/kibana/pull/198256","mergeCommit":{"message":"[ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group (#198256)\n\n## Summary\r\n\r\nFix for: [#196509](https://github.com/elastic/kibana/issues/196509)\r\n\r\nAfter fix:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/9d731676-fd47-41fe-8843-8b8e6c6e153d","sha":"9eb8b885148ba8fb5f22a1c64c02452eba5dfca9"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198256","number":198256,"mergeCommit":{"message":"[ML] Fixes link to anomaly explorer from anomaly embeddables when viewing by job group (#198256)\n\n## Summary\r\n\r\nFix for: [#196509](https://github.com/elastic/kibana/issues/196509)\r\n\r\nAfter fix:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/9d731676-fd47-41fe-8843-8b8e6c6e153d","sha":"9eb8b885148ba8fb5f22a1c64c02452eba5dfca9"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
318831e20a
|
[8.16] [ML] Fix overall bucket request for large number of job IDs (#198292) (#198415)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Fix overall bucket request for large number of job IDs (#198292)](https://github.com/elastic/kibana/pull/198292) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-30T17:30:16Z","message":"[ML] Fix overall bucket request for large number of job IDs (#198292)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190591\r\n\r\nAdds chunking for `over_buckets` request to prevent exceeding the\r\nrequest length URL.\r\n\r\n### Checklist\r\n\r\n\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","sha":"fa0f397a4269a37370d2101a8c5ece03ad0117bd","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Fix overall bucket request for large number of job IDs","number":198292,"url":"https://github.com/elastic/kibana/pull/198292","mergeCommit":{"message":"[ML] Fix overall bucket request for large number of job IDs (#198292)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190591\r\n\r\nAdds chunking for `over_buckets` request to prevent exceeding the\r\nrequest length URL.\r\n\r\n### Checklist\r\n\r\n\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","sha":"fa0f397a4269a37370d2101a8c5ece03ad0117bd"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198292","number":198292,"mergeCommit":{"message":"[ML] Fix overall bucket request for large number of job IDs (#198292)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/190591\r\n\r\nAdds chunking for `over_buckets` request to prevent exceeding the\r\nrequest length URL.\r\n\r\n### Checklist\r\n\r\n\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","sha":"fa0f397a4269a37370d2101a8c5ece03ad0117bd"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
8d35157628
|
[8.16] [ML] Fix the Trained Models table expanded row refresh (#198149) (#198391)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Fix the Trained Models table expanded row refresh (#198149)](https://github.com/elastic/kibana/pull/198149) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-30T15:34:29Z","message":"[ML] Fix the Trained Models table expanded row refresh (#198149)\n\n## Summary\r\n\r\nFixes a regression introduced in\r\nhttps://github.com/elastic/kibana/pull/194614/, where the content of\r\nexpanded rows in the Trained Model table stopped being updated on\r\nrefresh.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e05d5c2e8084212584770fa52fe5701e2dd2166","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","v8.16.0","backport:version"],"title":"[ML] Fix the Trained Models table expanded row refresh","number":198149,"url":"https://github.com/elastic/kibana/pull/198149","mergeCommit":{"message":"[ML] Fix the Trained Models table expanded row refresh (#198149)\n\n## Summary\r\n\r\nFixes a regression introduced in\r\nhttps://github.com/elastic/kibana/pull/194614/, where the content of\r\nexpanded rows in the Trained Model table stopped being updated on\r\nrefresh.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e05d5c2e8084212584770fa52fe5701e2dd2166"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198149","number":198149,"mergeCommit":{"message":"[ML] Fix the Trained Models table expanded row refresh (#198149)\n\n## Summary\r\n\r\nFixes a regression introduced in\r\nhttps://github.com/elastic/kibana/pull/194614/, where the content of\r\nexpanded rows in the Trained Model table stopped being updated on\r\nrefresh.\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"7e05d5c2e8084212584770fa52fe5701e2dd2166"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
af2cd0c47d
|
[8.16] [ML] Memory usage: Functional tests (#197415) (#197808)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Memory usage: Functional tests (#197415)](https://github.com/elastic/kibana/pull/197415) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-25T11:39:38Z","message":"[ML] Memory usage: Functional tests (#197415)\n\n## Summary\r\n\r\nFunctional tests for `memory usage` page in ML.","sha":"479280c0b74747056634421c9b9e05f94a3c7e07","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","release_note:skip","v9.0.0","Team:ML","v8.16.0","backport:version","v8.17.0"],"title":"[ML] Memory usage: Functional tests","number":197415,"url":"https://github.com/elastic/kibana/pull/197415","mergeCommit":{"message":"[ML] Memory usage: Functional tests (#197415)\n\n## Summary\r\n\r\nFunctional tests for `memory usage` page in ML.","sha":"479280c0b74747056634421c9b9e05f94a3c7e07"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197415","number":197415,"mergeCommit":{"message":"[ML] Memory usage: Functional tests (#197415)\n\n## Summary\r\n\r\nFunctional tests for `memory usage` page in ML.","sha":"479280c0b74747056634421c9b9e05f94a3c7e07"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
b0af74f1c3
|
[8.16] [ML] Trained models: Accessibility tests (#197446) (#197687)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Trained models: Accessibility tests (#197446)](https://github.com/elastic/kibana/pull/197446) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-24T16:22:53Z","message":"[ML] Trained models: Accessibility tests (#197446)\n\n## Summary\r\n\r\nAccessibility tests for Trained models page.","sha":"f279b39bde0136df1efb0b9cc4e97af68be69896","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","release_note:skip","v9.0.0","Team:ML","v8.16.0","backport:version","v8.17.0"],"title":"[ML] Trained models: Accessibility tests","number":197446,"url":"https://github.com/elastic/kibana/pull/197446","mergeCommit":{"message":"[ML] Trained models: Accessibility tests (#197446)\n\n## Summary\r\n\r\nAccessibility tests for Trained models page.","sha":"f279b39bde0136df1efb0b9cc4e97af68be69896"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197446","number":197446,"mergeCommit":{"message":"[ML] Trained models: Accessibility tests (#197446)\n\n## Summary\r\n\r\nAccessibility tests for Trained models page.","sha":"f279b39bde0136df1efb0b9cc4e97af68be69896"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
3d98f6c3f7
|
[8.16] [ML] Update allocations tooltip to clarify that it is per node (#197099) (#197488)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Update allocations tooltip to clarify that it's per node (#197099)](https://github.com/elastic/kibana/pull/197099) <!--- 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-10-23T15:30:13Z","message":"[ML] Update allocations tooltip to clarify that it's per node (#197099)\n\nClarifies text to mention nodes, conditional on being not-serverless","sha":"ea4ce57141019606b148016f667dd7a0cf98ff8c","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Update allocations tooltip to clarify that it's per node","number":197099,"url":"https://github.com/elastic/kibana/pull/197099","mergeCommit":{"message":"[ML] Update allocations tooltip to clarify that it's per node (#197099)\n\nClarifies text to mention nodes, conditional on being not-serverless","sha":"ea4ce57141019606b148016f667dd7a0cf98ff8c"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197099","number":197099,"mergeCommit":{"message":"[ML] Update allocations tooltip to clarify that it's per node (#197099)\n\nClarifies text to mention nodes, conditional on being not-serverless","sha":"ea4ce57141019606b148016f667dd7a0cf98ff8c"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> |
||
|
9752a92845
|
[8.16] [Chore] Isolate CCS check (#195988) (#196868)
# Backport This will backport the following commits from `main` to `8.16`: - [[Chore] Isolate CCS check (#195988)](https://github.com/elastic/kibana/pull/195988) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thomas Neirynck","email":"thomas@elastic.co"},"sourceCommit":{"committedDate":"2024-10-18T12:40:04Z","message":"[Chore] Isolate CCS check (#195988)\n\n## Summary\r\n\r\nIsolate CCS check in single location.\r\n\r\nCloses\r\nhttps://github.com/elastic/kibana/issues/193906#issuecomment-2400370478\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f86d1716b171d846851041d50da074683624fa02","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","v9.0.0","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-infra_services","apm:review","v8.16.0"],"title":"[Chore] Isolate CCS check","number":195988,"url":"https://github.com/elastic/kibana/pull/195988","mergeCommit":{"message":"[Chore] Isolate CCS check (#195988)\n\n## Summary\r\n\r\nIsolate CCS check in single location.\r\n\r\nCloses\r\nhttps://github.com/elastic/kibana/issues/193906#issuecomment-2400370478\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f86d1716b171d846851041d50da074683624fa02"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195988","number":195988,"mergeCommit":{"message":"[Chore] Isolate CCS check (#195988)\n\n## Summary\r\n\r\nIsolate CCS check in single location.\r\n\r\nCloses\r\nhttps://github.com/elastic/kibana/issues/193906#issuecomment-2400370478\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f86d1716b171d846851041d50da074683624fa02"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Thomas Neirynck <thomas@elastic.co> |
||
|
20c366a79c
|
[8.x] [ML] E5 discplaimer in the flyout (#196347) (#196574)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] E5 discplaimer in the flyout (#196347)](https://github.com/elastic/kibana/pull/196347) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-16T16:14:04Z","message":"[ML] E5 discplaimer in the flyout (#196347)\n\n## Summary\r\n\r\nAdds E5 disclaimer to the \"Add model\" flyout. \r\n\r\n<img width=\"1320\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c46a7ea-91c1-4bf2-8671-dc7df283c09c\">","sha":"8bd567b73a1b4385cfcfac26f7d18142a3b76a5d","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Feature:3rd Party Models","Team:ML","v8.16.0","backport:version"],"title":"[ML] Adds E5 disclaimer to the trained models flyout ","number":196347,"url":"https://github.com/elastic/kibana/pull/196347","mergeCommit":{"message":"[ML] E5 discplaimer in the flyout (#196347)\n\n## Summary\r\n\r\nAdds E5 disclaimer to the \"Add model\" flyout. \r\n\r\n<img width=\"1320\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c46a7ea-91c1-4bf2-8671-dc7df283c09c\">","sha":"8bd567b73a1b4385cfcfac26f7d18142a3b76a5d"}},"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/196347","number":196347,"mergeCommit":{"message":"[ML] E5 discplaimer in the flyout (#196347)\n\n## Summary\r\n\r\nAdds E5 disclaimer to the \"Add model\" flyout. \r\n\r\n<img width=\"1320\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/3c46a7ea-91c1-4bf2-8671-dc7df283c09c\">","sha":"8bd567b73a1b4385cfcfac26f7d18142a3b76a5d"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
5a67e4d2e1
|
[8.x] Update dependency @types/lodash to ^4.17.10 (main) (#194739) (#196234)
# Backport This will backport the following commits from `main` to `8.x`: - [Update dependency @types/lodash to ^4.17.10 (main) (#194739)](https://github.com/elastic/kibana/pull/194739) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-15T06:21:03Z","message":"Update dependency @types/lodash to ^4.17.10 (main) (#194739)","sha":"563910b672b6dbe4f9e7931e36ec41e674fe8eb3","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Feature:ExpressionLanguage","release_note:skip","💝community","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management"],"title":"Update dependency @types/lodash to ^4.17.10 (main)","number":194739,"url":"https://github.com/elastic/kibana/pull/194739","mergeCommit":{"message":"Update dependency @types/lodash to ^4.17.10 (main) (#194739)","sha":"563910b672b6dbe4f9e7931e36ec41e674fe8eb3"}},"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/194739","number":194739,"mergeCommit":{"message":"Update dependency @types/lodash to ^4.17.10 (main) (#194739)","sha":"563910b672b6dbe4f9e7931e36ec41e674fe8eb3"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
df849c5431
|
[8.x] [ML] Adds ability to toggle visibility for empty fields when choosing an aggregation or field in Anomaly detection, data frame analytics (#186670) (#196180)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Adds ability to toggle visibility for empty fields when choosing an aggregation or field in Anomaly detection, data frame analytics (#186670)](https://github.com/elastic/kibana/pull/186670) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-14T16:17:38Z","message":"[ML] Adds ability to toggle visibility for empty fields when choosing an aggregation or field in Anomaly detection, data frame analytics (#186670)\n\n## Summary\r\n\r\nThis PR adds new ability to toggle visibility for empty fields when\r\nchoosing an aggregation or field in Anomaly detection and Data frame\r\nanalytics\r\n\r\n\r\n |
||
|
107ff84cbf
|
[8.x] [ML] Update vCPUs ranges for start model deployment (#195617) (#196156)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Update vCPUs ranges for start model deployment (#195617)](https://github.com/elastic/kibana/pull/195617) <!--- Backport version: 9.4.3 --> ### 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":"2024-10-14T14:38:26Z","message":"[ML] Update vCPUs ranges for start model deployment (#195617)\n\n## Summary\r\n\r\n#### Different vCPUs ranges and enabling support for static allocations\r\nbased on the serverless project type\r\n\r\n- Each serverless config yml, e.g.\r\n[search.es.yml]( |
||
|
d4f7bad3e7
|
[8.x] [ML] Adds ML tasks to the kibana audit log (#195120) (#196099)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Adds ML tasks to the kibana audit log (#195120)](https://github.com/elastic/kibana/pull/195120) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2024-10-14T10:37:56Z","message":"[ML] Adds ML tasks to the kibana audit log (#195120)\n\nAdds a new `MlAuditLogger` service for logging calls to elasticsearch in\r\nkibana's audit log.\r\nNot all calls are logged, only ones which make changes to ML jobs or\r\ntrained models, e.g. creating, deleting, starting, stopping etc.\r\n\r\nCalls to the es client are wrapped in a logging function so successes\r\nand failures can be caught and logged.\r\n\r\nthe audit log can be enabed by adding this to the kibana yml or dev.yml\r\nfile\r\n`xpack.security.audit.enabled: true`\r\n\r\nAn example log entry (NDJSON formatted to make it readable):\r\n```\r\n{\r\n \"event\": {\r\n \"action\": \"ml_start_ad_datafeed\",\r\n \"type\": [\r\n \"change\"\r\n ],\r\n \"category\": [\r\n \"database\"\r\n ],\r\n \"outcome\": \"success\"\r\n },\r\n \"labels\": {\r\n \"application\": \"elastic/ml\"\r\n },\r\n \"user\": {\r\n \"id\": \"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\r\n \"name\": \"elastic\",\r\n \"roles\": [\r\n \"superuser\"\r\n ]\r\n },\r\n \"kibana\": {\r\n \"space_id\": \"default\",\r\n \"session_id\": \"U6HQCDkk+fAEUCXs7i4qM2/MZITPxE02pp8o7h09P68=\"\r\n },\r\n \"trace\": {\r\n \"id\": \"4f1b616b-8535-43e1-8516-32ea9fe76d19\"\r\n },\r\n \"client\": {\r\n \"ip\": \"127.0.0.1\"\r\n },\r\n \"http\": {\r\n \"request\": {\r\n \"headers\": {\r\n \"x-forwarded-for\": \"127.0.0.1\"\r\n }\r\n }\r\n },\r\n \"service\": {\r\n \"node\": {\r\n \"roles\": [\r\n \"background_tasks\",\r\n \"ui\"\r\n ]\r\n }\r\n },\r\n \"ecs\": {\r\n \"version\": \"8.11.0\"\r\n },\r\n \"@timestamp\": \"2024-10-11T09:07:47.933+01:00\",\r\n \"message\": \"Starting anomaly detection datafeed datafeed-11aaaa\",\r\n \"log\": {\r\n \"level\": \"INFO\",\r\n \"logger\": \"plugins.security.audit.ecs\"\r\n },\r\n \"process\": {\r\n \"pid\": 58305,\r\n \"uptime\": 100.982390291\r\n },\r\n \"transaction\": {\r\n \"id\": \"77c14aadc6901324\"\r\n }\r\n}\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"923c450c1b044a12dd938c0c5ea380a895eeaf88","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","v9.0.0","v8.16.0","backport:version"],"title":"[ML] Adds ML tasks to the kibana audit log","number":195120,"url":"https://github.com/elastic/kibana/pull/195120","mergeCommit":{"message":"[ML] Adds ML tasks to the kibana audit log (#195120)\n\nAdds a new `MlAuditLogger` service for logging calls to elasticsearch in\r\nkibana's audit log.\r\nNot all calls are logged, only ones which make changes to ML jobs or\r\ntrained models, e.g. creating, deleting, starting, stopping etc.\r\n\r\nCalls to the es client are wrapped in a logging function so successes\r\nand failures can be caught and logged.\r\n\r\nthe audit log can be enabed by adding this to the kibana yml or dev.yml\r\nfile\r\n`xpack.security.audit.enabled: true`\r\n\r\nAn example log entry (NDJSON formatted to make it readable):\r\n```\r\n{\r\n \"event\": {\r\n \"action\": \"ml_start_ad_datafeed\",\r\n \"type\": [\r\n \"change\"\r\n ],\r\n \"category\": [\r\n \"database\"\r\n ],\r\n \"outcome\": \"success\"\r\n },\r\n \"labels\": {\r\n \"application\": \"elastic/ml\"\r\n },\r\n \"user\": {\r\n \"id\": \"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\r\n \"name\": \"elastic\",\r\n \"roles\": [\r\n \"superuser\"\r\n ]\r\n },\r\n \"kibana\": {\r\n \"space_id\": \"default\",\r\n \"session_id\": \"U6HQCDkk+fAEUCXs7i4qM2/MZITPxE02pp8o7h09P68=\"\r\n },\r\n \"trace\": {\r\n \"id\": \"4f1b616b-8535-43e1-8516-32ea9fe76d19\"\r\n },\r\n \"client\": {\r\n \"ip\": \"127.0.0.1\"\r\n },\r\n \"http\": {\r\n \"request\": {\r\n \"headers\": {\r\n \"x-forwarded-for\": \"127.0.0.1\"\r\n }\r\n }\r\n },\r\n \"service\": {\r\n \"node\": {\r\n \"roles\": [\r\n \"background_tasks\",\r\n \"ui\"\r\n ]\r\n }\r\n },\r\n \"ecs\": {\r\n \"version\": \"8.11.0\"\r\n },\r\n \"@timestamp\": \"2024-10-11T09:07:47.933+01:00\",\r\n \"message\": \"Starting anomaly detection datafeed datafeed-11aaaa\",\r\n \"log\": {\r\n \"level\": \"INFO\",\r\n \"logger\": \"plugins.security.audit.ecs\"\r\n },\r\n \"process\": {\r\n \"pid\": 58305,\r\n \"uptime\": 100.982390291\r\n },\r\n \"transaction\": {\r\n \"id\": \"77c14aadc6901324\"\r\n }\r\n}\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"923c450c1b044a12dd938c0c5ea380a895eeaf88"}},"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/195120","number":195120,"mergeCommit":{"message":"[ML] Adds ML tasks to the kibana audit log (#195120)\n\nAdds a new `MlAuditLogger` service for logging calls to elasticsearch in\r\nkibana's audit log.\r\nNot all calls are logged, only ones which make changes to ML jobs or\r\ntrained models, e.g. creating, deleting, starting, stopping etc.\r\n\r\nCalls to the es client are wrapped in a logging function so successes\r\nand failures can be caught and logged.\r\n\r\nthe audit log can be enabed by adding this to the kibana yml or dev.yml\r\nfile\r\n`xpack.security.audit.enabled: true`\r\n\r\nAn example log entry (NDJSON formatted to make it readable):\r\n```\r\n{\r\n \"event\": {\r\n \"action\": \"ml_start_ad_datafeed\",\r\n \"type\": [\r\n \"change\"\r\n ],\r\n \"category\": [\r\n \"database\"\r\n ],\r\n \"outcome\": \"success\"\r\n },\r\n \"labels\": {\r\n \"application\": \"elastic/ml\"\r\n },\r\n \"user\": {\r\n \"id\": \"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\r\n \"name\": \"elastic\",\r\n \"roles\": [\r\n \"superuser\"\r\n ]\r\n },\r\n \"kibana\": {\r\n \"space_id\": \"default\",\r\n \"session_id\": \"U6HQCDkk+fAEUCXs7i4qM2/MZITPxE02pp8o7h09P68=\"\r\n },\r\n \"trace\": {\r\n \"id\": \"4f1b616b-8535-43e1-8516-32ea9fe76d19\"\r\n },\r\n \"client\": {\r\n \"ip\": \"127.0.0.1\"\r\n },\r\n \"http\": {\r\n \"request\": {\r\n \"headers\": {\r\n \"x-forwarded-for\": \"127.0.0.1\"\r\n }\r\n }\r\n },\r\n \"service\": {\r\n \"node\": {\r\n \"roles\": [\r\n \"background_tasks\",\r\n \"ui\"\r\n ]\r\n }\r\n },\r\n \"ecs\": {\r\n \"version\": \"8.11.0\"\r\n },\r\n \"@timestamp\": \"2024-10-11T09:07:47.933+01:00\",\r\n \"message\": \"Starting anomaly detection datafeed datafeed-11aaaa\",\r\n \"log\": {\r\n \"level\": \"INFO\",\r\n \"logger\": \"plugins.security.audit.ecs\"\r\n },\r\n \"process\": {\r\n \"pid\": 58305,\r\n \"uptime\": 100.982390291\r\n },\r\n \"transaction\": {\r\n \"id\": \"77c14aadc6901324\"\r\n }\r\n}\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"923c450c1b044a12dd938c0c5ea380a895eeaf88"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
7a80e6f1a7
|
[8.x] [ML] Remove legacy scss overwrites Single Metric Viewer (#195259) (#196085)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Remove legacy scss overwrites Single Metric Viewer (#195259)](https://github.com/elastic/kibana/pull/195259) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-14T10:14:37Z","message":"[ML] Remove legacy scss overwrites Single Metric Viewer (#195259)\n\n## Summary\r\n\r\nRemoves SCSS files for the Single Metric Viewer and adds BEM classes for\r\n`annotations`.\r\nAffects the Single Metric Viewer in ML and the embeddable.\r\nPart of [#140695](https://github.com/elastic/kibana/issues/140695)","sha":"87c91f4e258db1910e13daec7e8267d1110735dd","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Remove legacy scss overwrites Single Metric Viewer","number":195259,"url":"https://github.com/elastic/kibana/pull/195259","mergeCommit":{"message":"[ML] Remove legacy scss overwrites Single Metric Viewer (#195259)\n\n## Summary\r\n\r\nRemoves SCSS files for the Single Metric Viewer and adds BEM classes for\r\n`annotations`.\r\nAffects the Single Metric Viewer in ML and the embeddable.\r\nPart of [#140695](https://github.com/elastic/kibana/issues/140695)","sha":"87c91f4e258db1910e13daec7e8267d1110735dd"}},"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/195259","number":195259,"mergeCommit":{"message":"[ML] Remove legacy scss overwrites Single Metric Viewer (#195259)\n\n## Summary\r\n\r\nRemoves SCSS files for the Single Metric Viewer and adds BEM classes for\r\n`annotations`.\r\nAffects the Single Metric Viewer in ML and the embeddable.\r\nPart of [#140695](https://github.com/elastic/kibana/issues/140695)","sha":"87c91f4e258db1910e13daec7e8267d1110735dd"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
206041f16d
|
[8.x] Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#195860) (#195930)
# Backport This will backport the following commits from `main` to `8.x`: - [Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#195860)](https://github.com/elastic/kibana/pull/195860) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-10-11T14:15:53Z","message":"Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#195860)\n\n## Summary\r\n\r\nThis reverts #194517 ([ML] AIOps: Use package instead of context for\r\nusing field stats flyout) committed in\r\neebfba4f9bfe2592ce92d35aed9cf3c0c8540130.\r\n\r\nThe PR refactored how `FieldStatsFlyout` is passed in as a dependency to\r\nchange point detection. Unfortunately the refactor caused the dropdown\r\nto select the split field to break when used in the flyout for the\r\noptions of the change point detection embeddable.\r\n\r\nThis revert is done to restore the original behavior. In a follow up I\r\nwill revisit the refactor to work properly.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)","sha":"37a420b950aa7ced58360283ec4a4e63d5d410f8","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug",":ml","release_note:skip","v9.0.0","Feature:ML/AIOps","v8.16.0","backport:version"],"title":"Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517)","number":195860,"url":"https://github.com/elastic/kibana/pull/195860","mergeCommit":{"message":"Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#195860)\n\n## Summary\r\n\r\nThis reverts #194517 ([ML] AIOps: Use package instead of context for\r\nusing field stats flyout) committed in\r\neebfba4f9bfe2592ce92d35aed9cf3c0c8540130.\r\n\r\nThe PR refactored how `FieldStatsFlyout` is passed in as a dependency to\r\nchange point detection. Unfortunately the refactor caused the dropdown\r\nto select the split field to break when used in the flyout for the\r\noptions of the change point detection embeddable.\r\n\r\nThis revert is done to restore the original behavior. In a follow up I\r\nwill revisit the refactor to work properly.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)","sha":"37a420b950aa7ced58360283ec4a4e63d5d410f8"}},"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/195860","number":195860,"mergeCommit":{"message":"Revert [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#195860)\n\n## Summary\r\n\r\nThis reverts #194517 ([ML] AIOps: Use package instead of context for\r\nusing field stats flyout) committed in\r\neebfba4f9bfe2592ce92d35aed9cf3c0c8540130.\r\n\r\nThe PR refactored how `FieldStatsFlyout` is passed in as a dependency to\r\nchange point detection. Unfortunately the refactor caused the dropdown\r\nto select the split field to break when used in the flyout for the\r\noptions of the change point detection embeddable.\r\n\r\nThis revert is done to restore the original behavior. In a follow up I\r\nwill revisit the refactor to work properly.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)","sha":"37a420b950aa7ced58360283ec4a4e63d5d410f8"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
d383f3eaf5
|
[8.x] [ML] Fix Anomaly Swim Lane Embeddable not updating properly on query change (#195090) (#195725)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Fix Anomaly Swim Lane Embeddable not updating properly on query change (#195090)](https://github.com/elastic/kibana/pull/195090) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-10T09:19:28Z","message":"[ML] Fix Anomaly Swim Lane Embeddable not updating properly on query change (#195090)\n\n## Summary\r\n\r\nFix for: [#194579](https://github.com/elastic/kibana/issues/194579)\r\nIn Anomaly Explorer, we do not limit the query size, as it is based on a\r\nconstant value of `1000`.\r\nHowever, we did limit the query for the embeddable by setting the size\r\nto the value of the previous query cardinality.\r\nAfter discussing with @darnautov, we couldn't identify any potential\r\nregressions from removing this check.\r\nIncludes fix for issue mentioned in:\r\n[#2397303538](https://github.com/elastic/kibana/pull/195090#issuecomment-2397303538)\r\nWhen querying from a pagination page other than page 1, we didn’t reset\r\nthe `fromPage` value, which prevented the query from returning results.\r\nBefore:\r\n\r\n\r\n |
||
|
cbef50e179
|
[8.x] Remove unused`kbn-ace` code (#195353) (#195727)
# Backport This will backport the following commits from `main` to `8.x`: - [Remove unused`kbn-ace` code (#195353)](https://github.com/elastic/kibana/pull/195353) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2024-10-08T11:45:20Z","message":"Remove unused`kbn-ace` code (#195353)","sha":"83810ac9edba72f0bcad8f7e7e77a1bef89328cc","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.16.0"],"title":"Remove unused`kbn-ace` code","number":195353,"url":"https://github.com/elastic/kibana/pull/195353","mergeCommit":{"message":"Remove unused`kbn-ace` code (#195353)","sha":"83810ac9edba72f0bcad8f7e7e77a1bef89328cc"}},"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/195353","number":195353,"mergeCommit":{"message":"Remove unused`kbn-ace` code (#195353)","sha":"83810ac9edba72f0bcad8f7e7e77a1bef89328cc"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> |
||
|
9bdf698bb7
|
[8.x] [ML] Updates for Trained Models table layout and model states (#194614) (#195546) | ||
|
1aceffc3df
|
[8.x] [Presentation Util] Cleanup services (#194201) (#195445)
# Backport This will backport the following commits from `main` to `8.x`: - [[Presentation Util] Cleanup services (#194201)](https://github.com/elastic/kibana/pull/194201) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-08T15:15:33Z","message":"[Presentation Util] Cleanup services (#194201)\n\nCloses https://github.com/elastic/kibana/issues/167440\r\n\r\n## Summary\r\n\r\nThis PR refactors the `PresentationUtil` services to no longer use its\r\nown `PluginServiceProvider`. In doing this, it removes the\r\n`PresentationUtil` context provider, since it is no longer necessary.\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9f2208db1a83889c76fd2413a0a133a858f4891e","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","loe:small","technical debt","release_note:skip","impact:high","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[Presentation Util] Cleanup services","number":194201,"url":"https://github.com/elastic/kibana/pull/194201","mergeCommit":{"message":"[Presentation Util] Cleanup services (#194201)\n\nCloses https://github.com/elastic/kibana/issues/167440\r\n\r\n## Summary\r\n\r\nThis PR refactors the `PresentationUtil` services to no longer use its\r\nown `PluginServiceProvider`. In doing this, it removes the\r\n`PresentationUtil` context provider, since it is no longer necessary.\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9f2208db1a83889c76fd2413a0a133a858f4891e"}},"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/194201","number":194201,"mergeCommit":{"message":"[Presentation Util] Cleanup services (#194201)\n\nCloses https://github.com/elastic/kibana/issues/167440\r\n\r\n## Summary\r\n\r\nThis PR refactors the `PresentationUtil` services to no longer use its\r\nown `PluginServiceProvider`. In doing this, it removes the\r\n`PresentationUtil` context provider, since it is no longer necessary.\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"9f2208db1a83889c76fd2413a0a133a858f4891e"}}]}] BACKPORT--> Co-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com> |
||
|
6eb8471c31
|
[8.x] [ML] Anomaly Detection: adds ability to delete forecasts from job (#194896) (#195547)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly Detection: adds ability to delete forecasts from job (#194896)](https://github.com/elastic/kibana/pull/194896) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2024-10-09T08:40:45Z","message":"[ML] Anomaly Detection: adds ability to delete forecasts from job (#194896)\n\n## Summary\r\n\r\nRelated issues:\r\n- https://github.com/elastic/kibana/issues/18511\r\n- https://github.com/elastic/kibana/issues/192301\r\n\r\nIn this PR, in Job management > expanded row > Forecasts tab - a delete\r\naction has been added to each row in the forecasts table. A confirmation\r\nmodal allows the user to confirm the delete action.\r\n\r\nIn the SMV view, the forecast being currently viewed is now highlighted\r\nin the Forecast modal to make it easier to identify.\r\n\r\n\r\n\r\n\r\n<img width=\"881\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/accbd7d9-1bae-4f1f-af8f-8bd36eae0572\">\r\n\r\n<img width=\"1099\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6011936d-3773-41ce-bbce-3ca4c0154cab\">\r\n\r\nDark mode:\r\n\r\n<img width=\"882\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cbec6fc8-0c62-4e34-9546-0124ae80a568\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f4a4a681f58c1c64eb8a05070b44f0605c625458","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","v9.0.0","v8.16.0","backport:version"],"title":"[ML] Anomaly Detection: adds ability to delete forecasts from job","number":194896,"url":"https://github.com/elastic/kibana/pull/194896","mergeCommit":{"message":"[ML] Anomaly Detection: adds ability to delete forecasts from job (#194896)\n\n## Summary\r\n\r\nRelated issues:\r\n- https://github.com/elastic/kibana/issues/18511\r\n- https://github.com/elastic/kibana/issues/192301\r\n\r\nIn this PR, in Job management > expanded row > Forecasts tab - a delete\r\naction has been added to each row in the forecasts table. A confirmation\r\nmodal allows the user to confirm the delete action.\r\n\r\nIn the SMV view, the forecast being currently viewed is now highlighted\r\nin the Forecast modal to make it easier to identify.\r\n\r\n\r\n\r\n\r\n<img width=\"881\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/accbd7d9-1bae-4f1f-af8f-8bd36eae0572\">\r\n\r\n<img width=\"1099\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6011936d-3773-41ce-bbce-3ca4c0154cab\">\r\n\r\nDark mode:\r\n\r\n<img width=\"882\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cbec6fc8-0c62-4e34-9546-0124ae80a568\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f4a4a681f58c1c64eb8a05070b44f0605c625458"}},"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/194896","number":194896,"mergeCommit":{"message":"[ML] Anomaly Detection: adds ability to delete forecasts from job (#194896)\n\n## Summary\r\n\r\nRelated issues:\r\n- https://github.com/elastic/kibana/issues/18511\r\n- https://github.com/elastic/kibana/issues/192301\r\n\r\nIn this PR, in Job management > expanded row > Forecasts tab - a delete\r\naction has been added to each row in the forecasts table. A confirmation\r\nmodal allows the user to confirm the delete action.\r\n\r\nIn the SMV view, the forecast being currently viewed is now highlighted\r\nin the Forecast modal to make it easier to identify.\r\n\r\n\r\n\r\n\r\n<img width=\"881\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/accbd7d9-1bae-4f1f-af8f-8bd36eae0572\">\r\n\r\n<img width=\"1099\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/6011936d-3773-41ce-bbce-3ca4c0154cab\">\r\n\r\nDark mode:\r\n\r\n<img width=\"882\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/cbec6fc8-0c62-4e34-9546-0124ae80a568\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f4a4a681f58c1c64eb8a05070b44f0605c625458"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co> |
||
|
b8d7596193
|
[8.x] [ML] Hide ES|QL based saved searches in ML & Transforms (#195084) (#195541)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Hide ES|QL based saved searches in ML & Transforms (#195084)](https://github.com/elastic/kibana/pull/195084) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-09T08:14:50Z","message":"[ML] Hide ES|QL based saved searches in ML & Transforms (#195084)\n\n## Summary\r\n\r\nFix for: [#187962](https://github.com/elastic/kibana/issues/187962)\r\nWe were displaying ES|QL based searches in various areas of ML, not just\r\nin the places mentioned in the issue.\r\nBefore:\r\n\r\nThen, after selecting the ESQL based search:\r\n\r\n\r\nAfter the fix:\r\n\r\n","sha":"1b4ebaa85261074aec775d23165474863ddea45a","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Hide ES|QL based saved searches in ML & Transforms","number":195084,"url":"https://github.com/elastic/kibana/pull/195084","mergeCommit":{"message":"[ML] Hide ES|QL based saved searches in ML & Transforms (#195084)\n\n## Summary\r\n\r\nFix for: [#187962](https://github.com/elastic/kibana/issues/187962)\r\nWe were displaying ES|QL based searches in various areas of ML, not just\r\nin the places mentioned in the issue.\r\nBefore:\r\n\r\nThen, after selecting the ESQL based search:\r\n\r\n\r\nAfter the fix:\r\n\r\n","sha":"1b4ebaa85261074aec775d23165474863ddea45a"}},"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/195084","number":195084,"mergeCommit":{"message":"[ML] Hide ES|QL based saved searches in ML & Transforms (#195084)\n\n## Summary\r\n\r\nFix for: [#187962](https://github.com/elastic/kibana/issues/187962)\r\nWe were displaying ES|QL based searches in various areas of ML, not just\r\nin the places mentioned in the issue.\r\nBefore:\r\n\r\nThen, after selecting the ESQL based search:\r\n\r\n\r\nAfter the fix:\r\n\r\n","sha":"1b4ebaa85261074aec775d23165474863ddea45a"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
07c493c462
|
[8.x] [ML] AIOps: Cleanup context/embeddingOrigin (#194442) (#195284)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] AIOps: Cleanup context/embeddingOrigin (#194442)](https://github.com/elastic/kibana/pull/194442) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-10-07T15:32:18Z","message":"[ML] AIOps: Cleanup context/embeddingOrigin (#194442)\n\n## Summary\r\n\r\nPart of #187772.\r\n\r\nWe had a mix of passing around `embeddingOrigin` via props and context.\r\nThis PR cleans this up, `embeddingOrigin` is now be required to be\r\npassed in on the outer most component and will then be used internally\r\nvia context only.\r\n\r\nThe PR also renames references to `AppDependencies` to\r\n`AiopsAppContextValue`. Originally, this context was used only to pass\r\nin dependencies to be used via `useKibana`. Over time this changed a bit\r\nand we started passing in other non-changing values, the naming change\r\nnow reflects that more properly and brings the name in line with the\r\nother context related vars like `AiopsAppContext.Provider` and\r\n`useAiopsAppContext`.\r\n\r\n\r\n### Checklist\r\n\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ae36dd5bf2713cafc2e5eaa73629612686842c1a","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Feature:ML/AIOps","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0","backport:version"],"title":"[ML] AIOps: Cleanup context/embeddingOrigin","number":194442,"url":"https://github.com/elastic/kibana/pull/194442","mergeCommit":{"message":"[ML] AIOps: Cleanup context/embeddingOrigin (#194442)\n\n## Summary\r\n\r\nPart of #187772.\r\n\r\nWe had a mix of passing around `embeddingOrigin` via props and context.\r\nThis PR cleans this up, `embeddingOrigin` is now be required to be\r\npassed in on the outer most component and will then be used internally\r\nvia context only.\r\n\r\nThe PR also renames references to `AppDependencies` to\r\n`AiopsAppContextValue`. Originally, this context was used only to pass\r\nin dependencies to be used via `useKibana`. Over time this changed a bit\r\nand we started passing in other non-changing values, the naming change\r\nnow reflects that more properly and brings the name in line with the\r\nother context related vars like `AiopsAppContext.Provider` and\r\n`useAiopsAppContext`.\r\n\r\n\r\n### Checklist\r\n\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ae36dd5bf2713cafc2e5eaa73629612686842c1a"}},"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/194442","number":194442,"mergeCommit":{"message":"[ML] AIOps: Cleanup context/embeddingOrigin (#194442)\n\n## Summary\r\n\r\nPart of #187772.\r\n\r\nWe had a mix of passing around `embeddingOrigin` via props and context.\r\nThis PR cleans this up, `embeddingOrigin` is now be required to be\r\npassed in on the outer most component and will then be used internally\r\nvia context only.\r\n\r\nThe PR also renames references to `AppDependencies` to\r\n`AiopsAppContextValue`. Originally, this context was used only to pass\r\nin dependencies to be used via `useKibana`. Over time this changed a bit\r\nand we started passing in other non-changing values, the naming change\r\nnow reflects that more properly and brings the name in line with the\r\nother context related vars like `AiopsAppContext.Provider` and\r\n`useAiopsAppContext`.\r\n\r\n\r\n### Checklist\r\n\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ae36dd5bf2713cafc2e5eaa73629612686842c1a"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
8811474e3c
|
[8.x] [ML] Daylight saving time calendar events (#193605) (#195262)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Daylight saving time calendar events (#193605)](https://github.com/elastic/kibana/pull/193605) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2024-10-07T13:35:25Z","message":"[ML] Daylight saving time calendar events (#193605)\n\nAdds new pages for creating and managing DST calendars.\r\nCloses https://github.com/elastic/kibana/issues/189469\r\n\r\nNew section added to Settings home page.\r\n\r\n\r\n\r\nNew page for listing DST calendars. The original calendar page does not\r\nshow DST calendars.\r\n\r\n\r\n\r\nNew page for creating DST calendars.\r\nThe ability to apply to all jobs and add a description has been removed.\r\nIt is not possible manually add events. Events are automatically\r\ngenerated for a selected time zone.\r\n<img width=\"1170\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/557b8d39-6c17-448a-aa30-a282d8a424a7\">\r\n\r\nIf the selected time zone does not observe daylight savings, an info\r\ncallout is displayed\r\n<img width=\"1178\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/627043bf-0368-4ab3-8ca7-1931f9622387\">\r\n\r\n\r\nA new DST calendar section is added to all AD job wizards.\r\n\r\n","sha":"2881b0423d099649243ee01887f27a1fb6dbffe7","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","Feature:Anomaly Detection","v9.0.0","release_note:feature","v8.16.0","backport:version"],"title":"[ML] Daylight saving time calendar events","number":193605,"url":"https://github.com/elastic/kibana/pull/193605","mergeCommit":{"message":"[ML] Daylight saving time calendar events (#193605)\n\nAdds new pages for creating and managing DST calendars.\r\nCloses https://github.com/elastic/kibana/issues/189469\r\n\r\nNew section added to Settings home page.\r\n\r\n\r\n\r\nNew page for listing DST calendars. The original calendar page does not\r\nshow DST calendars.\r\n\r\n\r\n\r\nNew page for creating DST calendars.\r\nThe ability to apply to all jobs and add a description has been removed.\r\nIt is not possible manually add events. Events are automatically\r\ngenerated for a selected time zone.\r\n<img width=\"1170\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/557b8d39-6c17-448a-aa30-a282d8a424a7\">\r\n\r\nIf the selected time zone does not observe daylight savings, an info\r\ncallout is displayed\r\n<img width=\"1178\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/627043bf-0368-4ab3-8ca7-1931f9622387\">\r\n\r\n\r\nA new DST calendar section is added to all AD job wizards.\r\n\r\n","sha":"2881b0423d099649243ee01887f27a1fb6dbffe7"}},"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/193605","number":193605,"mergeCommit":{"message":"[ML] Daylight saving time calendar events (#193605)\n\nAdds new pages for creating and managing DST calendars.\r\nCloses https://github.com/elastic/kibana/issues/189469\r\n\r\nNew section added to Settings home page.\r\n\r\n\r\n\r\nNew page for listing DST calendars. The original calendar page does not\r\nshow DST calendars.\r\n\r\n\r\n\r\nNew page for creating DST calendars.\r\nThe ability to apply to all jobs and add a description has been removed.\r\nIt is not possible manually add events. Events are automatically\r\ngenerated for a selected time zone.\r\n<img width=\"1170\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/557b8d39-6c17-448a-aa30-a282d8a424a7\">\r\n\r\nIf the selected time zone does not observe daylight savings, an info\r\ncallout is displayed\r\n<img width=\"1178\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/627043bf-0368-4ab3-8ca7-1931f9622387\">\r\n\r\n\r\nA new DST calendar section is added to all AD job wizards.\r\n\r\n","sha":"2881b0423d099649243ee01887f27a1fb6dbffe7"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
a4075f7832
|
[8.x] Upgrade EUI to v96.1.0 (#194619) (#195141)
# Backport This will backport the following commits from `main` to `8.x`: - [Upgrade EUI to v96.1.0 (#194619)](https://github.com/elastic/kibana/pull/194619) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cee Chen","email":"549407+cee-chen@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-04T17:53:45Z","message":"Upgrade EUI to v96.1.0 (#194619)\n\n`v95.12.0`⏩`v96.1.0`\r\n\r\n_[Questions? Please see our Kibana upgrade\r\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)_\r\n\r\n---\r\n\r\n## [`v96.0.0`](https://github.com/elastic/eui/releases/v96.0.0)\r\n\r\n- Improved `EuiPageHeader`/`EuiPageTemplate.Header`'s responsive UX:\r\n([#8044](https://github.com/elastic/eui/pull/8044))\r\n- `rightSideItems` are no longer pushed to the side by wide `tabs`\r\ncontent\r\n- `rightSideItems` now wrap more responsively at smaller container\r\nwidths\r\n- Updated `EuiDraggable` with a new `usePortal` prop.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n- This prop portals the dragged element to the body, allowing it to\r\nescape stacking contexts which prevents buggy drag positioning in e.g.\r\npopovers, modals, and flyouts.\r\n\r\n**Bug fixes**\r\n\r\n- Fixed `EuiProvider`'s system color mode detection causing errors\r\nduring server-side rendering\r\n([#8040](https://github.com/elastic/eui/pull/8040))\r\n- Fixed an `EuiDataGrid` rendering bug that was causing bouncing\r\nscrollbar issues ([#8041](https://github.com/elastic/eui/pull/8041))\r\n- Fixed `EuiSearchBox` skips input when running with React 18 in Legacy\r\nMode ([#8047](https://github.com/elastic/eui/pull/8047))\r\n\r\n**Deprecations**\r\n\r\n- Deprecated `EuiPopover`'s `hasDragDrop` prop. Use `EuiDraggable`'s new\r\n`usePortal` prop instead.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n\r\n**Breaking changes**\r\n\r\n- Removed the following exported `.css` files:\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n - `@elastic/eui/dist/eui_theme_light.css`\r\n - `@elastic/eui/dist/eui_theme_light.min.css`\r\n - `@elastic/eui/dist/eui_theme_dark.css`\r\n - `@elastic/eui/dist/eui_theme_dark.min.css`\r\n- All EUI components are now on CSS-in-JS. A CSS file/import in\r\nconsuming applications is no longer needed, and is safe to remove.\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n- Removed all `src/theme/legacy` Sass exports\r\n([#8054](https://github.com/elastic/eui/pull/8054))\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass variables:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `$euiButtonColorDisabled`\r\n - `$euiButtonColorDisabledText`\r\n - `$euiButtonColorGhostDisabled`\r\n - `$euiButtonFontWeight`\r\n - `$euiFormControlIconSizes`\r\n - `$euiFormControlLayoutGroupInputHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedBorderRadius`\r\n - `$euiPageSidebarMinWidth`\r\n - `$euiPageDefaultMaxWidth`\r\n - `$euiPanelPaddingModifiers`\r\n - `$euiPanelBorderRadiusModifiers`\r\n - `$euiPanelBackgroundColorModifiers`\r\n - `$euiRangeTrackColor`\r\n - `$euiRangeHighlightColor`\r\n - `$euiRangeThumbHeight`\r\n - `$euiRangeThumbWidth`\r\n - `$euiRangeThumbBorderColor`\r\n - `$euiRangeThumbBackgroundColor`\r\n - `$euiRangeTrackWidth`\r\n - `$euiRangeTrackHeight`\r\n - `$euiRangeTrackCompressedHeight`\r\n - `$euiRangeTrackBorderWidth`\r\n - `$euiRangeTrackBorderColor`\r\n - `$euiRangeTrackRadius`\r\n - `$euiRangeDisabledOpacity`\r\n - `$euiRangeHighlightHeight`\r\n - `$euiRangeHighlightCompressedHeight`\r\n - `$euiRangeHeight`\r\n - `$euiRangeCompressedHeight`\r\n - `$euiTooltipAnimations`\r\n - `$euiTooltipBackgroundColor`\r\n - `$euiTooltipBorderColor`\r\n- Removed the following Sass mixins due to low external usage:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `euiHoverState`\r\n - `euiFocusState`\r\n - `euiDisabledState`\r\n - `euiInteractiveStates`\r\n - `euiFormControlStyle`\r\n - `euiFormControlStyleCompressed`\r\n - `euiFormControlFocusStyle`\r\n - `euiFormControlInvalidStyle`\r\n - `euiFormControlDisabledTextStyle`\r\n - `euiFormControlDisabledStyle`\r\n - `euiFormControlReadOnlyStyle`\r\n - `euiFormControlText`\r\n - `euiFormControlSize`\r\n - `euiFormControlGradient`\r\n - `euiFormControlLayoutPadding`\r\n - `euiFormControlWithIcon`\r\n - `euiFormControlIsLoading`\r\n - `euiFormControlSideBorderRadius`\r\n - `euiPlaceholderPerBrowser`\r\n - `euiHiddenSelectableInput`\r\n - `euiLink`\r\n - `euiLoadingSpinnerBorderColors`\r\n - `euiRangeTrackSize`\r\n - `euiRangeTrackPerBrowser`\r\n - `euiRangeThumbBorder`\r\n - `euiRangeThumbBoxShadow`\r\n - `euiRangeThumbFocusBoxShadow`\r\n - `euiRangeThumbStyle`\r\n - `euiRangeThumbPerBrowser`\r\n - `euiRangeThumbFocus`\r\n - `euiToolTipAnimation`\r\n\r\n## [`v96.1.0`](https://github.com/elastic/eui/releases/v96.1.0)\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass mixins:\r\n([#8055](https://github.com/elastic/eui/pull/8055))\r\n - `euiButton`\r\n - `euiButtonBase`\r\n - `euiButtonFocus`\r\n - `euiButtonContent`\r\n - `euiButtonContentDisabled`\r\n - `euiButtonDefaultStyle`\r\n - `euiButtonFillStyle`\r\n - `euiPanel`\r\n - `euiFormControlDefaultShadow`\r\n - `euiToolTipTitle`","sha":"19e37bf5c52bd0ae3f788ae2b4015c614c901950","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","EUI","v9.0.0","v8.16.0","backport:version"],"number":194619,"url":"https://github.com/elastic/kibana/pull/194619","mergeCommit":{"message":"Upgrade EUI to v96.1.0 (#194619)\n\n`v95.12.0`⏩`v96.1.0`\r\n\r\n_[Questions? Please see our Kibana upgrade\r\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)_\r\n\r\n---\r\n\r\n## [`v96.0.0`](https://github.com/elastic/eui/releases/v96.0.0)\r\n\r\n- Improved `EuiPageHeader`/`EuiPageTemplate.Header`'s responsive UX:\r\n([#8044](https://github.com/elastic/eui/pull/8044))\r\n- `rightSideItems` are no longer pushed to the side by wide `tabs`\r\ncontent\r\n- `rightSideItems` now wrap more responsively at smaller container\r\nwidths\r\n- Updated `EuiDraggable` with a new `usePortal` prop.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n- This prop portals the dragged element to the body, allowing it to\r\nescape stacking contexts which prevents buggy drag positioning in e.g.\r\npopovers, modals, and flyouts.\r\n\r\n**Bug fixes**\r\n\r\n- Fixed `EuiProvider`'s system color mode detection causing errors\r\nduring server-side rendering\r\n([#8040](https://github.com/elastic/eui/pull/8040))\r\n- Fixed an `EuiDataGrid` rendering bug that was causing bouncing\r\nscrollbar issues ([#8041](https://github.com/elastic/eui/pull/8041))\r\n- Fixed `EuiSearchBox` skips input when running with React 18 in Legacy\r\nMode ([#8047](https://github.com/elastic/eui/pull/8047))\r\n\r\n**Deprecations**\r\n\r\n- Deprecated `EuiPopover`'s `hasDragDrop` prop. Use `EuiDraggable`'s new\r\n`usePortal` prop instead.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n\r\n**Breaking changes**\r\n\r\n- Removed the following exported `.css` files:\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n - `@elastic/eui/dist/eui_theme_light.css`\r\n - `@elastic/eui/dist/eui_theme_light.min.css`\r\n - `@elastic/eui/dist/eui_theme_dark.css`\r\n - `@elastic/eui/dist/eui_theme_dark.min.css`\r\n- All EUI components are now on CSS-in-JS. A CSS file/import in\r\nconsuming applications is no longer needed, and is safe to remove.\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n- Removed all `src/theme/legacy` Sass exports\r\n([#8054](https://github.com/elastic/eui/pull/8054))\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass variables:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `$euiButtonColorDisabled`\r\n - `$euiButtonColorDisabledText`\r\n - `$euiButtonColorGhostDisabled`\r\n - `$euiButtonFontWeight`\r\n - `$euiFormControlIconSizes`\r\n - `$euiFormControlLayoutGroupInputHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedBorderRadius`\r\n - `$euiPageSidebarMinWidth`\r\n - `$euiPageDefaultMaxWidth`\r\n - `$euiPanelPaddingModifiers`\r\n - `$euiPanelBorderRadiusModifiers`\r\n - `$euiPanelBackgroundColorModifiers`\r\n - `$euiRangeTrackColor`\r\n - `$euiRangeHighlightColor`\r\n - `$euiRangeThumbHeight`\r\n - `$euiRangeThumbWidth`\r\n - `$euiRangeThumbBorderColor`\r\n - `$euiRangeThumbBackgroundColor`\r\n - `$euiRangeTrackWidth`\r\n - `$euiRangeTrackHeight`\r\n - `$euiRangeTrackCompressedHeight`\r\n - `$euiRangeTrackBorderWidth`\r\n - `$euiRangeTrackBorderColor`\r\n - `$euiRangeTrackRadius`\r\n - `$euiRangeDisabledOpacity`\r\n - `$euiRangeHighlightHeight`\r\n - `$euiRangeHighlightCompressedHeight`\r\n - `$euiRangeHeight`\r\n - `$euiRangeCompressedHeight`\r\n - `$euiTooltipAnimations`\r\n - `$euiTooltipBackgroundColor`\r\n - `$euiTooltipBorderColor`\r\n- Removed the following Sass mixins due to low external usage:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `euiHoverState`\r\n - `euiFocusState`\r\n - `euiDisabledState`\r\n - `euiInteractiveStates`\r\n - `euiFormControlStyle`\r\n - `euiFormControlStyleCompressed`\r\n - `euiFormControlFocusStyle`\r\n - `euiFormControlInvalidStyle`\r\n - `euiFormControlDisabledTextStyle`\r\n - `euiFormControlDisabledStyle`\r\n - `euiFormControlReadOnlyStyle`\r\n - `euiFormControlText`\r\n - `euiFormControlSize`\r\n - `euiFormControlGradient`\r\n - `euiFormControlLayoutPadding`\r\n - `euiFormControlWithIcon`\r\n - `euiFormControlIsLoading`\r\n - `euiFormControlSideBorderRadius`\r\n - `euiPlaceholderPerBrowser`\r\n - `euiHiddenSelectableInput`\r\n - `euiLink`\r\n - `euiLoadingSpinnerBorderColors`\r\n - `euiRangeTrackSize`\r\n - `euiRangeTrackPerBrowser`\r\n - `euiRangeThumbBorder`\r\n - `euiRangeThumbBoxShadow`\r\n - `euiRangeThumbFocusBoxShadow`\r\n - `euiRangeThumbStyle`\r\n - `euiRangeThumbPerBrowser`\r\n - `euiRangeThumbFocus`\r\n - `euiToolTipAnimation`\r\n\r\n## [`v96.1.0`](https://github.com/elastic/eui/releases/v96.1.0)\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass mixins:\r\n([#8055](https://github.com/elastic/eui/pull/8055))\r\n - `euiButton`\r\n - `euiButtonBase`\r\n - `euiButtonFocus`\r\n - `euiButtonContent`\r\n - `euiButtonContentDisabled`\r\n - `euiButtonDefaultStyle`\r\n - `euiButtonFillStyle`\r\n - `euiPanel`\r\n - `euiFormControlDefaultShadow`\r\n - `euiToolTipTitle`","sha":"19e37bf5c52bd0ae3f788ae2b4015c614c901950"}},"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/194619","number":194619,"mergeCommit":{"message":"Upgrade EUI to v96.1.0 (#194619)\n\n`v95.12.0`⏩`v96.1.0`\r\n\r\n_[Questions? Please see our Kibana upgrade\r\nFAQ.](https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md#faq-for-kibana-teams)_\r\n\r\n---\r\n\r\n## [`v96.0.0`](https://github.com/elastic/eui/releases/v96.0.0)\r\n\r\n- Improved `EuiPageHeader`/`EuiPageTemplate.Header`'s responsive UX:\r\n([#8044](https://github.com/elastic/eui/pull/8044))\r\n- `rightSideItems` are no longer pushed to the side by wide `tabs`\r\ncontent\r\n- `rightSideItems` now wrap more responsively at smaller container\r\nwidths\r\n- Updated `EuiDraggable` with a new `usePortal` prop.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n- This prop portals the dragged element to the body, allowing it to\r\nescape stacking contexts which prevents buggy drag positioning in e.g.\r\npopovers, modals, and flyouts.\r\n\r\n**Bug fixes**\r\n\r\n- Fixed `EuiProvider`'s system color mode detection causing errors\r\nduring server-side rendering\r\n([#8040](https://github.com/elastic/eui/pull/8040))\r\n- Fixed an `EuiDataGrid` rendering bug that was causing bouncing\r\nscrollbar issues ([#8041](https://github.com/elastic/eui/pull/8041))\r\n- Fixed `EuiSearchBox` skips input when running with React 18 in Legacy\r\nMode ([#8047](https://github.com/elastic/eui/pull/8047))\r\n\r\n**Deprecations**\r\n\r\n- Deprecated `EuiPopover`'s `hasDragDrop` prop. Use `EuiDraggable`'s new\r\n`usePortal` prop instead.\r\n([#8048](https://github.com/elastic/eui/pull/8048))\r\n\r\n**Breaking changes**\r\n\r\n- Removed the following exported `.css` files:\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n - `@elastic/eui/dist/eui_theme_light.css`\r\n - `@elastic/eui/dist/eui_theme_light.min.css`\r\n - `@elastic/eui/dist/eui_theme_dark.css`\r\n - `@elastic/eui/dist/eui_theme_dark.min.css`\r\n- All EUI components are now on CSS-in-JS. A CSS file/import in\r\nconsuming applications is no longer needed, and is safe to remove.\r\n([#8045](https://github.com/elastic/eui/pull/8045))\r\n- Removed all `src/theme/legacy` Sass exports\r\n([#8054](https://github.com/elastic/eui/pull/8054))\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass variables:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `$euiButtonColorDisabled`\r\n - `$euiButtonColorDisabledText`\r\n - `$euiButtonColorGhostDisabled`\r\n - `$euiButtonFontWeight`\r\n - `$euiFormControlIconSizes`\r\n - `$euiFormControlLayoutGroupInputHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedHeight`\r\n - `$euiFormControlLayoutGroupInputCompressedBorderRadius`\r\n - `$euiPageSidebarMinWidth`\r\n - `$euiPageDefaultMaxWidth`\r\n - `$euiPanelPaddingModifiers`\r\n - `$euiPanelBorderRadiusModifiers`\r\n - `$euiPanelBackgroundColorModifiers`\r\n - `$euiRangeTrackColor`\r\n - `$euiRangeHighlightColor`\r\n - `$euiRangeThumbHeight`\r\n - `$euiRangeThumbWidth`\r\n - `$euiRangeThumbBorderColor`\r\n - `$euiRangeThumbBackgroundColor`\r\n - `$euiRangeTrackWidth`\r\n - `$euiRangeTrackHeight`\r\n - `$euiRangeTrackCompressedHeight`\r\n - `$euiRangeTrackBorderWidth`\r\n - `$euiRangeTrackBorderColor`\r\n - `$euiRangeTrackRadius`\r\n - `$euiRangeDisabledOpacity`\r\n - `$euiRangeHighlightHeight`\r\n - `$euiRangeHighlightCompressedHeight`\r\n - `$euiRangeHeight`\r\n - `$euiRangeCompressedHeight`\r\n - `$euiTooltipAnimations`\r\n - `$euiTooltipBackgroundColor`\r\n - `$euiTooltipBorderColor`\r\n- Removed the following Sass mixins due to low external usage:\r\n([#8031](https://github.com/elastic/eui/pull/8031))\r\n - `euiHoverState`\r\n - `euiFocusState`\r\n - `euiDisabledState`\r\n - `euiInteractiveStates`\r\n - `euiFormControlStyle`\r\n - `euiFormControlStyleCompressed`\r\n - `euiFormControlFocusStyle`\r\n - `euiFormControlInvalidStyle`\r\n - `euiFormControlDisabledTextStyle`\r\n - `euiFormControlDisabledStyle`\r\n - `euiFormControlReadOnlyStyle`\r\n - `euiFormControlText`\r\n - `euiFormControlSize`\r\n - `euiFormControlGradient`\r\n - `euiFormControlLayoutPadding`\r\n - `euiFormControlWithIcon`\r\n - `euiFormControlIsLoading`\r\n - `euiFormControlSideBorderRadius`\r\n - `euiPlaceholderPerBrowser`\r\n - `euiHiddenSelectableInput`\r\n - `euiLink`\r\n - `euiLoadingSpinnerBorderColors`\r\n - `euiRangeTrackSize`\r\n - `euiRangeTrackPerBrowser`\r\n - `euiRangeThumbBorder`\r\n - `euiRangeThumbBoxShadow`\r\n - `euiRangeThumbFocusBoxShadow`\r\n - `euiRangeThumbStyle`\r\n - `euiRangeThumbPerBrowser`\r\n - `euiRangeThumbFocus`\r\n - `euiToolTipAnimation`\r\n\r\n## [`v96.1.0`](https://github.com/elastic/eui/releases/v96.1.0)\r\n\r\n**CSS-in-JS conversions**\r\n\r\n- Removed the following component-specific Sass mixins:\r\n([#8055](https://github.com/elastic/eui/pull/8055))\r\n - `euiButton`\r\n - `euiButtonBase`\r\n - `euiButtonFocus`\r\n - `euiButtonContent`\r\n - `euiButtonContentDisabled`\r\n - `euiButtonDefaultStyle`\r\n - `euiButtonFillStyle`\r\n - `euiPanel`\r\n - `euiFormControlDefaultShadow`\r\n - `euiToolTipTitle`","sha":"19e37bf5c52bd0ae3f788ae2b4015c614c901950"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
eeee8f7d4d
|
[8.x] [ML] AIOps: Use package instead of context for using field stats flyout (#194517) (#194710)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] AIOps: Use package instead of context for using field stats flyout (#194517)](https://github.com/elastic/kibana/pull/194517) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-10-02T13:23:23Z","message":"[ML] AIOps: Use package instead of context for using field stats flyout (#194517)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/187772.\r\nFollow up to #193657.\r\n\r\nThe previous PR #193657 moved `FieldStatsFlyout` to a package, the\r\n`aiops` plugin didn't make full use of that refactor by still passing in\r\nthe flyout into the app context.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"eebfba4f9bfe2592ce92d35aed9cf3c0c8540130","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Feature:ML/AIOps","v8.16.0","backport:version"],"title":"[ML] AIOps: Use package instead of context for using field stats flyout","number":194517,"url":"https://github.com/elastic/kibana/pull/194517","mergeCommit":{"message":"[ML] AIOps: Use package instead of context for using field stats flyout (#194517)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/187772.\r\nFollow up to #193657.\r\n\r\nThe previous PR #193657 moved `FieldStatsFlyout` to a package, the\r\n`aiops` plugin didn't make full use of that refactor by still passing in\r\nthe flyout into the app context.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"eebfba4f9bfe2592ce92d35aed9cf3c0c8540130"}},"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/194517","number":194517,"mergeCommit":{"message":"[ML] AIOps: Use package instead of context for using field stats flyout (#194517)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/187772.\r\nFollow up to #193657.\r\n\r\nThe previous PR #193657 moved `FieldStatsFlyout` to a package, the\r\n`aiops` plugin didn't make full use of that refactor by still passing in\r\nthe flyout into the app context.\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"eebfba4f9bfe2592ce92d35aed9cf3c0c8540130"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
28e012b2ed
|
[8.x] [ML] Various fixes for possible prototype pollution vulnerabilities (#194529) (#194660)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Various fixes for possible prototype pollution vulnerabilities (#194529)](https://github.com/elastic/kibana/pull/194529) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2024-10-02T07:47:19Z","message":"[ML] Various fixes for possible prototype pollution vulnerabilities (#194529)\n\nFixes potential prototype pollution vulnerability in `setNestedProperty`\r\nfunction.\r\nFixes incomplete string escaping issue in ML's saved object service.","sha":"d1f24b050b53cc7b13fbc47b6de3c5f69606e88e","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","v8.16.0","backport:version"],"title":"[ML] Various fixes for possible prototype pollution vulnerabilities","number":194529,"url":"https://github.com/elastic/kibana/pull/194529","mergeCommit":{"message":"[ML] Various fixes for possible prototype pollution vulnerabilities (#194529)\n\nFixes potential prototype pollution vulnerability in `setNestedProperty`\r\nfunction.\r\nFixes incomplete string escaping issue in ML's saved object service.","sha":"d1f24b050b53cc7b13fbc47b6de3c5f69606e88e"}},"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/194529","number":194529,"mergeCommit":{"message":"[ML] Various fixes for possible prototype pollution vulnerabilities (#194529)\n\nFixes potential prototype pollution vulnerability in `setNestedProperty`\r\nfunction.\r\nFixes incomplete string escaping issue in ML's saved object service.","sha":"d1f24b050b53cc7b13fbc47b6de3c5f69606e88e"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
1f4ffc4b3f
|
[8.x] [ML] Anomaly swim lane: Fix disappearing rows per page button (#194531) (#194674)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly swim lane: Fix disappearing rows per page button (#194531)](https://github.com/elastic/kibana/pull/194531) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-02T09:50:04Z","message":"[ML] Anomaly swim lane: Fix disappearing rows per page button (#194531)\n\n## Summary\r\n\r\nFix for: [#194027](https://github.com/elastic/kibana/issues/194027).\r\nFixed issue with disappearing `rows per page` button.\r\nEnhanced the logic to display only relevant pagination options, showing\r\nthe first larger option, which works like 'show all'.\r\n* For example, if there are 23 results, the available `rows per page`\r\noptions will be: `5,10,20,50`.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29c3f0db-84b8-4a0c-b4b5-a722cfc490c4","sha":"c84ee4c5293718ce4b4f7c8b6e4f502449b5aa34","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v9.0.0","Team:ML","v8.16.0","backport:version","v8.15.3"],"title":"[ML] Anomaly swim lane: Fix disappearing rows per page button","number":194531,"url":"https://github.com/elastic/kibana/pull/194531","mergeCommit":{"message":"[ML] Anomaly swim lane: Fix disappearing rows per page button (#194531)\n\n## Summary\r\n\r\nFix for: [#194027](https://github.com/elastic/kibana/issues/194027).\r\nFixed issue with disappearing `rows per page` button.\r\nEnhanced the logic to display only relevant pagination options, showing\r\nthe first larger option, which works like 'show all'.\r\n* For example, if there are 23 results, the available `rows per page`\r\noptions will be: `5,10,20,50`.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29c3f0db-84b8-4a0c-b4b5-a722cfc490c4","sha":"c84ee4c5293718ce4b4f7c8b6e4f502449b5aa34"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194531","number":194531,"mergeCommit":{"message":"[ML] Anomaly swim lane: Fix disappearing rows per page button (#194531)\n\n## Summary\r\n\r\nFix for: [#194027](https://github.com/elastic/kibana/issues/194027).\r\nFixed issue with disappearing `rows per page` button.\r\nEnhanced the logic to display only relevant pagination options, showing\r\nthe first larger option, which works like 'show all'.\r\n* For example, if there are 23 results, the available `rows per page`\r\noptions will be: `5,10,20,50`.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/29c3f0db-84b8-4a0c-b4b5-a722cfc490c4","sha":"c84ee4c5293718ce4b4f7c8b6e4f502449b5aa34"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
84b1122197
|
[8.x] Update dependency @elastic/charts to v67 (main) (#193694) (#194665)
# Backport This will backport the following commits from `main` to `8.x`: - [Update dependency @elastic/charts to v67 (main) (#193694)](https://github.com/elastic/kibana/pull/193694) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-02T08:52:56Z","message":"Update dependency @elastic/charts to v67 (main) (#193694)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n| [@elastic/charts](https://togithub.com/elastic/elastic-charts) |\r\ndependencies | major | [`66.1.1` ->\r\n`67.0.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/66.1.1/67.0.0)\r\n|\r\n\r\n---\r\n### Breaking changes\r\n\r\nElastic-charts theme API for line and area charts has changed:\r\n- the `point.visible` type for line and area charts is now a union\r\nbetween `'always' | 'never' | 'auto'`. Always and Never will replace the\r\nprevious boolean configuration, `auto` instead will provide a logic to\r\nshow the points only of the distance between consecutive points is\r\nbigger than the `pointVisibilityMinDistance`.\r\n- the isolatedPoint style for line and area doesn't contain the `radius`\r\nparameter anymore. The radius is derived from the `line.strokeWidth`\r\nparameter.\r\n\r\nCo-authored-by: Marco Vettorello <marco.vettorello@elastic.co>","sha":"30ef0ecb3c9d91b8f111f96bf0e024d03c49304b","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","💝community","v9.0.0","backport:prev-minor","Team:Obs AI Assistant","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","apm:review"],"title":"Update dependency @elastic/charts to v67 (main)","number":193694,"url":"https://github.com/elastic/kibana/pull/193694","mergeCommit":{"message":"Update dependency @elastic/charts to v67 (main) (#193694)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n| [@elastic/charts](https://togithub.com/elastic/elastic-charts) |\r\ndependencies | major | [`66.1.1` ->\r\n`67.0.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/66.1.1/67.0.0)\r\n|\r\n\r\n---\r\n### Breaking changes\r\n\r\nElastic-charts theme API for line and area charts has changed:\r\n- the `point.visible` type for line and area charts is now a union\r\nbetween `'always' | 'never' | 'auto'`. Always and Never will replace the\r\nprevious boolean configuration, `auto` instead will provide a logic to\r\nshow the points only of the distance between consecutive points is\r\nbigger than the `pointVisibilityMinDistance`.\r\n- the isolatedPoint style for line and area doesn't contain the `radius`\r\nparameter anymore. The radius is derived from the `line.strokeWidth`\r\nparameter.\r\n\r\nCo-authored-by: Marco Vettorello <marco.vettorello@elastic.co>","sha":"30ef0ecb3c9d91b8f111f96bf0e024d03c49304b"}},"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/193694","number":193694,"mergeCommit":{"message":"Update dependency @elastic/charts to v67 (main) (#193694)\n\nThis PR contains the following updates:\r\n\r\n| Package | Type | Update | Change |\r\n|---|---|---|---|\r\n| [@elastic/charts](https://togithub.com/elastic/elastic-charts) |\r\ndependencies | major | [`66.1.1` ->\r\n`67.0.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/66.1.1/67.0.0)\r\n|\r\n\r\n---\r\n### Breaking changes\r\n\r\nElastic-charts theme API for line and area charts has changed:\r\n- the `point.visible` type for line and area charts is now a union\r\nbetween `'always' | 'never' | 'auto'`. Always and Never will replace the\r\nprevious boolean configuration, `auto` instead will provide a logic to\r\nshow the points only of the distance between consecutive points is\r\nbigger than the `pointVisibilityMinDistance`.\r\n- the isolatedPoint style for line and area doesn't contain the `radius`\r\nparameter anymore. The radius is derived from the `line.strokeWidth`\r\nparameter.\r\n\r\nCo-authored-by: Marco Vettorello <marco.vettorello@elastic.co>","sha":"30ef0ecb3c9d91b8f111f96bf0e024d03c49304b"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
631cba307b
|
[8.x] [React@18] Upgrade @types to React 18 (#194144) (#194536)
# Backport This will backport the following commits from `main` to `8.x`: - [[React@18] Upgrade @types to React 18 (#194144)](https://github.com/elastic/kibana/pull/194144) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2024-10-01T09:40:11Z","message":"[React@18] Upgrade @types to React 18 (#194144)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/138222\r\n\r\nThis PR finilizes the breaking type fixes that are needed for upgrade to\r\nReact@18.\r\nMost of the remaining issues are muted with \"@ts-expect-error\" are\r\ntricky or could be runtime bugs that need to be looked at.\r\n\r\n**Since the types changes are backward compatible (except the new APIs)\r\nwe can upgrade to @types/react@18 now so that we \"save\" the progress and\r\nall the code in Kibana from now on is written in compatbile for react@18\r\nway from types perspective.**","sha":"bdd57b64fe19683c481f673d6f1571f91379e730","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:SharedUX","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","Team:obs-ux-management","apm:review"],"title":"[React@18] Upgrade @types to React 18","number":194144,"url":"https://github.com/elastic/kibana/pull/194144","mergeCommit":{"message":"[React@18] Upgrade @types to React 18 (#194144)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/138222\r\n\r\nThis PR finilizes the breaking type fixes that are needed for upgrade to\r\nReact@18.\r\nMost of the remaining issues are muted with \"@ts-expect-error\" are\r\ntricky or could be runtime bugs that need to be looked at.\r\n\r\n**Since the types changes are backward compatible (except the new APIs)\r\nwe can upgrade to @types/react@18 now so that we \"save\" the progress and\r\nall the code in Kibana from now on is written in compatbile for react@18\r\nway from types perspective.**","sha":"bdd57b64fe19683c481f673d6f1571f91379e730"}},"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/194144","number":194144,"mergeCommit":{"message":"[React@18] Upgrade @types to React 18 (#194144)\n\n## Summary\r\n\r\nPart of https://github.com/elastic/kibana/issues/138222\r\n\r\nThis PR finilizes the breaking type fixes that are needed for upgrade to\r\nReact@18.\r\nMost of the remaining issues are muted with \"@ts-expect-error\" are\r\ntricky or could be runtime bugs that need to be looked at.\r\n\r\n**Since the types changes are backward compatible (except the new APIs)\r\nwe can upgrade to @types/react@18 now so that we \"save\" the progress and\r\nall the code in Kibana from now on is written in compatbile for react@18\r\nway from types perspective.**","sha":"bdd57b64fe19683c481f673d6f1571f91379e730"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
|
f14c419d51
|
[8.x] [ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890) (#194527)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890)](https://github.com/elastic/kibana/pull/193890) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-01T08:32:37Z","message":"[ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890)\n\n## Summary\r\n\r\nFix for [#138193](https://github.com/elastic/kibana/issues/138193)\r\nI didn't find any relation between user permissions and the issue.\r\nThe error mentioned in the issue doesn't come from the ML package and is\r\nunrelated to the problem.\r\nThe view was visible due to the initial state of `jobsExist`. Added\r\nadditional loading state to prevent screen flickering.\r\n\r\nDisabled automatic display of the job selection flyout when no jobs are\r\navailable.\r\n\r\nAfter:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a8c6e5e2-ebcc-4320-b5be-f586ca6c0672","sha":"a2e995a9e735a50f54a314197ab1c2812a8416fb","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Data Frame Analytics","v9.0.0","Team:ML","v8.16.0","backport:version","v8.15.3"],"title":"[ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available","number":193890,"url":"https://github.com/elastic/kibana/pull/193890","mergeCommit":{"message":"[ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890)\n\n## Summary\r\n\r\nFix for [#138193](https://github.com/elastic/kibana/issues/138193)\r\nI didn't find any relation between user permissions and the issue.\r\nThe error mentioned in the issue doesn't come from the ML package and is\r\nunrelated to the problem.\r\nThe view was visible due to the initial state of `jobsExist`. Added\r\nadditional loading state to prevent screen flickering.\r\n\r\nDisabled automatic display of the job selection flyout when no jobs are\r\navailable.\r\n\r\nAfter:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a8c6e5e2-ebcc-4320-b5be-f586ca6c0672","sha":"a2e995a9e735a50f54a314197ab1c2812a8416fb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193890","number":193890,"mergeCommit":{"message":"[ML] Data frame analytics: Fix screen flickering in Results Explorer and Analytics Map when no jobs are available (#193890)\n\n## Summary\r\n\r\nFix for [#138193](https://github.com/elastic/kibana/issues/138193)\r\nI didn't find any relation between user permissions and the issue.\r\nThe error mentioned in the issue doesn't come from the ML package and is\r\nunrelated to the problem.\r\nThe view was visible due to the initial state of `jobsExist`. Added\r\nadditional loading state to prevent screen flickering.\r\n\r\nDisabled automatic display of the job selection flyout when no jobs are\r\navailable.\r\n\r\nAfter:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/a8c6e5e2-ebcc-4320-b5be-f586ca6c0672","sha":"a2e995a9e735a50f54a314197ab1c2812a8416fb"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
9e1829eacd
|
[8.x] [ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts (#194119) (#194426)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts (#194119)](https://github.com/elastic/kibana/pull/194119) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-30T12:17:29Z","message":"[ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts (#194119)\n\n## Summary\r\n\r\nFix for [#193885](https://github.com/elastic/kibana/issues/193885)\r\n\r\nSingle metric viewer:\r\n\r\n\r\nAnomaly explorer:\r\n| Before | After |\r\n| ------------- | ------------- |\r\n|\r\n\r\n| \r\n|","sha":"32144fc0244566db557646ff35cc82c29734df72","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v9.0.0","Team:ML","v8.16.0","backport:version"],"title":"[ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts","number":194119,"url":"https://github.com/elastic/kibana/pull/194119","mergeCommit":{"message":"[ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts (#194119)\n\n## Summary\r\n\r\nFix for [#193885](https://github.com/elastic/kibana/issues/193885)\r\n\r\nSingle metric viewer:\r\n\r\n\r\nAnomaly explorer:\r\n| Before | After |\r\n| ------------- | ------------- |\r\n|\r\n\r\n| \r\n|","sha":"32144fc0244566db557646ff35cc82c29734df72"}},"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/194119","number":194119,"mergeCommit":{"message":"[ML] Anomaly explorer: Show Data Gaps and Connect Anomalous Points on Single Metric Charts (#194119)\n\n## Summary\r\n\r\nFix for [#193885](https://github.com/elastic/kibana/issues/193885)\r\n\r\nSingle metric viewer:\r\n\r\n\r\nAnomaly explorer:\r\n| Before | After |\r\n| ------------- | ------------- |\r\n|\r\n\r\n| \r\n|","sha":"32144fc0244566db557646ff35cc82c29734df72"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
366679cebf
|
[8.x] [ML] Single Metric Viewer: Enable cross-filtering for 'by', 'over' and 'partition' field values (#193255) (#194280)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Single Metric Viewer: Enable cross-filtering for 'by', 'over' and 'partition' field values (#193255)](https://github.com/elastic/kibana/pull/193255) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-27T10:30:53Z","message":"[ML] Single Metric Viewer: Enable cross-filtering for 'by', 'over' and 'partition' field values (#193255)\n\n## Summary\r\n\r\nEnables cross-filtering for 'by', 'over' and 'partition' field values in\r\nthe Single Metric Viewer.\r\n\r\nFixes [#171932]( |
||
|
d5dd72b392
|
[8.x] [ML] Updating calendars schema (#194160) (#194181)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Updating calendars schema (#194160)](https://github.com/elastic/kibana/pull/194160) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2024-09-26T15:57:54Z","message":"[ML] Updating calendars schema (#194160)\n\nUpdating schema to add `skip_result`, `skip_model_update` and\r\n`force_time_shift`","sha":"8e29141c344d415087419c605bba7f07caa57cf4","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","v8.16.0","backport:version"],"title":"[ML] Updating calendars schema","number":194160,"url":"https://github.com/elastic/kibana/pull/194160","mergeCommit":{"message":"[ML] Updating calendars schema (#194160)\n\nUpdating schema to add `skip_result`, `skip_model_update` and\r\n`force_time_shift`","sha":"8e29141c344d415087419c605bba7f07caa57cf4"}},"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/194160","number":194160,"mergeCommit":{"message":"[ML] Updating calendars schema (#194160)\n\nUpdating schema to add `skip_result`, `skip_model_update` and\r\n`force_time_shift`","sha":"8e29141c344d415087419c605bba7f07caa57cf4"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
e72fd8f18a
|
[8.x] [ML] Redesign start/update model deployment dialog (#190243) (#194143)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Redesign start/update model deployment dialog (#190243)](https://github.com/elastic/kibana/pull/190243) <!--- Backport version: 9.4.3 --> ### 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":"2024-09-26T13:26:31Z","message":"[ML] Redesign start/update model deployment dialog (#190243)\n\n## Summary\r\n\r\n#### Notes for reviewers\r\n\r\nhttps://github.com/elastic/elasticsearch/pull/113455 PR has to be merged\r\nfirst to support `min_number_of_allocation: 0`. At the moment it's not\r\npossible to start a `Low` vCPUs usage deployment from the UI.\r\n\r\nResolves #189975\r\n\r\n- Updates the Start/Update model deployment dialogue, replacing\r\nallocation and threading params with use cases and advanced settings\r\nwith vCPUs/VCUs controls.\r\n\r\nThe vCPUs (or VCUs for serverless env) are derived from the number of\r\nallocations times threads per allocation.\r\n\r\n_Optimised for ingest_ sets 1 thread per allocation.\r\n_Optimised for search_ for low vCPUs level sets 2 threads per\r\nallocation, and the maximum available number of threads for medium and\r\nhigh. This value is limited to the `max_single_ml_node_processors`.\r\n\r\nvCPUs control acts differently depending on \"Adaptive resources\". \r\n\r\n- When On, it enables `adaptive_allocations` and sets the range\r\n`min_number_of_allocations` and `max_number_of_allocations` based on the\r\nuse-case (threads per allocation) and cluster configuration.\r\n- For cloud deployments with enabled ML autoscaling, vCPUs ranges are 1\r\n-2 for, 2-32, 33-max\r\n- For on-prem deployments and cloud deployments with disabled\r\nautoscaling, vCPUs ranges are based on the hardware limitations. E.g.\r\nwith `total_ml_processors` = 32, and `max_single_ml_node_processors` =\r\n16 ranges are 1-2, 3-16, 17-32.\r\n- When Off, it sets a static `number_of_allocations`. The number of\r\nallocations is an upper bound of the ranges mentioned above.\r\n\r\nFor serverless deployments adaptive resources are enabled at all times,\r\nand control is hidden.\r\n\r\n<img width=\"795\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20b2528f-b631-49f9-82f8-fef6175873fd\">\r\n\r\n- Start deployment modal checks if there is a deployment optimized for a\r\ncertain use case, and sets another use case by default. E.g. If an\r\noptimized deployment for a certain use case (e.g., ingestion) is found,\r\nthe modal will set a different use case (e.g., search) as the default\r\nupon opening.\r\n\r\n- For the cloud deployments, also display a message about vCPU values in\r\nthe Cloud Console and a link to edit the deployment:\r\n<img width=\"791\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2f98ebca-579e-43c1-ab78-e0dd38ce4786\">\r\n\r\n- For Serverless, the \"Adaptive Resources\" control is hidden, as\r\nadaptive allocations are enabled at all times.\r\n<img width=\"659\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8133ebf9-6b2b-4fea-95f1-7351cfcf85b6\">\r\n\r\n- Update action was updated accordingly. As it is not possible to update\r\nthreads per allocation, the optimize control is disabled. Advanced\r\nsettings are expanded by default and allows the user to adjust vCPUs\r\nlevel and enable/disable adaptive resources.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/13c3f0bc-4436-4528-8641-d33eb5384ea2\">\r\n\r\n\r\n- Indicate if adaptive allocations are enabled in the expanded row \r\n<img width=\"1322\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/894916df-4c77-4e75-b175-229131b8ecc8\">\r\n\r\n\r\n\r\n### Checklist\r\n\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- [ ]\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- [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"718444fec14ae2d22894cca1349a7e577443dd99","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","v9.0.0","Feature:3rd Party Models","Team:ML","v8.16.0","backport:version"],"title":"[ML] Redesign start/update model deployment dialog ","number":190243,"url":"https://github.com/elastic/kibana/pull/190243","mergeCommit":{"message":"[ML] Redesign start/update model deployment dialog (#190243)\n\n## Summary\r\n\r\n#### Notes for reviewers\r\n\r\nhttps://github.com/elastic/elasticsearch/pull/113455 PR has to be merged\r\nfirst to support `min_number_of_allocation: 0`. At the moment it's not\r\npossible to start a `Low` vCPUs usage deployment from the UI.\r\n\r\nResolves #189975\r\n\r\n- Updates the Start/Update model deployment dialogue, replacing\r\nallocation and threading params with use cases and advanced settings\r\nwith vCPUs/VCUs controls.\r\n\r\nThe vCPUs (or VCUs for serverless env) are derived from the number of\r\nallocations times threads per allocation.\r\n\r\n_Optimised for ingest_ sets 1 thread per allocation.\r\n_Optimised for search_ for low vCPUs level sets 2 threads per\r\nallocation, and the maximum available number of threads for medium and\r\nhigh. This value is limited to the `max_single_ml_node_processors`.\r\n\r\nvCPUs control acts differently depending on \"Adaptive resources\". \r\n\r\n- When On, it enables `adaptive_allocations` and sets the range\r\n`min_number_of_allocations` and `max_number_of_allocations` based on the\r\nuse-case (threads per allocation) and cluster configuration.\r\n- For cloud deployments with enabled ML autoscaling, vCPUs ranges are 1\r\n-2 for, 2-32, 33-max\r\n- For on-prem deployments and cloud deployments with disabled\r\nautoscaling, vCPUs ranges are based on the hardware limitations. E.g.\r\nwith `total_ml_processors` = 32, and `max_single_ml_node_processors` =\r\n16 ranges are 1-2, 3-16, 17-32.\r\n- When Off, it sets a static `number_of_allocations`. The number of\r\nallocations is an upper bound of the ranges mentioned above.\r\n\r\nFor serverless deployments adaptive resources are enabled at all times,\r\nand control is hidden.\r\n\r\n<img width=\"795\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20b2528f-b631-49f9-82f8-fef6175873fd\">\r\n\r\n- Start deployment modal checks if there is a deployment optimized for a\r\ncertain use case, and sets another use case by default. E.g. If an\r\noptimized deployment for a certain use case (e.g., ingestion) is found,\r\nthe modal will set a different use case (e.g., search) as the default\r\nupon opening.\r\n\r\n- For the cloud deployments, also display a message about vCPU values in\r\nthe Cloud Console and a link to edit the deployment:\r\n<img width=\"791\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2f98ebca-579e-43c1-ab78-e0dd38ce4786\">\r\n\r\n- For Serverless, the \"Adaptive Resources\" control is hidden, as\r\nadaptive allocations are enabled at all times.\r\n<img width=\"659\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8133ebf9-6b2b-4fea-95f1-7351cfcf85b6\">\r\n\r\n- Update action was updated accordingly. As it is not possible to update\r\nthreads per allocation, the optimize control is disabled. Advanced\r\nsettings are expanded by default and allows the user to adjust vCPUs\r\nlevel and enable/disable adaptive resources.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/13c3f0bc-4436-4528-8641-d33eb5384ea2\">\r\n\r\n\r\n- Indicate if adaptive allocations are enabled in the expanded row \r\n<img width=\"1322\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/894916df-4c77-4e75-b175-229131b8ecc8\">\r\n\r\n\r\n\r\n### Checklist\r\n\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- [ ]\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- [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"718444fec14ae2d22894cca1349a7e577443dd99"}},"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/190243","number":190243,"mergeCommit":{"message":"[ML] Redesign start/update model deployment dialog (#190243)\n\n## Summary\r\n\r\n#### Notes for reviewers\r\n\r\nhttps://github.com/elastic/elasticsearch/pull/113455 PR has to be merged\r\nfirst to support `min_number_of_allocation: 0`. At the moment it's not\r\npossible to start a `Low` vCPUs usage deployment from the UI.\r\n\r\nResolves #189975\r\n\r\n- Updates the Start/Update model deployment dialogue, replacing\r\nallocation and threading params with use cases and advanced settings\r\nwith vCPUs/VCUs controls.\r\n\r\nThe vCPUs (or VCUs for serverless env) are derived from the number of\r\nallocations times threads per allocation.\r\n\r\n_Optimised for ingest_ sets 1 thread per allocation.\r\n_Optimised for search_ for low vCPUs level sets 2 threads per\r\nallocation, and the maximum available number of threads for medium and\r\nhigh. This value is limited to the `max_single_ml_node_processors`.\r\n\r\nvCPUs control acts differently depending on \"Adaptive resources\". \r\n\r\n- When On, it enables `adaptive_allocations` and sets the range\r\n`min_number_of_allocations` and `max_number_of_allocations` based on the\r\nuse-case (threads per allocation) and cluster configuration.\r\n- For cloud deployments with enabled ML autoscaling, vCPUs ranges are 1\r\n-2 for, 2-32, 33-max\r\n- For on-prem deployments and cloud deployments with disabled\r\nautoscaling, vCPUs ranges are based on the hardware limitations. E.g.\r\nwith `total_ml_processors` = 32, and `max_single_ml_node_processors` =\r\n16 ranges are 1-2, 3-16, 17-32.\r\n- When Off, it sets a static `number_of_allocations`. The number of\r\nallocations is an upper bound of the ranges mentioned above.\r\n\r\nFor serverless deployments adaptive resources are enabled at all times,\r\nand control is hidden.\r\n\r\n<img width=\"795\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/20b2528f-b631-49f9-82f8-fef6175873fd\">\r\n\r\n- Start deployment modal checks if there is a deployment optimized for a\r\ncertain use case, and sets another use case by default. E.g. If an\r\noptimized deployment for a certain use case (e.g., ingestion) is found,\r\nthe modal will set a different use case (e.g., search) as the default\r\nupon opening.\r\n\r\n- For the cloud deployments, also display a message about vCPU values in\r\nthe Cloud Console and a link to edit the deployment:\r\n<img width=\"791\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/2f98ebca-579e-43c1-ab78-e0dd38ce4786\">\r\n\r\n- For Serverless, the \"Adaptive Resources\" control is hidden, as\r\nadaptive allocations are enabled at all times.\r\n<img width=\"659\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8133ebf9-6b2b-4fea-95f1-7351cfcf85b6\">\r\n\r\n- Update action was updated accordingly. As it is not possible to update\r\nthreads per allocation, the optimize control is disabled. Advanced\r\nsettings are expanded by default and allows the user to adjust vCPUs\r\nlevel and enable/disable adaptive resources.\r\n<img width=\"785\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/13c3f0bc-4436-4528-8641-d33eb5384ea2\">\r\n\r\n\r\n- Indicate if adaptive allocations are enabled in the expanded row \r\n<img width=\"1322\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/894916df-4c77-4e75-b175-229131b8ecc8\">\r\n\r\n\r\n\r\n### Checklist\r\n\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- [ ]\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- [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>","sha":"718444fec14ae2d22894cca1349a7e577443dd99"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
bc2bb0d77a
|
[8.x] [ML] Move FieldStatsFlyout, parseInterval, validators to packages. (#193657) (#193859)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Move FieldStatsFlyout, parseInterval, validators to packages. (#193657)](https://github.com/elastic/kibana/pull/193657) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-09-24T12:00:55Z","message":"[ML] Move FieldStatsFlyout, parseInterval, validators to packages. (#193657)\n\n## Summary\r\n\r\nPart of #159917.\r\n\r\nMoves code from `plugins/ml/common|public` to packages that is used by\r\ntransforms too.\r\n\r\nWhile the transforms plugin is maintained by the ML team too, the\r\ntransform plugin itself is independently available from the ML UI in the\r\nKibana management section. We should try to avoid that the transform\r\nplugin is directly depending on the `ml` plugin. This PR moves some code\r\nfrom `plugins/ml/common|public` to packages so that we can remove `ml`\r\nfrom the list of `requiredBundles` of the `transform` plugin.\r\n\r\nThe packages were created with these commands:\r\n\r\n```\r\nnode scripts/generate package @kbn/ml-field-stats-flyout --dir ./x-pack/packages/ml/field_stats_flyout\r\nnode scripts/generate package @kbn/ml-parse-interval --dir ./x-pack/packages/ml/parse_interval\r\nnode scripts/generate package @kbn/ml-validators --dir ./x-pack/packages/ml/validators\r\n```\r\n\r\nThe following commands were used to check missing jsdoc comments and\r\nexports:\r\n\r\n```\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats exports\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b2d85d5f8f10f7c460c3a3b732844a19c8b20d7b","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:Transforms","v9.0.0","backport:prev-minor","v8.16.0"],"number":193657,"url":"https://github.com/elastic/kibana/pull/193657","mergeCommit":{"message":"[ML] Move FieldStatsFlyout, parseInterval, validators to packages. (#193657)\n\n## Summary\r\n\r\nPart of #159917.\r\n\r\nMoves code from `plugins/ml/common|public` to packages that is used by\r\ntransforms too.\r\n\r\nWhile the transforms plugin is maintained by the ML team too, the\r\ntransform plugin itself is independently available from the ML UI in the\r\nKibana management section. We should try to avoid that the transform\r\nplugin is directly depending on the `ml` plugin. This PR moves some code\r\nfrom `plugins/ml/common|public` to packages so that we can remove `ml`\r\nfrom the list of `requiredBundles` of the `transform` plugin.\r\n\r\nThe packages were created with these commands:\r\n\r\n```\r\nnode scripts/generate package @kbn/ml-field-stats-flyout --dir ./x-pack/packages/ml/field_stats_flyout\r\nnode scripts/generate package @kbn/ml-parse-interval --dir ./x-pack/packages/ml/parse_interval\r\nnode scripts/generate package @kbn/ml-validators --dir ./x-pack/packages/ml/validators\r\n```\r\n\r\nThe following commands were used to check missing jsdoc comments and\r\nexports:\r\n\r\n```\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats exports\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b2d85d5f8f10f7c460c3a3b732844a19c8b20d7b"}},"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/193657","number":193657,"mergeCommit":{"message":"[ML] Move FieldStatsFlyout, parseInterval, validators to packages. (#193657)\n\n## Summary\r\n\r\nPart of #159917.\r\n\r\nMoves code from `plugins/ml/common|public` to packages that is used by\r\ntransforms too.\r\n\r\nWhile the transforms plugin is maintained by the ML team too, the\r\ntransform plugin itself is independently available from the ML UI in the\r\nKibana management section. We should try to avoid that the transform\r\nplugin is directly depending on the `ml` plugin. This PR moves some code\r\nfrom `plugins/ml/common|public` to packages so that we can remove `ml`\r\nfrom the list of `requiredBundles` of the `transform` plugin.\r\n\r\nThe packages were created with these commands:\r\n\r\n```\r\nnode scripts/generate package @kbn/ml-field-stats-flyout --dir ./x-pack/packages/ml/field_stats_flyout\r\nnode scripts/generate package @kbn/ml-parse-interval --dir ./x-pack/packages/ml/parse_interval\r\nnode scripts/generate package @kbn/ml-validators --dir ./x-pack/packages/ml/validators\r\n```\r\n\r\nThe following commands were used to check missing jsdoc comments and\r\nexports:\r\n\r\n```\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-field-stats-flyout --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-parse-interval --stats exports\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats comments\r\nnode scripts/build_api_docs --plugin @kbn/ml-validators --stats exports\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b2d85d5f8f10f7c460c3a3b732844a19c8b20d7b"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
5e064513bf
|
[8.x] [ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix. (#193386) (#193832)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix. (#193386)](https://github.com/elastic/kibana/pull/193386) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-09-24T08:41:46Z","message":"[ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix. (#193386)\n\n## Summary\r\n\r\nField names with `\\n` would fail to render the DFA scatterplot matrix:\r\n\r\n<img width=\"804\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/26e356b8-236d-4255-b556-2ebc2e5db4fc\">\r\n\r\nThis fixes the escaping and adds unit tests.\r\n\r\nThe fix isn't 100% ideal because there are cases when we may end up with\r\nan additional backslash being rendered for labels of the scatterplot.\r\nHowever, all other variations I tried caused rendering problems of the\r\ncharts and rendering would fail completely.\r\n\r\nFor example, just escaping `\\n` without the general backslash escaping\r\ncauses the following Vega error: `Duplicate scale or projection name:\r\n\"child__row_my_numbercolumn_my_number_x\"`\r\n\r\nOn the other hand escaping just the backslash without the additional\r\n`\\n` escaping causes an \"expression parse error\" in in Vega and the\r\nchart wouldn't render.\r\n\r\nNote this PR just focuses on escaping for the Vega spec for the\r\nscatterplot matrix. There are still other places in the UI (data grid\r\nheaders, fields selector).\r\n\r\n<img width=\"792\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/35532741-7a13-4707-b8da-c72dcc8c935b\">\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#kibana-release-notes-process)","sha":"194d6307dc41b6a4a295abc3e412de148e05386e","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug",":ml","release_note:skip","Feature:Data Frame Analytics","v9.0.0","backport:all-open","v8.16.0","v8.15.2","v7.17.25"],"title":"[ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix.","number":193386,"url":"https://github.com/elastic/kibana/pull/193386","mergeCommit":{"message":"[ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix. (#193386)\n\n## Summary\r\n\r\nField names with `\\n` would fail to render the DFA scatterplot matrix:\r\n\r\n<img width=\"804\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/26e356b8-236d-4255-b556-2ebc2e5db4fc\">\r\n\r\nThis fixes the escaping and adds unit tests.\r\n\r\nThe fix isn't 100% ideal because there are cases when we may end up with\r\nan additional backslash being rendered for labels of the scatterplot.\r\nHowever, all other variations I tried caused rendering problems of the\r\ncharts and rendering would fail completely.\r\n\r\nFor example, just escaping `\\n` without the general backslash escaping\r\ncauses the following Vega error: `Duplicate scale or projection name:\r\n\"child__row_my_numbercolumn_my_number_x\"`\r\n\r\nOn the other hand escaping just the backslash without the additional\r\n`\\n` escaping causes an \"expression parse error\" in in Vega and the\r\nchart wouldn't render.\r\n\r\nNote this PR just focuses on escaping for the Vega spec for the\r\nscatterplot matrix. There are still other places in the UI (data grid\r\nheaders, fields selector).\r\n\r\n<img width=\"792\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/35532741-7a13-4707-b8da-c72dcc8c935b\">\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#kibana-release-notes-process)","sha":"194d6307dc41b6a4a295abc3e412de148e05386e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.15","7.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193386","number":193386,"mergeCommit":{"message":"[ML] Data Frame Analytics: Fix field name escaping for Vega based scatterplot matrix. (#193386)\n\n## Summary\r\n\r\nField names with `\\n` would fail to render the DFA scatterplot matrix:\r\n\r\n<img width=\"804\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/26e356b8-236d-4255-b556-2ebc2e5db4fc\">\r\n\r\nThis fixes the escaping and adds unit tests.\r\n\r\nThe fix isn't 100% ideal because there are cases when we may end up with\r\nan additional backslash being rendered for labels of the scatterplot.\r\nHowever, all other variations I tried caused rendering problems of the\r\ncharts and rendering would fail completely.\r\n\r\nFor example, just escaping `\\n` without the general backslash escaping\r\ncauses the following Vega error: `Duplicate scale or projection name:\r\n\"child__row_my_numbercolumn_my_number_x\"`\r\n\r\nOn the other hand escaping just the backslash without the additional\r\n`\\n` escaping causes an \"expression parse error\" in in Vega and the\r\nchart wouldn't render.\r\n\r\nNote this PR just focuses on escaping for the Vega spec for the\r\nscatterplot matrix. There are still other places in the UI (data grid\r\nheaders, fields selector).\r\n\r\n<img width=\"792\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/35532741-7a13-4707-b8da-c72dcc8c935b\">\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#kibana-release-notes-process)","sha":"194d6307dc41b6a4a295abc3e412de148e05386e"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.25","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
49051eae6d
|
[8.x] [ML][Rules] Fixes deletion in Check interval input for anomaly detection rule (#193420) (#193731)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML][Rules] Fixes deletion in Check interval input for anomaly detection rule (#193420)](https://github.com/elastic/kibana/pull/193420) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-23T14:27:01Z","message":"[ML][Rules] Fixes deletion in Check interval input for anomaly detection rule (#193420)\n\n## Summary\r\n\r\nIt was trying to parse `null` values.\r\nAfter:\r\n\r\n\r\n\r\nFixes [#190732](https://github.com/elastic/kibana/issues/190732)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"65b7bf9586480b522393905ff21324f473ee90ed","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v9.0.0","Team:ML","backport:prev-major"],"title":"[ML][Rules] Fixes deletion in Check interval input for anomaly detection rule","number":193420,"url":"https://github.com/elastic/kibana/pull/193420","mergeCommit":{"message":"[ML][Rules] Fixes deletion in Check interval input for anomaly detection rule (#193420)\n\n## Summary\r\n\r\nIt was trying to parse `null` values.\r\nAfter:\r\n\r\n\r\n\r\nFixes [#190732](https://github.com/elastic/kibana/issues/190732)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"65b7bf9586480b522393905ff21324f473ee90ed"}},"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/193420","number":193420,"mergeCommit":{"message":"[ML][Rules] Fixes deletion in Check interval input for anomaly detection rule (#193420)\n\n## Summary\r\n\r\nIt was trying to parse `null` values.\r\nAfter:\r\n\r\n\r\n\r\nFixes [#190732](https://github.com/elastic/kibana/issues/190732)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"65b7bf9586480b522393905ff21324f473ee90ed"}}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
5f2de6d6d5
|
[8.x] [ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers (#192987) (#193568)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers (#192987)](https://github.com/elastic/kibana/pull/192987) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-09-20T12:06:29Z","message":"[ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers (#192987)\n\n# Summary\r\n\r\nFix for [#192679](https://github.com/elastic/kibana/issues/192679)\r\nHiding the top influencers panel when there are no influencers for the\r\nselected job.\r\nAdded a functional test to ensure the panel is hidden.\r\nExpanded a few types to improve type safety.","sha":"23b2595be39401214a1ef9e39b684f917020b9ad","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug",":ml","release_note:skip","v9.0.0","Team:ML","backport:prev-minor","v8.16.0"],"title":"[ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers","number":192987,"url":"https://github.com/elastic/kibana/pull/192987","mergeCommit":{"message":"[ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers (#192987)\n\n# Summary\r\n\r\nFix for [#192679](https://github.com/elastic/kibana/issues/192679)\r\nHiding the top influencers panel when there are no influencers for the\r\nselected job.\r\nAdded a functional test to ensure the panel is hidden.\r\nExpanded a few types to improve type safety.","sha":"23b2595be39401214a1ef9e39b684f917020b9ad"}},"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/192987","number":192987,"mergeCommit":{"message":"[ML] Anomaly Explorer: Hide top influencers panel for jobs without influencers (#192987)\n\n# Summary\r\n\r\nFix for [#192679](https://github.com/elastic/kibana/issues/192679)\r\nHiding the top influencers panel when there are no influencers for the\r\nselected job.\r\nAdded a functional test to ensure the panel is hidden.\r\nExpanded a few types to improve type safety.","sha":"23b2595be39401214a1ef9e39b684f917020b9ad"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Jaszczurek <92210485+rbrtj@users.noreply.github.com> |
||
|
e0e48ccfb1
|
[8.x] [ML] Anomaly Detection: Adds popover links menu to anomaly explorer charts. (#186587) (#193383)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly Detection: Adds popover links menu to anomaly explorer charts. (#186587)](https://github.com/elastic/kibana/pull/186587) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-09-19T06:10:38Z","message":"[ML] Anomaly Detection: Adds popover links menu to anomaly explorer charts. (#186587)\n\n## Summary\r\n\r\nAdds support for clicking on Anomaly Explorer charts to trigger the\r\nactions popover menu.\r\n\r\n- [x] ExplorerChartSingleMetric\r\n- [x] ExplorerChartDistribution\r\n- [x] Support for embedded charts\r\n\r\nAnomaly Explorer\r\n\r\n[ml-anomaly-charts-actions-0001.webm]( |
||
|
d253c0eb67
|
[8.x] [ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab (#193105) (#193485)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab (#193105)](https://github.com/elastic/kibana/pull/193105) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2024-09-19T20:40:44Z","message":"[ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab (#193105)\n\n## Summary\r\n\r\nRelated issue: https://github.com/elastic/kibana/issues/182199?reload=1\r\n\r\nThis PR adds a link to `ML > Anomaly Detection > Supplied\r\nConfigurations` from `Integration > Assets tab` for 'ML Modules' assets.\r\n\r\nThe naming of the asset is also updated in Fleet to be consistent with\r\nthe ML UI.\r\n\r\n<img width=\"429\" alt=\"Screenshot 2024-09-19 at 13 46 47\"\r\nsrc=\"https://github.com/user-attachments/assets/9fcc3606-cc08-483f-88b4-00c07de3fc57\">\r\n\r\n<img width=\"717\" alt=\"Screenshot 2024-09-19 at 13 47 52\"\r\nsrc=\"https://github.com/user-attachments/assets/847f3d6e-95a1-491c-aa3e-7d54da7df98a\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"052187ce180f0cbcb062486f36a562495f840bef","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Team:Fleet","v9.0.0","backport:prev-minor","v8.16.0"],"title":"[ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab","number":193105,"url":"https://github.com/elastic/kibana/pull/193105","mergeCommit":{"message":"[ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab (#193105)\n\n## Summary\r\n\r\nRelated issue: https://github.com/elastic/kibana/issues/182199?reload=1\r\n\r\nThis PR adds a link to `ML > Anomaly Detection > Supplied\r\nConfigurations` from `Integration > Assets tab` for 'ML Modules' assets.\r\n\r\nThe naming of the asset is also updated in Fleet to be consistent with\r\nthe ML UI.\r\n\r\n<img width=\"429\" alt=\"Screenshot 2024-09-19 at 13 46 47\"\r\nsrc=\"https://github.com/user-attachments/assets/9fcc3606-cc08-483f-88b4-00c07de3fc57\">\r\n\r\n<img width=\"717\" alt=\"Screenshot 2024-09-19 at 13 47 52\"\r\nsrc=\"https://github.com/user-attachments/assets/847f3d6e-95a1-491c-aa3e-7d54da7df98a\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"052187ce180f0cbcb062486f36a562495f840bef"}},"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/193105","number":193105,"mergeCommit":{"message":"[ML][Fleet] Adds link to anomaly detection configurations from Integration > Assets tab (#193105)\n\n## Summary\r\n\r\nRelated issue: https://github.com/elastic/kibana/issues/182199?reload=1\r\n\r\nThis PR adds a link to `ML > Anomaly Detection > Supplied\r\nConfigurations` from `Integration > Assets tab` for 'ML Modules' assets.\r\n\r\nThe naming of the asset is also updated in Fleet to be consistent with\r\nthe ML UI.\r\n\r\n<img width=\"429\" alt=\"Screenshot 2024-09-19 at 13 46 47\"\r\nsrc=\"https://github.com/user-attachments/assets/9fcc3606-cc08-483f-88b4-00c07de3fc57\">\r\n\r\n<img width=\"717\" alt=\"Screenshot 2024-09-19 at 13 47 52\"\r\nsrc=\"https://github.com/user-attachments/assets/847f3d6e-95a1-491c-aa3e-7d54da7df98a\">\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\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 renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"052187ce180f0cbcb062486f36a562495f840bef"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co> |