mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
1867 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Quynh Nguyen (Quinn)
|
7d1cc16f30
|
[8.12] [ML] Fixes Single Metric Viewer's zoom settings in URL are not restored if URL specifies a forecast ID (#176969) (#177124)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fixes Single Metric Viewer's zoom settings in URL are not restored if URL specifies a forecast ID (#176969)](https://github.com/elastic/kibana/pull/176969) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
Kibana Machine
|
9c1c90b350
|
[8.12] [ML] Anomaly Detection: Fix `values-dots` colors (#176303) (#176326)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Anomaly Detection: Fix `values-dots` colors (#176303)](https://github.com/elastic/kibana/pull/176303) <!--- 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-02-06T16:45:19Z","message":"[ML] Anomaly Detection: Fix `values-dots` colors (#176303)\n\n## Summary\r\n\r\nFixes the colors of \"value dots\", the dots that are shown in the Single\r\nMetric Viewer when theres sparse data and not a continuous line.\r\n\r\nBefore:\r\n\r\n<img width=\"1112\" alt=\"image\"\r\nsrc=\" |
||
|
Kibana Machine
|
095e65b901
|
[8.12] [ML] Fix Allocation rendering for failed deployments (#174882) (#174909)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fix Allocation rendering for failed deployments (#174882)](https://github.com/elastic/kibana/pull/174882) <!--- 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-01-16T12:43:31Z","message":"[ML] Fix Allocation rendering for failed deployments (#174882)\n\n## Summary\r\n\r\nFixes \"Allocation\" rendering for failed deployments of trained models.\r\n\r\n_We should also update the type definition in elasticsearch\r\nspecification marking `number_of_allocations` and\r\n`threads_per_allocation` as optional for [Get Trained Model\r\nStats](https://www.elastic.co/guide/en/elasticsearch/reference/current/get-trained-models-stats.html)\r\nendpoint._\r\n\r\n#### How to reproduce\r\n1. Start a model deployment \r\n2. Find a Process ID \r\n```\r\nps -ef | grep pytorch_inference\r\n```\r\n3. Kill the inference process manually \r\n```\r\nkill -9 <PID>\r\n```\r\n\r\nBefore:\r\n\r\n (#174484)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Data Frame Analytics: ensure option to delete data view is available when deleting job (#174381)](https://github.com/elastic/kibana/pull/174381) <!--- 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-01-08T19:12:36Z","message":"[ML] Data Frame Analytics: ensure option to delete data view is available when deleting job (#174381)\n\n## Summary\r\n\r\nThis PR sets refresh option to true when fetching existing Data Views to\r\nensure the data view exists check is up to date when deleting a newly\r\ncreated job.\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\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"befc63efd35b682bc9cea18add20652186b02da4","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:Data Frame Analytics","v8.12.0","v8.13.0"],"title":"[ML] Data Frame Analytics: ensure option to delete data view is available when deleting job","number":174381,"url":"https://github.com/elastic/kibana/pull/174381","mergeCommit":{"message":"[ML] Data Frame Analytics: ensure option to delete data view is available when deleting job (#174381)\n\n## Summary\r\n\r\nThis PR sets refresh option to true when fetching existing Data Views to\r\nensure the data view exists check is up to date when deleting a newly\r\ncreated job.\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\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"befc63efd35b682bc9cea18add20652186b02da4"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/174381","number":174381,"mergeCommit":{"message":"[ML] Data Frame Analytics: ensure option to delete data view is available when deleting job (#174381)\n\n## Summary\r\n\r\nThis PR sets refresh option to true when fetching existing Data Views to\r\nensure the data view exists check is up to date when deleting a newly\r\ncreated job.\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\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"befc63efd35b682bc9cea18add20652186b02da4"}}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co> |
||
|
Kibana Machine
|
72c06f5caa
|
[8.12] [ML] Data Frame Analytics: ensure job can be deleted from analytics map (#174212) (#174483)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Data Frame Analytics: ensure job can be deleted from analytics map (#174212)](https://github.com/elastic/kibana/pull/174212) <!--- 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-01-08T18:48:19Z","message":"[ML] Data Frame Analytics: ensure job can be deleted from analytics map (#174212)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/174131\r\n\r\nThis PR removes the failed job check - `stats` being undefined sometimes\r\nwas causing the issue.\r\nThe need for stats is removed when we default to using the `force=true`\r\noption in the delete endpoint.\r\nUsing that option removes the need to first try and stop the job, as\r\nthat is handled by the endpoint when using that option. This works\r\nregardless of the job's state.\r\n\r\n\r\n |
||
|
Kibana Machine
|
4ba26bcfde
|
[8.12] [ML][Enterprise Search] Reword E5 model description (#174171) (#174197)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML][Enterprise Search] Reword E5 model description (#174171)](https://github.com/elastic/kibana/pull/174171) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Adam Demjen","email":"demjened@gmail.com"},"sourceCommit":{"committedDate":"2024-01-03T16:08:58Z","message":"[ML][Enterprise Search] Reword E5 model description (#174171)\n\n## Summary\r\n\r\nAdding \"third party\" to E5 ML model description as per legal\r\nrequirements.\r\n\r\n<img width=\"1372\" alt=\"Screenshot 2024-01-03 at 09 11 25\"\r\nsrc=\" |
||
|
Kibana Machine
|
d7417f96b2
|
[8.12] [Obs AI Assistant] Make KB use recommended ELSER model (#173543) (#173937)
# Backport This will backport the following commits from `main` to `8.12`: - [[Obs AI Assistant] Make KB use recommended ELSER model (#173543)](https://github.com/elastic/kibana/pull/173543) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2023-12-22T19:28:57Z","message":"[Obs AI Assistant] Make KB use recommended ELSER model (#173543)\n\nThis PR changes the hard coded ELSER model ID to instead be resolved\r\nduring service `init` and Knowledge base setup using the ML plugin.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29ead617005bf3c22995289b99f1cad60c0b1dc5","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.12.0","v8.12.1","v8.13.0"],"number":173543,"url":"https://github.com/elastic/kibana/pull/173543","mergeCommit":{"message":"[Obs AI Assistant] Make KB use recommended ELSER model (#173543)\n\nThis PR changes the hard coded ELSER model ID to instead be resolved\r\nduring service `init` and Knowledge base setup using the ML plugin.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29ead617005bf3c22995289b99f1cad60c0b1dc5"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173543","number":173543,"mergeCommit":{"message":"[Obs AI Assistant] Make KB use recommended ELSER model (#173543)\n\nThis PR changes the hard coded ELSER model ID to instead be resolved\r\nduring service `init` and Knowledge base setup using the ML plugin.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"29ead617005bf3c22995289b99f1cad60c0b1dc5"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
|
Kibana Machine
|
193a858a6f
|
[8.12] [ML] Enable Trained models functional tests (#173517) (#173914)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Enable Trained models functional tests (#173517)](https://github.com/elastic/kibana/pull/173517) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2023-12-22T11:23:50Z","message":"[ML] Enable Trained models functional tests (#173517)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/168899\r\nCloses https://github.com/elastic/kibana/issues/168492\r\nCloses https://github.com/elastic/kibana/issues/156243\r\n\r\nEnables Trained models functional tests \r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n(https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4664)","sha":"b5cd85c21fa60c121c30219666a89135c9a95124","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","Team:ML","v8.12.0","v8.13.0"],"number":173517,"url":"https://github.com/elastic/kibana/pull/173517","mergeCommit":{"message":"[ML] Enable Trained models functional tests (#173517)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/168899\r\nCloses https://github.com/elastic/kibana/issues/168492\r\nCloses https://github.com/elastic/kibana/issues/156243\r\n\r\nEnables Trained models functional tests \r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n(https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4664)","sha":"b5cd85c21fa60c121c30219666a89135c9a95124"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173517","number":173517,"mergeCommit":{"message":"[ML] Enable Trained models functional tests (#173517)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/168899\r\nCloses https://github.com/elastic/kibana/issues/168492\r\nCloses https://github.com/elastic/kibana/issues/156243\r\n\r\nEnables Trained models functional tests \r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n(https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4664)","sha":"b5cd85c21fa60c121c30219666a89135c9a95124"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
ddcf10b7d9
|
[8.12] [ML] Fix registering of the ML alerting rules with the basic license (#173644) (#173733)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fix registering of the ML alerting rules with the basic license (#173644)](https://github.com/elastic/kibana/pull/173644) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2023-12-20T12:31:21Z","message":"[ML] Fix registering of the ML alerting rules with the basic license (#173644)\n\n## Summary\r\n\r\nFixes the license checks for registering ML alerting rules, so that if\r\nthe user doesn't have the required license to create a rule instance, we\r\nstill show the entry in the list. The alerting framework disables the\r\nrule type if license requirements aren't met.\r\n\r\n<img width=\"617\" alt=\"image\"\r\nsrc=\" |
||
|
Kibana Machine
|
f4d642d472
|
[8.12] [ML] Fixes display of actions column in the datafeed chart flyout (#173365) (#173726)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fixes display of actions column in the datafeed chart flyout (#173365)](https://github.com/elastic/kibana/pull/173365) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pete Harverson","email":"pete@elastic.co"},"sourceCommit":{"committedDate":"2023-12-20T11:02:57Z","message":"[ML] Fixes display of actions column in the datafeed chart flyout (#173365)\n\n## Summary\r\n\r\nFixes the 'Actions' column in the datafeed chart flyout, opened from the\r\nanomaly detection jobs list, so that the 'Toggle in chart' action is\r\nonly shown once per row.\r\n\r\n#### Before:\r\n\r\n<img width=\"851\" alt=\"datafeed_flyout_actions_before\"\r\nsrc=\" |
||
|
Kibana Machine
|
49f8243d90
|
[8.12] [ML] Remove beta badge from ML alerting rules (#173545) (#173623)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Remove beta badge from ML alerting rules (#173545)](https://github.com/elastic/kibana/pull/173545) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2023-12-19T13:13:02Z","message":"[ML] Remove beta badge from ML alerting rules (#173545)\n\n## Summary\r\n\r\n- Removes the beta badge from Anomaly detection and Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly detection\") for consistency with the other rules in the list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","Feature:Alerting/RuleTypes","Team:ML","v8.12.0","v8.13.0"],"number":173545,"url":"https://github.com/elastic/kibana/pull/173545","mergeCommit":{"message":"[ML] Remove beta badge from ML alerting rules (#173545)\n\n## Summary\r\n\r\n- Removes the beta badge from Anomaly detection and Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly detection\") for consistency with the other rules in the list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173545","number":173545,"mergeCommit":{"message":"[ML] Remove beta badge from ML alerting rules (#173545)\n\n## Summary\r\n\r\n- Removes the beta badge from Anomaly detection and Anomlay detection\r\njob health alerting rules.\r\n- Renames Anomaly detection alerting rule (\"Anomaly detection alert\" ->\r\n\"Anomaly detection\") for consistency with the other rules in the list","sha":"bf52a1396dfe0724d826744ddfbf20b16bebe1bb"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
9c36f051b9
|
[8.12] [ML] Fix View in Discover option in Anomaly explorer not handling multiple field values or values with quotation marks (#172897) (#173197)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fix View in Discover option in Anomaly explorer not handling multiple field values or values with quotation marks (#172897)](https://github.com/elastic/kibana/pull/172897) <!--- Backport version: 8.9.7 --> ### 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":"2023-12-12T19:17:36Z","message":"[ML] Fix View in Discover option in Anomaly explorer not handling multiple field values or values with quotation marks (#172897)\n\n## Summary\r\n\r\nThis PR addresses https://github.com/elastic/kibana/issues/172872 and\r\nhttps://github.com/elastic/kibana/issues/172461. Previously, clicking\r\n`View in Discover` option in Anomaly explorer for an anomaly with\r\ninfluencers containing quotation marks would lead to an error in\r\nDiscover. Likewise, if the influencer has multiple field values, the\r\nlink only brings over the first field value and not all. This PR fixes\r\nboth issues.\r\n\r\n\r\nAfter:\r\n\r\n\r\n |
||
|
Kibana Machine
|
ebfd9af4a1
|
[8.12] [ML] Update external URLs for E5 models (#172796) (#172975)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Update external URLs for E5 models (#172796)](https://github.com/elastic/kibana/pull/172796) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2023-12-08T16:27:59Z","message":"[ML] Update external URLs for E5 models (#172796)\n\n## Summary\r\n\r\nAdds external URLs for each version of the E5 model.\r\n\r\n<img width=\"1024\" alt=\"image\"\r\nsrc=\" |
||
|
Kibana Machine
|
05871ff18e
|
[8.12] [ML] Fix long field names overflowing in Anomaly detection wizard detector selection (#172715) (#172889)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Fix long field names overflowing in Anomaly detection wizard detector selection (#172715)](https://github.com/elastic/kibana/pull/172715) <!--- Backport version: 8.9.7 --> ### 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":"2023-12-07T20:51:29Z","message":"[ML] Fix long field names overflowing in Anomaly detection wizard detector selection (#172715)\n\n## Summary\r\n\r\nThis PR fixes https://github.com/elastic/kibana/issues/171963. Changes\r\nincluded fix long field names overflowing in Anomaly detection wizard\r\ndetector selection.\r\n\r\nBefore:\r\n<img width=\"435\" alt=\"image\"\r\nsrc=\" |
||
|
Kibana Machine
|
f3d21302c7
|
[8.12] [ML][AIOps] Remove Technical preview badge from AIOps log rate analysis (#172722) (#172882)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML][AIOps] Remove Technical preview badge from AIOps log rate analysis (#172722)](https://github.com/elastic/kibana/pull/172722) <!--- Backport version: 8.9.7 --> ### 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":"2023-12-07T20:07:12Z","message":"[ML][AIOps] Remove Technical preview badge from AIOps log rate analysis (#172722)\n\n## Summary\r\n\r\nThis PR removes the 'Technical Preview' badge from Log Rate Analysis in\r\nML AIOps labs.\r\n\r\n<img width=\"1225\" alt=\"image\"\r\nsrc=\" |
||
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="
|
||
Umberto Pepato
|
5dd46ad1ba
|
[RAM] Move common alerts table actions to triggersActionsUI (#170651)
## Summary
Add a mute/unmute action component to be used in alerts table row
actions, move all common alerts table row actions to triggersActionsUI
and re-export them for consumers to compose their table actions.
James Gowdy
|
004632ffc3
|
[ML] Adding pattern analysis to anomaly action menu (#169400)
Adds the ability to run pattern analysis on the index used for an
anomaly detection job.
The pattern analysis is run for the whole time range selected in the
page's time picker, but also adds a sub aggregation to focus on the
bucket time range for the selected anomaly.
This allows the user to view either patterns found in the bucket or the
full time range.
If partition field has been used in the detector, this is also added as
a filter in the sub agg, so the patterns shown are only ones where the
doc also matches the partition field value.
A sub agg was used rather than just running the whole analysis on the
bucket to ensure we get a good analysis and good patterns. The more data
we see, the more accurate the patterns.
This way we can find all of the patterns and then find which of those
patterns match the bucket.
The pattern analysis action item is added to the menu if the data view
has a `message` or `error.message` field.
|
||
|
James Gowdy
|
1598ed8761
|
[ML] Adding capabilities and ML node check to create job button in dashboard (#172022)
Fixes https://github.com/elastic/kibana/issues/163575 When no jobs are available for selection the `Create job` button should be disabled for users who cannot create jobs and when no ML nodes are available. **When user has insufficient permissions** <img width="1372" alt="image" src=" |
||
|
Dima Arnautov
|
823552fea5
|
[ML] Add E5 model configs (#172053)
## Summary
- Adds E5 model configurations available for download, portable and x86
linux optimized.
- Adds `getCuratedModelConfig` shared service to retrieve the model ID
and configuration appropriate for the current cluster architecture.
- Updates description for the ELSER model
- Renames tabs in the "Add trained model" flyout
- Renames the `name` property in the `ModelDefinitionResponse` interface
with `model_id`
<img width="1835" alt="image"
src="
|
||
|
James Gowdy
|
a4845721d3
|
[ML] Fixing kibana object list in new job from recognised index page (#171935)
Fixes issue where the list of kibana objects in a module are not being rendered correctly. The issue was caused by the kibana objects from the module not being initially added to the list. **Before** 
Walter Rafelsberger
|
9f86c05d03
|
[ML] Transforms/Data frame analytics: Align data view / destination index creation workflow in wizards. (#171202)
Consolidates UI elements and backend code to create/delete data views and destination indices related to transforms and data frame analytics. We ended up with two different approaches for creating data views in the wizards for transforms and data frame analytics, the original reason was we were not aware of the `allowNoIndex: true` setting and worked around that in different ways. This PR aligns UI workflows and moves related code to a new package `@kbn/ml-data-view-utils` for data views and `@kbn/ml-creation-wizard-utils` for the destination index form. The latter might be used for other shared components across wizard.. In Data Frame Analytics, the checkbox to create a data view was removed from the last "Create" step, instead the option to create a data view was moved to the "Details" step. In Transforms, the UI component to create the destination index was brought over from DFA where there is a switch option to automatically use the job ID as the name for the destination index by default. |
||
Melissa Alvarez
|
f89f980b15
|
[ML] Trained models: adds a missing job node to models map view when original job has been deleted (#171590)
## Summary
Fixes https://github.com/elastic/kibana/issues/164626
Instead of throwing an error when a model's source job has been deleted
- return a 'missing job' node.
<img width="1448" alt="image"
src="
|
||
Drew Tate
|
a8647151cb
|
Unify style for embeddable-stack loaders (#171238)
## Summary Fix https://github.com/elastic/kibana/issues/170428 The bug this is intended to resolve requires some in-depth steps to reproduce. Follow the instructions in the issue above. Then, merge in this branch and compare. ### Checklist - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Dima Arnautov
|
c8537bf964
|
[ML] "Add model" flyout for the Trained Models UI (#171024)
## Summary Adds the "Add trained model" button to the Trained Models UI that opens the flyout with available models for download. It also contains the "Third-party" tab with instructions for deploying 3rd party models with Eland. <img width="1685" 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="
|
||
|
Dima Arnautov
|
40e9ee33ea
|
[ML] Report render completion for the Anomaly swim lane embeddable (#171879)
## Summary Reports render completion for the Anomaly swim lane embeddable with the `onRenderChange` callback by elastic-charts. |
||
|
James Gowdy
|
e7c793e0d7
|
[ML] Fixing blocked jobs polling interval (#171878)
There is a bug with the way we check whether or not to start polling for blocked jobs. We should only start polling there isn't an existing poll running. This causes the polling to run as possible and to refresh the full jobs list on every check. Now the blocked jobs polling correctly runs at the interval of 2s and the full jobs list is only updated when there is a change in the list of blocked jobs. Partially fixes https://github.com/elastic/kibana/issues/171626 A more in-depth change as specified in the issue can be done in follow up work. It's good to get this change in for the next release just in case we run out of time for the larger change. |
||
|
Melissa Alvarez
|
0124a50937
|
[ML] Trained models: ensure 'Deploy model' disabled for Data Frame Analytics models when not enough permissions (#171686)
## Summary Fixes https://github.com/elastic/kibana/issues/171063 This PR ensures the 'Deploy model' action for Data Frame Analytics models in the trained models list is only enabled when the user has sufficient permissions. ### 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> |
||
|
Walter Rafelsberger
|
aae3e5d087
|
[ML] Rename index pattern references to data view (Part 2) (#171820)
- Renames references to index patterns to data views in function and variable names. - Some inconsistent naming of schemas for data frame analytics was cleaned up as part of this PR. - Note this doesn't cover the whole ml owned codebase but just code related to data frame analytics. |
||
|
Walter Rafelsberger
|
11acc025b5
|
[ML] Rename index pattern references to data view. (#171627)
Renames references to index pattern to data views. - Updates references in `data-test-subj` attributes for data frame analytics. - Renames methods in the ` ml.testResources` service used in tests. - `IndexPattern` references in testing code referring to single indices were renamed to use `IndexName`. For variable names still using `IndexPattern` they were prefixed with e.g. `esIndexPattern` to avoid ambiguity with the legacy data view name. Note there are still references in the state management code of the data frame analytics creation wizard, this wasn't picked up in this PR since it focuses mostly on test related code. |
||
|
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> |
||
Thomas Watson
|
4f9094caf3
|
Always throw error objects - never strings (#171498) | ||
Eyo O. Eyo
|
f27427b949
|
Removes duplicated RedirectAppLinks component (#170304)
## Summary
This PR removes the [duplicated RedirectAppLinks
component](https://github.com/elastic/kibana/blob/v8.10.4/src/plugins/kibana_react/public/app_links/redirect_app_link.tsx)
which has been marked as deprecated since
|
||
Alex Szabo
|
33757f64ca
|
fix: incorrect import causes storybook build to fail (#171033)
## Summary
[This
change](
|
||
|
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=" |
||
|
James Gowdy
|
91c50c2873
|
[ML] Kibana context types clean up (#170868)
Corrects the types describing the services added to ML's kibana context. Most of the churn here is me alphabetically sorting the lists of dependencies. Also Removes `appName` from the context as it was never actually set. In the places where it was being used I've switched to our `PLUGIN_ID` |
||
|
James Gowdy
|
c1681c8d49
|
[ML] Disable anomaly detection job creation from ES|QL lens visualizations (#170711)
Fixes https://github.com/elastic/kibana/issues/170670 We currently do not support ES|QL in anomaly detection jobs. An ES|QL Lens vis cannot have mixed layers, as in one layer using ES|QL and another using DSL, therefore we need to completely disable the ML action item in the menu. Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
Hannah Mudge
|
a7728e44c4
|
[Dashboard Navigation] Make locator generic (#167928)
Closes https://github.com/elastic/kibana/issues/164748 ## Summary Previously, the link embeddable **always** used the Dashboard plugin's locator - this meant that, for portable dashboards (such as those in Security or in APM), navigation through the link embeddable would always send the user to the Dashboard plugin rather than staying in whatever context the portable dashboard was in. This PR fixes that by ensuring that each `DashboardRenderer` consumer can provide their **own** locator as a prop - this means that the Dashboard app can still use its own locator, while the Security/APM plugins (for example) can **also** define a locator so that navigation remains in the security/APM app. ### Security @elastic/security-solution-platform While I did my best to modify each portable dashboard implementation to include this new locator prop, without the full context on how each plugin wants to handle the link embeddable, I've had to make a few assumptions about the behaviour. For example, in security.... - The Security dashboards **not** respond to the query bar in the same way that they do in the Dashboard app - therefore, the link embeddable settings for "Use filters and query from origin dashboard" and "Use date range from origin dashboard" do not make sense in this context. For example, in Security, it is (from my understanding) **expected** that the query bar would always remain constant, regardless of these settings; therefore, these settings are more-or-less ignored. Unfortunately, this opens up a potential confusion for users, especially if the are editing/creating a link embeddable in the security context. - The Security app does not currently use real locators, and my attempts to remedy this were unsuccessful. Therefore, rather than requiring a **true** `Locator` object to be passed in as a prop to the `DashboardRenderer`, I had to instead accept any object that has both a `navigate` and `getRedirectUrl` method defined. It would be **much** cleaner for the Security plugin to define its own locator - that way, the `DashboardRenderer` could instead just accept a locator ID as a prop, and the link embeddable could use that ID fetch the appropriate locator as necessary; however, this is a pretty major refactor, since the Security app handles URLs/navigation in a much different way than any other Kibana app. **Before:** |
||
|
James Gowdy
|
ac0d04d355
|
[ML] Assigning elser models to the * space (#169939)
Fixes https://github.com/elastic/kibana/issues/169771 Adds a new endpoint `/internal/ml/trained_models/install_elastic_trained_model/:modelId` which wraps the `putTrainedModel` call to start the download of the elser model. It then reassigns the saved object's space to be `*`. Also updates the saved object sync call to ensure any internal models (ones which start with `.`) are assigned to the `*` space, if they've needed syncing. It is still possible for a user to reassign the spaces for an elser model and get themselves into the situation covered described in https://github.com/elastic/kibana/issues/169771. In this situation, I believe the best we can do is suggest the user adjusts the spaces via the stack management page. At the moment a `Model already exists` error is displayed in a toast. In a follow up PR we could catch this and show more information to direct the user to the stack management page. --------- Co-authored-by: Dima Arnautov <arnautov.dima@gmail.com> |
||
Alejandro Fernández Haro
|
dfec895836
|
Fix unhandledRejections part 2 (#169522)
|
||
Cee Chen
|
d079e9573d
|
Upgrade EUI to v90.0.0 (#170179)
`v89.1.0`⏩`v90.0.0`
The majority of changes in this PR come from:
- **EuiContextMenu** being converted to Emotion
(https://github.com/elastic/eui/pull/7312). If your usage of
`EuiContextMenu` was significantly affected, we recommend pulling down
this PR and QAing it locally.
- `defaultProps` being removed from some very widespread components,
particularly **EuiButton**, in anticipation of React's upcoming
deprecation.
(
|
||
James Rodewig
|
0997cb2523
|
Update UI copy for tech preview (#170143)
|
||
|
James Gowdy
|
a509a3abf8
|
[ML] Allow temporary data views in AD job wizards (#170112)
When creating a brand new job, temporary data views can be created and
used in the wizard.
When cloning a job where the data view cannot be found, a new temporary
data view is created to be used in the wizard.
This can happen if the data view used to create the original job has
been deleted or the job was created with a temporary data view.
|
||
|
Walter Rafelsberger
|
3ea90b3baa
|
[ML] Fixes multi line truncation for id/description columns in job lists (#169830)
Makes use of EUI's new multi-line truncation option for table columns (https://github.com/elastic/eui/issues/7226). For columns that use this feature, this PR wraps the text in custom render functions which add a `span` element with a `title` attribute and the cells text. |
||
|
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> |
||
Ignacio Rivas
|
9d0c7d7df2
|
[ES UI Shared] Remove old ace based EuiCodeEditor (#169613)
|
||
|
Melissa Alvarez
|
7e97dd90e7
|
[ML][AIOps] Telemetry: Track change point detection runs (#169158)
## Summary This PR adds UI tracking for Change Point Detection for AIOps. - tracks type of analysis and source (where the analysis is being run from) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com> |
||
Anton Dosov
|
ce9a765d8e
|
Improve ML serverless breadcrumbs for oblt and security (#169513)
## Summary close https://github.com/elastic/kibana/issues/167337 It introduces a new way to automatically set the deeper context breadcrumbs in serverless navigation. Instead of using the `serverless.setBreadcrumbs` for setting deeper context breadcrumbs in serverless, the project navigation service merges navigational breadcrumbs with regular chrome's breadcrumbs by deepLinkId |