mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
21368 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
d3a625ef4a
|
[8.6] [Monitoring] Read expiryDateMS from the right path in License rule (#148129) (#148212)
# Backport This will backport the following commits from `main` to `8.6`: - [[Monitoring] Read expiryDateMS from the right path in License rule (#148129)](https://github.com/elastic/kibana/pull/148129) <!--- 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":"2022-12-29T17:28:13Z","message":"[Monitoring] Read expiryDateMS from the right path in License rule (#148129)\n\nThe license details have been placed under the `meta` property but the\r\ncontext messages were not updated to read correctly from that path, this\r\nPR fixes that little issue.","sha":"0b83a2a61a1a560bc8394574d50db4e9ced00731","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","Feature:Stack Monitoring","backport:all-open","v8.7.0"],"number":148129,"url":"https://github.com/elastic/kibana/pull/148129","mergeCommit":{"message":"[Monitoring] Read expiryDateMS from the right path in License rule (#148129)\n\nThe license details have been placed under the `meta` property but the\r\ncontext messages were not updated to read correctly from that path, this\r\nPR fixes that little issue.","sha":"0b83a2a61a1a560bc8394574d50db4e9ced00731"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148129","number":148129,"mergeCommit":{"message":"[Monitoring] Read expiryDateMS from the right path in License rule (#148129)\n\nThe license details have been placed under the `meta` property but the\r\ncontext messages were not updated to read correctly from that path, this\r\nPR fixes that little issue.","sha":"0b83a2a61a1a560bc8394574d50db4e9ced00731"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
Marco Antonio Ghiani
|
a02f42b9ac
|
[8.6] [Stack Monitoring] Filter CCR list by currently viewed cluster (#148018) (#148363)
# Backport This will backport the following commits from `main` to `8.6`: - [[Stack Monitoring] Filter CCR list by currently viewed cluster (#148018)](https://github.com/elastic/kibana/pull/148018) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2023-01-04T07:16:28Z","message":"[Stack Monitoring] Filter CCR list by currently viewed cluster (#148018)\n\n## 📓 Summary\r\n\r\nCloses #147224 \r\n\r\nThe issue was caused by the missing usage of the `clusterUuid` parameter\r\nin the query used to retrieve the cluster followers and stats.\r\n\r\nAdding a `term` condition for the cluster_uuid now retrieves only the\r\nfollowers related to the interested cluster. In case a cluster has no\r\nfollowers, an empty list will be returned by the endpoint.\r\n\r\nThis PR also adds stronger typing against the data returned by the\r\nendpoint and adds some minor improvements.\r\n\r\n## 🧪 Testing\r\nTesting locally this PR requires some effort since is necessary to\r\ncreate a multi-cluster locally.\r\nFollowing [this\r\nguide](https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/dev_docs/how_to/running_components_from_source.md#multi-cluster-tests-for-ccrccs-or-listing)\r\nis possible to locally setup the 2 cluster and make one of them follow\r\nthe other.\r\nAlso, the new issue\r\n[oblt#3279](https://github.com/elastic/observability-test-environments/issues/3279)\r\nhas been opened to have an easier way to access a multi-cluster setup\r\nwith oblt clusters.\r\n\r\n### Before bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954682-b519fcd3-888b-472a-8a1d-acf57ff5de05.mov\r\n\r\n### After bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954718-5045c49e-f113-42e5-aabf-81d2c5f53556.mov\r\n\r\nCo-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"296025b1e7c7c29490bc7d8137c33375b83adb58","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","Feature:Stack Monitoring","backport:prev-minor","v8.6.0","v8.7.0"],"number":148018,"url":"https://github.com/elastic/kibana/pull/148018","mergeCommit":{"message":"[Stack Monitoring] Filter CCR list by currently viewed cluster (#148018)\n\n## 📓 Summary\r\n\r\nCloses #147224 \r\n\r\nThe issue was caused by the missing usage of the `clusterUuid` parameter\r\nin the query used to retrieve the cluster followers and stats.\r\n\r\nAdding a `term` condition for the cluster_uuid now retrieves only the\r\nfollowers related to the interested cluster. In case a cluster has no\r\nfollowers, an empty list will be returned by the endpoint.\r\n\r\nThis PR also adds stronger typing against the data returned by the\r\nendpoint and adds some minor improvements.\r\n\r\n## 🧪 Testing\r\nTesting locally this PR requires some effort since is necessary to\r\ncreate a multi-cluster locally.\r\nFollowing [this\r\nguide](https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/dev_docs/how_to/running_components_from_source.md#multi-cluster-tests-for-ccrccs-or-listing)\r\nis possible to locally setup the 2 cluster and make one of them follow\r\nthe other.\r\nAlso, the new issue\r\n[oblt#3279](https://github.com/elastic/observability-test-environments/issues/3279)\r\nhas been opened to have an easier way to access a multi-cluster setup\r\nwith oblt clusters.\r\n\r\n### Before bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954682-b519fcd3-888b-472a-8a1d-acf57ff5de05.mov\r\n\r\n### After bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954718-5045c49e-f113-42e5-aabf-81d2c5f53556.mov\r\n\r\nCo-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"296025b1e7c7c29490bc7d8137c33375b83adb58"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148018","number":148018,"mergeCommit":{"message":"[Stack Monitoring] Filter CCR list by currently viewed cluster (#148018)\n\n## 📓 Summary\r\n\r\nCloses #147224 \r\n\r\nThe issue was caused by the missing usage of the `clusterUuid` parameter\r\nin the query used to retrieve the cluster followers and stats.\r\n\r\nAdding a `term` condition for the cluster_uuid now retrieves only the\r\nfollowers related to the interested cluster. In case a cluster has no\r\nfollowers, an empty list will be returned by the endpoint.\r\n\r\nThis PR also adds stronger typing against the data returned by the\r\nendpoint and adds some minor improvements.\r\n\r\n## 🧪 Testing\r\nTesting locally this PR requires some effort since is necessary to\r\ncreate a multi-cluster locally.\r\nFollowing [this\r\nguide](https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/dev_docs/how_to/running_components_from_source.md#multi-cluster-tests-for-ccrccs-or-listing)\r\nis possible to locally setup the 2 cluster and make one of them follow\r\nthe other.\r\nAlso, the new issue\r\n[oblt#3279](https://github.com/elastic/observability-test-environments/issues/3279)\r\nhas been opened to have an easier way to access a multi-cluster setup\r\nwith oblt clusters.\r\n\r\n### Before bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954682-b519fcd3-888b-472a-8a1d-acf57ff5de05.mov\r\n\r\n### After bugfix\r\n\r\n\r\nhttps://user-images.githubusercontent.com/34506779/209954718-5045c49e-f113-42e5-aabf-81d2c5f53556.mov\r\n\r\nCo-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"296025b1e7c7c29490bc7d8137c33375b83adb58"}}]}] BACKPORT--> |
||
Katerina Patticha
|
1804a3479e
|
[8.6] [APM] Enable Operations Breakdown by default (#148305) (#148345)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Enable Operations Breakdown by default (#148305)](https://github.com/elastic/kibana/pull/148305) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Katerina Patticha","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2023-01-03T16:57:16Z","message":"[APM] Enable Operations Breakdown by default (#148305)\n\n## Summary\r\n\r\ncloses: |
||
|
Kibana Machine
|
03032f86d3
|
[8.6] increase bulk action retry to 5 (#148169) (#148194)
# Backport This will backport the following commits from `main` to `8.6`: - [increase bulk action retry to 5 (#148169)](https://github.com/elastic/kibana/pull/148169) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-29T14:28:36Z","message":"increase bulk action retry to 5 (#148169)\n\n## Summary\r\n\r\nIncrease retry count to 5 to help retry on agent doc version conflict.\r\nIt looks like 3 retries are not enough for 100k agents update tags.\r\nhttps://github.com/elastic/kibana/issues/144161\r\n\r\nThis can be tested on an ECE high memory instance with 100k horde\r\nagents.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a9ac5aeb1eac631a2c365004c3f38fdca5c33291","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","ci:cloud-deploy","v8.7.0","v8.6.1"],"number":148169,"url":"https://github.com/elastic/kibana/pull/148169","mergeCommit":{"message":"increase bulk action retry to 5 (#148169)\n\n## Summary\r\n\r\nIncrease retry count to 5 to help retry on agent doc version conflict.\r\nIt looks like 3 retries are not enough for 100k agents update tags.\r\nhttps://github.com/elastic/kibana/issues/144161\r\n\r\nThis can be tested on an ECE high memory instance with 100k horde\r\nagents.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a9ac5aeb1eac631a2c365004c3f38fdca5c33291"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148169","number":148169,"mergeCommit":{"message":"increase bulk action retry to 5 (#148169)\n\n## Summary\r\n\r\nIncrease retry count to 5 to help retry on agent doc version conflict.\r\nIt looks like 3 retries are not enough for 100k agents update tags.\r\nhttps://github.com/elastic/kibana/issues/144161\r\n\r\nThis can be tested on an ECE high memory instance with 100k horde\r\nagents.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"a9ac5aeb1eac631a2c365004c3f38fdca5c33291"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
973aba5971
|
[8.6] [Enterprise Search] Fix buggy data loading for index details page (#148032) (#148149)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Fix buggy data loading for index details page (#148032)](https://github.com/elastic/kibana/pull/148032) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sloane Perrault","email":"sloane.perrault@elastic.co"},"sourceCommit":{"committedDate":"2022-12-28T14:29:48Z","message":"[Enterprise Search] Fix buggy data loading for index details page (#148032)\n\n## Summary\r\n\r\nCalling this on mount and on `setIndexName` which is issued via React\r\n`useEffect` would cause a data race. This would sometimes cause the last\r\nviewed index to be fetched at first and the data for the index actually\r\nbeing viewed wouldn't show until the first poll.\r\n\r\n<details>\r\n<summary>🐛 Buggy behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1410658/195652568-7e269b45-17ae-4941-96e5-0bcc2fae1af5.mov\r\n\r\n</details>\r\n\r\n<details>\r\n<summary>🔧 Fixed behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1699281/209221538-4f518689-f44e-468b-870a-226503760d9b.mov\r\n\r\n</details>\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cc38847c4ef2d50336bab3ed163c37fbd3a80d1d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","backport:prev-minor","v8.7.0"],"number":148032,"url":"https://github.com/elastic/kibana/pull/148032","mergeCommit":{"message":"[Enterprise Search] Fix buggy data loading for index details page (#148032)\n\n## Summary\r\n\r\nCalling this on mount and on `setIndexName` which is issued via React\r\n`useEffect` would cause a data race. This would sometimes cause the last\r\nviewed index to be fetched at first and the data for the index actually\r\nbeing viewed wouldn't show until the first poll.\r\n\r\n<details>\r\n<summary>🐛 Buggy behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1410658/195652568-7e269b45-17ae-4941-96e5-0bcc2fae1af5.mov\r\n\r\n</details>\r\n\r\n<details>\r\n<summary>🔧 Fixed behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1699281/209221538-4f518689-f44e-468b-870a-226503760d9b.mov\r\n\r\n</details>\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cc38847c4ef2d50336bab3ed163c37fbd3a80d1d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148032","number":148032,"mergeCommit":{"message":"[Enterprise Search] Fix buggy data loading for index details page (#148032)\n\n## Summary\r\n\r\nCalling this on mount and on `setIndexName` which is issued via React\r\n`useEffect` would cause a data race. This would sometimes cause the last\r\nviewed index to be fetched at first and the data for the index actually\r\nbeing viewed wouldn't show until the first poll.\r\n\r\n<details>\r\n<summary>🐛 Buggy behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1410658/195652568-7e269b45-17ae-4941-96e5-0bcc2fae1af5.mov\r\n\r\n</details>\r\n\r\n<details>\r\n<summary>🔧 Fixed behavior</summary>\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1699281/209221538-4f518689-f44e-468b-870a-226503760d9b.mov\r\n\r\n</details>\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cc38847c4ef2d50336bab3ed163c37fbd3a80d1d"}}]}] BACKPORT--> Co-authored-by: Sloane Perrault <sloane.perrault@elastic.co> |
||
|
Kibana Machine
|
b4a10d4356
|
[8.6] [Cloud Posture] update data views spaces (#148093)
# Backport This will backport the following commits from `main` to `8.6`: - [[Cloud Posture] update data views spaces](https://github.com/elastic/kibana/pull/148087) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ido Cohen","email":"90558359+CohenIdo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-26T13:08:50Z","message":"[Cloud Posture] update data views spaces","sha":"4cd9246639cf67b7e3d85ab8a966add8deffacde","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","ReleaseStatus","v8.6.0","v8.7.0"],"number":148087,"url":"https://github.com/elastic/kibana/pull/148087","mergeCommit":{"message":"[Cloud Posture] update data views spaces","sha":"4cd9246639cf67b7e3d85ab8a966add8deffacde"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148087","number":148087,"mergeCommit":{"message":"[Cloud Posture] update data views spaces","sha":"4cd9246639cf67b7e3d85ab8a966add8deffacde"}}]}] BACKPORT--> Co-authored-by: Ido Cohen <90558359+CohenIdo@users.noreply.github.com> |
||
|
Kibana Machine
|
6a5d6d96a5
|
[8.6] [Enterprise Search] Make add domain input full width (#148064) (#148072)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Make add domain input full width (#148064)](https://github.com/elastic/kibana/pull/148064) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-23T16:46:26Z","message":"[Enterprise Search] Make add domain input full width (#148064)\n\nThis makes the add domain input in the Elastic crawler full width","sha":"ff228e6470955949cca74540f5e40682eeddaf9d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":148064,"url":"https://github.com/elastic/kibana/pull/148064","mergeCommit":{"message":"[Enterprise Search] Make add domain input full width (#148064)\n\nThis makes the add domain input in the Elastic crawler full width","sha":"ff228e6470955949cca74540f5e40682eeddaf9d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148064","number":148064,"mergeCommit":{"message":"[Enterprise Search] Make add domain input full width (#148064)\n\nThis makes the add domain input in the Elastic crawler full width","sha":"ff228e6470955949cca74540f5e40682eeddaf9d"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
Ashokaditya
|
15ecaa9469
|
[8.6] [Security Solution][Endpoint] Removes id field on nested entries for event filters (#148000) (#148046)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Endpoint] Removes id field on nested entries for event filters (#148000)](https://github.com/elastic/kibana/pull/148000) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"David Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T17:12:39Z","message":"[Security Solution][Endpoint] Removes id field on nested entries for event filters (#148000)\n\n## Summary\r\n\r\n- Removes id field on nested entries for event filters using the write\r\ntransform method.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6bdbf70fe3efc6fdf1877aaabbe4e525411b6d31","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Onboarding and Lifecycle Mgt","v8.6.0","v8.7.0"],"number":148000,"url":"https://github.com/elastic/kibana/pull/148000","mergeCommit":{"message":"[Security Solution][Endpoint] Removes id field on nested entries for event filters (#148000)\n\n## Summary\r\n\r\n- Removes id field on nested entries for event filters using the write\r\ntransform method.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6bdbf70fe3efc6fdf1877aaabbe4e525411b6d31"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148000","number":148000,"mergeCommit":{"message":"[Security Solution][Endpoint] Removes id field on nested entries for event filters (#148000)\n\n## Summary\r\n\r\n- Removes id field on nested entries for event filters using the write\r\ntransform method.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"6bdbf70fe3efc6fdf1877aaabbe4e525411b6d31"}}]}] BACKPORT--> Co-authored-by: David Sánchez <david.sanchezsoler@elastic.co> |
||
Aleh Zasypkin
|
1d08980636
|
[8.6] Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013) (#148044)
# Backport This will backport the following commits from `main` to `8.6`: - [Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)](https://github.com/elastic/kibana/pull/148013) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T18:44:11Z","message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:Security","Feature:Users/Roles/API Keys","release_note:skip","ci:no-auto-commit","backport:all-open","v8.7.0"],"number":148013,"url":"https://github.com/elastic/kibana/pull/148013","mergeCommit":{"message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148013","number":148013,"mergeCommit":{"message":"Ensure that API keys are rendered before performing bulk delete in functional tests. (#148013)","sha":"3a5f5626b2c3631eb2646782937171d2f87ce525"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
008b9efae5
|
[8.6] [Security Solution] [Exceptions] UX updates (#147955) (#148019)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] UX updates (#147955)](https://github.com/elastic/kibana/pull/147955) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T16:56:30Z","message":"[Security Solution] [Exceptions] UX updates (#147955)\n\n## Summary\r\n\r\n<details><summary>Display link on rule details page -> add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds manage rules functionality to list view overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot 2022-12-21 at 4 59 11 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames page to Shared exception lists and updates\r\npage description with hyperlink to manage rules page</summary>\r\n<img width=\"635\" alt=\"Screen Shot 2022-12-21 at 4 58 58 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates sidebar title + navigation title</summary>\r\n<img width=\"590\" alt=\"Screen Shot 2022-12-21 at 4 58 36 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null FYI displaying all shared exception lists on the rule\r\ndetails -> add exception flyout is not possible for 8.6. The ability to\r\nadd any exception to any list was not part of the original design of the\r\ncomponent and would require more time to update the component and the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks like the above is possible if we pass in `null` for the rules\r\nproperty of the `AddExceptionFlyout` but we might want to finalize a\r\ndesign to better help users trying to add the exception to a shared list\r\nwhile **inside** of the rule details page.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [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### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Rule Exceptions","Team:Security Solution Platform","backport:prev-minor","v8.6.0","v8.7.0"],"number":147955,"url":"https://github.com/elastic/kibana/pull/147955","mergeCommit":{"message":"[Security Solution] [Exceptions] UX updates (#147955)\n\n## Summary\r\n\r\n<details><summary>Display link on rule details page -> add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds manage rules functionality to list view overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot 2022-12-21 at 4 59 11 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames page to Shared exception lists and updates\r\npage description with hyperlink to manage rules page</summary>\r\n<img width=\"635\" alt=\"Screen Shot 2022-12-21 at 4 58 58 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates sidebar title + navigation title</summary>\r\n<img width=\"590\" alt=\"Screen Shot 2022-12-21 at 4 58 36 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null FYI displaying all shared exception lists on the rule\r\ndetails -> add exception flyout is not possible for 8.6. The ability to\r\nadd any exception to any list was not part of the original design of the\r\ncomponent and would require more time to update the component and the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks like the above is possible if we pass in `null` for the rules\r\nproperty of the `AddExceptionFlyout` but we might want to finalize a\r\ndesign to better help users trying to add the exception to a shared list\r\nwhile **inside** of the rule details page.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [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### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147955","number":147955,"mergeCommit":{"message":"[Security Solution] [Exceptions] UX updates (#147955)\n\n## Summary\r\n\r\n<details><summary>Display link on rule details page -> add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds manage rules functionality to list view overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot 2022-12-21 at 4 59 11 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames page to Shared exception lists and updates\r\npage description with hyperlink to manage rules page</summary>\r\n<img width=\"635\" alt=\"Screen Shot 2022-12-21 at 4 58 58 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates sidebar title + navigation title</summary>\r\n<img width=\"590\" alt=\"Screen Shot 2022-12-21 at 4 58 36 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null FYI displaying all shared exception lists on the rule\r\ndetails -> add exception flyout is not possible for 8.6. The ability to\r\nadd any exception to any list was not part of the original design of the\r\ncomponent and would require more time to update the component and the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks like the above is possible if we pass in `null` for the rules\r\nproperty of the `AddExceptionFlyout` but we might want to finalize a\r\ndesign to better help users trying to add the exception to a shared list\r\nwhile **inside** of the rule details page.\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [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### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
5f4de824fd
|
[8.6] [Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806) (#147817)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806)](https://github.com/elastic/kibana/pull/147806) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T21:49:00Z","message":"[Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806)\n\n**Fixes:** https://github.com/elastic/kibana/issues/146362\r\n\r\n## Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\" network throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:low","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rules","Feature:Rule Details","v8.6.0","v8.7.0"],"number":147806,"url":"https://github.com/elastic/kibana/pull/147806","mergeCommit":{"message":"[Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806)\n\n**Fixes:** https://github.com/elastic/kibana/issues/146362\r\n\r\n## Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\" network throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147806","number":147806,"mergeCommit":{"message":"[Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806)\n\n**Fixes:** https://github.com/elastic/kibana/issues/146362\r\n\r\n## Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\" network throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c"}}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> |
||
Terrance DeJesus
|
8a6f1ec8c1
|
[8.6] Remove Guided Onboarding Rule from 8.6 (#147936)
## Summary The guided onboarding feature is not ready for 8.6 and was pushed back to 8.7. As a result we need to remove the detection rule from the 8.6 branch. The rule is fine to remain in main as we intend it to be ready for the 8.7 release. As a side note, this rule should not make it into the 8.6 release either. |
||
|
Kibana Machine
|
1c30c54075
|
[8.6] [APM] Add parallel builds for cypress tests (#142598) (#147930)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Add parallel builds for cypress tests (#142598)](https://github.com/elastic/kibana/pull/142598) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Giorgos Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2022-12-21T15:36:08Z","message":"[APM] Add parallel builds for cypress tests (#142598)\n\n- Tests runs initiated by the flaky test runner are not recorded or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","v8.6.0","v8.7.0"],"number":142598,"url":"https://github.com/elastic/kibana/pull/142598","mergeCommit":{"message":"[APM] Add parallel builds for cypress tests (#142598)\n\n- Tests runs initiated by the flaky test runner are not recorded or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/142598","number":142598,"mergeCommit":{"message":"[APM] Add parallel builds for cypress tests (#142598)\n\n- Tests runs initiated by the flaky test runner are not recorded or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5"}}]}] BACKPORT--> Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co> |
||
|
Kibana Machine
|
867319cfae
|
[8.6] [Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641) (#147794)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641)](https://github.com/elastic/kibana/pull/147641) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:52:19Z","message":"[Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641)\n\n## Summary\r\n\r\nref: https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks @nkhristinin for pairing up on this today!\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","impact:critical","Feature:Rule Exceptions","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":147641,"url":"https://github.com/elastic/kibana/pull/147641","mergeCommit":{"message":"[Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641)\n\n## Summary\r\n\r\nref: https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks @nkhristinin for pairing up on this today!\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147641","number":147641,"mergeCommit":{"message":"[Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641)\n\n## Summary\r\n\r\nref: https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks @nkhristinin for pairing up on this today!\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Gloria Hornero <gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
6c82749a8c
|
[8.6] [Security Solution] Reduce load on Kibana generated by Cypress tests (#147349) (#147875)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Reduce load on Kibana generated by Cypress tests (#147349)](https://github.com/elastic/kibana/pull/147349) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2022-12-12T17:56:32Z","message":"[Security Solution] Reduce load on Kibana generated by Cypress tests (#147349)\n\n## Summary\r\n\r\nThis PR makes the following adjustments in the Cypress tests:\r\n\r\n- Increases the default rule interval from 1 second to 100 minutes.\r\n- Increases the long-polling interval for the\r\n`api/detection_engine/rules/prepackaged/_status` endpoint from 0.1 to 2\r\nseconds.\r\n\r\nThis should hopefully reduce the load that Cypress tests generate on CI\r\non Kibana which makes the tests themselves slower.\r\n\r\nIn the next episodes:\r\n\r\n- https://github.com/elastic/kibana/issues/147377\r\n\r\n## Background\r\n\r\nWith the recent issues related to installing the prebuilt rules package,\r\n\r\n> @dhurley14 did some initial research and found that there are some\r\nbulk_edit cypress tests that are going into an infinitely loop. Looks\r\nlike the infinite loops can be reproduced locally and are happening here\r\n[ |
||
|
Kibana Machine
|
e8c73a3189
|
[8.6] [Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854) (#147911)
# Backport This will backport the following commits from `main` to `8.6`: - [[Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854)](https://github.com/elastic/kibana/pull/147854) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2022-12-21T11:30:15Z","message":"[Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n## Summary\r\n\r\nFixes the bug that pdf reports can be generated with blurry text, for\r\nexample:\r\n\r\n\r\n\r\n\r\nFixed version example: \r\n\r\n\r\n\r\n\r\nThe bug happened because the device pixel ration was changing\r\nmid-capture. The the page was opened with scaleFactor=1. Before the\r\nscreenshot is captured, the viewport is resized to scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts as most of them don't\r\nredraw on devicePixelRatio changes (this has to be fixed separately).\r\nThis fix attempts to open the page with the final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n### Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF reports\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Reporting","Team:Global Experience","backport:prev-minor","v8.7.0"],"number":147854,"url":"https://github.com/elastic/kibana/pull/147854","mergeCommit":{"message":"[Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n## Summary\r\n\r\nFixes the bug that pdf reports can be generated with blurry text, for\r\nexample:\r\n\r\n\r\n\r\n\r\nFixed version example: \r\n\r\n\r\n\r\n\r\nThe bug happened because the device pixel ration was changing\r\nmid-capture. The the page was opened with scaleFactor=1. Before the\r\nscreenshot is captured, the viewport is resized to scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts as most of them don't\r\nredraw on devicePixelRatio changes (this has to be fixed separately).\r\nThis fix attempts to open the page with the final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n### Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF reports\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147854","number":147854,"mergeCommit":{"message":"[Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n## Summary\r\n\r\nFixes the bug that pdf reports can be generated with blurry text, for\r\nexample:\r\n\r\n\r\n\r\n\r\nFixed version example: \r\n\r\n\r\n\r\n\r\nThe bug happened because the device pixel ration was changing\r\nmid-capture. The the page was opened with scaleFactor=1. Before the\r\nscreenshot is captured, the viewport is resized to scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts as most of them don't\r\nredraw on devicePixelRatio changes (this has to be fixed separately).\r\nThis fix attempts to open the page with the final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n### Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF reports\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
Walter Rafelsberger
|
0586a4bc15
|
[8.6] [ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711) (#147889)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711)](https://github.com/elastic/kibana/pull/147711) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-20T19:29:47Z","message":"[ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711)\n\nFix to avoid aggregating on `aggregate_metric_double` field types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Transforms","v8.6.0","v8.7.0"],"number":147711,"url":"https://github.com/elastic/kibana/pull/147711","mergeCommit":{"message":"[ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711)\n\nFix to avoid aggregating on `aggregate_metric_double` field types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147711","number":147711,"mergeCommit":{"message":"[ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711)\n\nFix to avoid aggregating on `aggregate_metric_double` field types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
bed40632ae
|
[8.6] [Enterprise Search] Gate native connectors for low-memory deployments (#147845) (#147883)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Gate native connectors for low-memory deployments (#147845)](https://github.com/elastic/kibana/pull/147845) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-20T17:31:04Z","message":"[Enterprise Search] Gate native connectors for low-memory deployments (#147845)\n\nThis blocks native connectors from being deployed on deployments with\r\ntoo little memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":147845,"url":"https://github.com/elastic/kibana/pull/147845","mergeCommit":{"message":"[Enterprise Search] Gate native connectors for low-memory deployments (#147845)\n\nThis blocks native connectors from being deployed on deployments with\r\ntoo little memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147845","number":147845,"mergeCommit":{"message":"[Enterprise Search] Gate native connectors for low-memory deployments (#147845)\n\nThis blocks native connectors from being deployed on deployments with\r\ntoo little memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
35ca3798b9
|
[8.6] [ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597) (#147865)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597)](https://github.com/elastic/kibana/pull/147597) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-20T15:31:12Z","message":"[ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597)\n\nFor groups that have multiple values for the same field, the group\r\nhistogram query wasn't able to fetch data because it filters with a bool\r\n`must` and individual `term` aggregations. This PR fixes it by using a\r\n`terms` aggregation if there are multiple values for a field so just\r\nthese get treated as `OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147597,"url":"https://github.com/elastic/kibana/pull/147597","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597)\n\nFor groups that have multiple values for the same field, the group\r\nhistogram query wasn't able to fetch data because it filters with a bool\r\n`must` and individual `term` aggregations. This PR fixes it by using a\r\n`terms` aggregation if there are multiple values for a field so just\r\nthese get treated as `OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147597","number":147597,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597)\n\nFor groups that have multiple values for the same field, the group\r\nhistogram query wasn't able to fetch data because it filters with a bool\r\n`must` and individual `term` aggregations. This PR fixes it by using a\r\n`terms` aggregation if there are multiple values for a field so just\r\nthese get treated as `OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
Kibana Machine
|
335b86a633
|
[8.6] [Fleet] refactored bulk update tags retry (#147594) (#147839)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] refactored bulk update tags retry (#147594)](https://github.com/elastic/kibana/pull/147594) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-20T09:36:36Z","message":"[Fleet] refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/144161\r\n\r\nAs discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe existing implementation of update tags doesn't work well with real\r\nagents, as there are many conflicts with checkin, even when trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries more efficient:\r\n- Instead of aborting the whole bulk action on conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but only the 1k conflicts,\r\nthis makes it less likely to conflict on retry.\r\n- Because of this, on retry we have to know which agents don't yet have\r\nthe tag added/removed. For this, added an additional filter to the\r\n`updateByQuery` request. Only adding the filter if there is exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use case from the\r\nUI, and handling other cases would complicate the logic more (each\r\nadditional tag to add/remove would result in another OR query, which\r\nwould match more agents, making conflicts more likely).\r\n- Added this additional query on the initial request as well (not only\r\nretries) to save on unnecessary work e.g. if the user tries to add a tag\r\non 50k agents, but 48k already have it, it is enough to update the\r\nremaining 2k agents.\r\n- This improvement has the effect that 'Agent activity' shows the real\r\nupdated agent count, not the total selected. I think this is not really\r\na problem for update tags.\r\n- Cleaned up some of the UI logic, because the conflicts are fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll 50k agents (I used 50k with create_agents script, and 1k with\r\nhorde). Enroll 50k with horde if possible.\r\n- Select all on UI and try to add/remove one or more tags\r\n- Expect the changes to propagate quickly (up to 1m). It might take a\r\nfew refreshes to see the result on agent list and tags list, because the\r\nUI polls the agents every 30s. It is expected that the tags list\r\ntemporarily shows incorrect data because the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag quickly:\r\n<img width=\"1776\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img width=\"422\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe logs show the details of how many `version_conflicts` were there,\r\nand it decreased with retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet] {\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet] {\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet] Action failed: version conflict of 10857 agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet] Action failed: version conflict of 26245 agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet] {\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de failed: version conflict of 1000 agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO ][plugins.fleet] processed 26245 agents, took 5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet] {\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] processed 1000 agents, took 379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.7.0","v8.6.1"],"number":147594,"url":"https://github.com/elastic/kibana/pull/147594","mergeCommit":{"message":"[Fleet] refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/144161\r\n\r\nAs discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe existing implementation of update tags doesn't work well with real\r\nagents, as there are many conflicts with checkin, even when trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries more efficient:\r\n- Instead of aborting the whole bulk action on conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but only the 1k conflicts,\r\nthis makes it less likely to conflict on retry.\r\n- Because of this, on retry we have to know which agents don't yet have\r\nthe tag added/removed. For this, added an additional filter to the\r\n`updateByQuery` request. Only adding the filter if there is exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use case from the\r\nUI, and handling other cases would complicate the logic more (each\r\nadditional tag to add/remove would result in another OR query, which\r\nwould match more agents, making conflicts more likely).\r\n- Added this additional query on the initial request as well (not only\r\nretries) to save on unnecessary work e.g. if the user tries to add a tag\r\non 50k agents, but 48k already have it, it is enough to update the\r\nremaining 2k agents.\r\n- This improvement has the effect that 'Agent activity' shows the real\r\nupdated agent count, not the total selected. I think this is not really\r\na problem for update tags.\r\n- Cleaned up some of the UI logic, because the conflicts are fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll 50k agents (I used 50k with create_agents script, and 1k with\r\nhorde). Enroll 50k with horde if possible.\r\n- Select all on UI and try to add/remove one or more tags\r\n- Expect the changes to propagate quickly (up to 1m). It might take a\r\nfew refreshes to see the result on agent list and tags list, because the\r\nUI polls the agents every 30s. It is expected that the tags list\r\ntemporarily shows incorrect data because the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag quickly:\r\n<img width=\"1776\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img width=\"422\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe logs show the details of how many `version_conflicts` were there,\r\nand it decreased with retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet] {\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet] {\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet] Action failed: version conflict of 10857 agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet] Action failed: version conflict of 26245 agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet] {\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de failed: version conflict of 1000 agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO ][plugins.fleet] processed 26245 agents, took 5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet] {\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] processed 1000 agents, took 379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147594","number":147594,"mergeCommit":{"message":"[Fleet] refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/144161\r\n\r\nAs discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe existing implementation of update tags doesn't work well with real\r\nagents, as there are many conflicts with checkin, even when trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries more efficient:\r\n- Instead of aborting the whole bulk action on conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but only the 1k conflicts,\r\nthis makes it less likely to conflict on retry.\r\n- Because of this, on retry we have to know which agents don't yet have\r\nthe tag added/removed. For this, added an additional filter to the\r\n`updateByQuery` request. Only adding the filter if there is exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use case from the\r\nUI, and handling other cases would complicate the logic more (each\r\nadditional tag to add/remove would result in another OR query, which\r\nwould match more agents, making conflicts more likely).\r\n- Added this additional query on the initial request as well (not only\r\nretries) to save on unnecessary work e.g. if the user tries to add a tag\r\non 50k agents, but 48k already have it, it is enough to update the\r\nremaining 2k agents.\r\n- This improvement has the effect that 'Agent activity' shows the real\r\nupdated agent count, not the total selected. I think this is not really\r\na problem for update tags.\r\n- Cleaned up some of the UI logic, because the conflicts are fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll 50k agents (I used 50k with create_agents script, and 1k with\r\nhorde). Enroll 50k with horde if possible.\r\n- Select all on UI and try to add/remove one or more tags\r\n- Expect the changes to propagate quickly (up to 1m). It might take a\r\nfew refreshes to see the result on agent list and tags list, because the\r\nUI polls the agents every 30s. It is expected that the tags list\r\ntemporarily shows incorrect data because the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag quickly:\r\n<img width=\"1776\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img width=\"422\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe logs show the details of how many `version_conflicts` were there,\r\nand it decreased with retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet] {\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet] {\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet] Action failed: version conflict of 10857 agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet] Action failed: version conflict of 26245 agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet] {\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents: 52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet] Retry #1 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de failed: version conflict of 1000 agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet] Retrying in task: fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO ][plugins.fleet] processed 26245 agents, took 5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO ][plugins.fleet] Running bulk action retry task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2 of task fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Running action asynchronously, actionId: 90acd541-19ac-4738-b3d3-db32789233de, total agents: 52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO ][plugins.fleet] Scheduling task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet] {\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] processed 1000 agents, took 379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing task fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Walter Rafelsberger
|
32265b766d
|
[8.6] [ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592) (#147832)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)](https://github.com/elastic/kibana/pull/147592) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-20T08:19:11Z","message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147592,"url":"https://github.com/elastic/kibana/pull/147592","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147592","number":147592,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592)\n\nFixes client side code to transform groups into table rows. Because the\r\ntransformation used a dictionary like structure with field names as\r\nkeys, we missed if there were multiple values for a field. This changes\r\nthe structure to an array of field/value pairs so we can support\r\nmultiple values per field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
47066b37dc
|
[8.6] [ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614) (#147792)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)](https://github.com/elastic/kibana/pull/147614) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-19T17:35:31Z","message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147614,"url":"https://github.com/elastic/kibana/pull/147614","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147614","number":147614,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
Kibana Machine
|
3d1a52e139
|
[8.6] [Enterprise Search] Add copy button for pipelines (#147712) (#147771)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Add copy button for pipelines (#147712)](https://github.com/elastic/kibana/pull/147712) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-19T14:24:26Z","message":"[Enterprise Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy button shows up for curl requests on the\r\nconnectors pipeline page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":147712,"url":"https://github.com/elastic/kibana/pull/147712","mergeCommit":{"message":"[Enterprise Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy button shows up for curl requests on the\r\nconnectors pipeline page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147712","number":147712,"mergeCommit":{"message":"[Enterprise Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy button shows up for curl requests on the\r\nconnectors pipeline page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
Ersin Erdal
|
77715566f2
|
[8.6] [Fix] scheduling multiple recovered alert actions (#147617) (#147715)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fix] scheduling multiple recovered alert actions (#147617)](https://github.com/elastic/kibana/pull/147617) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ersin Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-16T18:04:36Z","message":"[Fix] scheduling multiple recovered alert actions (#147617)\n\nRemoves the code that blocks running multiple recovered actions of an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","ci:cloud-deploy","v8.7.0","v8.6.1"],"number":147617,"url":"https://github.com/elastic/kibana/pull/147617","mergeCommit":{"message":"[Fix] scheduling multiple recovered alert actions (#147617)\n\nRemoves the code that blocks running multiple recovered actions of an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147617","number":147617,"mergeCommit":{"message":"[Fix] scheduling multiple recovered alert actions (#147617)\n\nRemoves the code that blocks running multiple recovered actions of an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Alison Goryachev
|
49a1e9b2e7
|
[Guided onboarding] Disable guided onboarding (#147649) | ||
|
Kibana Machine
|
74baee4a17
|
[8.6] Consistency fixes for Elasticsearch client custom integrations (#147690)
# Backport This will backport the following commits from `main` to `8.6`: - [Consistency fixes for Elasticsearch client custom integrations](https://github.com/elastic/kibana/pull/147627) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Seth Michael Larson","email":"seth.larson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-16T13:27:36Z","message":"Consistency fixes for Elasticsearch client custom integrations\n\nThis PR is a follow-up to a set of consistency fixes identified after\r\nall integrations were completed. Removes the \"Generate API Key\" button\r\nand also removes the example Cloud ID in favor of an obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.7.0"],"number":147627,"url":"https://github.com/elastic/kibana/pull/147627","mergeCommit":{"message":"Consistency fixes for Elasticsearch client custom integrations\n\nThis PR is a follow-up to a set of consistency fixes identified after\r\nall integrations were completed. Removes the \"Generate API Key\" button\r\nand also removes the example Cloud ID in favor of an obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147627","number":147627,"mergeCommit":{"message":"Consistency fixes for Elasticsearch client custom integrations\n\nThis PR is a follow-up to a set of consistency fixes identified after\r\nall integrations were completed. Removes the \"Generate API Key\" button\r\nand also removes the example Cloud ID in favor of an obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239"}}]}] BACKPORT--> Co-authored-by: Seth Michael Larson <seth.larson@elastic.co> |
||
|
Kibana Machine
|
c6c52e17d5
|
[8.6] [ML] Explain Log Rate Spikes: Fix item set post processing. (#147499) (#147670)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix item set post processing. (#147499)](https://github.com/elastic/kibana/pull/147499) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-16T08:21:47Z","message":"[ML] Explain Log Rate Spikes: Fix item set post processing. (#147499)\n\nFixes cases where the item set post processing would end up with duplicate entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147499,"url":"https://github.com/elastic/kibana/pull/147499","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix item set post processing. (#147499)\n\nFixes cases where the item set post processing would end up with duplicate entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147499","number":147499,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix item set post processing. (#147499)\n\nFixes cases where the item set post processing would end up with duplicate entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
Jonathan Budzenski
|
8fc7affcbf | skip flaky suite (#147222) | ||
|
Kibana Machine
|
65a1706be4
|
[8.6] [Fleet] publish agents_per_version telemetry as separate docs (#147615) (#147622)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] publish `agents_per_version` telemetry as separate docs (#147615)](https://github.com/elastic/kibana/pull/147615) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-15T15:15:10Z","message":"[Fleet] publish `agents_per_version` telemetry as separate docs (#147615)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147543\r\n\r\nSending `agents_per_version` telemetry as separate docs with a new type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to kibana, will result in 2\r\ndocuments sent\r\n```\r\n{ \"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{ \"agents_per_version\": {\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add a new indexer to have proper data types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img width=\"605\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":147615,"url":"https://github.com/elastic/kibana/pull/147615","mergeCommit":{"message":"[Fleet] publish `agents_per_version` telemetry as separate docs (#147615)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147543\r\n\r\nSending `agents_per_version` telemetry as separate docs with a new type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to kibana, will result in 2\r\ndocuments sent\r\n```\r\n{ \"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{ \"agents_per_version\": {\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add a new indexer to have proper data types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img width=\"605\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147615","number":147615,"mergeCommit":{"message":"[Fleet] publish `agents_per_version` telemetry as separate docs (#147615)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147543\r\n\r\nSending `agents_per_version` telemetry as separate docs with a new type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to kibana, will result in 2\r\ndocuments sent\r\n```\r\n{ \"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{ \"agents_per_version\": {\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add a new indexer to have proper data types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img width=\"605\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
2f08d7ddaa
|
[8.6] [Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598) (#147609)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598)](https://github.com/elastic/kibana/pull/147598) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Juan Pablo Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2022-12-15T13:10:32Z","message":"[Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598)\n\nRelates to https://github.com/elastic/kibana/issues/147564\r\n\r\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the behaviour of\r\nthe Rules Table, so that the table was fully disabled (with an overlay\r\nloading spinner) during preflight requests. In the other requests types,\r\n`enable`ing, `disable`ing and actual `edit` requests, each rule would be\r\ndisabled individually.\r\n\r\nThis however did not include **deletion**, so we incorrectly still\r\nallowed the user to enable and disable rules while they were being bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","Team:Detection Rules","backport:prev-minor","v8.6.0","v8.7.0"],"number":147598,"url":"https://github.com/elastic/kibana/pull/147598","mergeCommit":{"message":"[Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598)\n\nRelates to https://github.com/elastic/kibana/issues/147564\r\n\r\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the behaviour of\r\nthe Rules Table, so that the table was fully disabled (with an overlay\r\nloading spinner) during preflight requests. In the other requests types,\r\n`enable`ing, `disable`ing and actual `edit` requests, each rule would be\r\ndisabled individually.\r\n\r\nThis however did not include **deletion**, so we incorrectly still\r\nallowed the user to enable and disable rules while they were being bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147598","number":147598,"mergeCommit":{"message":"[Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598)\n\nRelates to https://github.com/elastic/kibana/issues/147564\r\n\r\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the behaviour of\r\nthe Rules Table, so that the table was fully disabled (with an overlay\r\nloading spinner) during preflight requests. In the other requests types,\r\n`enable`ing, `disable`ing and actual `edit` requests, each rule would be\r\ndisabled individually.\r\n\r\nThis however did not include **deletion**, so we incorrectly still\r\nallowed the user to enable and disable rules while they were being bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\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### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24"}}]}] BACKPORT--> Co-authored-by: Juan Pablo Djeredjian <jpdjeredjian@gmail.com> |
||
Dmitry Tomashevich
|
66d0f5590d
|
[8.6] [Discover] Fix Discover navigation from Lens embeddable (#147000) (#147608)
# Backport This will backport the following commits from `main` to `8.6`: - [[Discover] Fix Discover navigation from Lens embeddable (#147000)](https://github.com/elastic/kibana/pull/147000) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitry Tomashevich","email":"39378793+dimaanj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-14T13:17:17Z","message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","auto-backport","Team:DataDiscovery","v8.7.0","v8.6.1"],"number":147000,"url":"https://github.com/elastic/kibana/pull/147000","mergeCommit":{"message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147000","number":147000,"mergeCommit":{"message":"[Discover] Fix Discover navigation from Lens embeddable (#147000)\n\n## Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Marco Liberati <dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
5d961c8ec0
|
[8.6] [Profiling] Add color for PHP JIT frames (#147495) (#147588)
# Backport This will backport the following commits from `main` to `8.6`: - [[Profiling] Add color for PHP JIT frames (#147495)](https://github.com/elastic/kibana/pull/147495) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Florian Lehner","email":"florianl@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-15T06:35:21Z","message":"[Profiling] Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.7.0","v8.6.1"],"number":147495,"url":"https://github.com/elastic/kibana/pull/147495","mergeCommit":{"message":"[Profiling] Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147495","number":147495,"mergeCommit":{"message":"[Profiling] Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner <florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Florian Lehner <florianl@users.noreply.github.com> |
||
Xavier Mouligneau
|
6842085e4e
|
[8.6] [RAM] Reactivate most tests in triggers_actions_ui #147535 (#147582)
# Backport This will backport the following commits from `main` to `8.6`: - [[RAM] Reactivate most tests in triggers_actions_ui #147535](https://github.com/elastic/kibana/pull/147535) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T21:15:30Z","message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":147550,"url":"https://github.com/elastic/kibana/pull/147550","mergeCommit":{"message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147550","number":147550,"mergeCommit":{"message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}}]}] BACKPORT--> Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com> |
||
|
Kibana Machine
|
74a68fd452
|
[8.6] [Security Solution] ML job enchancement: update warning message (#147550) (#147580)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] ML job enchancement: update warning message (#147550)](https://github.com/elastic/kibana/pull/147550) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T21:15:30Z","message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":147550,"url":"https://github.com/elastic/kibana/pull/147550","mergeCommit":{"message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147550","number":147550,"mergeCommit":{"message":"[Security Solution] ML job enchancement: update warning message (#147550)\n\n## Summary\r\n\r\nThese changes update the wording around the ML job selection in ML rule.\r\nAs we gonna try to start selected job/s in case those are not running,\r\nwe should accordingly mention that in the callout below the job\r\nselection combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50 48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
346a7a0c78
|
[8.6] [Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502) (#147559)
# Backport This will backport the following commits from `main` to `8.6`: - [[Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502)](https://github.com/elastic/kibana/pull/147502) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T17:24:11Z","message":"[Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a regression that exists on 8.6.0 when the users are trying to\r\nVisualize a field and have selected columns in Discover.\r\n\r\nThe problem is that the text based datasource is also providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra checks:\r\n\r\n- if the context has the fieldname it returns empty suggestions (in the\r\ntext based mode we suggest based on the query and not the field\r\n- If there is no aggregate query we also return empty suggestions\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.7.0","v8.6.1"],"number":147502,"url":"https://github.com/elastic/kibana/pull/147502","mergeCommit":{"message":"[Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a regression that exists on 8.6.0 when the users are trying to\r\nVisualize a field and have selected columns in Discover.\r\n\r\nThe problem is that the text based datasource is also providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra checks:\r\n\r\n- if the context has the fieldname it returns empty suggestions (in the\r\ntext based mode we suggest based on the query and not the field\r\n- If there is no aggregate query we also return empty suggestions\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147502","number":147502,"mergeCommit":{"message":"[Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a regression that exists on 8.6.0 when the users are trying to\r\nVisualize a field and have selected columns in Discover.\r\n\r\nThe problem is that the text based datasource is also providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra checks:\r\n\r\n- if the context has the fieldname it returns empty suggestions (in the\r\ntext based mode we suggest based on the query and not the field\r\n- If there is no aggregate query we also return empty suggestions\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
1adab28560
|
[8.6] [maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207) (#147556)
# Backport This will backport the following commits from `main` to `8.6`: - [[maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207)](https://github.com/elastic/kibana/pull/147207) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T17:08:00Z","message":"[maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207)\n\nFixes https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge case where when uploading a file containing a\r\nFeatureCollection with a single feature, the results incorrectly state\r\nthat 2 features where indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","backport:prev-minor","Feature:Maps","v8.7.0"],"number":147207,"url":"https://github.com/elastic/kibana/pull/147207","mergeCommit":{"message":"[maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207)\n\nFixes https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge case where when uploading a file containing a\r\nFeatureCollection with a single feature, the results incorrectly state\r\nthat 2 features where indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147207","number":147207,"mergeCommit":{"message":"[maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207)\n\nFixes https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge case where when uploading a file containing a\r\nFeatureCollection with a single feature, the results incorrectly state\r\nthat 2 features where indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705"}}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> |
||
|
Kibana Machine
|
8079031ff2
|
[8.6] [Profiling] Remove link to 'Other' bucket (#147523) (#147540)
# Backport This will backport the following commits from `main` to `8.6`: - [[Profiling] Remove link to 'Other' bucket (#147523)](https://github.com/elastic/kibana/pull/147523) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T15:57:32Z","message":"[Profiling] Remove link to 'Other' bucket (#147523)\n\nCloses https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v8.7.0","v8.6.1"],"number":147523,"url":"https://github.com/elastic/kibana/pull/147523","mergeCommit":{"message":"[Profiling] Remove link to 'Other' bucket (#147523)\n\nCloses https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147523","number":147523,"mergeCommit":{"message":"[Profiling] Remove link to 'Other' bucket (#147523)\n\nCloses https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> |
||
|
Kibana Machine
|
690e4a15b3
|
[8.6] [Fleet] added a logic to use destinationId when tagging imported SOs (#147439) (#147528)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] added a logic to use `destinationId` when tagging imported SOs (#147439)](https://github.com/elastic/kibana/pull/147439) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-14T14:09:23Z","message":"[Fleet] added a logic to use `destinationId` when tagging imported SOs (#147439)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing an integration, and some assets already exist in Kibana,\r\nthe imported SOs will recieve a newly generated ID. This caused a\r\nproblem previously when the tagging logic didn't find the SOs with their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to verify**\r\n1. Add system integration in default space\r\n2. Enroll an agent and wait for system metrics to be ingested\r\n3. Create an Admin space\r\n4. Remove the system package policy, and uninstall the system package\r\nfrom Default space\r\n5. Go to Admin space and add system integration again\r\n6. Verify that the integration is added successfully, assets are created\r\nin Admin space and assets are tagged with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0","v8.5.4"],"number":147439,"url":"https://github.com/elastic/kibana/pull/147439","mergeCommit":{"message":"[Fleet] added a logic to use `destinationId` when tagging imported SOs (#147439)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing an integration, and some assets already exist in Kibana,\r\nthe imported SOs will recieve a newly generated ID. This caused a\r\nproblem previously when the tagging logic didn't find the SOs with their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to verify**\r\n1. Add system integration in default space\r\n2. Enroll an agent and wait for system metrics to be ingested\r\n3. Create an Admin space\r\n4. Remove the system package policy, and uninstall the system package\r\nfrom Default space\r\n5. Go to Admin space and add system integration again\r\n6. Verify that the integration is added successfully, assets are created\r\nin Admin space and assets are tagged with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147439","number":147439,"mergeCommit":{"message":"[Fleet] added a logic to use `destinationId` when tagging imported SOs (#147439)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing an integration, and some assets already exist in Kibana,\r\nthe imported SOs will recieve a newly generated ID. This caused a\r\nproblem previously when the tagging logic didn't find the SOs with their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to verify**\r\n1. Add system integration in default space\r\n2. Enroll an agent and wait for system metrics to be ingested\r\n3. Create an Admin space\r\n4. Remove the system package policy, and uninstall the system package\r\nfrom Default space\r\n5. Go to Admin space and add system integration again\r\n6. Verify that the integration is added successfully, assets are created\r\nin Admin space and assets are tagged with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266"}},{"branch":"8.5","label":"v8.5.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Yngrid Coello
|
e4711bb3eb
|
[8.6] [APM] Switching service groups from grid to flex layout (#147448) (#147513)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Switching service groups from grid to flex layout (#147448)](https://github.com/elastic/kibana/pull/147448) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yngrid Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T11:03:32Z","message":"[APM] Switching service groups from grid to flex layout (#147448)\n\nCloses https://github.com/elastic/kibana/issues/147435.\r\n\r\n### Changes\r\n- `ServiceGroupList` is now using `EuiFlexGroup`. Grid is not suitable\r\nfor this case since the `ServiceGroupCard` has a fixed width.\r\n- `ServiceGroupCard` width is changed to `100%` when we are in mobile\r\nresolutions.\r\n\r\n**Before**\r\n\r\n\r\n |
||
|
Yngrid Coello
|
511e7c66ad
|
[8.6] [APM] Added env filter to agent explorer ui (#146326) (#146584)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Added env filter to agent explorer ui (#146326)](https://github.com/elastic/kibana/pull/146326) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yngrid Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2022-11-29T16:02:57Z","message":"[APM] Added env filter to agent explorer ui (#146326)\n\nRelates to https://github.com/elastic/kibana/issues/146019.\r\n\r\nThis PR added environment filter to Agent explorer view.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203838057-0892c0e1-4023-400e-8217-b394002860df.mov\r\n\r\nSince Agent explorer doesn't have a timeRange component, takes into\r\naccount always data from the last 24h, I added a `customTimeRange`\r\noptional input to `EnvironmentsContextProvider`.\r\n\r\nApart from this the `serviceName`, `rangeFrom` and `rangeTo` that we use\r\nin `EnvironmentSelect` are coming now from the context as well instead\r\nof picking them from the url.","sha":"d86313f2c5b6bb104d7ded8b344f09517a644726","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","v8.6.0","v8.7.0"],"number":146326,"url":"https://github.com/elastic/kibana/pull/146326","mergeCommit":{"message":"[APM] Added env filter to agent explorer ui (#146326)\n\nRelates to https://github.com/elastic/kibana/issues/146019.\r\n\r\nThis PR added environment filter to Agent explorer view.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203838057-0892c0e1-4023-400e-8217-b394002860df.mov\r\n\r\nSince Agent explorer doesn't have a timeRange component, takes into\r\naccount always data from the last 24h, I added a `customTimeRange`\r\noptional input to `EnvironmentsContextProvider`.\r\n\r\nApart from this the `serviceName`, `rangeFrom` and `rangeTo` that we use\r\nin `EnvironmentSelect` are coming now from the context as well instead\r\nof picking them from the url.","sha":"d86313f2c5b6bb104d7ded8b344f09517a644726"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146326","number":146326,"mergeCommit":{"message":"[APM] Added env filter to agent explorer ui (#146326)\n\nRelates to https://github.com/elastic/kibana/issues/146019.\r\n\r\nThis PR added environment filter to Agent explorer view.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203838057-0892c0e1-4023-400e-8217-b394002860df.mov\r\n\r\nSince Agent explorer doesn't have a timeRange component, takes into\r\naccount always data from the last 24h, I added a `customTimeRange`\r\noptional input to `EnvironmentsContextProvider`.\r\n\r\nApart from this the `serviceName`, `rangeFrom` and `rangeTo` that we use\r\nin `EnvironmentSelect` are coming now from the context as well instead\r\nof picking them from the url.","sha":"d86313f2c5b6bb104d7ded8b344f09517a644726"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
33bc977a8a
|
[8.6] [Fix][Infrastructure UI] Incorrect payload in time range when landing on the Hosts View (#147390) (#147424)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fix][Infrastructure UI] Incorrect payload in time range when landing on the Hosts View (#147390)](https://github.com/elastic/kibana/pull/147390) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2022-12-13T09:43:15Z","message":"[Fix][Infrastructure UI] Incorrect payload in time range when landing on the Hosts View (#147390)\n\nCloses #146581 \r\n\r\n## Summary\r\n\r\nThis PR fixes the initial `from` date range calculation. The idea is to\r\nconvert first the initial range of minutes to milliseconds. Then in\r\norder to get the date of `CALCULATED_DATE_RANGE_TO` - (the calculated\r\ninitial range in milliseconds) and call `getTime()` to receive the\r\ncalculated `from` date as timestamp.\r\n\r\nTo test that you can open the host page without the time range in the\r\nURL. Then check the `from` value as in the screenshot attached to the\r\nstory and you can use an [Unix timestamp\r\nconverter](https://www.unixtimestamp.com/) to verify that the\r\ncalculation is correct","sha":"29841da10b140d8bb0e24d5af4c55e64b6f473c9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Infra Monitoring UI","backport:prev-minor","v8.7.0"],"number":147390,"url":"https://github.com/elastic/kibana/pull/147390","mergeCommit":{"message":"[Fix][Infrastructure UI] Incorrect payload in time range when landing on the Hosts View (#147390)\n\nCloses #146581 \r\n\r\n## Summary\r\n\r\nThis PR fixes the initial `from` date range calculation. The idea is to\r\nconvert first the initial range of minutes to milliseconds. Then in\r\norder to get the date of `CALCULATED_DATE_RANGE_TO` - (the calculated\r\ninitial range in milliseconds) and call `getTime()` to receive the\r\ncalculated `from` date as timestamp.\r\n\r\nTo test that you can open the host page without the time range in the\r\nURL. Then check the `from` value as in the screenshot attached to the\r\nstory and you can use an [Unix timestamp\r\nconverter](https://www.unixtimestamp.com/) to verify that the\r\ncalculation is correct","sha":"29841da10b140d8bb0e24d5af4c55e64b6f473c9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147390","number":147390,"mergeCommit":{"message":"[Fix][Infrastructure UI] Incorrect payload in time range when landing on the Hosts View (#147390)\n\nCloses #146581 \r\n\r\n## Summary\r\n\r\nThis PR fixes the initial `from` date range calculation. The idea is to\r\nconvert first the initial range of minutes to milliseconds. Then in\r\norder to get the date of `CALCULATED_DATE_RANGE_TO` - (the calculated\r\ninitial range in milliseconds) and call `getTime()` to receive the\r\ncalculated `from` date as timestamp.\r\n\r\nTo test that you can open the host page without the time range in the\r\nURL. Then check the `from` value as in the screenshot attached to the\r\nstory and you can use an [Unix timestamp\r\nconverter](https://www.unixtimestamp.com/) to verify that the\r\ncalculation is correct","sha":"29841da10b140d8bb0e24d5af4c55e64b6f473c9"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Kibana Machine
|
952ad51e5c
|
[8.6] [Enterprise Search][ML Inference] migrate add inference pipeline from modal to flyout (#146924) (#147402)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search][ML Inference] migrate add inference pipeline from modal to flyout (#146924)](https://github.com/elastic/kibana/pull/146924) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rodney Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2022-12-12T23:28:21Z","message":"[Enterprise Search][ML Inference] migrate add inference pipeline from modal to flyout (#146924)\n\n## Summary\r\n\r\nMoved the Add inference pipeline from a modal to a flyout to improve the\r\nUX and follow our own design guidelines.\r\n\r\n\r\n### Screenshots\r\nConfigure:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386204-0e1c605b-3fcb-4f2f-9665-6b46c9bd39fc.png\">\r\nTest:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386273-85f17deb-b321-4a9e-9c04-5871c316cf81.png\">\r\nReview:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386305-1861f699-e65e-4531-9820-41f4362a4b4e.png\">\r\n\r\nNo Models:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386430-889f726f-5eea-48b1-94f5-921193ca3adc.png\">","sha":"942eec07fa30e17ed510468d90bde9c03c3908fa","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146924,"url":"https://github.com/elastic/kibana/pull/146924","mergeCommit":{"message":"[Enterprise Search][ML Inference] migrate add inference pipeline from modal to flyout (#146924)\n\n## Summary\r\n\r\nMoved the Add inference pipeline from a modal to a flyout to improve the\r\nUX and follow our own design guidelines.\r\n\r\n\r\n### Screenshots\r\nConfigure:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386204-0e1c605b-3fcb-4f2f-9665-6b46c9bd39fc.png\">\r\nTest:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386273-85f17deb-b321-4a9e-9c04-5871c316cf81.png\">\r\nReview:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386305-1861f699-e65e-4531-9820-41f4362a4b4e.png\">\r\n\r\nNo Models:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386430-889f726f-5eea-48b1-94f5-921193ca3adc.png\">","sha":"942eec07fa30e17ed510468d90bde9c03c3908fa"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146924","number":146924,"mergeCommit":{"message":"[Enterprise Search][ML Inference] migrate add inference pipeline from modal to flyout (#146924)\n\n## Summary\r\n\r\nMoved the Add inference pipeline from a modal to a flyout to improve the\r\nUX and follow our own design guidelines.\r\n\r\n\r\n### Screenshots\r\nConfigure:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386204-0e1c605b-3fcb-4f2f-9665-6b46c9bd39fc.png\">\r\nTest:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386273-85f17deb-b321-4a9e-9c04-5871c316cf81.png\">\r\nReview:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386305-1861f699-e65e-4531-9820-41f4362a4b4e.png\">\r\n\r\nNo Models:\r\n<img width=\"1433\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/1972968/205386430-889f726f-5eea-48b1-94f5-921193ca3adc.png\">","sha":"942eec07fa30e17ed510468d90bde9c03c3908fa"}}]}] BACKPORT--> Co-authored-by: Rodney Norris <rodney.norris@elastic.co> |
||
|
Kibana Machine
|
36dbb40cb6
|
[8.6] [DOCS] Create open API specification for find rules (#147061) (#147391)
# Backport This will backport the following commits from `main` to `8.6`: - [[DOCS] Create open API specification for find rules (#147061)](https://github.com/elastic/kibana/pull/147061) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-12T19:36:44Z","message":"[DOCS] Create open API specification for find rules (#147061)","sha":"d862f46c2a6930a9f219ec5287dcce7bb286b305","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","v8.7.0","v8.6.1"],"number":147061,"url":"https://github.com/elastic/kibana/pull/147061","mergeCommit":{"message":"[DOCS] Create open API specification for find rules (#147061)","sha":"d862f46c2a6930a9f219ec5287dcce7bb286b305"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147061","number":147061,"mergeCommit":{"message":"[DOCS] Create open API specification for find rules (#147061)","sha":"d862f46c2a6930a9f219ec5287dcce7bb286b305"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
fc28e48b42
|
[8.6] [Osquery] [Fix] Fix osquery results table fullscreen height issue (#147076) (#147381)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] [Fix] Fix osquery results table fullscreen height issue (#147076)](https://github.com/elastic/kibana/pull/147076) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2022-12-12T18:18:09Z","message":"[Osquery] [Fix] Fix osquery results table fullscreen height issue (#147076)","sha":"5d0855a08f9882b82f544ea01dc9325ff9a0f87b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":147076,"url":"https://github.com/elastic/kibana/pull/147076","mergeCommit":{"message":"[Osquery] [Fix] Fix osquery results table fullscreen height issue (#147076)","sha":"5d0855a08f9882b82f544ea01dc9325ff9a0f87b"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147076","number":147076,"mergeCommit":{"message":"[Osquery] [Fix] Fix osquery results table fullscreen height issue (#147076)","sha":"5d0855a08f9882b82f544ea01dc9325ff9a0f87b"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
ab6ee034ba
|
[8.6] [Security Solution] [Bugfix] add redirect for old external alert route to new one on events page (#146896) (#147376)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Bugfix] add redirect for old external alert route to new one on events page (#146896)](https://github.com/elastic/kibana/pull/146896) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kristof C","email":"kpac.ja@gmail.com"},"sourceCommit":{"committedDate":"2022-12-12T17:24:23Z","message":"[Security Solution] [Bugfix] add redirect for old external alert route to new one on events page (#146896)\n\nas per https://github.com/elastic/kibana/issues/140158, old external\r\nalert route should either take user back to main entity page or to\r\nexternal alerts.\r\n\r\n## Summary\r\nTake advantage of `onlyExternalAlerts` param to redirect users with old\r\nurls to the new one for external alerts.\r\n\r\nThe gif below shows the old url before hitting enter- causing the page\r\nto redirect to the events page with external alerts checked.\r\n\r\n\r\nCo-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>","sha":"0d645937699c4d8e8f81210c08ae9d5f07b83afe","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:prev-minor","v8.7.0"],"number":146896,"url":"https://github.com/elastic/kibana/pull/146896","mergeCommit":{"message":"[Security Solution] [Bugfix] add redirect for old external alert route to new one on events page (#146896)\n\nas per https://github.com/elastic/kibana/issues/140158, old external\r\nalert route should either take user back to main entity page or to\r\nexternal alerts.\r\n\r\n## Summary\r\nTake advantage of `onlyExternalAlerts` param to redirect users with old\r\nurls to the new one for external alerts.\r\n\r\nThe gif below shows the old url before hitting enter- causing the page\r\nto redirect to the events page with external alerts checked.\r\n\r\n\r\nCo-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>","sha":"0d645937699c4d8e8f81210c08ae9d5f07b83afe"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146896","number":146896,"mergeCommit":{"message":"[Security Solution] [Bugfix] add redirect for old external alert route to new one on events page (#146896)\n\nas per https://github.com/elastic/kibana/issues/140158, old external\r\nalert route should either take user back to main entity page or to\r\nexternal alerts.\r\n\r\n## Summary\r\nTake advantage of `onlyExternalAlerts` param to redirect users with old\r\nurls to the new one for external alerts.\r\n\r\nThe gif below shows the old url before hitting enter- causing the page\r\nto redirect to the events page with external alerts checked.\r\n\r\n\r\nCo-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>","sha":"0d645937699c4d8e8f81210c08ae9d5f07b83afe"}}]}] BACKPORT--> Co-authored-by: Kristof C <kpac.ja@gmail.com> |
||
|
Kibana Machine
|
4072170eda
|
[8.6] [SecuritySolution] Fix KPIs disappear after clicking users / host risk score tabs (#147180) (#147361)
# Backport This will backport the following commits from `main` to `8.6`: - [[SecuritySolution] Fix KPIs disappear after clicking users / host risk score tabs (#147180)](https://github.com/elastic/kibana/pull/147180) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-12T14:50:03Z","message":"[SecuritySolution] Fix KPIs disappear after clicking users / host risk score tabs (#147180)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/145720\r\nKPIs disappear after clicking users / host risk score tabs\r\n\r\nRoot cause:\r\nuseGlobalTime on users and host risk score tabs called\r\n`inputsActions.deleteAllQueries`, so KPIs' queries info were deleted\r\naccordingly.\r\n\r\n**Steps to Verify**\r\n\r\n**Please enable feature flag:** `chartEmbeddablesEnabled`\r\n\r\n1. Visit app/security/hosts/allHosts\r\n2. Click on Host risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed \r\n\r\n1. Visit app/security/users/allUsers\r\n2. Click on User risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed\r\n\r\nCo-authored-by: Kristof C <kpac.ja@gmail.com>","sha":"96b30745f25f394d51702d8315facc3016b671d9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat Hunting","Team: SecuritySolution","Team:Threat Hunting:Explore","v8.6.0","v8.7.0"],"number":147180,"url":"https://github.com/elastic/kibana/pull/147180","mergeCommit":{"message":"[SecuritySolution] Fix KPIs disappear after clicking users / host risk score tabs (#147180)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/145720\r\nKPIs disappear after clicking users / host risk score tabs\r\n\r\nRoot cause:\r\nuseGlobalTime on users and host risk score tabs called\r\n`inputsActions.deleteAllQueries`, so KPIs' queries info were deleted\r\naccordingly.\r\n\r\n**Steps to Verify**\r\n\r\n**Please enable feature flag:** `chartEmbeddablesEnabled`\r\n\r\n1. Visit app/security/hosts/allHosts\r\n2. Click on Host risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed \r\n\r\n1. Visit app/security/users/allUsers\r\n2. Click on User risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed\r\n\r\nCo-authored-by: Kristof C <kpac.ja@gmail.com>","sha":"96b30745f25f394d51702d8315facc3016b671d9"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147180","number":147180,"mergeCommit":{"message":"[SecuritySolution] Fix KPIs disappear after clicking users / host risk score tabs (#147180)\n\n## Summary\r\n\r\nOriginal issue: https://github.com/elastic/kibana/issues/145720\r\nKPIs disappear after clicking users / host risk score tabs\r\n\r\nRoot cause:\r\nuseGlobalTime on users and host risk score tabs called\r\n`inputsActions.deleteAllQueries`, so KPIs' queries info were deleted\r\naccordingly.\r\n\r\n**Steps to Verify**\r\n\r\n**Please enable feature flag:** `chartEmbeddablesEnabled`\r\n\r\n1. Visit app/security/hosts/allHosts\r\n2. Click on Host risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed \r\n\r\n1. Visit app/security/users/allUsers\r\n2. Click on User risk score tab and then click on anomalies tab\r\n3. Please verify KPIs are displayed\r\n4. Click any tabs in any order, please verify KPIs are displayed\r\n\r\nCo-authored-by: Kristof C <kpac.ja@gmail.com>","sha":"96b30745f25f394d51702d8315facc3016b671d9"}}]}] BACKPORT--> Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com> |
||
|
Kibana Machine
|
7d81c5133e
|
[8.6] [Uptime] Monitor list fix default search behaviour (#147336) (#147358)
# Backport This will backport the following commits from `main` to `8.6`: - [[Uptime] Monitor list fix default search behaviour (#147336)](https://github.com/elastic/kibana/pull/147336) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2022-12-12T14:26:07Z","message":"[Uptime] Monitor list fix default search behaviour (#147336)\n\nCo-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>\r\nFixes https://github.com/elastic/kibana/issues/147245","sha":"80a6e6c6d7fedcf690afeabeb75e6683e274f2ea","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":147336,"url":"https://github.com/elastic/kibana/pull/147336","mergeCommit":{"message":"[Uptime] Monitor list fix default search behaviour (#147336)\n\nCo-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>\r\nFixes https://github.com/elastic/kibana/issues/147245","sha":"80a6e6c6d7fedcf690afeabeb75e6683e274f2ea"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147336","number":147336,"mergeCommit":{"message":"[Uptime] Monitor list fix default search behaviour (#147336)\n\nCo-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>\r\nFixes https://github.com/elastic/kibana/issues/147245","sha":"80a6e6c6d7fedcf690afeabeb75e6683e274f2ea"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
cde67e90d2
|
[8.6] [ML] Explain Log Rate Spikes: Fix wide time range display with sparse data. (#147129) (#147347)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix wide time range display with sparse data. (#147129)](https://github.com/elastic/kibana/pull/147129) <!--- Backport version: 8.9.7 --> ### 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":"2022-12-12T12:27:15Z","message":"[ML] Explain Log Rate Spikes: Fix wide time range display with sparse data. (#147129)\n\nThe `date_histogram` query was updated to use `min_doc_count: 0` and set\r\n`extended_bounds` to the date pickers time range so it returns buckets\r\nfor all necessary time slots necessary for the full date histogram bar\r\nchart.","sha":"a152bf98b7675876d66ca42c42de4f6cb244ae0b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","v8.6.0","v8.7.0"],"number":147129,"url":"https://github.com/elastic/kibana/pull/147129","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix wide time range display with sparse data. (#147129)\n\nThe `date_histogram` query was updated to use `min_doc_count: 0` and set\r\n`extended_bounds` to the date pickers time range so it returns buckets\r\nfor all necessary time slots necessary for the full date histogram bar\r\nchart.","sha":"a152bf98b7675876d66ca42c42de4f6cb244ae0b"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147129","number":147129,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Fix wide time range display with sparse data. (#147129)\n\nThe `date_histogram` query was updated to use `min_doc_count: 0` and set\r\n`extended_bounds` to the date pickers time range so it returns buckets\r\nfor all necessary time slots necessary for the full date histogram bar\r\nchart.","sha":"a152bf98b7675876d66ca42c42de4f6cb244ae0b"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
Kibana Machine
|
34e5a4642d
|
[8.6] [Fleet] fix for apm not found in epr + prerelease flag (#147257) (#147335)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] fix for apm not found in epr + prerelease flag (#147257)](https://github.com/elastic/kibana/pull/147257) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-12T10:06:50Z","message":"[Fleet] fix for apm not found in epr + prerelease flag (#147257)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/146312\r\n\r\nFall back to bundled packages when loading package archive.\r\n\r\nAlso fixed an issue with prerelease flag caused by\r\nhttps://github.com/elastic/kibana/pull/144431\r\n\r\nLoading prerelease setting on Add/Edit integration page, so that it\r\nworks well for cases where the url doesn't contain a concrete version\r\nlike APM\r\n\r\nSteps to verify:\r\n- Start kibana locally, make sure that APM bundled package is there in\r\n`x-pack/plugins/fleet/target/bundled_packages`\r\n- Load http://localhost:5601/julia/app/integrations/detail/apm/overview\r\n(with default \"beta integrations\" off flag)\r\n- Expect that 8.6.0 version is showing up (or 8.7.0 depending on the\r\nbuild)\r\n- When clicking on Add Elastic APM, expect 8.6.0 to be loaded\r\nsuccessfully\r\n\r\n<img width=\"1773\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206482128-634ca823-bb21-46a9-a8b9-fc81d5dc126d.png\">\r\n\r\nNote: there is still a UI issue with loading assets on Overview page if\r\nthe package is not in EPR.\r\n\r\n<img width=\"1747\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206478275-ee8e9494-234f-44c8-88d9-a91c791b0196.png\">\r\n\r\n- switch \"beta integrations\" on on Integrations page\r\n- Open APM overview page again\r\n- expect `8.7.0-preview` version with the selector to change to last GA\r\n\r\n<img width=\"1100\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206480986-2ed05b12-49e4-4c88-97c6-6cdf12f819da.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"24e2fcf47014d937a5019d83b95565a010ae4e22","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":147257,"url":"https://github.com/elastic/kibana/pull/147257","mergeCommit":{"message":"[Fleet] fix for apm not found in epr + prerelease flag (#147257)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/146312\r\n\r\nFall back to bundled packages when loading package archive.\r\n\r\nAlso fixed an issue with prerelease flag caused by\r\nhttps://github.com/elastic/kibana/pull/144431\r\n\r\nLoading prerelease setting on Add/Edit integration page, so that it\r\nworks well for cases where the url doesn't contain a concrete version\r\nlike APM\r\n\r\nSteps to verify:\r\n- Start kibana locally, make sure that APM bundled package is there in\r\n`x-pack/plugins/fleet/target/bundled_packages`\r\n- Load http://localhost:5601/julia/app/integrations/detail/apm/overview\r\n(with default \"beta integrations\" off flag)\r\n- Expect that 8.6.0 version is showing up (or 8.7.0 depending on the\r\nbuild)\r\n- When clicking on Add Elastic APM, expect 8.6.0 to be loaded\r\nsuccessfully\r\n\r\n<img width=\"1773\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206482128-634ca823-bb21-46a9-a8b9-fc81d5dc126d.png\">\r\n\r\nNote: there is still a UI issue with loading assets on Overview page if\r\nthe package is not in EPR.\r\n\r\n<img width=\"1747\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206478275-ee8e9494-234f-44c8-88d9-a91c791b0196.png\">\r\n\r\n- switch \"beta integrations\" on on Integrations page\r\n- Open APM overview page again\r\n- expect `8.7.0-preview` version with the selector to change to last GA\r\n\r\n<img width=\"1100\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206480986-2ed05b12-49e4-4c88-97c6-6cdf12f819da.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"24e2fcf47014d937a5019d83b95565a010ae4e22"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147257","number":147257,"mergeCommit":{"message":"[Fleet] fix for apm not found in epr + prerelease flag (#147257)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/146312\r\n\r\nFall back to bundled packages when loading package archive.\r\n\r\nAlso fixed an issue with prerelease flag caused by\r\nhttps://github.com/elastic/kibana/pull/144431\r\n\r\nLoading prerelease setting on Add/Edit integration page, so that it\r\nworks well for cases where the url doesn't contain a concrete version\r\nlike APM\r\n\r\nSteps to verify:\r\n- Start kibana locally, make sure that APM bundled package is there in\r\n`x-pack/plugins/fleet/target/bundled_packages`\r\n- Load http://localhost:5601/julia/app/integrations/detail/apm/overview\r\n(with default \"beta integrations\" off flag)\r\n- Expect that 8.6.0 version is showing up (or 8.7.0 depending on the\r\nbuild)\r\n- When clicking on Add Elastic APM, expect 8.6.0 to be loaded\r\nsuccessfully\r\n\r\n<img width=\"1773\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206482128-634ca823-bb21-46a9-a8b9-fc81d5dc126d.png\">\r\n\r\nNote: there is still a UI issue with loading assets on Overview page if\r\nthe package is not in EPR.\r\n\r\n<img width=\"1747\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206478275-ee8e9494-234f-44c8-88d9-a91c791b0196.png\">\r\n\r\n- switch \"beta integrations\" on on Integrations page\r\n- Open APM overview page again\r\n- expect `8.7.0-preview` version with the selector to change to last GA\r\n\r\n<img width=\"1100\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/206480986-2ed05b12-49e4-4c88-97c6-6cdf12f819da.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"24e2fcf47014d937a5019d83b95565a010ae4e22"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Ahmad Bamieh
|
a232b21207
|
[i18n] [8.6] Integrate 8.6.0 Translations (#147320) |
