mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 16:29:04 -04:00
27354 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
3a64902a7a
|
[8.6] [Security Solution] Add loading overlay during bulk edit preflight requests (#145905) (#146528)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Add loading overlay during bulk edit preflight requests (#145905)](https://github.com/elastic/kibana/pull/145905) <!--- 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-11-29T11:41:52Z","message":"[Security Solution] Add loading overlay during bulk edit preflight requests (#145905)\n\n## Summary (outdated, see discussion in comments below)\r\n\r\nRelates to: https://github.com/elastic/kibana/issues/144264\r\n\r\n- Adds additional `isDryRun` boolean option to the `setLoadingRules`\r\nstate setter provided by `RulesTableContextProvider`. It is optional and\r\ndefaults to `false`.\r\n- Set loading state during pre-flight (dry run) bulk edit requests to\r\n`true`, in order for the loading overlay to display over the Rules Table\r\nwhile the dry run is executed.\r\n\r\n## Context\r\n\r\nWe currently [have a check that prevents the loading\r\noverlay](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/public/detection_engine/rule_management_ui/components/rules_table/rules_table/rules_table_context.tsx#L199)\r\nto display during bulk `edit` API requests (also `enable` and `disable`)\r\n, since that is the current expected UX.\r\n\r\nHowever, we want the loading overlay to display during `dryRun`\r\nrequests, but not in the subsequent requests, when the `edit`ing is\r\nactually being done. That is why we need to differentiate the two types\r\nof requests, while maintaining backwards compatibility with the logic\r\nalready present. Therefore, the proposal of the optional `isDryRun`\r\nboolean option.\r\n\r\n## Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136754-53fb657b-f594-4e91-980f-95de7c11579d.mp4\r\n\r\n## After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136922-7e90f10d-64d8-4907-8aae-16e7d759107b.mp4\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] 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":"033dcceb8b5a478252f11476d6ebffc44dc2e496","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections and Resp","fixed","Team: SecuritySolution","Team:Detection Rules","8.6 candidate","backport:prev-minor","v8.6.0","v8.7.0"],"number":145905,"url":"https://github.com/elastic/kibana/pull/145905","mergeCommit":{"message":"[Security Solution] Add loading overlay during bulk edit preflight requests (#145905)\n\n## Summary (outdated, see discussion in comments below)\r\n\r\nRelates to: https://github.com/elastic/kibana/issues/144264\r\n\r\n- Adds additional `isDryRun` boolean option to the `setLoadingRules`\r\nstate setter provided by `RulesTableContextProvider`. It is optional and\r\ndefaults to `false`.\r\n- Set loading state during pre-flight (dry run) bulk edit requests to\r\n`true`, in order for the loading overlay to display over the Rules Table\r\nwhile the dry run is executed.\r\n\r\n## Context\r\n\r\nWe currently [have a check that prevents the loading\r\noverlay](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/public/detection_engine/rule_management_ui/components/rules_table/rules_table/rules_table_context.tsx#L199)\r\nto display during bulk `edit` API requests (also `enable` and `disable`)\r\n, since that is the current expected UX.\r\n\r\nHowever, we want the loading overlay to display during `dryRun`\r\nrequests, but not in the subsequent requests, when the `edit`ing is\r\nactually being done. That is why we need to differentiate the two types\r\nof requests, while maintaining backwards compatibility with the logic\r\nalready present. Therefore, the proposal of the optional `isDryRun`\r\nboolean option.\r\n\r\n## Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136754-53fb657b-f594-4e91-980f-95de7c11579d.mp4\r\n\r\n## After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136922-7e90f10d-64d8-4907-8aae-16e7d759107b.mp4\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] 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":"033dcceb8b5a478252f11476d6ebffc44dc2e496"}},"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/145905","number":145905,"mergeCommit":{"message":"[Security Solution] Add loading overlay during bulk edit preflight requests (#145905)\n\n## Summary (outdated, see discussion in comments below)\r\n\r\nRelates to: https://github.com/elastic/kibana/issues/144264\r\n\r\n- Adds additional `isDryRun` boolean option to the `setLoadingRules`\r\nstate setter provided by `RulesTableContextProvider`. It is optional and\r\ndefaults to `false`.\r\n- Set loading state during pre-flight (dry run) bulk edit requests to\r\n`true`, in order for the loading overlay to display over the Rules Table\r\nwhile the dry run is executed.\r\n\r\n## Context\r\n\r\nWe currently [have a check that prevents the loading\r\noverlay](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/public/detection_engine/rule_management_ui/components/rules_table/rules_table/rules_table_context.tsx#L199)\r\nto display during bulk `edit` API requests (also `enable` and `disable`)\r\n, since that is the current expected UX.\r\n\r\nHowever, we want the loading overlay to display during `dryRun`\r\nrequests, but not in the subsequent requests, when the `edit`ing is\r\nactually being done. That is why we need to differentiate the two types\r\nof requests, while maintaining backwards compatibility with the logic\r\nalready present. Therefore, the proposal of the optional `isDryRun`\r\nboolean option.\r\n\r\n## Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136754-53fb657b-f594-4e91-980f-95de7c11579d.mp4\r\n\r\n## After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/5354282/203136922-7e90f10d-64d8-4907-8aae-16e7d759107b.mp4\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] 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":"033dcceb8b5a478252f11476d6ebffc44dc2e496"}}]}] BACKPORT--> Co-authored-by: Juan Pablo Djeredjian <jpdjeredjian@gmail.com> |
||
Abdul Wahab Zahid
|
d1d2537aac
|
[8.6] [Synthetics] Fix infinite loading of Monitor Details page (#146336) (#146383)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Fix infinite loading of Monitor Details page (#146336)](https://github.com/elastic/kibana/pull/146336) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2022-11-28T10:43:20Z","message":"[Synthetics] Fix infinite loading of Monitor Details page (#146336)\n\nWith the `SyntheticsRefreshContext` now refreshing itself periodically,\r\nhooks which are called from multiple child components in parallel and\r\nwhich load data when initialized, may cause multiple redundant, or based\r\non the flow, unending back to back calls to server. This is because a\r\nhook called multiple times in parallel, will dispatch the same action\r\nthe number of times it is initialized.\r\n\r\nThe PR solves one such case on Monitor details page, which was loading\r\nitself over and over.\r\n\r\nThe PR also fixes the issue where **Last test run** panel on Monitor\r\nDetails page stays out of date when data is auto refreshed.","sha":"da5da4a31054a54a34cc1f6908ae934762238083","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","ci:build-cloud-image","v8.6.0","v8.7.0"],"number":146336,"url":"https://github.com/elastic/kibana/pull/146336","mergeCommit":{"message":"[Synthetics] Fix infinite loading of Monitor Details page (#146336)\n\nWith the `SyntheticsRefreshContext` now refreshing itself periodically,\r\nhooks which are called from multiple child components in parallel and\r\nwhich load data when initialized, may cause multiple redundant, or based\r\non the flow, unending back to back calls to server. This is because a\r\nhook called multiple times in parallel, will dispatch the same action\r\nthe number of times it is initialized.\r\n\r\nThe PR solves one such case on Monitor details page, which was loading\r\nitself over and over.\r\n\r\nThe PR also fixes the issue where **Last test run** panel on Monitor\r\nDetails page stays out of date when data is auto refreshed.","sha":"da5da4a31054a54a34cc1f6908ae934762238083"}},"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/146336","number":146336,"mergeCommit":{"message":"[Synthetics] Fix infinite loading of Monitor Details page (#146336)\n\nWith the `SyntheticsRefreshContext` now refreshing itself periodically,\r\nhooks which are called from multiple child components in parallel and\r\nwhich load data when initialized, may cause multiple redundant, or based\r\non the flow, unending back to back calls to server. This is because a\r\nhook called multiple times in parallel, will dispatch the same action\r\nthe number of times it is initialized.\r\n\r\nThe PR solves one such case on Monitor details page, which was loading\r\nitself over and over.\r\n\r\nThe PR also fixes the issue where **Last test run** panel on Monitor\r\nDetails page stays out of date when data is auto refreshed.","sha":"da5da4a31054a54a34cc1f6908ae934762238083"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
6249c39c64
|
[8.6] [Enterprise Search] Set featureset on native connector creation (#146534) (#146543)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Set featureset on native connector creation (#146534)](https://github.com/elastic/kibana/pull/146534) <!--- 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-11-29T13:16:26Z","message":"[Enterprise Search] Set featureset on native connector creation (#146534)\n\nThis moves setting native connector features to selecting a connector\r\ntype.","sha":"7c557a26cd1b35e94a1c1b7a88e85ac38d3cd6e3","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","auto-backport","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146534,"url":"https://github.com/elastic/kibana/pull/146534","mergeCommit":{"message":"[Enterprise Search] Set featureset on native connector creation (#146534)\n\nThis moves setting native connector features to selecting a connector\r\ntype.","sha":"7c557a26cd1b35e94a1c1b7a88e85ac38d3cd6e3"}},"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/146534","number":146534,"mergeCommit":{"message":"[Enterprise Search] Set featureset on native connector creation (#146534)\n\nThis moves setting native connector features to selecting a connector\r\ntype.","sha":"7c557a26cd1b35e94a1c1b7a88e85ac38d3cd6e3"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
85e6fc5448
|
[8.6] [Stack Monitoring] Remove visible semicolon from LoadingPage (#146500) (#146506)
# Backport This will backport the following commits from `main` to `8.6`: - [[Stack Monitoring] Remove visible semicolon from LoadingPage (#146500)](https://github.com/elastic/kibana/pull/146500) <!--- 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-11-29T09:17:29Z","message":"[Stack Monitoring] Remove visible semicolon from LoadingPage (#146500)\n\nFixes #146342\r\n\r\nThere was a semicolon added to the JSX markup which would show on slower\r\ndevices where loading takes longer.\r\nPlease refer to the issue for a screenshot of that.","sha":"5c13741663fdc750adad0df28330e0a226dc11a8","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":146500,"url":"https://github.com/elastic/kibana/pull/146500","mergeCommit":{"message":"[Stack Monitoring] Remove visible semicolon from LoadingPage (#146500)\n\nFixes #146342\r\n\r\nThere was a semicolon added to the JSX markup which would show on slower\r\ndevices where loading takes longer.\r\nPlease refer to the issue for a screenshot of that.","sha":"5c13741663fdc750adad0df28330e0a226dc11a8"}},"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/146500","number":146500,"mergeCommit":{"message":"[Stack Monitoring] Remove visible semicolon from LoadingPage (#146500)\n\nFixes #146342\r\n\r\nThere was a semicolon added to the JSX markup which would show on slower\r\ndevices where loading takes longer.\r\nPlease refer to the issue for a screenshot of that.","sha":"5c13741663fdc750adad0df28330e0a226dc11a8"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
|
Kibana Machine
|
5589d33d09
|
[8.6] [ML] Fix caret direction for expanded state of table rows (#146451) (#146530)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix caret direction for expanded state of table rows (#146451)](https://github.com/elastic/kibana/pull/146451) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pete Harverson","email":"pete@elastic.co"},"sourceCommit":{"committedDate":"2022-11-29T11:58:23Z","message":"[ML] Fix caret direction for expanded state of table rows (#146451)\n\n## Summary\r\n\r\nFixes the icons used to indicate the collapsed / expanded state of table\r\nrows in the Data Frame Analytics, Trained Models and Explain Log Rate\r\nSpikes pages in the ML plugin, and the Transforms list page. They are\r\nnow consistent with other tables, with a **right caret** to indicate a\r\n**closed section** and a **down caret** for **open sections**.\r\n\r\n### Data frame analytics jobs list\r\n<img width=\"689\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346940-e56436e1-2e21-4f4d-a618-2b243438a55f.png\">\r\n\r\n### Data frame analytics results\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346993-32c600d1-f94c-4cb3-8740-e5344ecd6b4e.png\">\r\n\r\n### Trained models list\r\n<img width=\"788\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347063-2a50ac16-456c-4ca0-a446-b8535f5ba5cb.png\">\r\n\r\n### Nodes list\r\n<img width=\"506\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347215-970a07fe-062c-4c6f-bdfc-ed0f473e9681.png\">\r\n\r\n### Explain Log Rate Spikes grouped results\r\n<img width=\"809\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347302-10975598-5e88-42ac-a648-eae64976ed84.png\">\r\n\r\n### Transform management\r\n<img width=\"1063\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347393-124a366e-f5a9-44ba-8bfc-94788f334ba9.png\">\r\n\r\n\r\n\r\nFixes #142898","sha":"3a92e247a62e0b1f181b3c2d392bb2704a8bbcf7","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:fix",":ml","cosmetic","Feature:Transforms","Feature:Data Frame Analytics","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":146451,"url":"https://github.com/elastic/kibana/pull/146451","mergeCommit":{"message":"[ML] Fix caret direction for expanded state of table rows (#146451)\n\n## Summary\r\n\r\nFixes the icons used to indicate the collapsed / expanded state of table\r\nrows in the Data Frame Analytics, Trained Models and Explain Log Rate\r\nSpikes pages in the ML plugin, and the Transforms list page. They are\r\nnow consistent with other tables, with a **right caret** to indicate a\r\n**closed section** and a **down caret** for **open sections**.\r\n\r\n### Data frame analytics jobs list\r\n<img width=\"689\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346940-e56436e1-2e21-4f4d-a618-2b243438a55f.png\">\r\n\r\n### Data frame analytics results\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346993-32c600d1-f94c-4cb3-8740-e5344ecd6b4e.png\">\r\n\r\n### Trained models list\r\n<img width=\"788\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347063-2a50ac16-456c-4ca0-a446-b8535f5ba5cb.png\">\r\n\r\n### Nodes list\r\n<img width=\"506\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347215-970a07fe-062c-4c6f-bdfc-ed0f473e9681.png\">\r\n\r\n### Explain Log Rate Spikes grouped results\r\n<img width=\"809\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347302-10975598-5e88-42ac-a648-eae64976ed84.png\">\r\n\r\n### Transform management\r\n<img width=\"1063\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347393-124a366e-f5a9-44ba-8bfc-94788f334ba9.png\">\r\n\r\n\r\n\r\nFixes #142898","sha":"3a92e247a62e0b1f181b3c2d392bb2704a8bbcf7"}},"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/146451","number":146451,"mergeCommit":{"message":"[ML] Fix caret direction for expanded state of table rows (#146451)\n\n## Summary\r\n\r\nFixes the icons used to indicate the collapsed / expanded state of table\r\nrows in the Data Frame Analytics, Trained Models and Explain Log Rate\r\nSpikes pages in the ML plugin, and the Transforms list page. They are\r\nnow consistent with other tables, with a **right caret** to indicate a\r\n**closed section** and a **down caret** for **open sections**.\r\n\r\n### Data frame analytics jobs list\r\n<img width=\"689\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346940-e56436e1-2e21-4f4d-a618-2b243438a55f.png\">\r\n\r\n### Data frame analytics results\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204346993-32c600d1-f94c-4cb3-8740-e5344ecd6b4e.png\">\r\n\r\n### Trained models list\r\n<img width=\"788\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347063-2a50ac16-456c-4ca0-a446-b8535f5ba5cb.png\">\r\n\r\n### Nodes list\r\n<img width=\"506\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347215-970a07fe-062c-4c6f-bdfc-ed0f473e9681.png\">\r\n\r\n### Explain Log Rate Spikes grouped results\r\n<img width=\"809\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347302-10975598-5e88-42ac-a648-eae64976ed84.png\">\r\n\r\n### Transform management\r\n<img width=\"1063\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/7405507/204347393-124a366e-f5a9-44ba-8bfc-94788f334ba9.png\">\r\n\r\n\r\n\r\nFixes #142898","sha":"3a92e247a62e0b1f181b3c2d392bb2704a8bbcf7"}}]}] BACKPORT--> Co-authored-by: Pete Harverson <pete@elastic.co> |
||
|
Kibana Machine
|
2e3606842a
|
[8.6] Add some 8.6 Endpoint telemetry fields (#146459) (#146512)
# Backport This will backport the following commits from `main` to `8.6`: - [Add some 8.6 Endpoint telemetry fields (#146459)](https://github.com/elastic/kibana/pull/146459) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gabriel Landau","email":"42078554+gabriellandau@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-29T09:54:57Z","message":"Add some 8.6 Endpoint telemetry fields (#146459)\n\n## Summary\r\n\r\nAdd some fields to Endpoint telemetry which are mistakenly stripped by\r\nthe PII filter. These fields enable the Endpoint Protections team to\r\nbetter triage alerts and create exceptions.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"414ca820604c666af889a472da7e598fdcf5cfee","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Telemetry","release_note:skip","Team: SecuritySolution","auto-backport","v8.6.0"],"number":146459,"url":"https://github.com/elastic/kibana/pull/146459","mergeCommit":{"message":"Add some 8.6 Endpoint telemetry fields (#146459)\n\n## Summary\r\n\r\nAdd some fields to Endpoint telemetry which are mistakenly stripped by\r\nthe PII filter. These fields enable the Endpoint Protections team to\r\nbetter triage alerts and create exceptions.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"414ca820604c666af889a472da7e598fdcf5cfee"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gabriel Landau <42078554+gabriellandau@users.noreply.github.com> |
||
Sander Philipse
|
10e20e33b8
|
[8.6] [Enterprise Search] Replace long-running jobs with stuck jobs (#146419) (#146524)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Replace long-running jobs with stuck jobs (#146419)](https://github.com/elastic/kibana/pull/146419) <!--- 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-11-28T16:25:59Z","message":"[Enterprise Search] Replace long-running jobs with stuck jobs (#146419)\n\nThis replaces the long-running syncs view with stuck syncs.","sha":"1e5f7034cc324182641dcbeb5d37730ed3c3fd02","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":146419,"url":"https://github.com/elastic/kibana/pull/146419","mergeCommit":{"message":"[Enterprise Search] Replace long-running jobs with stuck jobs (#146419)\n\nThis replaces the long-running syncs view with stuck syncs.","sha":"1e5f7034cc324182641dcbeb5d37730ed3c3fd02"}},"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/146419","number":146419,"mergeCommit":{"message":"[Enterprise Search] Replace long-running jobs with stuck jobs (#146419)\n\nThis replaces the long-running syncs view with stuck syncs.","sha":"1e5f7034cc324182641dcbeb5d37730ed3c3fd02"}}]}] BACKPORT--> |
||
Kfir Peled
|
f851bdd5a0
|
[8.6] [Cloud Posture] UI for insufficient ES privileges (#145794) (#146522)
# Backport This will backport the following commits from `main` to `8.6`: - [[Cloud Posture] UI for insufficient ES privileges (#145794)](https://github.com/elastic/kibana/pull/145794) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ari Aviran","email":"ari.aviran@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T19:14:32Z","message":"[Cloud Posture] UI for insufficient ES privileges (#145794)\n\nCo-authored-by: Kfir Peled <kfir.peled@elastic.co>","sha":"55b59722f7b1445ae6be1084c0ac3d804f524692","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security Posture","ci:cloud-deploy","ci:cloud-redeploy","v8.6.0","v8.7.0","v8.5.3"],"number":145794,"url":"https://github.com/elastic/kibana/pull/145794","mergeCommit":{"message":"[Cloud Posture] UI for insufficient ES privileges (#145794)\n\nCo-authored-by: Kfir Peled <kfir.peled@elastic.co>","sha":"55b59722f7b1445ae6be1084c0ac3d804f524692"}},"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/145794","number":145794,"mergeCommit":{"message":"[Cloud Posture] UI for insufficient ES privileges (#145794)\n\nCo-authored-by: Kfir Peled <kfir.peled@elastic.co>","sha":"55b59722f7b1445ae6be1084c0ac3d804f524692"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ari Aviran <ari.aviran@elastic.co> |
||
|
Sander Philipse
|
218162f282
|
[8.6] [Enterprise Search] Fix logic for long running and orphaned jobs (#145714) (#146514)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Fix logic for long running and orphaned jobs (#145714)](https://github.com/elastic/kibana/pull/145714) <!--- 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-11-22T13:27:46Z","message":"[Enterprise Search] Fix logic for long running and orphaned jobs (#145714)\n\nThis fixes the logic for long-running connector sync jobs: they should\r\nlook at started_at rather than last_seen.\r\nIt also fixes the logic for orphaned jobs, which were displaying the\r\nopposite of what they should have been displaying.","sha":"2e178f8f450ad6019903af17881c8368806816c8","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":145714,"url":"https://github.com/elastic/kibana/pull/145714","mergeCommit":{"message":"[Enterprise Search] Fix logic for long running and orphaned jobs (#145714)\n\nThis fixes the logic for long-running connector sync jobs: they should\r\nlook at started_at rather than last_seen.\r\nIt also fixes the logic for orphaned jobs, which were displaying the\r\nopposite of what they should have been displaying.","sha":"2e178f8f450ad6019903af17881c8368806816c8"}},"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/145714","number":145714,"mergeCommit":{"message":"[Enterprise Search] Fix logic for long running and orphaned jobs (#145714)\n\nThis fixes the logic for long-running connector sync jobs: they should\r\nlook at started_at rather than last_seen.\r\nIt also fixes the logic for orphaned jobs, which were displaying the\r\nopposite of what they should have been displaying.","sha":"2e178f8f450ad6019903af17881c8368806816c8"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
ba7a37ef34
|
[8.6] [Security Sollution][Alerts] fixes rule preview issue for new terms field (#145707) (#146449)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Sollution][Alerts] fixes rule preview issue for new terms field (#145707)](https://github.com/elastic/kibana/pull/145707) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-28T17:36:40Z","message":"[Security Sollution][Alerts] fixes rule preview issue for new terms field (#145707)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/144322\r\n- details on underlying\r\n[issue](https://github.com/elastic/kibana/issues/144322#issuecomment-1321838136)\r\nwithin form-lib\r\n\r\n### Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202687215-e9606bd0-5cfd-4a92-9abf-edaf90868505.mov\r\n\r\n### After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202688418-7cb7d250-02f3-4020-bfa0-65191b8a529b.mov","sha":"c086220f1ba89c9db0fe2c7500d86e3375aeee86","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","v8.6.0","v8.7.0"],"number":145707,"url":"https://github.com/elastic/kibana/pull/145707","mergeCommit":{"message":"[Security Sollution][Alerts] fixes rule preview issue for new terms field (#145707)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/144322\r\n- details on underlying\r\n[issue](https://github.com/elastic/kibana/issues/144322#issuecomment-1321838136)\r\nwithin form-lib\r\n\r\n### Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202687215-e9606bd0-5cfd-4a92-9abf-edaf90868505.mov\r\n\r\n### After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202688418-7cb7d250-02f3-4020-bfa0-65191b8a529b.mov","sha":"c086220f1ba89c9db0fe2c7500d86e3375aeee86"}},"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/145707","number":145707,"mergeCommit":{"message":"[Security Sollution][Alerts] fixes rule preview issue for new terms field (#145707)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/144322\r\n- details on underlying\r\n[issue](https://github.com/elastic/kibana/issues/144322#issuecomment-1321838136)\r\nwithin form-lib\r\n\r\n### Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202687215-e9606bd0-5cfd-4a92-9abf-edaf90868505.mov\r\n\r\n### After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/92328789/202688418-7cb7d250-02f3-4020-bfa0-65191b8a529b.mov","sha":"c086220f1ba89c9db0fe2c7500d86e3375aeee86"}}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
934c6ee813
|
[8.6] [Security Solution][Alerts] fixes new terms multi fields timeline issue (#146185) (#146446)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Alerts] fixes new terms multi fields timeline issue (#146185)](https://github.com/elastic/kibana/pull/146185) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-28T17:26:07Z","message":"[Security Solution][Alerts] fixes new terms multi fields timeline issue (#146185)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/146131\r\n\r\n### Before\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203600097-589d4b8b-c238-48e4-bf72-2f2efcc39ac2.mp4\r\n\r\n### After\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203599864-37a4ccc3-12b8-4c48-87ea-559d15582ef9.mov\r\n\r\n\r\n### For maintainers\r\n\r\n\r\n\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0f31951235ecf11530c23977d028069f427bae67","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Feature:Detection Alerts","Team:Detection Alerts","backport:prev-minor","v8.6.0","v8.7.0"],"number":146185,"url":"https://github.com/elastic/kibana/pull/146185","mergeCommit":{"message":"[Security Solution][Alerts] fixes new terms multi fields timeline issue (#146185)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/146131\r\n\r\n### Before\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203600097-589d4b8b-c238-48e4-bf72-2f2efcc39ac2.mp4\r\n\r\n### After\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203599864-37a4ccc3-12b8-4c48-87ea-559d15582ef9.mov\r\n\r\n\r\n### For maintainers\r\n\r\n\r\n\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0f31951235ecf11530c23977d028069f427bae67"}},"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/146185","number":146185,"mergeCommit":{"message":"[Security Solution][Alerts] fixes new terms multi fields timeline issue (#146185)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/146131\r\n\r\n### Before\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203600097-589d4b8b-c238-48e4-bf72-2f2efcc39ac2.mp4\r\n\r\n### After\r\n\r\nhttps://user-images.githubusercontent.com/92328789/203599864-37a4ccc3-12b8-4c48-87ea-559d15582ef9.mov\r\n\r\n\r\n### For maintainers\r\n\r\n\r\n\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"0f31951235ecf11530c23977d028069f427bae67"}}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
2458f6f283
|
[8.6] [APM][AWS] fix compute usage calc (#146328) (#146510)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM][AWS] fix compute usage calc (#146328)](https://github.com/elastic/kibana/pull/146328) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cauê Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-29T09:42:59Z","message":"[APM][AWS] fix compute usage calc (#146328)\n\ncloses https://github.com/elastic/kibana/issues/146206\r\n\r\n**Before** we were averaging the memory and billed duration and then we\r\ncalculated the compute usage.\r\n**Now** We first calculate the compute usage then get the average and\r\nthen convert to GB-Sec.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9cadd361ded281514626db5d0d49154a62d7484a","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":146328,"url":"https://github.com/elastic/kibana/pull/146328","mergeCommit":{"message":"[APM][AWS] fix compute usage calc (#146328)\n\ncloses https://github.com/elastic/kibana/issues/146206\r\n\r\n**Before** we were averaging the memory and billed duration and then we\r\ncalculated the compute usage.\r\n**Now** We first calculate the compute usage then get the average and\r\nthen convert to GB-Sec.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9cadd361ded281514626db5d0d49154a62d7484a"}},"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/146328","number":146328,"mergeCommit":{"message":"[APM][AWS] fix compute usage calc (#146328)\n\ncloses https://github.com/elastic/kibana/issues/146206\r\n\r\n**Before** we were averaging the memory and billed duration and then we\r\ncalculated the compute usage.\r\n**Now** We first calculate the compute usage then get the average and\r\nthen convert to GB-Sec.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9cadd361ded281514626db5d0d49154a62d7484a"}}]}] BACKPORT--> Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com> |
||
|
Kibana Machine
|
1b2ce1a5a8
|
[8.6] Fixes issue in sorting using TX and RX columns (#145994) (#146509)
# Backport This will backport the following commits from `main` to `8.6`: - [Fixes issue in sorting using TX and RX columns (#145994)](https://github.com/elastic/kibana/pull/145994) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"mohamedhamed-ahmed","email":"eng_mohamedhamed@hotmail.com"},"sourceCommit":{"committedDate":"2022-11-29T09:41:18Z","message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Infra Monitoring UI","Feature:Observability Overview","backport:prev-minor","v8.7.0"],"number":145994,"url":"https://github.com/elastic/kibana/pull/145994","mergeCommit":{"message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b"}},"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/145994","number":145994,"mergeCommit":{"message":"Fixes issue in sorting using TX and RX columns (#145994)\n\n## Summary\r\ncloses #142667\r\nMore details about the issue can be found\r\n[here](https://github.com/elastic/kibana/issues/142667)\r\n\r\n## Problem \r\n\r\nThe problem here is the use of bucket script in the query which doesn't\r\nreturn a single metric value and thus can't be used for pipeline\r\naggregation.\r\n```\r\nbucket_script: {\r\n buckets_path: {\r\n value: 'rx_avg',\r\n period: 'rx_period>period',\r\n },\r\n script: {\r\n source: 'params.value / (params.period / 1000)',\r\n lang: 'painless',\r\n },\r\n gap_policy: 'skip'\r\n }\r\n```\r\n\r\n## Proposed Solutions:\r\n\r\n1. Using\r\n[Runtime](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html)\r\nfield as below:\r\n```\r\n\"runtime_mappings\": {\r\n \"rx_bytes_per_period\": {\r\n \"type\": \"long\",\r\n \"script\": {\r\n \"source\": \"\"\"\r\n emit(doc['host.network.ingress.bytes'].size()==0 ? -1 : (doc['host.network.ingress.bytes'].value/doc['metricset.period'].value));\r\n \"\"\"\r\n }\r\n }\r\n }\r\n```\r\n\r\n2. Using\r\n[Scripted_Metric](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-scripted-metric-aggregation.html):\r\n\r\n```\r\nscripted_metric\": {\r\n \"init_script\": \"state.bytes_per_period = []\",\r\n \"map_script\": \"state.bytes_per_period.add(doc['host.network.ingress.bytes'].value/(doc['metricset.period'].value/1000))\",\r\n \"combine_script\": \"double avg_bytes_per_period = 0; for (t in state.bytes_per_period) { avg_bytes_per_period += t } return avg_bytes_per_period/state.bytes_per_period.size()\",\r\n \"reduce_script\": \"double result = 0; for (a in states) { result += a) } return result/states.size()\"\r\n }\r\n```\r\n\r\n## Conclusion\r\n\r\nI decided to go with the runtime field as its a bit more concise and\r\neasier to understand and performance wise it was slightly faster than\r\nthe scripted metric in most times.\r\n\r\n### Testing\r\n\r\nNavigate to `Observability` -> `Overview` -> `Hosts Table` try to filter\r\nwith Rx and Tx columns","sha":"6e4f22d12dfc18ceff35b9bd0f6038b7fbf5ec7b"}}]}] BACKPORT--> Co-authored-by: mohamedhamed-ahmed <eng_mohamedhamed@hotmail.com> |
||
|
Kibana Machine
|
7375f91e28
|
[8.6] [ML] Modifies script for population analysis screenshot (#146393) (#146496)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Modifies script for population analysis screenshot (#146393)](https://github.com/elastic/kibana/pull/146393) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"István Zoltán Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2022-11-29T06:44:25Z","message":"[ML] Modifies script for population analysis screenshot (#146393)\n\nThis PR adjusts the screenshot automation script to take the\r\n`ml-population-results` screenshots with swim lanes visible.","sha":"115c250a9b79f552395e75b5534d86acc8789597","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v8.7.0","v8.5.3","v8.6.1"],"number":146393,"url":"https://github.com/elastic/kibana/pull/146393","mergeCommit":{"message":"[ML] Modifies script for population analysis screenshot (#146393)\n\nThis PR adjusts the screenshot automation script to take the\r\n`ml-population-results` screenshots with swim lanes visible.","sha":"115c250a9b79f552395e75b5534d86acc8789597"}},"sourceBranch":"main","suggestedTargetBranches":["8.5","8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146393","number":146393,"mergeCommit":{"message":"[ML] Modifies script for population analysis screenshot (#146393)\n\nThis PR adjusts the screenshot automation script to take the\r\n`ml-population-results` screenshots with swim lanes visible.","sha":"115c250a9b79f552395e75b5534d86acc8789597"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com> |
||
|
Kibana Machine
|
f7d8bee976
|
[8.6] [Security Solution] Inspect button title missing (#146473) (#146490)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Inspect button title missing (#146473)](https://github.com/elastic/kibana/pull/146473) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-29T00:36:40Z","message":"[Security Solution] Inspect button title missing (#146473)\n\nThis PR is a quick bug fix for\r\nhttps://github.com/elastic/kibana/issues/141617\r\n\r\n- https://github.com/elastic/kibana/pull/143601 fixes the inspect title\r\nissue by passing a 'title' prop to `initializeTGridSettings`.\r\n- It appears subsequent enhancements in `sessions_viewer` also calls\r\n`initializeTGridSettings`, but in a separate manner. This PR combines\r\nthe two t-grid initialization calls into one.\r\n\r\n\r\n","sha":"32d1dbb1f98053ac34d278d945034363695227c3","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:Investigations","v8.6.0","v8.7.0"],"number":146473,"url":"https://github.com/elastic/kibana/pull/146473","mergeCommit":{"message":"[Security Solution] Inspect button title missing (#146473)\n\nThis PR is a quick bug fix for\r\nhttps://github.com/elastic/kibana/issues/141617\r\n\r\n- https://github.com/elastic/kibana/pull/143601 fixes the inspect title\r\nissue by passing a 'title' prop to `initializeTGridSettings`.\r\n- It appears subsequent enhancements in `sessions_viewer` also calls\r\n`initializeTGridSettings`, but in a separate manner. This PR combines\r\nthe two t-grid initialization calls into one.\r\n\r\n\r\n","sha":"32d1dbb1f98053ac34d278d945034363695227c3"}},"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/146473","number":146473,"mergeCommit":{"message":"[Security Solution] Inspect button title missing (#146473)\n\nThis PR is a quick bug fix for\r\nhttps://github.com/elastic/kibana/issues/141617\r\n\r\n- https://github.com/elastic/kibana/pull/143601 fixes the inspect title\r\nissue by passing a 'title' prop to `initializeTGridSettings`.\r\n- It appears subsequent enhancements in `sessions_viewer` also calls\r\n`initializeTGridSettings`, but in a separate manner. This PR combines\r\nthe two t-grid initialization calls into one.\r\n\r\n\r\n","sha":"32d1dbb1f98053ac34d278d945034363695227c3"}}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com> |
||
Kevin Logan
|
1752c8eadf
|
[8.6] [Security Solution] Add missed policy migration export (#146481) (#146489)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Add missed policy migration export (#146481)](https://github.com/elastic/kibana/pull/146481) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Logan","email":"56395104+kevinlog@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-29T00:11:17Z","message":"[Security Solution] Add missed policy migration export (#146481)\n\n## Summary\r\n\r\nAdds a missing export to the policy migration for 8.6.0\r\n\r\nPR with the migration for reference:\r\nhttps://github.com/elastic/kibana/pull/146050\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":"3fa88f289609ae8565e9d6b05d502adcc912b43a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","Team:Onboarding and Lifecycle Mgt","auto-backport","v8.6.0","v8.7.0"],"number":146481,"url":"https://github.com/elastic/kibana/pull/146481","mergeCommit":{"message":"[Security Solution] Add missed policy migration export (#146481)\n\n## Summary\r\n\r\nAdds a missing export to the policy migration for 8.6.0\r\n\r\nPR with the migration for reference:\r\nhttps://github.com/elastic/kibana/pull/146050\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":"3fa88f289609ae8565e9d6b05d502adcc912b43a"}},"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/146481","number":146481,"mergeCommit":{"message":"[Security Solution] Add missed policy migration export (#146481)\n\n## Summary\r\n\r\nAdds a missing export to the policy migration for 8.6.0\r\n\r\nPR with the migration for reference:\r\nhttps://github.com/elastic/kibana/pull/146050\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":"3fa88f289609ae8565e9d6b05d502adcc912b43a"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
5f8b171ee3
|
[8.6] [Security Solution][Alerts] Add tour to rule management page for suppression and new terms multi fields (#145775) (#146479)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Alerts] Add tour to rule management page for suppression and new terms multi fields (#145775)](https://github.com/elastic/kibana/pull/145775) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-28T21:35:02Z","message":"[Security Solution][Alerts] Add tour to rule management page for suppression and new terms multi fields (#145775)\n\n## Summary\r\n\r\nAdds new tour highlighting new rule capabilities in 8.6 - new terms\r\nmulti fields (https://github.com/elastic/kibana/pull/143943) and alert\r\nsuppression (https://github.com/elastic/kibana/pull/142686).\r\n\r\nI tried using the generic `RulesFeatureTour` again\r\n(https://github.com/elastic/kibana/compare/main...marshallmain:kibana:failed-tour)\r\nbut it still crashes the page.\r\n\r\nI also looked at integrating this tour with the Guided onboarding tour\r\nfor rules management (https://github.com/elastic/kibana/pull/145223),\r\nbut concluded that they should be separate since guided onboarding is\r\nexperimental and this tour should be displayed to users even if they are\r\nnot new users.\r\n\r\nThis PR is essentially a copy of the new terms tour in 8.4\r\n(https://github.com/elastic/kibana/pull/138469).","sha":"13c1b0b863b7d8b324d33f2aaf45d90d5c8c108e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Detection Alerts","v8.6.0","v8.7.0"],"number":145775,"url":"https://github.com/elastic/kibana/pull/145775","mergeCommit":{"message":"[Security Solution][Alerts] Add tour to rule management page for suppression and new terms multi fields (#145775)\n\n## Summary\r\n\r\nAdds new tour highlighting new rule capabilities in 8.6 - new terms\r\nmulti fields (https://github.com/elastic/kibana/pull/143943) and alert\r\nsuppression (https://github.com/elastic/kibana/pull/142686).\r\n\r\nI tried using the generic `RulesFeatureTour` again\r\n(https://github.com/elastic/kibana/compare/main...marshallmain:kibana:failed-tour)\r\nbut it still crashes the page.\r\n\r\nI also looked at integrating this tour with the Guided onboarding tour\r\nfor rules management (https://github.com/elastic/kibana/pull/145223),\r\nbut concluded that they should be separate since guided onboarding is\r\nexperimental and this tour should be displayed to users even if they are\r\nnot new users.\r\n\r\nThis PR is essentially a copy of the new terms tour in 8.4\r\n(https://github.com/elastic/kibana/pull/138469).","sha":"13c1b0b863b7d8b324d33f2aaf45d90d5c8c108e"}},"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/145775","number":145775,"mergeCommit":{"message":"[Security Solution][Alerts] Add tour to rule management page for suppression and new terms multi fields (#145775)\n\n## Summary\r\n\r\nAdds new tour highlighting new rule capabilities in 8.6 - new terms\r\nmulti fields (https://github.com/elastic/kibana/pull/143943) and alert\r\nsuppression (https://github.com/elastic/kibana/pull/142686).\r\n\r\nI tried using the generic `RulesFeatureTour` again\r\n(https://github.com/elastic/kibana/compare/main...marshallmain:kibana:failed-tour)\r\nbut it still crashes the page.\r\n\r\nI also looked at integrating this tour with the Guided onboarding tour\r\nfor rules management (https://github.com/elastic/kibana/pull/145223),\r\nbut concluded that they should be separate since guided onboarding is\r\nexperimental and this tour should be displayed to users even if they are\r\nnot new users.\r\n\r\nThis PR is essentially a copy of the new terms tour in 8.4\r\n(https://github.com/elastic/kibana/pull/138469).","sha":"13c1b0b863b7d8b324d33f2aaf45d90d5c8c108e"}}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
|
Kibana Machine
|
c4de26f9e0
|
[8.6] [Enterprise Search] Fix support for cron scheduling for Elastic Crawler Indices (#146357) (#146463)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Fix support for cron scheduling for Elastic Crawler Indices (#146357)](https://github.com/elastic/kibana/pull/146357) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Byron Hulcher","email":"byronhulcher@gmail.com"},"sourceCommit":{"committedDate":"2022-11-28T19:13:08Z","message":"[Enterprise Search] Fix support for cron scheduling for Elastic Crawler Indices (#146357)","sha":"5b79dbea96c9e4694cec2e47d87b1bcbea6740b5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","backport:prev-minor","v8.6.0","v8.7.0"],"number":146357,"url":"https://github.com/elastic/kibana/pull/146357","mergeCommit":{"message":"[Enterprise Search] Fix support for cron scheduling for Elastic Crawler Indices (#146357)","sha":"5b79dbea96c9e4694cec2e47d87b1bcbea6740b5"}},"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/146357","number":146357,"mergeCommit":{"message":"[Enterprise Search] Fix support for cron scheduling for Elastic Crawler Indices (#146357)","sha":"5b79dbea96c9e4694cec2e47d87b1bcbea6740b5"}}]}] BACKPORT--> Co-authored-by: Byron Hulcher <byronhulcher@gmail.com> |
||
|
Kibana Machine
|
3dbe45667d
|
[8.6] Fixes auto suggest in security solution (#145924) (#146439)
# Backport This will backport the following commits from `main` to `8.6`: - [Fixes auto suggest in security solution (#145924)](https://github.com/elastic/kibana/pull/145924) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T16:52:03Z","message":"Fixes auto suggest in security solution (#145924)","sha":"3a6825cf47e80dab9aeae373a1a93ab740e733eb","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":145924,"url":"https://github.com/elastic/kibana/pull/145924","mergeCommit":{"message":"Fixes auto suggest in security solution (#145924)","sha":"3a6825cf47e80dab9aeae373a1a93ab740e733eb"}},"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/145924","number":145924,"mergeCommit":{"message":"Fixes auto suggest in security solution (#145924)","sha":"3a6825cf47e80dab9aeae373a1a93ab740e733eb"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
d00d67ddd0
|
[8.6] fix for the skipped functional test sync_colors.ts (#146083) (#146457)
# Backport This will backport the following commits from `main` to `8.6`: - [fix for the skipped functional test `sync_colors.ts` (#146083)](https://github.com/elastic/kibana/pull/146083) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rashmi Kulkarni","email":"rashmi.kulkarni@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T18:08:50Z","message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","v8.6.0","v8.7.0"],"number":146083,"url":"https://github.com/elastic/kibana/pull/146083","mergeCommit":{"message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f"}},"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/146083","number":146083,"mergeCommit":{"message":"fix for the skipped functional test `sync_colors.ts` (#146083)\n\ntrying to fix https://github.com/elastic/kibana/issues/97403\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"a270d75f36207567f340a63b3666f9229deb7a7f"}}]}] BACKPORT--> Co-authored-by: Rashmi Kulkarni <rashmi.kulkarni@elastic.co> |
||
|
Kibana Machine
|
8bb5ea2b5e
|
[8.6] [Osquery] Fix issue with packs not running on different than Default space (#146410) (#146429)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] Fix issue with packs not running on different than Default space (#146410)](https://github.com/elastic/kibana/pull/146410) <!--- 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-11-28T16:21:18Z","message":"[Osquery] Fix issue with packs not running on different than Default space (#146410)","sha":"29a4424566d37984efa9898a5f86d9af57934dd5","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","v8.5.3"],"number":146410,"url":"https://github.com/elastic/kibana/pull/146410","mergeCommit":{"message":"[Osquery] Fix issue with packs not running on different than Default space (#146410)","sha":"29a4424566d37984efa9898a5f86d9af57934dd5"}},"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/146410","number":146410,"mergeCommit":{"message":"[Osquery] Fix issue with packs not running on different than Default space (#146410)","sha":"29a4424566d37984efa9898a5f86d9af57934dd5"}},{"branch":"8.5","label":"v8.5.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com> |
||
Shahzad
|
2f04daef98
|
[8.6] [Synthetics] Update monitor details page loading (#145931) (#146282)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Update monitor details page loading (#145931)](https://github.com/elastic/kibana/pull/145931) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T11:33:40Z","message":"[Synthetics] Update monitor details page loading (#145931)\n\nCo-authored-by: Abdul Zahid <awahab07@yahoo.com>","sha":"698504708a48b4706fbe2d4cb98bd2f997da3d6d","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":145931,"url":"https://github.com/elastic/kibana/pull/145931","mergeCommit":{"message":"[Synthetics] Update monitor details page loading (#145931)\n\nCo-authored-by: Abdul Zahid <awahab07@yahoo.com>","sha":"698504708a48b4706fbe2d4cb98bd2f997da3d6d"}},"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/145931","number":145931,"mergeCommit":{"message":"[Synthetics] Update monitor details page loading (#145931)\n\nCo-authored-by: Abdul Zahid <awahab07@yahoo.com>","sha":"698504708a48b4706fbe2d4cb98bd2f997da3d6d"}}]}] BACKPORT--> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d3c8d82a88
|
[8.6] [Security Solution] Stop Job should show when ml job toggle is on (#146407) (#146438)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Stop Job should show when ml job toggle is on (#146407)](https://github.com/elastic/kibana/pull/146407) <!--- 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-11-28T16:47:29Z","message":"[Security Solution] Stop Job should show when ml job toggle is on (#146407)\n\n## Summary\r\n\r\nThis PR fixes incorrect wording of the ML Job run/stop status label.\r\nRight now we always show \"Run job\" label even when job has been started\r\nalready. With this fix we will show \"Stop job\" in case of running job.\r\n\r\nJob is not running state:\r\n\r\n<img width=\"782\" alt=\"Screenshot 2022-11-28 at 15 55 37\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308912-b53fa125-715a-4240-b6a3-e75be68d4251.png\">\r\n\r\nJob is running state:\r\n\r\n<img width=\"785\" alt=\"Screenshot 2022-11-28 at 15 55 29\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308956-c0fb7cae-8c95-4f26-8bae-ddff3e44a214.png\">\r\n\r\nTicket: #145324","sha":"3c30b3f8ce58da3316959a3bee36d89d6fcc2103","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":146407,"url":"https://github.com/elastic/kibana/pull/146407","mergeCommit":{"message":"[Security Solution] Stop Job should show when ml job toggle is on (#146407)\n\n## Summary\r\n\r\nThis PR fixes incorrect wording of the ML Job run/stop status label.\r\nRight now we always show \"Run job\" label even when job has been started\r\nalready. With this fix we will show \"Stop job\" in case of running job.\r\n\r\nJob is not running state:\r\n\r\n<img width=\"782\" alt=\"Screenshot 2022-11-28 at 15 55 37\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308912-b53fa125-715a-4240-b6a3-e75be68d4251.png\">\r\n\r\nJob is running state:\r\n\r\n<img width=\"785\" alt=\"Screenshot 2022-11-28 at 15 55 29\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308956-c0fb7cae-8c95-4f26-8bae-ddff3e44a214.png\">\r\n\r\nTicket: #145324","sha":"3c30b3f8ce58da3316959a3bee36d89d6fcc2103"}},"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/146407","number":146407,"mergeCommit":{"message":"[Security Solution] Stop Job should show when ml job toggle is on (#146407)\n\n## Summary\r\n\r\nThis PR fixes incorrect wording of the ML Job run/stop status label.\r\nRight now we always show \"Run job\" label even when job has been started\r\nalready. With this fix we will show \"Stop job\" in case of running job.\r\n\r\nJob is not running state:\r\n\r\n<img width=\"782\" alt=\"Screenshot 2022-11-28 at 15 55 37\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308912-b53fa125-715a-4240-b6a3-e75be68d4251.png\">\r\n\r\nJob is running state:\r\n\r\n<img width=\"785\" alt=\"Screenshot 2022-11-28 at 15 55 29\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/204308956-c0fb7cae-8c95-4f26-8bae-ddff3e44a214.png\">\r\n\r\nTicket: #145324","sha":"3c30b3f8ce58da3316959a3bee36d89d6fcc2103"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
82bf59b272
|
[8.6] [UA] fix flaky test (#146351) (#146441)
# Backport This will backport the following commits from `main` to `8.6`: - [[UA] fix flaky test (#146351)](https://github.com/elastic/kibana/pull/146351) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ahmad Bamieh","email":"ahmad.bamyeh@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T16:52:15Z","message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0","8.6.1"],"number":146351,"url":"https://github.com/elastic/kibana/pull/146351","mergeCommit":{"message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600"}},"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/146351","number":146351,"mergeCommit":{"message":"[UA] fix flaky test (#146351)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCloses https://github.com/elastic/kibana/issues/144885","sha":"ab8dd04073a4f9b8bcf26444f35a33d85f98b600"}}]}] BACKPORT--> Co-authored-by: Ahmad Bamieh <ahmad.bamyeh@elastic.co> |
||
|
Kibana Machine
|
0cd9b32440
|
[8.6] [Fleet] Fix open API for output to support logstash (#146396) (#146432)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Fix open API for output to support logstash (#146396)](https://github.com/elastic/kibana/pull/146396) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T16:23:50Z","message":"[Fleet] Fix open API for output to support logstash (#146396)","sha":"a5c17d3d9aec59e366d70dfd4a5a14f04713b7df","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":146396,"url":"https://github.com/elastic/kibana/pull/146396","mergeCommit":{"message":"[Fleet] Fix open API for output to support logstash (#146396)","sha":"a5c17d3d9aec59e366d70dfd4a5a14f04713b7df"}},"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/146396","number":146396,"mergeCommit":{"message":"[Fleet] Fix open API for output to support logstash (#146396)","sha":"a5c17d3d9aec59e366d70dfd4a5a14f04713b7df"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
9a6a1181a6
|
[8.6] [APM] Agent explorer UI issues (#146140) (#146431)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Agent explorer UI issues (#146140)](https://github.com/elastic/kibana/pull/146140) <!--- 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-28T16:24:46Z","message":"[APM] Agent explorer UI issues (#146140)\n\nCloses https://github.com/elastic/kibana/issues/146019.\r\n\r\n- `ManagedTable` was switched by `EuiInMemoryTable` to dettach table in\r\nflyout form url params. This solves\r\n * when sorting the table in the flyout sorts out the agent list\r\n * Pagination in flyout doesn't work\r\n* Agent instances table inherits props from the agent list table (ex.\r\nrows per)\r\n * Agent instances table inherits pagination from the agent list\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547187-67070fe8-0067-4a16-a522-1d24e5df8320.mov\r\n\r\n\r\n- fieldLabel was created in flyout sticky properties so what we see when\r\nhovering is not the key anymore\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547424-470e0298-4cbb-4316-a895-c803810a315c.mov\r\n\r\n\r\n- Agent list table column now have `%` witdh so we can keep sticking to\r\n`fixed` table Layout and at the same time we don't lose serviceName\r\ncolumn for small resolutions\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203550989-04af15cc-8ad7-44b6-8cf8-c9207263d8d0.mov","sha":"9efdc44429da5fa78796150b541d72cfe6fa99e0","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":146140,"url":"https://github.com/elastic/kibana/pull/146140","mergeCommit":{"message":"[APM] Agent explorer UI issues (#146140)\n\nCloses https://github.com/elastic/kibana/issues/146019.\r\n\r\n- `ManagedTable` was switched by `EuiInMemoryTable` to dettach table in\r\nflyout form url params. This solves\r\n * when sorting the table in the flyout sorts out the agent list\r\n * Pagination in flyout doesn't work\r\n* Agent instances table inherits props from the agent list table (ex.\r\nrows per)\r\n * Agent instances table inherits pagination from the agent list\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547187-67070fe8-0067-4a16-a522-1d24e5df8320.mov\r\n\r\n\r\n- fieldLabel was created in flyout sticky properties so what we see when\r\nhovering is not the key anymore\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547424-470e0298-4cbb-4316-a895-c803810a315c.mov\r\n\r\n\r\n- Agent list table column now have `%` witdh so we can keep sticking to\r\n`fixed` table Layout and at the same time we don't lose serviceName\r\ncolumn for small resolutions\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203550989-04af15cc-8ad7-44b6-8cf8-c9207263d8d0.mov","sha":"9efdc44429da5fa78796150b541d72cfe6fa99e0"}},"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/146140","number":146140,"mergeCommit":{"message":"[APM] Agent explorer UI issues (#146140)\n\nCloses https://github.com/elastic/kibana/issues/146019.\r\n\r\n- `ManagedTable` was switched by `EuiInMemoryTable` to dettach table in\r\nflyout form url params. This solves\r\n * when sorting the table in the flyout sorts out the agent list\r\n * Pagination in flyout doesn't work\r\n* Agent instances table inherits props from the agent list table (ex.\r\nrows per)\r\n * Agent instances table inherits pagination from the agent list\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547187-67070fe8-0067-4a16-a522-1d24e5df8320.mov\r\n\r\n\r\n- fieldLabel was created in flyout sticky properties so what we see when\r\nhovering is not the key anymore\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203547424-470e0298-4cbb-4316-a895-c803810a315c.mov\r\n\r\n\r\n- Agent list table column now have `%` witdh so we can keep sticking to\r\n`fixed` table Layout and at the same time we don't lose serviceName\r\ncolumn for small resolutions\r\n\r\n\r\nhttps://user-images.githubusercontent.com/1313018/203550989-04af15cc-8ad7-44b6-8cf8-c9207263d8d0.mov","sha":"9efdc44429da5fa78796150b541d72cfe6fa99e0"}}]}] BACKPORT--> Co-authored-by: Yngrid Coello <yngrid.coello@elastic.co> |
||
|
Kibana Machine
|
e7de9cfded
|
[8.6] [Enterprise Search] Make sync jobs use filtering array (#146405) (#146426)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Make sync jobs use filtering array (#146405)](https://github.com/elastic/kibana/pull/146405) <!--- 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-11-28T16:07:19Z","message":"[Enterprise Search] Make sync jobs use filtering array (#146405)\n\nThis fixes a bug where sync jobs were using an object to access the\r\nfiltering property instead of an object.","sha":"01a4c7a43d621b3cf9a69de6a23077a4781bbe74","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":146405,"url":"https://github.com/elastic/kibana/pull/146405","mergeCommit":{"message":"[Enterprise Search] Make sync jobs use filtering array (#146405)\n\nThis fixes a bug where sync jobs were using an object to access the\r\nfiltering property instead of an object.","sha":"01a4c7a43d621b3cf9a69de6a23077a4781bbe74"}},"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/146405","number":146405,"mergeCommit":{"message":"[Enterprise Search] Make sync jobs use filtering array (#146405)\n\nThis fixes a bug where sync jobs were using an object to access the\r\nfiltering property instead of an object.","sha":"01a4c7a43d621b3cf9a69de6a23077a4781bbe74"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
5ea653ecf3
|
[8.6] [Enterprise Search][ML Inference] Improve no models copy (#145772) (#146422)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search][ML Inference] Improve no models copy (#145772)](https://github.com/elastic/kibana/pull/145772) <!--- 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-11-28T15:40:51Z","message":"[Enterprise Search][ML Inference] Improve no models copy (#145772)\n\n## Summary\r\n\r\nUpdated the no models learn more to link to the new machine learning\r\ngetting started guide\r\nUpdated the copy on the no models modal to be more explicit and provide\r\ninformation on the types of models that are supported.\r\n\r\n### Screenshot\r\n\r\n\r\n\r\n\r\n### Checklist\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)","sha":"210b2f0f0e1dcb4798b5cd04eea5abe3f6e638f3","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":145772,"url":"https://github.com/elastic/kibana/pull/145772","mergeCommit":{"message":"[Enterprise Search][ML Inference] Improve no models copy (#145772)\n\n## Summary\r\n\r\nUpdated the no models learn more to link to the new machine learning\r\ngetting started guide\r\nUpdated the copy on the no models modal to be more explicit and provide\r\ninformation on the types of models that are supported.\r\n\r\n### Screenshot\r\n\r\n\r\n\r\n\r\n### Checklist\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)","sha":"210b2f0f0e1dcb4798b5cd04eea5abe3f6e638f3"}},"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/145772","number":145772,"mergeCommit":{"message":"[Enterprise Search][ML Inference] Improve no models copy (#145772)\n\n## Summary\r\n\r\nUpdated the no models learn more to link to the new machine learning\r\ngetting started guide\r\nUpdated the copy on the no models modal to be more explicit and provide\r\ninformation on the types of models that are supported.\r\n\r\n### Screenshot\r\n\r\n\r\n\r\n\r\n### Checklist\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)","sha":"210b2f0f0e1dcb4798b5cd04eea5abe3f6e638f3"}}]}] BACKPORT--> Co-authored-by: Rodney Norris <rodney.norris@elastic.co> |
||
|
Kibana Machine
|
0560c95def
|
[8.6] [Security Solution][Investigations][Timeline] - Update getExceptions to use parameters (#145889) (#146415)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Investigations][Timeline] - Update getExceptions to use parameters (#145889)](https://github.com/elastic/kibana/pull/145889) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T15:08:48Z","message":"[Security Solution][Investigations][Timeline] - Update getExceptions to use parameters (#145889)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/136772\r\n\r\nThe issue was introduced by a couple of changes:\r\n\r\nFirst:\r\nhttps://github.com/elastic/kibana/pull/136163/files#diff-02d33a1ed6679f7775dc01941ca21b085d7c008ecffe5e029f5967407a5e5b13L23\r\nin 8.4.\r\n\r\nThe bug: A filter on the timeline UI relied on the `exceptions_list`\r\nfield provided on `_source` to auto-generate a filter when investigating\r\nin timeline labelled `Not Exceptions` which would filter out the\r\nexceptions from the timeline. This PR resolves that issue by pulling the\r\n`exceptions_list` field from `kibana.alert.rule.parameters`.\r\n\r\nSecond:\r\nhttps://github.com/elastic/kibana/pull/133254/files#diff-0f69b69fd9cefef6ed04a048d7df86b7e385e816bdf17309212437dc3f69726cL74\r\n\r\nThe filter actually stopped being passed to timeline entirely because of\r\nthe above change.\r\n\r\nWith the fixes in place:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/17211684/203111748-7a0c2eb5-a46f-4f88-9d77-3628204625ac.mov","sha":"b32c8b9df89188cdcb149bd1d9494d3f99999ad6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","backport","release_note:fix","Team:Threat Hunting:Investigations","v8.5.0","v8.6.0","v8.7.0"],"number":145889,"url":"https://github.com/elastic/kibana/pull/145889","mergeCommit":{"message":"[Security Solution][Investigations][Timeline] - Update getExceptions to use parameters (#145889)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/136772\r\n\r\nThe issue was introduced by a couple of changes:\r\n\r\nFirst:\r\nhttps://github.com/elastic/kibana/pull/136163/files#diff-02d33a1ed6679f7775dc01941ca21b085d7c008ecffe5e029f5967407a5e5b13L23\r\nin 8.4.\r\n\r\nThe bug: A filter on the timeline UI relied on the `exceptions_list`\r\nfield provided on `_source` to auto-generate a filter when investigating\r\nin timeline labelled `Not Exceptions` which would filter out the\r\nexceptions from the timeline. This PR resolves that issue by pulling the\r\n`exceptions_list` field from `kibana.alert.rule.parameters`.\r\n\r\nSecond:\r\nhttps://github.com/elastic/kibana/pull/133254/files#diff-0f69b69fd9cefef6ed04a048d7df86b7e385e816bdf17309212437dc3f69726cL74\r\n\r\nThe filter actually stopped being passed to timeline entirely because of\r\nthe above change.\r\n\r\nWith the fixes in place:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/17211684/203111748-7a0c2eb5-a46f-4f88-9d77-3628204625ac.mov","sha":"b32c8b9df89188cdcb149bd1d9494d3f99999ad6"}},"sourceBranch":"main","suggestedTargetBranches":["8.5","8.6"],"targetPullRequestStates":[{"branch":"8.5","label":"v8.5.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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/145889","number":145889,"mergeCommit":{"message":"[Security Solution][Investigations][Timeline] - Update getExceptions to use parameters (#145889)\n\n## Summary\r\n\r\nFixes: https://github.com/elastic/kibana/issues/136772\r\n\r\nThe issue was introduced by a couple of changes:\r\n\r\nFirst:\r\nhttps://github.com/elastic/kibana/pull/136163/files#diff-02d33a1ed6679f7775dc01941ca21b085d7c008ecffe5e029f5967407a5e5b13L23\r\nin 8.4.\r\n\r\nThe bug: A filter on the timeline UI relied on the `exceptions_list`\r\nfield provided on `_source` to auto-generate a filter when investigating\r\nin timeline labelled `Not Exceptions` which would filter out the\r\nexceptions from the timeline. This PR resolves that issue by pulling the\r\n`exceptions_list` field from `kibana.alert.rule.parameters`.\r\n\r\nSecond:\r\nhttps://github.com/elastic/kibana/pull/133254/files#diff-0f69b69fd9cefef6ed04a048d7df86b7e385e816bdf17309212437dc3f69726cL74\r\n\r\nThe filter actually stopped being passed to timeline entirely because of\r\nthe above change.\r\n\r\nWith the fixes in place:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/17211684/203111748-7a0c2eb5-a46f-4f88-9d77-3628204625ac.mov","sha":"b32c8b9df89188cdcb149bd1d9494d3f99999ad6"}}]}] BACKPORT--> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> |
||
|
Kibana Machine
|
e6c75cd1cd
|
[8.6] fix timepicker default start day (#145947) (#146408)
# Backport This will backport the following commits from `main` to `8.6`: - [fix timepicker default start day (#145947)](https://github.com/elastic/kibana/pull/145947) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lee Drengenberg","email":"lee.drengenberg@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T14:59:09Z","message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","test_ui_functional","release_note:skip","backport:prev-minor","v8.7.0"],"number":145947,"url":"https://github.com/elastic/kibana/pull/145947","mergeCommit":{"message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac"}},"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/145947","number":145947,"mergeCommit":{"message":"fix timepicker default start day (#145947)\n\n## Summary\r\n\r\nThis PR is mainly some cleanup before another PR I have in the works to\r\nshortcut timepicker.setAbsoluteTime() by checking if we already have the\r\ndesired time set.\r\n\r\nThis PR changes the timePicker defaultStartTimeUTC value from September\r\n18th to September 19th to match the value of defaultStartTimeUTC.\r\nThe variable name defaultStartTimeUTC implies it's a different timezone\r\nbut actually it's the same date time but in a different ISO format.\r\nIt seems there was only 1 place in tests which expected that Sep 18th\r\ndate.\r\n\r\nAnother small change in\r\n`x-pack/test/functional/apps/lens/group1/text_based_languages.ts` is to\r\nuse uiSettings.update insteda of uiSettings.replace. `replace` wipes out\r\nthe default UTC timezone and the defaultTime settings.\r\n\r\nI added a few calls to cleanStandardList to make sure any saved objects\r\ncreated by the tests are cleaned up, and to get a clean run if other\r\ntests left something.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9c9c66cd0b16f7514b407912d1b0bbcb0cab00ac"}}]}] BACKPORT--> Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co> |
||
|
Kibana Machine
|
23f0d710d3
|
[8.6] [Osquery] Fix osquery response actions validations (#144994) (#146391)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] Fix osquery response actions validations (#144994)](https://github.com/elastic/kibana/pull/144994) <!--- 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-11-28T13:37:14Z","message":"[Osquery] Fix osquery response actions validations (#144994)","sha":"1cb49bb4352b0c175c908727c6bd9e67dc73c70d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":144994,"url":"https://github.com/elastic/kibana/pull/144994","mergeCommit":{"message":"[Osquery] Fix osquery response actions validations (#144994)","sha":"1cb49bb4352b0c175c908727c6bd9e67dc73c70d"}},"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/144994","number":144994,"mergeCommit":{"message":"[Osquery] Fix osquery response actions validations (#144994)","sha":"1cb49bb4352b0c175c908727c6bd9e67dc73c70d"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
12f1b6179c
|
[8.6] [Osquery] - Enable resizing of Osquery query editor (#145231) (#146386)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] - Enable resizing of Osquery query editor (#145231)](https://github.com/elastic/kibana/pull/145231) <!--- 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-11-28T13:01:28Z","message":"[Osquery] - Enable resizing of Osquery query editor (#145231)","sha":"b300aa55fb421a3b0c98d24faa1895f28ccd67f2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":145231,"url":"https://github.com/elastic/kibana/pull/145231","mergeCommit":{"message":"[Osquery] - Enable resizing of Osquery query editor (#145231)","sha":"b300aa55fb421a3b0c98d24faa1895f28ccd67f2"}},"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/145231","number":145231,"mergeCommit":{"message":"[Osquery] - Enable resizing of Osquery query editor (#145231)","sha":"b300aa55fb421a3b0c98d24faa1895f28ccd67f2"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
857c20a1f3
|
[8.6] [Osquery] Fix small issues (#146101) (#146387)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] Fix small issues (#146101)](https://github.com/elastic/kibana/pull/146101) <!--- 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-11-28T13:02:21Z","message":"[Osquery] Fix small issues (#146101)","sha":"bc2eeda0d80a62adb8a6620df51bc9b5b41dd4ad","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Asset Management","Feature:Osquery","v8.6.0","v8.7.0"],"number":146101,"url":"https://github.com/elastic/kibana/pull/146101","mergeCommit":{"message":"[Osquery] Fix small issues (#146101)","sha":"bc2eeda0d80a62adb8a6620df51bc9b5b41dd4ad"}},"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/146101","number":146101,"mergeCommit":{"message":"[Osquery] Fix small issues (#146101)","sha":"bc2eeda0d80a62adb8a6620df51bc9b5b41dd4ad"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
8320b80002
|
[8.6] [Security Solution] Update cache invalidation logic to handle error responses (#146271) (#146380)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Update cache invalidation logic to handle error responses (#146271)](https://github.com/elastic/kibana/pull/146271) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T11:50:40Z","message":"[Security Solution] Update cache invalidation logic to handle error responses (#146271)\n\n**Resolves: https://github.com/elastic/kibana/issues/146277**\r\n\r\n## Summary\r\n\r\nPreviously, we invalidated the rules table cache only after successful\r\nserver-side state mutations. So when an action like bulk edit was\r\nsuccessfully updating some rules and failing for others, the table\r\ncontinued showing outdated results.\r\n\r\nThis PR moves the cache invalidation from the `onSuccess` handlers to\r\nthe `onSettled` handlers to prevent showing partially stale data after\r\nfailed updates.","sha":"e9bc60355858c82fe39676622004f8e9cdfa61a2","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","auto-backport","Feature:Rule Management","Team:Detection Rules","v8.6.0","v8.7.0"],"number":146271,"url":"https://github.com/elastic/kibana/pull/146271","mergeCommit":{"message":"[Security Solution] Update cache invalidation logic to handle error responses (#146271)\n\n**Resolves: https://github.com/elastic/kibana/issues/146277**\r\n\r\n## Summary\r\n\r\nPreviously, we invalidated the rules table cache only after successful\r\nserver-side state mutations. So when an action like bulk edit was\r\nsuccessfully updating some rules and failing for others, the table\r\ncontinued showing outdated results.\r\n\r\nThis PR moves the cache invalidation from the `onSuccess` handlers to\r\nthe `onSettled` handlers to prevent showing partially stale data after\r\nfailed updates.","sha":"e9bc60355858c82fe39676622004f8e9cdfa61a2"}},"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/146271","number":146271,"mergeCommit":{"message":"[Security Solution] Update cache invalidation logic to handle error responses (#146271)\n\n**Resolves: https://github.com/elastic/kibana/issues/146277**\r\n\r\n## Summary\r\n\r\nPreviously, we invalidated the rules table cache only after successful\r\nserver-side state mutations. So when an action like bulk edit was\r\nsuccessfully updating some rules and failing for others, the table\r\ncontinued showing outdated results.\r\n\r\nThis PR moves the cache invalidation from the `onSuccess` handlers to\r\nthe `onSettled` handlers to prevent showing partially stale data after\r\nfailed updates.","sha":"e9bc60355858c82fe39676622004f8e9cdfa61a2"}}]}] BACKPORT--> Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co> |
||
|
Kibana Machine
|
3a04b73aa1
|
[8.6] [Enterprise Search] Display sync errors in draft validation (#146317) (#146382)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Display sync errors in draft validation (#146317)](https://github.com/elastic/kibana/pull/146317) <!--- 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-11-28T12:09:36Z","message":"[Enterprise Search] Display sync errors in draft validation (#146317)\n\nThis shows validation rule violations after validation in the edit draft\r\nsnippet.\r\n\r\n<img width=\"1001\" alt=\"Screenshot 2022-11-24 at 16 56 02\"\r\nsrc=\"https://user-images.githubusercontent.com/94373878/203825526-f8b919d6-6c2e-400e-b0b8-9c3d2ab1b8b9.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"911d9e9b0d327e68f67c82712ed4a8c7ad5dfbb4","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":146317,"url":"https://github.com/elastic/kibana/pull/146317","mergeCommit":{"message":"[Enterprise Search] Display sync errors in draft validation (#146317)\n\nThis shows validation rule violations after validation in the edit draft\r\nsnippet.\r\n\r\n<img width=\"1001\" alt=\"Screenshot 2022-11-24 at 16 56 02\"\r\nsrc=\"https://user-images.githubusercontent.com/94373878/203825526-f8b919d6-6c2e-400e-b0b8-9c3d2ab1b8b9.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"911d9e9b0d327e68f67c82712ed4a8c7ad5dfbb4"}},"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/146317","number":146317,"mergeCommit":{"message":"[Enterprise Search] Display sync errors in draft validation (#146317)\n\nThis shows validation rule violations after validation in the edit draft\r\nsnippet.\r\n\r\n<img width=\"1001\" alt=\"Screenshot 2022-11-24 at 16 56 02\"\r\nsrc=\"https://user-images.githubusercontent.com/94373878/203825526-f8b919d6-6c2e-400e-b0b8-9c3d2ab1b8b9.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"911d9e9b0d327e68f67c82712ed4a8c7ad5dfbb4"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
716ce019b4
|
[8.6] [8.6] Fix: Wrong default filtering rule (#146259) (#146275)
# Backport This will backport the following commits from `main` to `8.6`: - [[8.6] Fix: Wrong default filtering rule (#146259)](https://github.com/elastic/kibana/pull/146259) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tim Grein","email":"tim.grein@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T10:50:42Z","message":"[8.6] Fix: Wrong default filtering rule (#146259)\n\n## Closes https://github.com/elastic/enterprise-search-team/issues/3422\r\n\r\nThe default rule for connectors simple rule filtering should be\r\n**INCLUDE '_' REGEX '.*'** and not **INCLUDE '_' EQUALS '.*'**","sha":"ca6451f25a65853e92450dbd3760902a385d9766","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0"],"number":146259,"url":"https://github.com/elastic/kibana/pull/146259","mergeCommit":{"message":"[8.6] Fix: Wrong default filtering rule (#146259)\n\n## Closes https://github.com/elastic/enterprise-search-team/issues/3422\r\n\r\nThe default rule for connectors simple rule filtering should be\r\n**INCLUDE '_' REGEX '.*'** and not **INCLUDE '_' EQUALS '.*'**","sha":"ca6451f25a65853e92450dbd3760902a385d9766"}},"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/146259","number":146259,"mergeCommit":{"message":"[8.6] Fix: Wrong default filtering rule (#146259)\n\n## Closes https://github.com/elastic/enterprise-search-team/issues/3422\r\n\r\nThe default rule for connectors simple rule filtering should be\r\n**INCLUDE '_' REGEX '.*'** and not **INCLUDE '_' EQUALS '.*'**","sha":"ca6451f25a65853e92450dbd3760902a385d9766"}}]}] BACKPORT--> Co-authored-by: Tim Grein <tim.grein@elastic.co> |
||
|
Kibana Machine
|
38feeef956
|
[8.6] [ML] Fixing recognizer wizard input fields (#146325) (#146372)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fixing recognizer wizard input fields (#146325)](https://github.com/elastic/kibana/pull/146325) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T11:01:50Z","message":"[ML] Fixing recognizer wizard input fields (#146325)\n\nFixes https://github.com/elastic/kibana/issues/144504\r\n\r\nRemoves the use of `usePartialState` which was causing an infinite\r\nrender loop in favour of individual `useStates` for the input settings.\r\n\r\nAlso contains a bit of code clean up, fixing hook dependencies and\r\nremoving dependency cache use.","sha":"9eee4c3d47ee2ca120921de08b7310ed98df0002","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly Detection","v8.6.0","v8.7.0"],"number":146325,"url":"https://github.com/elastic/kibana/pull/146325","mergeCommit":{"message":"[ML] Fixing recognizer wizard input fields (#146325)\n\nFixes https://github.com/elastic/kibana/issues/144504\r\n\r\nRemoves the use of `usePartialState` which was causing an infinite\r\nrender loop in favour of individual `useStates` for the input settings.\r\n\r\nAlso contains a bit of code clean up, fixing hook dependencies and\r\nremoving dependency cache use.","sha":"9eee4c3d47ee2ca120921de08b7310ed98df0002"}},"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/146325","number":146325,"mergeCommit":{"message":"[ML] Fixing recognizer wizard input fields (#146325)\n\nFixes https://github.com/elastic/kibana/issues/144504\r\n\r\nRemoves the use of `usePartialState` which was causing an infinite\r\nrender loop in favour of individual `useStates` for the input settings.\r\n\r\nAlso contains a bit of code clean up, fixing hook dependencies and\r\nremoving dependency cache use.","sha":"9eee4c3d47ee2ca120921de08b7310ed98df0002"}}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
Kibana Machine
|
269987e42b
|
[8.6] [Uptime] Use query string for simple text search (#145533) (#146370)
# Backport This will backport the following commits from `main` to `8.6`: - [[Uptime] Use query string for simple text search (#145533)](https://github.com/elastic/kibana/pull/145533) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-11-28T10:58:48Z","message":"[Uptime] Use query string for simple text search (#145533)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\r\nFixes https://github.com/elastic/kibana/issues/145530","sha":"35e581534c1cbdaaef911b3d4770216dacf8a34f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:uptime","v8.6.0","v8.7.0"],"number":145533,"url":"https://github.com/elastic/kibana/pull/145533","mergeCommit":{"message":"[Uptime] Use query string for simple text search (#145533)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\r\nFixes https://github.com/elastic/kibana/issues/145530","sha":"35e581534c1cbdaaef911b3d4770216dacf8a34f"}},"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/145533","number":145533,"mergeCommit":{"message":"[Uptime] Use query string for simple text search (#145533)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>\r\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>\r\nFixes https://github.com/elastic/kibana/issues/145530","sha":"35e581534c1cbdaaef911b3d4770216dacf8a34f"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
Kibana Machine
|
249b3ebdae
|
[8.6] [DOCS] Alert limit for cases (#145950) (#146321) | ||
|
Kibana Machine
|
a08c594582
|
[8.6] Add open API specification for list connector types (#145951) (#146330)
# Backport This will backport the following commits from `main` to `8.6`: - [Add open API specification for list connector types (#145951)](https://github.com/elastic/kibana/pull/145951) <!--- 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-11-24T18:30:51Z","message":"Add open API specification for list connector types (#145951)","sha":"94b67781e8d56171a58b72ad2bb68171de4b67ea","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorTypes","v8.6.0","v8.7.0"],"number":145951,"url":"https://github.com/elastic/kibana/pull/145951","mergeCommit":{"message":"Add open API specification for list connector types (#145951)","sha":"94b67781e8d56171a58b72ad2bb68171de4b67ea"}},"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/145951","number":145951,"mergeCommit":{"message":"Add open API specification for list connector types (#145951)","sha":"94b67781e8d56171a58b72ad2bb68171de4b67ea"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
ae23e97a67
|
[8.6] [ML] Removing duplicate tooltip text (#146308) (#146329)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Removing duplicate tooltip text (#146308)](https://github.com/elastic/kibana/pull/146308) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T17:48:31Z","message":"[ML] Removing duplicate tooltip text (#146308)\n\nTooltip sentence was mistakenly repeated.","sha":"e05fac15c619335f60dc143e28a9bb24051edc28","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","Feature:Anomaly Detection","release_note:skip","v8.6.0","v8.7.0"],"number":146308,"url":"https://github.com/elastic/kibana/pull/146308","mergeCommit":{"message":"[ML] Removing duplicate tooltip text (#146308)\n\nTooltip sentence was mistakenly repeated.","sha":"e05fac15c619335f60dc143e28a9bb24051edc28"}},"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/146308","number":146308,"mergeCommit":{"message":"[ML] Removing duplicate tooltip text (#146308)\n\nTooltip sentence was mistakenly repeated.","sha":"e05fac15c619335f60dc143e28a9bb24051edc28"}}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
Tiago Costa
|
69c72cb284
|
skip flaky suite (#143408) | ||
|
Kibana Machine
|
de647f64f7
|
[8.6] [ResponseOps][Alerting] Update Kibana Alerting scaling metrics to be running counts (#145296) (#146310)
# Backport This will backport the following commits from `main` to `8.6`: - [[ResponseOps][Alerting] Update Kibana Alerting scaling metrics to be running counts (#145296)](https://github.com/elastic/kibana/pull/145296) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-24T15:47:27Z","message":"[ResponseOps][Alerting] Update Kibana Alerting scaling metrics to be running counts (#145296)\n\nResolves https://github.com/elastic/kibana/issues/145289\r\n\r\n## Summary\r\n\r\nThis pr removed a field and fixes a bug with the previous metrics and\r\nkeeps a running count for the life of the kibana.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n\r\n### To verify\r\n\r\n- Create a rule and hit the\r\n`/internal/task_manager/_background_task_utilization` api\r\n- Verify that the counts are increasing\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"105a15c5c23ec70df228cc95d4eb355094ee1ead","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","v8.6.0","v8.7.0"],"number":145296,"url":"https://github.com/elastic/kibana/pull/145296","mergeCommit":{"message":"[ResponseOps][Alerting] Update Kibana Alerting scaling metrics to be running counts (#145296)\n\nResolves https://github.com/elastic/kibana/issues/145289\r\n\r\n## Summary\r\n\r\nThis pr removed a field and fixes a bug with the previous metrics and\r\nkeeps a running count for the life of the kibana.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n\r\n### To verify\r\n\r\n- Create a rule and hit the\r\n`/internal/task_manager/_background_task_utilization` api\r\n- Verify that the counts are increasing\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"105a15c5c23ec70df228cc95d4eb355094ee1ead"}},"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/145296","number":145296,"mergeCommit":{"message":"[ResponseOps][Alerting] Update Kibana Alerting scaling metrics to be running counts (#145296)\n\nResolves https://github.com/elastic/kibana/issues/145289\r\n\r\n## Summary\r\n\r\nThis pr removed a field and fixes a bug with the previous metrics and\r\nkeeps a running count for the life of the kibana.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n\r\n### To verify\r\n\r\n- Create a rule and hit the\r\n`/internal/task_manager/_background_task_utilization` api\r\n- Verify that the counts are increasing\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"105a15c5c23ec70df228cc95d4eb355094ee1ead"}}]}] BACKPORT--> Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com> |
||
|
Shahzad
|
fcc857c2f9
|
[8.6] [Synthetics] Update monitor detail data on refresh (#145468) (#146319)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Update monitor detail data on refresh (#145468)](https://github.com/elastic/kibana/pull/145468) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T19:20:42Z","message":"[Synthetics] Update monitor detail data on refresh (#145468)\n\n## Summary\r\n\r\nResolves #143662.\r\n\r\nResolves #144367.\r\n\r\nThis patch will add refresh capabilities to the monitor detail page and\r\nits child views. Today, the page needs to be hard-refreshed in order for\r\nthis to work.\r\n\r\n### Arch changes\r\n\r\n#### App-wide refresh interval\r\n\r\nTo simplify how auto-refreshing works, I have\r\n[extracted](https://github.com/elastic/kibana/pull/145468/files#diff-09f3a6de5b54c7d3933df933d83e963f6ff6a5c18a3d83238bd658623595fe35L47)\r\nthe existing `interval` logic from the Overview page and put it into the\r\n[`RefreshContext`](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR36)\r\nitself. I am not overly fond of this solution, so if someone has a\r\nbetter suggestion for how to handle this, I am open to recommendations.\r\n\r\nThis refresh context also ties into the date picker components we use\r\nfor some of these pages, so everything should continue to work\r\nseamlessly, but there's going to be a conflicting auto-refresh between\r\ndate pickers and the internal context value itself. It might be\r\nworthwhile for us to discuss this in a tech sync and have a dedicated\r\nenhancement.\r\n\r\n#### New absolute date formatting hook\r\n\r\nI've introduced a [new hook for changing relative date values into\r\nabsolute ISO\r\nstrings](https://github.com/elastic/kibana/pull/145468/files#diff-48912058ac736ca8aece834bb50369cc5589b94b9c8b2b3e418e9d7690241525).\r\nThis is because we are making extensive use of Exploratory View\r\nEmbeddables, which do not have any kind of refresh mechanism exposed.\r\nThe simplest way to get these to refresh when our `lastRefresh` field\r\nupdates is to supply the embeddable with absolute values, which\r\ncorrespond directly to the existing `from` and `to` fields we're already\r\nusing.\r\n\r\n#### Existing hook updates\r\n\r\nI have tried to avoid manipulating the existing behavior of our fetch\r\nhooks, but there were a few cases where I added optional parameters to\r\nthem to support refresh functionality. It's worth extra attention to\r\nmake sure we're not adding something that we should avoid for these\r\nhooks.\r\n\r\n### Testing this PR\r\n\r\nThe best way to test this PR is to configure a monitor and open the\r\ndetail pages for `Overview`, `History`, and `Errors`. Let your monitor\r\nrun for some time and look at all the visualizations, while avoiding a\r\nhard refresh. If you run this patch from source, you can also modify the\r\n[interval](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR39)\r\nfrom `30s` to some smaller value if you want to make sure things are\r\nupdating where they should more easily.","sha":"06b7596810a285868db58c9040da868ff8ab6e4d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":145468,"url":"https://github.com/elastic/kibana/pull/145468","mergeCommit":{"message":"[Synthetics] Update monitor detail data on refresh (#145468)\n\n## Summary\r\n\r\nResolves #143662.\r\n\r\nResolves #144367.\r\n\r\nThis patch will add refresh capabilities to the monitor detail page and\r\nits child views. Today, the page needs to be hard-refreshed in order for\r\nthis to work.\r\n\r\n### Arch changes\r\n\r\n#### App-wide refresh interval\r\n\r\nTo simplify how auto-refreshing works, I have\r\n[extracted](https://github.com/elastic/kibana/pull/145468/files#diff-09f3a6de5b54c7d3933df933d83e963f6ff6a5c18a3d83238bd658623595fe35L47)\r\nthe existing `interval` logic from the Overview page and put it into the\r\n[`RefreshContext`](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR36)\r\nitself. I am not overly fond of this solution, so if someone has a\r\nbetter suggestion for how to handle this, I am open to recommendations.\r\n\r\nThis refresh context also ties into the date picker components we use\r\nfor some of these pages, so everything should continue to work\r\nseamlessly, but there's going to be a conflicting auto-refresh between\r\ndate pickers and the internal context value itself. It might be\r\nworthwhile for us to discuss this in a tech sync and have a dedicated\r\nenhancement.\r\n\r\n#### New absolute date formatting hook\r\n\r\nI've introduced a [new hook for changing relative date values into\r\nabsolute ISO\r\nstrings](https://github.com/elastic/kibana/pull/145468/files#diff-48912058ac736ca8aece834bb50369cc5589b94b9c8b2b3e418e9d7690241525).\r\nThis is because we are making extensive use of Exploratory View\r\nEmbeddables, which do not have any kind of refresh mechanism exposed.\r\nThe simplest way to get these to refresh when our `lastRefresh` field\r\nupdates is to supply the embeddable with absolute values, which\r\ncorrespond directly to the existing `from` and `to` fields we're already\r\nusing.\r\n\r\n#### Existing hook updates\r\n\r\nI have tried to avoid manipulating the existing behavior of our fetch\r\nhooks, but there were a few cases where I added optional parameters to\r\nthem to support refresh functionality. It's worth extra attention to\r\nmake sure we're not adding something that we should avoid for these\r\nhooks.\r\n\r\n### Testing this PR\r\n\r\nThe best way to test this PR is to configure a monitor and open the\r\ndetail pages for `Overview`, `History`, and `Errors`. Let your monitor\r\nrun for some time and look at all the visualizations, while avoiding a\r\nhard refresh. If you run this patch from source, you can also modify the\r\n[interval](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR39)\r\nfrom `30s` to some smaller value if you want to make sure things are\r\nupdating where they should more easily.","sha":"06b7596810a285868db58c9040da868ff8ab6e4d"}},"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/145468","number":145468,"mergeCommit":{"message":"[Synthetics] Update monitor detail data on refresh (#145468)\n\n## Summary\r\n\r\nResolves #143662.\r\n\r\nResolves #144367.\r\n\r\nThis patch will add refresh capabilities to the monitor detail page and\r\nits child views. Today, the page needs to be hard-refreshed in order for\r\nthis to work.\r\n\r\n### Arch changes\r\n\r\n#### App-wide refresh interval\r\n\r\nTo simplify how auto-refreshing works, I have\r\n[extracted](https://github.com/elastic/kibana/pull/145468/files#diff-09f3a6de5b54c7d3933df933d83e963f6ff6a5c18a3d83238bd658623595fe35L47)\r\nthe existing `interval` logic from the Overview page and put it into the\r\n[`RefreshContext`](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR36)\r\nitself. I am not overly fond of this solution, so if someone has a\r\nbetter suggestion for how to handle this, I am open to recommendations.\r\n\r\nThis refresh context also ties into the date picker components we use\r\nfor some of these pages, so everything should continue to work\r\nseamlessly, but there's going to be a conflicting auto-refresh between\r\ndate pickers and the internal context value itself. It might be\r\nworthwhile for us to discuss this in a tech sync and have a dedicated\r\nenhancement.\r\n\r\n#### New absolute date formatting hook\r\n\r\nI've introduced a [new hook for changing relative date values into\r\nabsolute ISO\r\nstrings](https://github.com/elastic/kibana/pull/145468/files#diff-48912058ac736ca8aece834bb50369cc5589b94b9c8b2b3e418e9d7690241525).\r\nThis is because we are making extensive use of Exploratory View\r\nEmbeddables, which do not have any kind of refresh mechanism exposed.\r\nThe simplest way to get these to refresh when our `lastRefresh` field\r\nupdates is to supply the embeddable with absolute values, which\r\ncorrespond directly to the existing `from` and `to` fields we're already\r\nusing.\r\n\r\n#### Existing hook updates\r\n\r\nI have tried to avoid manipulating the existing behavior of our fetch\r\nhooks, but there were a few cases where I added optional parameters to\r\nthem to support refresh functionality. It's worth extra attention to\r\nmake sure we're not adding something that we should avoid for these\r\nhooks.\r\n\r\n### Testing this PR\r\n\r\nThe best way to test this PR is to configure a monitor and open the\r\ndetail pages for `Overview`, `History`, and `Errors`. Let your monitor\r\nrun for some time and look at all the visualizations, while avoiding a\r\nhard refresh. If you run this patch from source, you can also modify the\r\n[interval](https://github.com/elastic/kibana/pull/145468/files#diff-660f9a1ed6f641662eff6682448bac7d1b167b4ea518ddc43634192b2959be1fR39)\r\nfrom `30s` to some smaller value if you want to make sure things are\r\nupdating where they should more easily.","sha":"06b7596810a285868db58c9040da868ff8ab6e4d"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
|
Kibana Machine
|
b7d1fd7cda
|
[8.6] [ML] Functional tests - stabilize index data visualizer tests (#146285) (#146307)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Functional tests - stabilize index data visualizer tests (#146285)](https://github.com/elastic/kibana/pull/146285) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T15:41:43Z","message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.6.0","v8.7.0"],"number":146285,"url":"https://github.com/elastic/kibana/pull/146285","mergeCommit":{"message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e"}},"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/146285","number":146285,"mergeCommit":{"message":"[ML] Functional tests - stabilize index data visualizer tests (#146285)\n\nThis PR stabilizes the index data visualizer tests.","sha":"40a424b5ea5b0e36b9a74830355e9cfc30964f7e"}}]}] BACKPORT--> Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co> |
||
|
Kibana Machine
|
ab4cecc503
|
[8.6] [ML] Functional tests - stabilize notifications tests (#146280) (#146294)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Functional tests - stabilize notifications tests (#146280)](https://github.com/elastic/kibana/pull/146280) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T14:16:34Z","message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.6.0","v8.7.0"],"number":146280,"url":"https://github.com/elastic/kibana/pull/146280","mergeCommit":{"message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28"}},"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/146280","number":146280,"mergeCommit":{"message":"[ML] Functional tests - stabilize notifications tests (#146280)\n\nThis PR stabilizes the functional UI tests for the ML notifications page.","sha":"820cffddb9067dc820e2c0c98ca50466bcdf1f28"}}]}] BACKPORT--> Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co> |
||
|
Kibana Machine
|
08e61997d5
|
[8.6] [ML] Fix polling for notifications after leaving the ML app (#146203) (#146292)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix polling for notifications after leaving the ML app (#146203)](https://github.com/elastic/kibana/pull/146203) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T14:08:33Z","message":"[ML] Fix polling for notifications after leaving the ML app (#146203)\n\n## Summary\r\n\r\nFixes notifications count polling on app leave. The issue was with the\r\n`useMount` hook that doesn't support a callback execution on unmount.\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":"93c594aa56ceda86d39f5ad9657d2ba45ddb138f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Team:ML","v8.6.0","v8.7.0"],"number":146203,"url":"https://github.com/elastic/kibana/pull/146203","mergeCommit":{"message":"[ML] Fix polling for notifications after leaving the ML app (#146203)\n\n## Summary\r\n\r\nFixes notifications count polling on app leave. The issue was with the\r\n`useMount` hook that doesn't support a callback execution on unmount.\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":"93c594aa56ceda86d39f5ad9657d2ba45ddb138f"}},"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/146203","number":146203,"mergeCommit":{"message":"[ML] Fix polling for notifications after leaving the ML app (#146203)\n\n## Summary\r\n\r\nFixes notifications count polling on app leave. The issue was with the\r\n`useMount` hook that doesn't support a callback execution on unmount.\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":"93c594aa56ceda86d39f5ad9657d2ba45ddb138f"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
9f0e2d6874
|
[8.6] [Enterprise Search] Allow empty config values to be saved (#146278) (#146287)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Allow empty config values to be saved (#146278)](https://github.com/elastic/kibana/pull/146278) <!--- 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-11-24T12:58:39Z","message":"[Enterprise Search] Allow empty config values to be saved (#146278)\n\nThis allows null values for connector configuration values, which was\r\ninitially breaking some configuration setting.","sha":"c9eebf262c65d6c3104592b6ea0bb61f1d6e0d1f","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":146278,"url":"https://github.com/elastic/kibana/pull/146278","mergeCommit":{"message":"[Enterprise Search] Allow empty config values to be saved (#146278)\n\nThis allows null values for connector configuration values, which was\r\ninitially breaking some configuration setting.","sha":"c9eebf262c65d6c3104592b6ea0bb61f1d6e0d1f"}},"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/146278","number":146278,"mergeCommit":{"message":"[Enterprise Search] Allow empty config values to be saved (#146278)\n\nThis allows null values for connector configuration values, which was\r\ninitially breaking some configuration setting.","sha":"c9eebf262c65d6c3104592b6ea0bb61f1d6e0d1f"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
d4567dc2ea
|
[8.6] [Enterprise Search] Improve connector status signaling (#146194) (#146269)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search] Improve connector status signaling (#146194)](https://github.com/elastic/kibana/pull/146194) <!--- 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-11-24T10:18:09Z","message":"[Enterprise Search] Improve connector status signaling (#146194)\n\nThis improves the connector status signals by:\r\n- Showing the last sync's error if available and the connector doesn't\r\nhave its own error\r\n- Showing errors in the config page\r\n- Showing a success message for connected native connectors\r\n\r\nIt also sets the configuration to edit mode if it needs configuration\r\nchanges.","sha":"04e3772104a128cab26ad0e9688fa26b2b6c39ab","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":146194,"url":"https://github.com/elastic/kibana/pull/146194","mergeCommit":{"message":"[Enterprise Search] Improve connector status signaling (#146194)\n\nThis improves the connector status signals by:\r\n- Showing the last sync's error if available and the connector doesn't\r\nhave its own error\r\n- Showing errors in the config page\r\n- Showing a success message for connected native connectors\r\n\r\nIt also sets the configuration to edit mode if it needs configuration\r\nchanges.","sha":"04e3772104a128cab26ad0e9688fa26b2b6c39ab"}},"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/146194","number":146194,"mergeCommit":{"message":"[Enterprise Search] Improve connector status signaling (#146194)\n\nThis improves the connector status signals by:\r\n- Showing the last sync's error if available and the connector doesn't\r\nhave its own error\r\n- Showing errors in the config page\r\n- Showing a success message for connected native connectors\r\n\r\nIt also sets the configuration to edit mode if it needs configuration\r\nchanges.","sha":"04e3772104a128cab26ad0e9688fa26b2b6c39ab"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
d9f0ccc247
|
[8.6] [ML] Explain Log Rate Spikes: Additional API integration tests (#146113) (#146263)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)](https://github.com/elastic/kibana/pull/146113) <!--- 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-11-24T09:41:11Z","message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":146113,"url":"https://github.com/elastic/kibana/pull/146113","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646"}},"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/146113","number":146113,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Additional API integration tests (#146113)\n\nAdditional API integration tests.\r\n\r\n- The test data was moved to its own file `test_data.ts` and types for\r\nits structure defined in `types.ts` to be in line with the structure\r\nused for functional tests.\r\n- The file that runs the test was extended so it can run an array of\r\ntest data definitions.\r\n- The datasets used in the funcional tests (`ecommerce` with some\r\nadditional documents added to create a significant spike and the\r\ncomputationally generated spike data set to create distinct groups) were\r\nmoved to a service `ExplainLogRateSpikesDataGenerator` so they can be\r\ngenerated and used across functional and API integration tests.\r\n- The computationally generated spike data set\r\n`artificial_logs_with_spike` is now also used for API integration tests.\r\n- Additional assertions have been added to check the grouping result.\r\n`ecommerce` does not return any groups whereas\r\n`artificial_logs_with_spike` does.\r\n- The functional tests code is now consolidated and one test file is\r\nable to run multiple test data definitions too.","sha":"5481f07f79e6923a982ae5ce42af051630b10646"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
