mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
437 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
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> |
||
|
Kibana Machine
|
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> |
||
|
Kibana Machine
|
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]( |
||
|
Kibana Machine
|
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> |
||
|
Kibana Machine
|
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> |
||
|
Kibana Machine
|
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]( |
||
|
Kibana Machine
|
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> |
||
Walter Rafelsberger
|
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--> |
||
|
Kibana Machine
|
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]( |
||
|
Kibana Machine
|
6113e6c1e5
|
[8.x] [ML] Anomaly Explorer: Display markers for scheduled events in distribution type anomaly charts (#192377) (#193118)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Anomaly Explorer: Display markers for scheduled events in distribution type anomaly charts (#192377)](https://github.com/elastic/kibana/pull/192377) <!--- 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-17T07:53:32Z","message":"[ML] Anomaly Explorer: Display markers for scheduled events in distribution type anomaly charts (#192377)\n\n## Summary\r\n\r\nFix for [#129304](https://github.com/elastic/kibana/issues/129304)\r\n\r\nPreviously, for distribution type charts, we displayed calendar event\r\nmarkers only for anomalous data points. The changes improve the display\r\nof event markers for such chart types, including showing calendar event\r\nmarkers even when there is no underlying data point.\r\n\r\n| Scenario | Before | After |\r\n| :---: | :---: | :---: |\r\n| Rare chart |\r\n
Melissa Alvarez
|
e5600b18b1
|
[ML] Anomaly Detection supplied configurations: adds page in ML UI for Supplied configurations (ML Modules) (#191564)
## Summary This PR adds a page in the UI for 'Supplied configurations' Dependent on this fix to the endpoint schema going in first: https://github.com/elastic/kibana/pull/191633 NOTE: This item will be added to the side-nav of oblt serverless once this update is in: https://github.com/elastic/kibana/issues/190458 Adds dedicated UI page for preconfigured job packages - subitem of the Anomaly Detection navigation: <img width="1721" alt="image" src="https://github.com/user-attachments/assets/194bbf44-aa7c-4afa-94e3-587fb9e5f601"> When they can't be run in the ML UI: <img width="1467" alt="image" src="https://github.com/user-attachments/assets/487463e8-7520-48de-8806-1d45a82e452e"> When selected - flyout opens to reveal package assets: <img width="1098" alt="image" src="https://github.com/user-attachments/assets/a648a6d8-df79-4bb3-a797-61f02e246c9b"> Clicking the `Run data recognizer` button shows matching data views (if any) with link to job creation: <img width="1099" alt="image" src="https://github.com/user-attachments/assets/05e9f7f7-e41f-486d-ba41-84cacf534cd0"> Empty table when no matching dataviews are found: <img width="999" alt="image" src="https://github.com/user-attachments/assets/d8bbf3be-7035-4e2f-956e-83dfbc26b247"> Jobs tab of flyout: <img width="1102" alt="image" src="https://github.com/user-attachments/assets/e94efb2e-1f21-4883-aa2b-2c42db5be970"> kibana tab of flyout: <img width="1100" alt="image" src="https://github.com/user-attachments/assets/0021a527-8d9d-4e06-9fae-d832015f7f7d"> ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
James Gowdy
|
0a1be162fe
|
[ML] Improve expired license check (#191503)
When a trial license expires, the license falls into a state where it is not seen as being a valid basic license, but rather an "expired" license. The license is still valid and our `isMinimumLicense` check needs to return true in this situation to allow the ML app to redirect to the expired license page. Before (ML page fails to load):  After (we redirect to the license page):  |
||
|
James Gowdy
|
5ea65f9ed7
|
[ML] Improving empty object creation (#191518)
Replacing instances of empty object creation with `Object.create(null)` to remove any risk of prototype pollution. Only touching server and common code. Follows on from https://github.com/elastic/kibana/pull/186821 |
||
Larry Gregory
|
74d88580a5
|
Migrate codebase to use Object.hasOwn instead of Object.hasOwnProperty (#186829)
## Summary This PR has breadth, but not depth. This adds 3 new `eslint` rules. The first two protect against the use of code generated from strings (`eval` and friends), which will not work client-side due to our CSP, and is not something we wish to support server-side. The last rule aims to prevent a subtle class of bugs, and to defend against a subset of prototype pollution exploits: - `no-new-func` to be compliant with our CSP, and to prevent code execution from strings server-side: https://eslint.org/docs/latest/rules/no-new-func - `no-implied-eval` to be compliant with our CSP, and to prevent code execution from strings server-side: https://eslint.org/docs/latest/rules/no-implied-eval. Note that this function implies that it prevents no-new-func, but I don't see [test cases](https://github.com/eslint/eslint/blob/main/tests/lib/rules/no-implied-eval.js) covering this behavior, so I think we should play it safe and enable both rules. - `no-prototype-builtins` to prevent accessing shadowed properties: https://eslint.org/docs/latest/rules/no-prototype-builtins In order to be compliant with `no-prototype-builtins`, I've migrated all usages and variants of `Object.hasOwnProperty` to use the newer [`Object.hasOwn`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn). |
||
|
Melissa Alvarez
|
8be5ad8fc9
|
[ML][Fleet] Link to ML assets from Integration > Assets tab (#189767)
## Summary
Related issue: https://github.com/elastic/kibana/issues/182199
This PR adds links for ML assets installed via Integrations.
For `transform` and `ml_model` (as they are ES asset types) the manual
mappings in
[get_bulk_assets.ts](
|
||
Dima Arnautov
|
514db549d2
|
[ML] Support E5 model download from the list view, mark not supported/not optimized models (#189372)
## Summary - Adds the "Show all" switch at the top of the page (off by default) that responsible for hiding unsupported/not optimised model versions - Adds a download action for E5 models - Removes the toast notification on successful start of a model download - Adds a warning icon with an appropriate tooltip text if model version is not supported by the cluster architecture or not optimised for it <img width="1401" alt="image" src="https://github.com/user-attachments/assets/30748315-3018-46e2-91dd-fd5128b0695e"> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios |
||
Lisa Cawley
|
841e95c64b
|
[OAS][ML] Add sync API tags and description, minor OpenAPI fixes (#189230) | ||
Valeriy Khakhutskyy
|
bd843dda3f
|
[ML] Add new custom rule action to force time shift (#188710)
This PR follows up https://github.com/elastic/elasticsearch/pull/110974 and extends the schema for custom rules. A valid schema looks like this: ```http POST _ml/anomaly_detectors/my_job/_update { "detectors": { "detector_index": 0, "custom_rules": [ // update the detector with a custom rule that forces a time shift of 1 hour back starting now { "actions": [ "force_time_shift" ], "params": { "force_time_shift": { "time_shift_amount": 3600} } }, "conditions": [{ "applies_to": "time", "operator": "gt", "value": "now" }, { "applies_to": "time", "operator": "lt", "value": "now+bucket_span" }, ] }, ... ``` --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Nick Partridge
|
49a985625b
|
Upgrade prettier dependencies (#188032)
## Summary - Upgrade `prettier` to `v2.8.x`. - Upgrade related decencies. - Adds `prettier` group to renovate config. - Fixes bootstrapping type error. ## Main Changes ### Add parentheses for `TypeofTypeAnnotation` to improve readability [link](https://github.com/prettier/prettier/blob/main/CHANGELOG.md#add-parentheses-for-typeoftypeannotation-to-improve-readability-14458-by-fisker) ```ts // Input type A = (typeof node.children)[]; // Prettier 2.8.4 type A = typeof node.children[]; // Prettier 2.8.5 type A = (typeof node.children)[]; ``` ### Add parentheses to head of `ExpressionStatement` instead of the whole statement [link](https://github.com/prettier/prettier/blob/main/CHANGELOG.md#add-parentheses-to-head-of-expressionstatement-instead-of-the-whole-statement-14077-by-fisker) ```ts // Input ({}).toString.call(foo) === "[object Array]" ? foo.forEach(iterateArray) : iterateObject(foo); // Prettier 2.8.1 ({}.toString.call(foo) === "[object Array]" ? foo.forEach(iterateArray) : iterateObject(foo)); // Prettier 2.8.2 ({}).toString.call(foo.forEach) === "[object Array]" ? foo.forEach(iterateArray) : iterateObject(foo); ``` ## Details This started because I noticed we were on `typescript@^5` but still on an old prettier that complained about use of new TS features such as [`satisfies`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-9.html#the-satisfies-operator). --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Dima Arnautov
|
9669bfde47
|
[ML] Fixes display of model state in trained models list with starting and stopping deployments (#188847)
## Summary Fixes #188035 and #181093 <img width="1434" alt="image" src="https://github.com/user-attachments/assets/6c14afa3-2908-45ff-a68d-88ee18f18964"> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios |
||
Eyo O. Eyo
|
22e0545d0e
|
Redesign the "Add Panel" Experience (#183764)
## Summary Closes https://github.com/elastic/kibana/issues/144418 This PR introduces changes to the dashboard add panel selection functionality, so that panel selection would now happen from within a flyout, and as such panels are now grouped together logically. With this implementation any panel that is intended to show up within this new flyout is required to have either been registered leveraging the ui action trigger `ADD_PANEL_TRIGGER` and have it's `grouping` value defined or belong to a subset of visualization types (`PROMOTED`, `TOOLS`, and `LEGACY`) that would automatically get grouped. It's worth pointing out that because we can't control the order at which UI actions gets registered, we won't always get the the panel groups in the same order, for this specific reason ~a new optional property (`placementPriority`) has been added in~ the property `order` is now leveraged such that it allows a user registering a UI action define a relative weight for where they'd like their group to show up. All registered actions would be rendered in descending order considering all `order` defined, in the case where no order is defined `0` is assumed for the group. In addition an action which is registered without a group, would automatically get assigned into a default group titled "Other". The search implemented within the add panel is rudimentary, checking if the group titles and group item titles contain the input character; when a group title is matched the entire group is remains highlighted, in the case that the group isn't matched and it's just the group item, only said item is highlighted within it's group. ## Visuals #### Default view <img width="2560" alt="Screenshot 2024-06-10 at 17 44 17" src=" |
||
|
Lisa Cawley
|
dde8ef93bb
|
[OAS] Edits OpenAPI documents for machine learning sync API (#186318) | ||
|
Dima Arnautov
|
074220db87
|
[ML] Progress bar for trained models download (#184906)
## Summary
Closes #182004
Adds a progress bar for trained model downloads.
<img width="1592" alt="image"
src="
|
||
|
Melissa Alvarez
|
2ec4ec362d
|
[ML] Anomaly Detection: Single Metric Viewer - add cases action (#183423)
## Summary Related meta issue https://github.com/elastic/kibana/issues/181272 This PR adds the 'Add to case' action in the Single Metric Viewer ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Dima Arnautov <arnautov.dima@gmail.com> |
||
Patryk Kopyciński
|
0780c19322
|
Add explicit children types (#181257)
## Summary Prep work for React@18 bump tl;dr In React@18 `React.FC` doesn't contain `children` anymore, so in order to make the bump easier I have decided to split the effort in multiple faces and hopefully this will make it easier for everyone This PR focuses only on adding explicit `children` declaration either by using `React.PropsWithChildren` type or by adding `children: React.ReactNode` to the existing props types https://github.com/DefinitelyTyped/DefinitelyTyped/issues/46691 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com> Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
Saarika Bhasi
|
439f4a8876
|
[ML] Support adding inference_id in a flyout (#180330)
## Summary
* Creates a new package - ` @kbn/inference_integration_flyout`
* Above package has implementation for adding new inference endpoint id,
including Elastic, third party integration and instructions to upload
via Eland python client, in a flyout.
* The above package is used for supporting semantic_text feature and is
accessed via`add a new inference endpoint` button
## Screen Recording
|
||
Clint Andrew Hall
|
67ab4f7732
|
[ml] Optimize bundles, reduce page load async chunks by 74% (#179311)
## Summary The `AnomalyExplorerChartsService` was importing the `SWIM_LANE_LABEL_WIDTH` numerical constant from `swimlane_container.tsx`. As a result, the _entirety_ of that file was being included in the async bundle. `AnomalyExplorerChartsService` is loaded asynchronously on page load by the embeddable. By relocating the constant to its own file-- as well as other optimizations (see below)-- we reduce the async page load by 74%, (in dev mode). ### Before - `351k` <img width="1220" alt="Screenshot 2024-03-24 at 10 09 31 AM" src=" |
||
Saikat Sarkar
|
fff6bcffde
|
Add semantic_text to index mapping (#179575)
In this PR, we added the following items. - Add a semantic_text field type - Allow the users to add semantic_text to index mapping - Allow the user to select a text field as reference field - Allow the user to select inference_id for semantic_text field Please be aware that currently, we won't be able to save the mapping using the 'Save mappings' button because the 'semantic_text' functionality doesn't support 'inference_id'. However, there is ongoing parallel work in a GitHub [branch](https://github.com/elastic/elasticsearch/tree/feature/semantic-text) to enable 'inference_id' in 'semantic_text' for Elasticsearch. |
||
Alejandro Fernández Haro
|
1c1e20afdb
|
Use rxjs instead of rxjs/operators (#179553)
|
||
Zacqary Adam Xeper
|
bfc91b0cb0
|
[RAM] [Rule Form v2] Add feature flag (#179184)
## Summary Closes #179110 This adds a series of feature flags to all plugins that are currently using the **Rule Form Flyout**, in preparation for development of the new Create Rule Flow V2 (#175634). Unfortunately true Kibana feature-flagging is still not yet implemented, so we need to implement this as a config option for every individual affected plugin. The following `kibana.yml` config will enable the upcoming V2 rule form: ```yaml xpack.trigger_actions_ui.enableExperimental: ['ruleFormV2'] xpack.infra.featureFlags.ruleFormV2Enabled: true xpack.ml.experimental.ruleFormV2.enabled: true xpack.transform.experimental.ruleFormV2Enabled: true xpack.legacy_uptime.experimental.ruleFormV2Enabled: true xpack.observability.unsafe.ruleFormV2.enabled: true xpack.slo.experimental.ruleFormV2.enabled: true xpack.apm.featureFlags.ruleFormV2Enabled: true discover.experimental.ruleFormV2Enabled: true ``` **These feature flags will not enable anything yet.** This PR is for the sole purpose of adding these browser-enabled flags now, so that we can reduce the amount of code committed later. ### Why feature flag every plugin? The V1 rule form is currently exported from Triggers Actions UI. In V2, we're moving away from this model and exporting the rule form in a KBN package. Therefore we can't simply export the results of a single feature flag from Triggers Actions UI, we need to signal to each individual plugin whether it should be pulling from the new KBN package or from the old cross-plugin export. ### Plugins affected #### Triggers Actions UI, Infra, Observability, APM These plugins already contained interfaces for experimental features or feature flags, so this PR simply adds a new flag to these existing structures. #### Discover, ML, Transform, Uptime, SLO These plugins did **not** have existing browser-exposed feature flag systems, so this PR adds these interfaces. The transform plugin notably did not yet have any config options configured at all. |
||
|
James Gowdy
|
a66d42b50c
|
[ML] Fixes polling for blocked anomaly detection jobs (#178246)
Fixes two issues: - When a job is in a blocked state (resetting, deleting reverting) but the underlying task [cannot be found](https://github.com/elastic/elasticsearch/issues/105928), the task polling fails to start correctly and instead enters a loop where the tasks are checked as fast as possible. - Some tasks can legitimately take a long time to run, but we still poll at the same 2 second rate. This PR fixes the feedback loop and adds a check for when a poll has been running for over a minute, the poll interval is increased to 2 minutes. Related to https://github.com/elastic/kibana/issues/171626 |
||
|
James Gowdy
|
3670b4fa5f
|
[ML] Enable consistent-type-imports eslint rule (#176921)
Enabling `consistent-type-imports` rule and running `node scripts/eslint --no-cache --fix` to fix every type import. Affects x-pack plugins: `ml`, `transform`, `aiops`, `data_visualizer` and `x-pack/packages/ml` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
James Gowdy
|
64fa491043
|
[ML] Fixing quick create geo job created by ID (#177691)
We should differentiate between geo jobs created in lens, and the ones created in the original wizards. We do this for single and multi metric jobs. |
||
|
Dima Arnautov
|
ec8e464251
|
[ML] Update alerts-as-data payload for Anomaly detection health and Transform health rules (#176307) | ||
|
Dima Arnautov
|
2598b81704
|
[ML] Warn the user if trained model is referenced by the _inference API (#175880)
|
||
|
Dima Arnautov
|
550c10dc5e
|
[ML] AIOps: UI action for Change Point Detection embeddable to open in the ML app (#176694)
## Summary
Closes #161248
Added a UI action to open change point detection in the AIOps labs.
<img width="1137" alt="image"
src="
|
||
Quynh Nguyen (Quinn)
|
53c3907529
|
[ML] Add support for ES|QL in Data visualizer (#174188)
## Summary This PR adds support for ES|QL queries in Data visualizer. <img width="1695" alt="Screenshot 2024-01-26 at 17 07 59" src=" |
||
Xavier Mouligneau
|
5d5f0d1073
|
[RAM] Stack management rules available with only ml feature (#174791)
## Summary Fix => https://github.com/elastic/kibana/issues/173573 |
||
|
Dima Arnautov
|
2a61da251b
|
[ML] Fix Allocation rendering for failed deployments (#174882)
## Summary Fixes "Allocation" rendering for failed deployments of trained models. _We should also update the type definition in elasticsearch specification marking `number_of_allocations` and `threads_per_allocation` as optional for [Get Trained Model Stats](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-trained-models-stats.html) endpoint._ #### How to reproduce 1. Start a model deployment 2. Find a Process ID ``` ps -ef | grep pytorch_inference ``` 3. Kill the inference process manually ``` kill -9 <PID> ``` Before: 
## Summary From the rule management page in observability, user will be able to create an anomaly detection rule. <img width="1789" alt="image" src=" |
||
|
Dima Arnautov
|
50dabea70f
|
[ML] Add anomaly description as an alert message for anomaly detection rule type (#172473)
## Summary
Closes #136391
Uses a description of the anomaly for the alert message for anomaly
detection alerting rules with the `record` result type. This messages is
used for example in the `Reason` field in the alert table and details
flyout.
<img width="753" alt="image"
src="
|
||
|
Dima Arnautov
|
808990a78d
|
[ML] Validate and limit threading parameters for starting model deployment (#171921)
## Summary
Closes #171883
This PR adds:
- Limiting options for "Threads per allocation" control for a model
deployment based on the `max_single_ml_node_processors` limit
- Validation of the number of allocation according to the
`total_ml_processors` field
<img width="1018" alt="image"
src="
|
||
|
Lisa Cawley
|
2f258a229c
|
[OAS] Migrate machine learning APIs to v3.1.0 (#171594) | ||
|
James Gowdy
|
5e3b124ae0
|
[ML] Create categorization job from pattern analysis (#170567)
Adds the ability to quickly create a categorisation anomaly detection job from the pattern analysis flyout. Adds a new `created_by` ID `categorization-wizard-from-pattern-analysis` which can be picked up by telemetry. Creates a new package for sharing our AIOPs ui actions IDs. I think we should move the pattern analysis ID to this package too, but that can be done in a separate PR. |
||
|
Melissa Alvarez
|
39af788067
|
[ML] Trained models list: disable 'View training data' action if data frame analytics job no longer exists (#171061)
## Summary Fixes https://github.com/elastic/kibana/issues/167667, disabling the 'View training data' action for models in the Trained Models list if the data frame analytics job which created the model no longer exists Adds `origin_job_exists` property to trained models list model items. This is set during the models fetch for models with associated data frame analytics jobs. ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Dima Arnautov
|
875268d558
|
[ML] Show alerts data on the Anomaly timeline (#167998)
## Summary With alerts-as-data integration added in https://github.com/elastic/kibana/pull/166349, we're enabled to incorporate alerts historical data into views in the ML UI to see how it correlates with the anomaly results. This PR add alerts data to the Anomaly Explorer page. If selected anomaly detection jobs have associated alerting rules, we show a new "Alerts" panel. It contains: <img width="1675" alt="image" src=" |
||
|
Lisa Cawley
|
8924218d6a
|
[OAS] Simplify server declaration in ML APIs (#169885) | ||
|
James Gowdy
|
6a6df9d72f
|
[ML] Module filtering (#168721)
Adds a new `tags` property to our ML Modules which contains an array of strings to used to filter the modules returned when calling `/internal/ml/modules/get_module` or `/internal/ml/modules/recognize` Adds a new kibana config setting `xpack.ml.compatibleModuleType` which will enforce a module filter. This setting supports the values `security`, `observability` or `search` and will be used by the serverless projects to ensure only modules relevant to the current project are discoverable. When matching against the `xpack.ml.compatibleModuleType` setting, modules with no tags will be returned along with modules which match the `compatibleModuleType` value. The endpoints `/internal/ml/modules/get_module` and `/internal/ml/modules/recognize` can also take a `filter` query parameter in the form of a comma separated list of values. If any of these filter values match a module's tags, the module will be returned. Modules with no tags will not be matched when using the `filter` parameter. This PR also updates the security plugin to apply a `security` filter when retrieving modules and running recognize. This will improve performance, especially for recognize which runs the queries from every module on the supplied index pattern. Examples **Running the Security serverless project.** Request: `/internal/ml/modules/get_module` Response: All modules containing `tags: ["security"]` Plus all modules with no `tags` or `tags: []` Request: `/internal/ml/modules/get_module?filter=observability` Response: An empty list **Running stateful es** Request: `/internal/ml/modules/get_module` Response: All modules Request: `/internal/ml/modules/get_module?filter=security` Response: Only modules containing `tags: ["security"]` Request: `/internal/ml/modules/get_module?filter=security,observability` Response: Modules containing `tags: ["security"]` and `tags: ["observability"]` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Lisa Cawley
|
61e8ca2a39
|
[OAS] Add Serverless machine learning APIs (#168777) | ||
|
Dima Arnautov
|
0c6dfbf209
|
[ML] ELSER v2 download in the Trained Models UI (#167407)
## Summary
Adds support for ELSER v2 download from the Trained Models UI.
- Marks an appropriate model version for the current cluster
configuration with the recommended flag.
- Updates the state column with better human-readable labels and colour
indicators.
- Adds a callout promoting a new version of ELSER
<img width="1686" alt="image"
src="
|