mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
27354 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
5d65f4e40b
|
[8.6] Ent search 3392 fix canceling syncs (#145885) (#145998)
# Backport
This will backport the following commits from `main` to `8.6`:
- Ent search 3392 fix canceling syncs (#145885) (
|
||
|
Kibana Machine
|
6f0a5b37bb
|
[8.6] [ML] Fixing missing multi label checkbox and basic input validation (#145357) (#145735)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fixing missing multi label checkbox and basic input validation (#145357)](https://github.com/elastic/kibana/pull/145357) <!--- 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-18T13:58:32Z","message":"[ML] Fixing missing multi label checkbox and basic input validation (#145357)\n\nThe `multi_label` flag for question answering models should be user\r\nconfigurable.\r\nAdds a multi label switch to the zero shot classification testing UI.\r\n\r\n\r\n\r\n\r\nAdds basic input validation to ensure the Test button is not enabled\r\nunless all required inputs are filled in.\r\nFor `fill_mask` that includes every string needing contain the `[MASK]`\r\nkeyword.\r\n\r\nAlso fixes the `Test model` menu item to ensure it is disabled if\r\n`PyTorch` models not started.\r\n\r\n\r\n\r\nAlso fixes generated pipeline to ensure it's always up to date with the\r\nuser's selections.","sha":"a929099c9e80c9bd31bbbc34b3bf3450e016bcbc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","release_note:skip","Feature:3rd Party Models","v8.6.0","v8.7.0"],"number":145357,"url":"https://github.com/elastic/kibana/pull/145357","mergeCommit":{"message":"[ML] Fixing missing multi label checkbox and basic input validation (#145357)\n\nThe `multi_label` flag for question answering models should be user\r\nconfigurable.\r\nAdds a multi label switch to the zero shot classification testing UI.\r\n\r\n\r\n\r\n\r\nAdds basic input validation to ensure the Test button is not enabled\r\nunless all required inputs are filled in.\r\nFor `fill_mask` that includes every string needing contain the `[MASK]`\r\nkeyword.\r\n\r\nAlso fixes the `Test model` menu item to ensure it is disabled if\r\n`PyTorch` models not started.\r\n\r\n\r\n\r\nAlso fixes generated pipeline to ensure it's always up to date with the\r\nuser's selections.","sha":"a929099c9e80c9bd31bbbc34b3bf3450e016bcbc"}},"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/145357","number":145357,"mergeCommit":{"message":"[ML] Fixing missing multi label checkbox and basic input validation (#145357)\n\nThe `multi_label` flag for question answering models should be user\r\nconfigurable.\r\nAdds a multi label switch to the zero shot classification testing UI.\r\n\r\n\r\n\r\n\r\nAdds basic input validation to ensure the Test button is not enabled\r\nunless all required inputs are filled in.\r\nFor `fill_mask` that includes every string needing contain the `[MASK]`\r\nkeyword.\r\n\r\nAlso fixes the `Test model` menu item to ensure it is disabled if\r\n`PyTorch` models not started.\r\n\r\n\r\n\r\nAlso fixes generated pipeline to ensure it's always up to date with the\r\nuser's selections.","sha":"a929099c9e80c9bd31bbbc34b3bf3450e016bcbc"}}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
Kibana Machine
|
52133e6c41
|
[8.6] [Stack Monitoring] api tests for cluster and elasticsearch (#145138) (#145985)
# Backport This will backport the following commits from `main` to `8.6`: - [[Stack Monitoring] api tests for cluster and elasticsearch (#145138)](https://github.com/elastic/kibana/pull/145138) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Lacabane","email":"kevin.lacabane@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T13:02:50Z","message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","Feature:Stack Monitoring","v8.6.0","v8.7.0"],"number":145138,"url":"https://github.com/elastic/kibana/pull/145138","mergeCommit":{"message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296"}},"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/145138","number":145138,"mergeCommit":{"message":"[Stack Monitoring] api tests for cluster and elasticsearch (#145138)\n\n### Summary\r\nPart of https://github.com/elastic/kibana/issues/119658\r\n\r\nAdd api integration tests for cluster and elasticsearch routes to\r\nvalidate behavior when reading data ingested by elastic-agent.\r\n\r\nWe currently have a testing suite for legacy and another one for\r\nmetricbeat. Since metricbeat and agent documents only differ in their\r\nmetadata, for example agent will populate a `data_stream.*` property to\r\nidentify the document types while metricbeat uses `metricset.*`, the\r\ntests assertion validating _business_ data should pass regardless of the\r\ndocuments source. With this in mind the metricbeat tests were updated to\r\nrun the tests twice, one time with metricbeat data and a second time\r\nwith package data.\r\n\r\nTo generate the archives the `metrics-*` mappings were extracted with\r\nesArchiver from an elasticsearch with the package installed, and the\r\ndocuments were transformed from the metricbeat documents with [this\r\nscript](https://gist.github.com/klacabane/654497ff86053c60af6df15fa6f6f657).\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"5cf0d0f24817db4b36501c6c06f6cfb4cd61c296"}}]}] BACKPORT--> Co-authored-by: Kevin Lacabane <kevin.lacabane@elastic.co> |
||
|
Kibana Machine
|
93d7303dfd
|
[8.6] [Synthetics] Monitor editing and deletion - prefer config_id for editing and deleting monitor (#145879) (#145981)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Monitor editing and deletion - prefer config_id for editing and deleting monitor (#145879)](https://github.com/elastic/kibana/pull/145879) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T12:51:27Z","message":"[Synthetics] Monitor editing and deletion - prefer config_id for editing and deleting monitor (#145879)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/145780\r\nResolves https://github.com/elastic/kibana/issues/145881\r\n\r\nStandardized the configuration used for monitor editing and deleting, so\r\nthat both project monitors and UI monitors can be deleted successfully.\r\n\r\nAlso updates content for the delete monitor modal for project monitors\r\n\r\n<img width=\"789\" alt=\"Screen Shot 2022-11-21 at 6 14 08 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203183292-ace95578-baea-400c-b48d-71015d9a5bd3.png\">\r\n\r\n### Testing\r\n1. Create at least one project monitor and one UI monitor\r\n2. Navigate to the Synthetics App monitors page\r\n3. Click edit for both monitors. Ensure the edit page is loaded\r\n4. Delete both monitors. Ensure both monitors are able to be deleted\r\nsuccessfully.","sha":"1f9cd757920008b5dbe09c1a4295611bca0b6190","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145879,"url":"https://github.com/elastic/kibana/pull/145879","mergeCommit":{"message":"[Synthetics] Monitor editing and deletion - prefer config_id for editing and deleting monitor (#145879)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/145780\r\nResolves https://github.com/elastic/kibana/issues/145881\r\n\r\nStandardized the configuration used for monitor editing and deleting, so\r\nthat both project monitors and UI monitors can be deleted successfully.\r\n\r\nAlso updates content for the delete monitor modal for project monitors\r\n\r\n<img width=\"789\" alt=\"Screen Shot 2022-11-21 at 6 14 08 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203183292-ace95578-baea-400c-b48d-71015d9a5bd3.png\">\r\n\r\n### Testing\r\n1. Create at least one project monitor and one UI monitor\r\n2. Navigate to the Synthetics App monitors page\r\n3. Click edit for both monitors. Ensure the edit page is loaded\r\n4. Delete both monitors. Ensure both monitors are able to be deleted\r\nsuccessfully.","sha":"1f9cd757920008b5dbe09c1a4295611bca0b6190"}},"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/145879","number":145879,"mergeCommit":{"message":"[Synthetics] Monitor editing and deletion - prefer config_id for editing and deleting monitor (#145879)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/145780\r\nResolves https://github.com/elastic/kibana/issues/145881\r\n\r\nStandardized the configuration used for monitor editing and deleting, so\r\nthat both project monitors and UI monitors can be deleted successfully.\r\n\r\nAlso updates content for the delete monitor modal for project monitors\r\n\r\n<img width=\"789\" alt=\"Screen Shot 2022-11-21 at 6 14 08 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203183292-ace95578-baea-400c-b48d-71015d9a5bd3.png\">\r\n\r\n### Testing\r\n1. Create at least one project monitor and one UI monitor\r\n2. Navigate to the Synthetics App monitors page\r\n3. Click edit for both monitors. Ensure the edit page is loaded\r\n4. Delete both monitors. Ensure both monitors are able to be deleted\r\nsuccessfully.","sha":"1f9cd757920008b5dbe09c1a4295611bca0b6190"}}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
|
Kibana Machine
|
6dfa1dd1a4
|
[8.6] [ML] Fix anomaly detection jobs list not refreshing (#145757) (#145971)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix anomaly detection jobs list not refreshing (#145757)](https://github.com/elastic/kibana/pull/145757) <!--- 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-22T10:53:18Z","message":"[ML] Fix anomaly detection jobs list not refreshing (#145757)\n\nFixes https://github.com/elastic/kibana/issues/144529\r\n\r\nRemoves the `blockRefresh` prop which is no longer needed since the page\r\nrefresh controls trigger a whole re-render of the `JobsPage` component.","sha":"c5208695a9fc7c88de781500179864141ca99098","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Anomaly Detection","v8.6.0","v8.7.0"],"number":145757,"url":"https://github.com/elastic/kibana/pull/145757","mergeCommit":{"message":"[ML] Fix anomaly detection jobs list not refreshing (#145757)\n\nFixes https://github.com/elastic/kibana/issues/144529\r\n\r\nRemoves the `blockRefresh` prop which is no longer needed since the page\r\nrefresh controls trigger a whole re-render of the `JobsPage` component.","sha":"c5208695a9fc7c88de781500179864141ca99098"}},"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/145757","number":145757,"mergeCommit":{"message":"[ML] Fix anomaly detection jobs list not refreshing (#145757)\n\nFixes https://github.com/elastic/kibana/issues/144529\r\n\r\nRemoves the `blockRefresh` prop which is no longer needed since the page\r\nrefresh controls trigger a whole re-render of the `JobsPage` component.","sha":"c5208695a9fc7c88de781500179864141ca99098"}}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
Cee
|
b52b34c2ff
|
[EUI] Fix temporary selectable horizontal card workaround (#145932)
## Summary
closes https://github.com/elastic/kibana/issues/145508
This workaround was added in
|
||
Wafaa Nasr
|
acd9091616
|
[8.6] [Security Solution][List Details Page]: Fix exception list details page route and adding breadcrumb (#145605) (#145960)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][List Details Page]: Fix `exception list details` page route and adding breadcrumb (#145605)](https://github.com/elastic/kibana/pull/145605) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T15:38:33Z","message":"[Security Solution][List Details Page]: Fix `exception list details` page route and adding breadcrumb (#145605)\n\n## Summary\r\n\r\nAs per this\r\n[discussion](https://github.com/elastic/kibana/pull/145605#pullrequestreview-1186305242)\r\n\r\n- Remove the `Exception-List-details` definition from the [management\r\nlinks]( |
||
|
Kibana Machine
|
db96bd0122
|
[8.6] Fix Notable Anomalies context visible under collapse (#145726) (#145958)
# Backport This will backport the following commits from `main` to `8.6`: - [Fix Notable Anomalies context visible under collapse (#145726)](https://github.com/elastic/kibana/pull/145726) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T08:38:02Z","message":"Fix Notable Anomalies context visible under collapse (#145726)\n\nissue: https://github.com/elastic/kibana/issues/145534\r\n\r\n## Summary\r\n\r\nHide warning messages when the card is collapsed\r\n<img\r\nsrc=\"https://user-images.githubusercontent.com/59917825/202425479-d3cdc27d-3b72-4bc2-9bb5-9e09a35457fe.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab0cede59c6abe27eaf6c6d51b07232e2723b5e9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat Hunting","Team: SecuritySolution","Team:Threat Hunting:Explore","v8.6.0","v8.7.0"],"number":145726,"url":"https://github.com/elastic/kibana/pull/145726","mergeCommit":{"message":"Fix Notable Anomalies context visible under collapse (#145726)\n\nissue: https://github.com/elastic/kibana/issues/145534\r\n\r\n## Summary\r\n\r\nHide warning messages when the card is collapsed\r\n<img\r\nsrc=\"https://user-images.githubusercontent.com/59917825/202425479-d3cdc27d-3b72-4bc2-9bb5-9e09a35457fe.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab0cede59c6abe27eaf6c6d51b07232e2723b5e9"}},"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/145726","number":145726,"mergeCommit":{"message":"Fix Notable Anomalies context visible under collapse (#145726)\n\nissue: https://github.com/elastic/kibana/issues/145534\r\n\r\n## Summary\r\n\r\nHide warning messages when the card is collapsed\r\n<img\r\nsrc=\"https://user-images.githubusercontent.com/59917825/202425479-d3cdc27d-3b72-4bc2-9bb5-9e09a35457fe.png\">\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"ab0cede59c6abe27eaf6c6d51b07232e2723b5e9"}}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
25786e042f
|
[8.6] [Synthetics] step details - test run details - fix breadcrumbs (#145953) (#145956)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] step details - test run details - fix breadcrumbs (#145953)](https://github.com/elastic/kibana/pull/145953) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T07:14:03Z","message":"[Synthetics] step details - test run details - fix breadcrumbs (#145953)\n\nResolves https://github.com/elastic/kibana/issues/145952","sha":"d5a5870273b1ca05c1137d9bea6bea3918f2d4b5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145953,"url":"https://github.com/elastic/kibana/pull/145953","mergeCommit":{"message":"[Synthetics] step details - test run details - fix breadcrumbs (#145953)\n\nResolves https://github.com/elastic/kibana/issues/145952","sha":"d5a5870273b1ca05c1137d9bea6bea3918f2d4b5"}},"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/145953","number":145953,"mergeCommit":{"message":"[Synthetics] step details - test run details - fix breadcrumbs (#145953)\n\nResolves https://github.com/elastic/kibana/issues/145952","sha":"d5a5870273b1ca05c1137d9bea6bea3918f2d4b5"}}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
|
Kibana Machine
|
17e2fecfa2
|
[8.6] [ML] Api Integration tests: adds tests for 'api/ml/results/datafeed_results_chart' (#145619) (#145933)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Api Integration tests: adds tests for 'api/ml/results/datafeed_results_chart' (#145619)](https://github.com/elastic/kibana/pull/145619) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Melissa Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T20:19:07Z","message":"[ML] Api Integration tests: adds tests for 'api/ml/results/datafeed_results_chart' (#145619)\n\n## Summary\r\n\r\nRelated meta issue https://github.com/elastic/kibana/issues/142456\r\n\r\nThis PR adds api integration tests for the\r\n`api/ml/results/datafeed_results_chart` endpoint\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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":"a74bfee93f174e9cde586c27746053f71d899b55","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","test-api-integration","v8.6.0","v8.7.0"],"number":145619,"url":"https://github.com/elastic/kibana/pull/145619","mergeCommit":{"message":"[ML] Api Integration tests: adds tests for 'api/ml/results/datafeed_results_chart' (#145619)\n\n## Summary\r\n\r\nRelated meta issue https://github.com/elastic/kibana/issues/142456\r\n\r\nThis PR adds api integration tests for the\r\n`api/ml/results/datafeed_results_chart` endpoint\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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":"a74bfee93f174e9cde586c27746053f71d899b55"}},"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/145619","number":145619,"mergeCommit":{"message":"[ML] Api Integration tests: adds tests for 'api/ml/results/datafeed_results_chart' (#145619)\n\n## Summary\r\n\r\nRelated meta issue https://github.com/elastic/kibana/issues/142456\r\n\r\nThis PR adds api integration tests for the\r\n`api/ml/results/datafeed_results_chart` endpoint\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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":"a74bfee93f174e9cde586c27746053f71d899b55"}}]}] BACKPORT--> Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co> |
||
|
Kibana Machine
|
33fe536a4e
|
[8.6] [RAM] need to return the async id to avoid new request (#145731) (#145930)
# Backport This will backport the following commits from `main` to `8.6`: - [[RAM] need to return the async id to avoid new request (#145731)](https://github.com/elastic/kibana/pull/145731) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Xavier Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T20:02:06Z","message":"[RAM] need to return the async id to avoid new request (#145731)\n\n## Summary\r\n\r\nFix: https://github.com/elastic/kibana/issues/129219 &\r\nhttps://github.com/elastic/kibana/issues/144619\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58a374799b41108929527a239bae68b3ac7cc346","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:ResponseOps","ci:cloud-deploy","ci:cloud-redeploy","v8.6.0","v8.7.0"],"number":145731,"url":"https://github.com/elastic/kibana/pull/145731","mergeCommit":{"message":"[RAM] need to return the async id to avoid new request (#145731)\n\n## Summary\r\n\r\nFix: https://github.com/elastic/kibana/issues/129219 &\r\nhttps://github.com/elastic/kibana/issues/144619\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58a374799b41108929527a239bae68b3ac7cc346"}},"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/145731","number":145731,"mergeCommit":{"message":"[RAM] need to return the async id to avoid new request (#145731)\n\n## Summary\r\n\r\nFix: https://github.com/elastic/kibana/issues/129219 &\r\nhttps://github.com/elastic/kibana/issues/144619\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"58a374799b41108929527a239bae68b3ac7cc346"}}]}] BACKPORT--> Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co> |
||
|
Kibana Machine
|
c0391abcdd
|
[8.6] [Synthetics] Update status count viz on monitor upsert (#145898) (#145920)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Update status count viz on monitor upsert (#145898)](https://github.com/elastic/kibana/pull/145898) <!--- 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-21T19:24:31Z","message":"[Synthetics] Update status count viz on monitor upsert (#145898)\n\n## Summary\r\n\r\nResolves #145845.\r\n\r\nThis resolves the issue of count not updating when a monitor is\r\nenabled/disabled by listening for the `success` version of the saved\r\nobject upsert action. This way, any time the frontend verifies that a\r\nmonitor has had its state changed, we'll update the status count as a\r\nsecondary effect.\r\n\r\nThis could introduce some risk if we start using that action in some\r\nsort of batched way in the future, but at present it seems to only be\r\ndriven by direct 1:1 user input to the Actions Popover component that\r\nwe've reused in the detail flyout and on the overview cards.\r\n\r\n## Testing this PR\r\n\r\nYou can simply create some managed monitors and change their state from\r\nthe Overview page.\r\n\r\n\r\n","sha":"bf7c3bc502b4fce11db2df90f1ed58a2c65ee5a1","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":145898,"url":"https://github.com/elastic/kibana/pull/145898","mergeCommit":{"message":"[Synthetics] Update status count viz on monitor upsert (#145898)\n\n## Summary\r\n\r\nResolves #145845.\r\n\r\nThis resolves the issue of count not updating when a monitor is\r\nenabled/disabled by listening for the `success` version of the saved\r\nobject upsert action. This way, any time the frontend verifies that a\r\nmonitor has had its state changed, we'll update the status count as a\r\nsecondary effect.\r\n\r\nThis could introduce some risk if we start using that action in some\r\nsort of batched way in the future, but at present it seems to only be\r\ndriven by direct 1:1 user input to the Actions Popover component that\r\nwe've reused in the detail flyout and on the overview cards.\r\n\r\n## Testing this PR\r\n\r\nYou can simply create some managed monitors and change their state from\r\nthe Overview page.\r\n\r\n\r\n","sha":"bf7c3bc502b4fce11db2df90f1ed58a2c65ee5a1"}},"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/145898","number":145898,"mergeCommit":{"message":"[Synthetics] Update status count viz on monitor upsert (#145898)\n\n## Summary\r\n\r\nResolves #145845.\r\n\r\nThis resolves the issue of count not updating when a monitor is\r\nenabled/disabled by listening for the `success` version of the saved\r\nobject upsert action. This way, any time the frontend verifies that a\r\nmonitor has had its state changed, we'll update the status count as a\r\nsecondary effect.\r\n\r\nThis could introduce some risk if we start using that action in some\r\nsort of batched way in the future, but at present it seems to only be\r\ndriven by direct 1:1 user input to the Actions Popover component that\r\nwe've reused in the detail flyout and on the overview cards.\r\n\r\n## Testing this PR\r\n\r\nYou can simply create some managed monitors and change their state from\r\nthe Overview page.\r\n\r\n\r\n","sha":"bf7c3bc502b4fce11db2df90f1ed58a2c65ee5a1"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
|
Kibana Machine
|
210cde75fe
|
[8.6] Endpoint fixes (#145834) (#145901)
# Backport This will backport the following commits from `main` to `8.6`: - [Endpoint fixes (#145834)](https://github.com/elastic/kibana/pull/145834) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T17:37:35Z","message":"Endpoint fixes (#145834)\n\n## Summary\r\n\r\nAddress: \r\n[145806](https://github.com/elastic/kibana/issues/145806), \r\n[145535](https://github.com/elastic/kibana/issues/145535), \r\n[145541](https://github.com/elastic/kibana/issues/145541), \r\n[145676](https://github.com/elastic/kibana/issues/145676), \r\n[145673](https://github.com/elastic/kibana/issues/145673), \r\n\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/203031829-bcbd5db2-e9af-4ef6-ad8d-0016c33b785b.mov\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f24e75d3920d71806d588d281d433737012373c9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Solution Platform","backport:prev-minor","v8.7.0"],"number":145834,"url":"https://github.com/elastic/kibana/pull/145834","mergeCommit":{"message":"Endpoint fixes (#145834)\n\n## Summary\r\n\r\nAddress: \r\n[145806](https://github.com/elastic/kibana/issues/145806), \r\n[145535](https://github.com/elastic/kibana/issues/145535), \r\n[145541](https://github.com/elastic/kibana/issues/145541), \r\n[145676](https://github.com/elastic/kibana/issues/145676), \r\n[145673](https://github.com/elastic/kibana/issues/145673), \r\n\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/203031829-bcbd5db2-e9af-4ef6-ad8d-0016c33b785b.mov\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f24e75d3920d71806d588d281d433737012373c9"}},"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/145834","number":145834,"mergeCommit":{"message":"Endpoint fixes (#145834)\n\n## Summary\r\n\r\nAddress: \r\n[145806](https://github.com/elastic/kibana/issues/145806), \r\n[145535](https://github.com/elastic/kibana/issues/145535), \r\n[145541](https://github.com/elastic/kibana/issues/145541), \r\n[145676](https://github.com/elastic/kibana/issues/145676), \r\n[145673](https://github.com/elastic/kibana/issues/145673), \r\n\r\n\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/203031829-bcbd5db2-e9af-4ef6-ad8d-0016c33b785b.mov\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f24e75d3920d71806d588d281d433737012373c9"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
Tiago Costa
|
8eaa22706c
|
skip flaky suite (#145204) | ||
|
Kibana Machine
|
ba53e78eb0
|
[8.6] [APM] Add title in apm settings callout (#145857) (#145915)
# Backport This will backport the following commits from `main` to `8.6`: - [[APM] Add title in apm settings callout (#145857)](https://github.com/elastic/kibana/pull/145857) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Katerina Patticha","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T18:40:38Z","message":"[APM] Add title in apm settings callout (#145857)\n\n## Summary\r\ncloses |
||
|
Kibana Machine
|
50e50f0737
|
[8.6] unload from remote (#145641) (#145914)
# Backport This will backport the following commits from `main` to `8.6`: - [unload from remote (#145641)](https://github.com/elastic/kibana/pull/145641) <!--- 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-21T18:39:39Z","message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","release_note:skip","backport:prev-minor","v8.7.0"],"number":145641,"url":"https://github.com/elastic/kibana/pull/145641","mergeCommit":{"message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4"}},"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/145641","number":145641,"mergeCommit":{"message":"unload from remote (#145641)\n\n## Summary\r\n\r\nIt appears that the before method sets esNode to either esArchiver or\r\nremoteEsArchiver, but in the after method it uses esArchiver. This\r\ncauses the unload to fail on the CCS case.","sha":"393b37811dbaa46a4a1ca6fa22d8941e580854c4"}}]}] BACKPORT--> Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co> |
||
|
Kibana Machine
|
6cd73aa31b
|
[8.6] [Fleet] Disable agent policy containing managed package policies (#145727) (#145908)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Disable agent policy containing managed package policies (#145727)](https://github.com/elastic/kibana/pull/145727) <!--- 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-21T18:05:19Z","message":"[Fleet] Disable agent policy containing managed package policies (#145727)\n\nFixes https://github.com/elastic/kibana/issues/142863","sha":"daf385c05253dc0be799d2b2539a2d6051181791","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":145727,"url":"https://github.com/elastic/kibana/pull/145727","mergeCommit":{"message":"[Fleet] Disable agent policy containing managed package policies (#145727)\n\nFixes https://github.com/elastic/kibana/issues/142863","sha":"daf385c05253dc0be799d2b2539a2d6051181791"}},"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/145727","number":145727,"mergeCommit":{"message":"[Fleet] Disable agent policy containing managed package policies (#145727)\n\nFixes https://github.com/elastic/kibana/issues/142863","sha":"daf385c05253dc0be799d2b2539a2d6051181791"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
Kibana Machine
|
a62d5d9089
|
[8.6] [Synthetics] Monitor details page fix empty state errors (#145588) (#145907)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Monitor details page fix empty state errors (#145588)](https://github.com/elastic/kibana/pull/145588) <!--- 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-21T18:04:47Z","message":"[Synthetics] Monitor details page fix empty state errors (#145588)\n\nFixes https://github.com/elastic/kibana/issues/144365","sha":"beff4b756bb3b6f188c7ece527fa813bcecb410f","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":145588,"url":"https://github.com/elastic/kibana/pull/145588","mergeCommit":{"message":"[Synthetics] Monitor details page fix empty state errors (#145588)\n\nFixes https://github.com/elastic/kibana/issues/144365","sha":"beff4b756bb3b6f188c7ece527fa813bcecb410f"}},"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/145588","number":145588,"mergeCommit":{"message":"[Synthetics] Monitor details page fix empty state errors (#145588)\n\nFixes https://github.com/elastic/kibana/issues/144365","sha":"beff4b756bb3b6f188c7ece527fa813bcecb410f"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
Kibana Machine
|
d6fb3e08da
|
[8.6] [ML] Fix a redirect loop (#145738) (#145904)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix a redirect loop (#145738)](https://github.com/elastic/kibana/pull/145738) <!--- 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-21T17:56:33Z","message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.6.0","v8.7.0"],"number":145738,"url":"https://github.com/elastic/kibana/pull/145738","mergeCommit":{"message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099"}},"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/145738","number":145738,"mergeCommit":{"message":"[ML] Fix a redirect loop (#145738)","sha":"4d1495440842106f389dd85c81eb2cda1617d099"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
22c00575cc
|
[8.6] [Enterprise Search][ML Inference] UX improvements (#145305) (#145902)
# Backport This will backport the following commits from `main` to `8.6`: - [[Enterprise Search][ML Inference] UX improvements (#145305)](https://github.com/elastic/kibana/pull/145305) <!--- 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-21T17:42:56Z","message":"[Enterprise Search][ML Inference] UX improvements (#145305)\n\n## Summary\r\n\r\n- [x] Drop subtext from \"Ingestion error logs\" card\r\n- [x] Update no items copy for Ingestion history table, align with\r\nerrors no items message\r\n- [x] Add to complete name help text \"This will create a pipeline named\r\n{complete name}\"\r\n- [x] Capitalize \"Space\" in \"This model isn't available in the space\"\r\nmessage\r\n- [x] Re-use \"This model isn't available in the space\" message for model\r\nselect display when re-using a pipeline with a redacted model.\r\n- [x] Add right padding to add inference modal back button, going back\r\nfrom review to test it is highlighted and ends at the `k` of `Back`\r\n- [x] Rename \"Destination field\" to \"Target field\" to align with\r\npipelines UI\r\n- [x] Update help text for Target field to call-out first class field\r\nwill be created\r\nSomething like: \"This names the field that holds the commonly searched\r\nvalue and names the subfield used to contain the complete processor\r\nresult. {{Line break}} Learn more (link to docs - to the guide when\r\navailable)\"\r\n- [x] Existing or New select value not retained when leaving configure\r\nstep and going back\r\n- [x] Removed inference history footer as we do not have a good doc to\r\nlink to currently.\r\n\r\n### Screenshots\r\nPipelines Screen\r\n\r\n\r\nAdd Inference Modal\r\n\r\n\r\nAdd inference pipeline modal Back button padding\r\n\r\n","sha":"acb4db605a61cd089c736946ce8fc0048775a1ad","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":145305,"url":"https://github.com/elastic/kibana/pull/145305","mergeCommit":{"message":"[Enterprise Search][ML Inference] UX improvements (#145305)\n\n## Summary\r\n\r\n- [x] Drop subtext from \"Ingestion error logs\" card\r\n- [x] Update no items copy for Ingestion history table, align with\r\nerrors no items message\r\n- [x] Add to complete name help text \"This will create a pipeline named\r\n{complete name}\"\r\n- [x] Capitalize \"Space\" in \"This model isn't available in the space\"\r\nmessage\r\n- [x] Re-use \"This model isn't available in the space\" message for model\r\nselect display when re-using a pipeline with a redacted model.\r\n- [x] Add right padding to add inference modal back button, going back\r\nfrom review to test it is highlighted and ends at the `k` of `Back`\r\n- [x] Rename \"Destination field\" to \"Target field\" to align with\r\npipelines UI\r\n- [x] Update help text for Target field to call-out first class field\r\nwill be created\r\nSomething like: \"This names the field that holds the commonly searched\r\nvalue and names the subfield used to contain the complete processor\r\nresult. {{Line break}} Learn more (link to docs - to the guide when\r\navailable)\"\r\n- [x] Existing or New select value not retained when leaving configure\r\nstep and going back\r\n- [x] Removed inference history footer as we do not have a good doc to\r\nlink to currently.\r\n\r\n### Screenshots\r\nPipelines Screen\r\n\r\n\r\nAdd Inference Modal\r\n\r\n\r\nAdd inference pipeline modal Back button padding\r\n\r\n","sha":"acb4db605a61cd089c736946ce8fc0048775a1ad"}},"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/145305","number":145305,"mergeCommit":{"message":"[Enterprise Search][ML Inference] UX improvements (#145305)\n\n## Summary\r\n\r\n- [x] Drop subtext from \"Ingestion error logs\" card\r\n- [x] Update no items copy for Ingestion history table, align with\r\nerrors no items message\r\n- [x] Add to complete name help text \"This will create a pipeline named\r\n{complete name}\"\r\n- [x] Capitalize \"Space\" in \"This model isn't available in the space\"\r\nmessage\r\n- [x] Re-use \"This model isn't available in the space\" message for model\r\nselect display when re-using a pipeline with a redacted model.\r\n- [x] Add right padding to add inference modal back button, going back\r\nfrom review to test it is highlighted and ends at the `k` of `Back`\r\n- [x] Rename \"Destination field\" to \"Target field\" to align with\r\npipelines UI\r\n- [x] Update help text for Target field to call-out first class field\r\nwill be created\r\nSomething like: \"This names the field that holds the commonly searched\r\nvalue and names the subfield used to contain the complete processor\r\nresult. {{Line break}} Learn more (link to docs - to the guide when\r\navailable)\"\r\n- [x] Existing or New select value not retained when leaving configure\r\nstep and going back\r\n- [x] Removed inference history footer as we do not have a good doc to\r\nlink to currently.\r\n\r\n### Screenshots\r\nPipelines Screen\r\n\r\n\r\nAdd Inference Modal\r\n\r\n\r\nAdd inference pipeline modal Back button padding\r\n\r\n","sha":"acb4db605a61cd089c736946ce8fc0048775a1ad"}}]}] BACKPORT--> Co-authored-by: Rodney Norris <rodney.norris@elastic.co> |
||
|
Kibana Machine
|
e1c4607e48
|
[8.6] [Fleet] Fix fleet server flyout not closing when clicking continue enrolling (#145874) (#145899)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Fix fleet server flyout not closing when clicking continue enrolling (#145874)](https://github.com/elastic/kibana/pull/145874) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-21T17:30:06Z","message":"[Fleet] Fix fleet server flyout not closing when clicking continue enrolling (#145874)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/144965\r\n\r\nSmall bugfix for fleet server flyout. \r\n\r\n- When clicking on \"fleet settings\" link the user was navigated to\r\nsettings but the flyout was staying open\r\n\r\n- Also, After clicking on \"Continue enrolling\", the agent flyout was\r\nopening on top of the fleet server flyout, which then stayed open.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9417bc11c4d0d531b640a15417a3e9d809d18014","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":145874,"url":"https://github.com/elastic/kibana/pull/145874","mergeCommit":{"message":"[Fleet] Fix fleet server flyout not closing when clicking continue enrolling (#145874)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/144965\r\n\r\nSmall bugfix for fleet server flyout. \r\n\r\n- When clicking on \"fleet settings\" link the user was navigated to\r\nsettings but the flyout was staying open\r\n\r\n- Also, After clicking on \"Continue enrolling\", the agent flyout was\r\nopening on top of the fleet server flyout, which then stayed open.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9417bc11c4d0d531b640a15417a3e9d809d18014"}},"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/145874","number":145874,"mergeCommit":{"message":"[Fleet] Fix fleet server flyout not closing when clicking continue enrolling (#145874)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/144965\r\n\r\nSmall bugfix for fleet server flyout. \r\n\r\n- When clicking on \"fleet settings\" link the user was navigated to\r\nsettings but the flyout was staying open\r\n\r\n- Also, After clicking on \"Continue enrolling\", the agent flyout was\r\nopening on top of the fleet server flyout, which then stayed open.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9417bc11c4d0d531b640a15417a3e9d809d18014"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com> |
||
Ashokaditya
|
87ac6522e3
|
[8.6] [Security Solution][Endpoint][Response Actions] Show Actions history on Endpoint Details for platinum users (#145837) (#145890)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Endpoint][Response Actions] Show Actions history on Endpoint Details for platinum users (#145837)](https://github.com/elastic/kibana/pull/145837) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ashokaditya","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-21T15:33:03Z","message":"[Security Solution][Endpoint][Response Actions] Show Actions history on Endpoint Details for platinum users (#145837)\n\n## Summary\r\n\r\nFixes a bug where response actions history was not shown for platinum\r\nusers with Actions Log RBAC privileges.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7e5c361e3820ca9831bc25b6fb50e75a3010b318","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:fix","Team:Onboarding and Lifecycle Mgt","OLM Sprint","v8.6.0","v8.7.0"],"number":145837,"url":"https://github.com/elastic/kibana/pull/145837","mergeCommit":{"message":"[Security Solution][Endpoint][Response Actions] Show Actions history on Endpoint Details for platinum users (#145837)\n\n## Summary\r\n\r\nFixes a bug where response actions history was not shown for platinum\r\nusers with Actions Log RBAC privileges.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7e5c361e3820ca9831bc25b6fb50e75a3010b318"}},"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/145837","number":145837,"mergeCommit":{"message":"[Security Solution][Endpoint][Response Actions] Show Actions history on Endpoint Details for platinum users (#145837)\n\n## Summary\r\n\r\nFixes a bug where response actions history was not shown for platinum\r\nusers with Actions Log RBAC privileges.\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7e5c361e3820ca9831bc25b6fb50e75a3010b318"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
6fa7cc475a
|
[8.6] [Cases] Bulk edit tags: Prevent error when updating cases with the same tags (#145608) (#145886)
# Backport This will backport the following commits from `main` to `8.6`: - [[Cases] Bulk edit tags: Prevent error when updating cases with the same tags (#145608)](https://github.com/elastic/kibana/pull/145608) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T15:51:00Z","message":"[Cases] Bulk edit tags: Prevent error when updating cases with the same tags (#145608)\n\n## Summary\r\n\r\nThis PR fixes a bug where an error occurs when updating the case with\r\nthe same tags. To fix it, we filter cases without any changes.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/145217\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1fb286d84158f75b95d4a9f875df6d07d6c1214","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Cases","v8.6.0","v8.7.0"],"number":145608,"url":"https://github.com/elastic/kibana/pull/145608","mergeCommit":{"message":"[Cases] Bulk edit tags: Prevent error when updating cases with the same tags (#145608)\n\n## Summary\r\n\r\nThis PR fixes a bug where an error occurs when updating the case with\r\nthe same tags. To fix it, we filter cases without any changes.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/145217\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1fb286d84158f75b95d4a9f875df6d07d6c1214"}},"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/145608","number":145608,"mergeCommit":{"message":"[Cases] Bulk edit tags: Prevent error when updating cases with the same tags (#145608)\n\n## Summary\r\n\r\nThis PR fixes a bug where an error occurs when updating the case with\r\nthe same tags. To fix it, we filter cases without any changes.\r\n\r\nFixes: https://github.com/elastic/kibana/issues/145217\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b1fb286d84158f75b95d4a9f875df6d07d6c1214"}}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co> |
||
|
Kibana Machine
|
2580d720cc
|
[8.6] [Osquery] Fix Global Packs (#145820) (#145869)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] Fix Global Packs (#145820)](https://github.com/elastic/kibana/pull/145820) <!--- 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-21T14:25:43Z","message":"[Osquery] Fix Global Packs (#145820)","sha":"80af40e3005527b948ba045eb5681024882f6310","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":145820,"url":"https://github.com/elastic/kibana/pull/145820","mergeCommit":{"message":"[Osquery] Fix Global Packs (#145820)","sha":"80af40e3005527b948ba045eb5681024882f6310"}},"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/145820","number":145820,"mergeCommit":{"message":"[Osquery] Fix Global Packs (#145820)","sha":"80af40e3005527b948ba045eb5681024882f6310"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
27a44f3733
|
[8.6] Fix shared list creation message (#145701) (#145862)
# Backport This will backport the following commits from `main` to `8.6`: - [Fix shared list creation message (#145701)](https://github.com/elastic/kibana/pull/145701) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T13:42:52Z","message":"Fix shared list creation message (#145701)\n\nFix: https://github.com/elastic/kibana/issues/145542\r\n<img width=\"342\" alt=\"Screenshot 2022-11-18 at 10 49 10\"\r\nsrc=\"https://user-images.githubusercontent.com/7609147/202672812-5693a050-8f08-4ac8-b52b-059dd1bc58f8.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b0d93db0cc328f9a242469d3282b64a07fa3032","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Solution Platform","backport:prev-minor","v8.7.0"],"number":145701,"url":"https://github.com/elastic/kibana/pull/145701","mergeCommit":{"message":"Fix shared list creation message (#145701)\n\nFix: https://github.com/elastic/kibana/issues/145542\r\n<img width=\"342\" alt=\"Screenshot 2022-11-18 at 10 49 10\"\r\nsrc=\"https://user-images.githubusercontent.com/7609147/202672812-5693a050-8f08-4ac8-b52b-059dd1bc58f8.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b0d93db0cc328f9a242469d3282b64a07fa3032"}},"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/145701","number":145701,"mergeCommit":{"message":"Fix shared list creation message (#145701)\n\nFix: https://github.com/elastic/kibana/issues/145542\r\n<img width=\"342\" alt=\"Screenshot 2022-11-18 at 10 49 10\"\r\nsrc=\"https://user-images.githubusercontent.com/7609147/202672812-5693a050-8f08-4ac8-b52b-059dd1bc58f8.png\">\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b0d93db0cc328f9a242469d3282b64a07fa3032"}}]}] BACKPORT--> Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co> |
||
|
Kibana Machine
|
c27eedd28c
|
[8.6] [Security Solution][List Details Page]: Fixing not found page (#145833) (#145860)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][List Details Page]: Fixing not found page (#145833)](https://github.com/elastic/kibana/pull/145833) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T13:35:12Z","message":"[Security Solution][List Details Page]: Fixing not found page (#145833)\n\n## Summary\r\n\r\n- Fixing showing Page not found in case the URL is incorrect or listId\r\n- Address https://github.com/elastic/kibana/issues/145548\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f96d81cae374d6b08f2201a2da22691cda9c70d4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":145833,"url":"https://github.com/elastic/kibana/pull/145833","mergeCommit":{"message":"[Security Solution][List Details Page]: Fixing not found page (#145833)\n\n## Summary\r\n\r\n- Fixing showing Page not found in case the URL is incorrect or listId\r\n- Address https://github.com/elastic/kibana/issues/145548\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f96d81cae374d6b08f2201a2da22691cda9c70d4"}},"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/145833","number":145833,"mergeCommit":{"message":"[Security Solution][List Details Page]: Fixing not found page (#145833)\n\n## Summary\r\n\r\n- Fixing showing Page not found in case the URL is incorrect or listId\r\n- Address https://github.com/elastic/kibana/issues/145548\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f96d81cae374d6b08f2201a2da22691cda9c70d4"}}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
Kibana Machine
|
c2871d07b8
|
[8.6] [Uptime] Ping histogram fix using local timezone or configured (#145412) (#145853)
# Backport This will backport the following commits from `main` to `8.6`: - [[Uptime] Ping histogram fix using local timezone or configured (#145412)](https://github.com/elastic/kibana/pull/145412) <!--- 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-21T12:43:39Z","message":"[Uptime] Ping histogram fix using local timezone or configured (#145412)\n\nFixes https://github.com/elastic/kibana/issues/144054","sha":"082e4aa71372f8120928d68b6acbdcf329f67b54","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":145412,"url":"https://github.com/elastic/kibana/pull/145412","mergeCommit":{"message":"[Uptime] Ping histogram fix using local timezone or configured (#145412)\n\nFixes https://github.com/elastic/kibana/issues/144054","sha":"082e4aa71372f8120928d68b6acbdcf329f67b54"}},"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/145412","number":145412,"mergeCommit":{"message":"[Uptime] Ping histogram fix using local timezone or configured (#145412)\n\nFixes https://github.com/elastic/kibana/issues/144054","sha":"082e4aa71372f8120928d68b6acbdcf329f67b54"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad.muhammad@elastic.co> |
||
|
Kibana Machine
|
0cf8fa18f8
|
[8.6] [Synthethics] Use monitor.config_id for the URLs (#145825) (#145850)
# Backport This will backport the following commits from `main` to `8.6`: - [[Synthethics] Use `monitor.config_id` for the URLs (#145825)](https://github.com/elastic/kibana/pull/145825) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Gómez","email":"alejandro.fernandez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T12:15:50Z","message":"[Synthethics] Use `monitor.config_id` for the URLs (#145825)\n\n## Summary\r\n\r\nCloses #145758","sha":"cc50e51fedd666ee065008be1ced33defa375582","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145825,"url":"https://github.com/elastic/kibana/pull/145825","mergeCommit":{"message":"[Synthethics] Use `monitor.config_id` for the URLs (#145825)\n\n## Summary\r\n\r\nCloses #145758","sha":"cc50e51fedd666ee065008be1ced33defa375582"}},"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/145825","number":145825,"mergeCommit":{"message":"[Synthethics] Use `monitor.config_id` for the URLs (#145825)\n\n## Summary\r\n\r\nCloses #145758","sha":"cc50e51fedd666ee065008be1ced33defa375582"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Gómez <alejandro.fernandez@elastic.co> |
||
|
Kibana Machine
|
7215c33aee
|
[8.6] [Cases] Fix flaky test in user actions (#145725) (#145848)
# Backport This will backport the following commits from `main` to `8.6`: - [[Cases] Fix flaky test in user actions (#145725)](https://github.com/elastic/kibana/pull/145725) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T11:57:31Z","message":"[Cases] Fix flaky test in user actions (#145725)\n\n## Summary\r\n\r\nThis PR un skips and fix a flaky test in user actions\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144660\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5c15658756aefc85ce87c5326f97c85c3e5845b8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","v8.6.0","v8.7.0"],"number":145725,"url":"https://github.com/elastic/kibana/pull/145725","mergeCommit":{"message":"[Cases] Fix flaky test in user actions (#145725)\n\n## Summary\r\n\r\nThis PR un skips and fix a flaky test in user actions\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144660\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5c15658756aefc85ce87c5326f97c85c3e5845b8"}},"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/145725","number":145725,"mergeCommit":{"message":"[Cases] Fix flaky test in user actions (#145725)\n\n## Summary\r\n\r\nThis PR un skips and fix a flaky test in user actions\r\n\r\nFixes: https://github.com/elastic/kibana/issues/144660\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- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5c15658756aefc85ce87c5326f97c85c3e5845b8"}}]}] BACKPORT--> Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co> |
||
|
Kibana Machine
|
8d29d1d65a
|
[8.6] [Infrastructure UI] Navigate to node detail page without refresh (#145742) (#145841)
# Backport This will backport the following commits from `main` to `8.6`: - [[Infrastructure UI] Navigate to node detail page without refresh (#145742)](https://github.com/elastic/kibana/pull/145742) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2022-11-21T11:19:31Z","message":"[Infrastructure UI] Navigate to node detail page without refresh (#145742)\n\nCloses [#110219](https://github.com/elastic/kibana/issues/110219)\r\n\r\n## Summary\r\n\r\nThis change fixes the forced page refresh when opening the node detail\r\nfrom the inventory page.\r\n\r\nThis happened due to the property `href` rendering a native anchor tag\r\nwhich interpreted the navigation to the detail view as a completely new\r\npage, refreshing the whole Kibana view.\r\n\r\nSpreading the properties returned by the\r\n[useLinkProps]( |
||
|
Kibana Machine
|
310dd4177f
|
[8.6] [RAM] Fix broken action type filter in rules list (#145691) (#145809)
# Backport This will backport the following commits from `main` to `8.6`: - [[RAM] Fix broken action type filter in rules list (#145691)](https://github.com/elastic/kibana/pull/145691) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-21T08:18:34Z","message":"[RAM] Fix broken action type filter in rules list (#145691)\n\n## Summary\r\n\r\nCloses |
||
|
Kibana Machine
|
47b9663a03
|
[8.6] [upgrade] change OK to Succeeded in rules test (#145770) (#145783)
# Backport This will backport the following commits from `main` to `8.6`: - [[upgrade] change OK to Succeeded in rules test (#145770)](https://github.com/elastic/kibana/pull/145770) <!--- 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-18T23:28:53Z","message":"[upgrade] change OK to Succeeded in rules test (#145770)\n\n## Summary\r\n\r\nRule \"Last response\" changed from OK to Succeeded. See\r\nhttps://github.com/elastic/kibana/issues/136039","sha":"73cf0a2ac6bb88d0e01ac783970a793261028ac2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","release_note:skip","backport:prev-minor","v8.6.0","v8.7.0"],"number":145770,"url":"https://github.com/elastic/kibana/pull/145770","mergeCommit":{"message":"[upgrade] change OK to Succeeded in rules test (#145770)\n\n## Summary\r\n\r\nRule \"Last response\" changed from OK to Succeeded. See\r\nhttps://github.com/elastic/kibana/issues/136039","sha":"73cf0a2ac6bb88d0e01ac783970a793261028ac2"}},"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/145770","number":145770,"mergeCommit":{"message":"[upgrade] change OK to Succeeded in rules test (#145770)\n\n## Summary\r\n\r\nRule \"Last response\" changed from OK to Succeeded. See\r\nhttps://github.com/elastic/kibana/issues/136039","sha":"73cf0a2ac6bb88d0e01ac783970a793261028ac2"}}]}] BACKPORT--> Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co> |
||
|
Kibana Machine
|
16f1d027d6
|
[8.6] [DOCS] Clarify alertId and index in add comment API (#145189) (#145760) | ||
|
Kibana Machine
|
c2454237bb
|
[8.6] [Security Solution] Parse Snapshot Versions for Kibana Artifacts (#145626) (#145771)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] Parse Snapshot Versions for Kibana Artifacts (#145626)](https://github.com/elastic/kibana/pull/145626) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"JD Kurma","email":"JDKurma@gmail.com"},"sourceCommit":{"committedDate":"2022-11-18T19:40:57Z","message":"[Security Solution] Parse Snapshot Versions for Kibana Artifacts (#145626)\n\n## Summary\r\n\r\nThere are instances where the cluster info comes with a snapshot version\r\nsuch as \"8.6.0-SNAPSHOT\". This version string is used to construct the\r\nmanifest url needed to retrieve kibana artifacts; however, those\r\nartifacts are categorized under non-snapshot versions(e.g. \"8.6.0\").\r\nHence, to properly retrieve the respective kibana artifacts, I am\r\nsplitting the version string at '-' to get the applicable kibana\r\nartifact version. Similar methods of splitting are seen\r\n[here](https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/server/plugin.ts#L58)\r\n\r\nAlso for additional reference: here is a\r\n[discussion](https://elastic.slack.com/archives/C5TQ33ND8/p1594726063167100)\r\nfrom #kibana-core slack channel on splitting at '-' for the version\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0db3ab0c1909ca587f897bd0b3be0e58ef3a089f","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":145626,"url":"https://github.com/elastic/kibana/pull/145626","mergeCommit":{"message":"[Security Solution] Parse Snapshot Versions for Kibana Artifacts (#145626)\n\n## Summary\r\n\r\nThere are instances where the cluster info comes with a snapshot version\r\nsuch as \"8.6.0-SNAPSHOT\". This version string is used to construct the\r\nmanifest url needed to retrieve kibana artifacts; however, those\r\nartifacts are categorized under non-snapshot versions(e.g. \"8.6.0\").\r\nHence, to properly retrieve the respective kibana artifacts, I am\r\nsplitting the version string at '-' to get the applicable kibana\r\nartifact version. Similar methods of splitting are seen\r\n[here](https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/server/plugin.ts#L58)\r\n\r\nAlso for additional reference: here is a\r\n[discussion](https://elastic.slack.com/archives/C5TQ33ND8/p1594726063167100)\r\nfrom #kibana-core slack channel on splitting at '-' for the version\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0db3ab0c1909ca587f897bd0b3be0e58ef3a089f"}},"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: JD Kurma <JDKurma@gmail.com> |
||
|
Kibana Machine
|
36d67972a4
|
[8.6] [RAM] Add ability to toggle new rule status UI via experimental features flag (#145630) (#145767)
# Backport This will backport the following commits from `main` to `8.6`: - [[RAM] Add ability to toggle new rule status UI via experimental features flag (#145630)](https://github.com/elastic/kibana/pull/145630) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jiawei Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-18T18:44:41Z","message":"[RAM] Add ability to toggle new rule status UI via experimental features flag (#145630)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/145300\r\n\r\nAllows the new last run outcome UI in the rules list and rule details\r\nview to be turned off via an experimental flag.\r\n\r\nTo test:\r\n- Add the following: `xpack.trigger_actions_ui.enableExperimental:\r\n[\"ruleUseExecutionStatus\"]` to your `kibana.dev.yml`\r\n- Rule management UI should revert back to using execution status\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a0622bb2ea86400aad5a8f367cd31d104a53778","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","backport:prev-minor","v8.6.0","v8.7.0"],"number":145630,"url":"https://github.com/elastic/kibana/pull/145630","mergeCommit":{"message":"[RAM] Add ability to toggle new rule status UI via experimental features flag (#145630)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/145300\r\n\r\nAllows the new last run outcome UI in the rules list and rule details\r\nview to be turned off via an experimental flag.\r\n\r\nTo test:\r\n- Add the following: `xpack.trigger_actions_ui.enableExperimental:\r\n[\"ruleUseExecutionStatus\"]` to your `kibana.dev.yml`\r\n- Rule management UI should revert back to using execution status\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a0622bb2ea86400aad5a8f367cd31d104a53778"}},"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/145630","number":145630,"mergeCommit":{"message":"[RAM] Add ability to toggle new rule status UI via experimental features flag (#145630)\n\n## Summary\r\nResolves: https://github.com/elastic/kibana/issues/145300\r\n\r\nAllows the new last run outcome UI in the rules list and rule details\r\nview to be turned off via an experimental flag.\r\n\r\nTo test:\r\n- Add the following: `xpack.trigger_actions_ui.enableExperimental:\r\n[\"ruleUseExecutionStatus\"]` to your `kibana.dev.yml`\r\n- Rule management UI should revert back to using execution status\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"9a0622bb2ea86400aad5a8f367cd31d104a53778"}}]}] BACKPORT--> Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com> |
||
|
Kibana Machine
|
dec5dbc8cc
|
[8.6] [Fleet] Fix add fleet server host from advanced tab (#145622) (#145733)
# Backport This will backport the following commits from `main` to `8.6`: - [[Fleet] Fix add fleet server host from advanced tab (#145622)](https://github.com/elastic/kibana/pull/145622) <!--- 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-18T13:55:30Z","message":"[Fleet] Fix add fleet server host from advanced tab (#145622)","sha":"904fc21f65e6815b7698d1e65993cd956aef27e8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":145622,"url":"https://github.com/elastic/kibana/pull/145622","mergeCommit":{"message":"[Fleet] Fix add fleet server host from advanced tab (#145622)","sha":"904fc21f65e6815b7698d1e65993cd956aef27e8"}},"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/145622","number":145622,"mergeCommit":{"message":"[Fleet] Fix add fleet server host from advanced tab (#145622)","sha":"904fc21f65e6815b7698d1e65993cd956aef27e8"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
4ed7e7048f
|
[8.6] increase uptime/synthetics timespan filter from -5m to -20m (#144769) (#145762)
# Backport This will backport the following commits from `main` to `8.6`: - [increase uptime/synthetics timespan filter from -5m to -20m (#144769)](https://github.com/elastic/kibana/pull/144769) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T17:00:33Z","message":"increase uptime/synthetics timespan filter from -5m to -20m (#144769)\n\nCo-authored-by: shahzad31 <shahzad.muhammad@elastic.co>\r\nResolves https://github.com/elastic/kibana/issues/144097","sha":"9b87a14599416566953f9135b58f760f0bf0ba93","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":144769,"url":"https://github.com/elastic/kibana/pull/144769","mergeCommit":{"message":"increase uptime/synthetics timespan filter from -5m to -20m (#144769)\n\nCo-authored-by: shahzad31 <shahzad.muhammad@elastic.co>\r\nResolves https://github.com/elastic/kibana/issues/144097","sha":"9b87a14599416566953f9135b58f760f0bf0ba93"}},"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/144769","number":144769,"mergeCommit":{"message":"increase uptime/synthetics timespan filter from -5m to -20m (#144769)\n\nCo-authored-by: shahzad31 <shahzad.muhammad@elastic.co>\r\nResolves https://github.com/elastic/kibana/issues/144097","sha":"9b87a14599416566953f9135b58f760f0bf0ba93"}}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
|
Kibana Machine
|
8f1802dd32
|
[8.6] [ML] Fix the default time range on the Notifications page (#145578) (#145754)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Fix the default time range on the Notifications page (#145578)](https://github.com/elastic/kibana/pull/145578) <!--- 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-18T16:18:00Z","message":"[ML] Fix the default time range on the Notifications page (#145578)\n\n## Summary\r\n\r\nIf the user never visited the Notification page, we start polling\r\nnotifications for the last week and update the Notification indicator\r\naccordingly. This PR fixes the time range on the Notification page\r\nitself, to make sure it is aligned with the time bounds from the side\r\nnav indicator.\r\n\r\n","sha":"dd162ac561c557bed60203e6afcdf47b6be9a7d3","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.6.0","v8.7.0"],"number":145578,"url":"https://github.com/elastic/kibana/pull/145578","mergeCommit":{"message":"[ML] Fix the default time range on the Notifications page (#145578)\n\n## Summary\r\n\r\nIf the user never visited the Notification page, we start polling\r\nnotifications for the last week and update the Notification indicator\r\naccordingly. This PR fixes the time range on the Notification page\r\nitself, to make sure it is aligned with the time bounds from the side\r\nnav indicator.\r\n\r\n","sha":"dd162ac561c557bed60203e6afcdf47b6be9a7d3"}},"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/145578","number":145578,"mergeCommit":{"message":"[ML] Fix the default time range on the Notifications page (#145578)\n\n## Summary\r\n\r\nIf the user never visited the Notification page, we start polling\r\nnotifications for the last week and update the Notification indicator\r\naccordingly. This PR fixes the time range on the Notification page\r\nitself, to make sure it is aligned with the time bounds from the side\r\nnav indicator.\r\n\r\n","sha":"dd162ac561c557bed60203e6afcdf47b6be9a7d3"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
a693baa3cf
|
[8.6] [RAM] allow no indices on alert search bar (#145437) (#145732)
# Backport This will backport the following commits from `main` to `8.6`: - [[RAM] allow no indices on alert search bar (#145437)](https://github.com/elastic/kibana/pull/145437) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Xavier Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T13:53:18Z","message":"[RAM] allow no indices on alert search bar (#145437)\n\n## Summary\r\n\r\nResolve: https://github.com/elastic/kibana/issues/145246\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"beeea7d91e7bc39b80996f0713633800ecb1f708","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:ResponseOps","v8.6.0","v8.7.0"],"number":145437,"url":"https://github.com/elastic/kibana/pull/145437","mergeCommit":{"message":"[RAM] allow no indices on alert search bar (#145437)\n\n## Summary\r\n\r\nResolve: https://github.com/elastic/kibana/issues/145246\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"beeea7d91e7bc39b80996f0713633800ecb1f708"}},"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/145437","number":145437,"mergeCommit":{"message":"[RAM] allow no indices on alert search bar (#145437)\n\n## Summary\r\n\r\nResolve: https://github.com/elastic/kibana/issues/145246\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"beeea7d91e7bc39b80996f0713633800ecb1f708"}}]}] BACKPORT--> Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co> |
||
|
Kibana Machine
|
31f3c3ea62
|
[8.6] [ResponseOps][Cases] Back button navigation out of the cases view (#145358) (#145734)
# Backport This will backport the following commits from `main` to `8.6`: - [[ResponseOps][Cases] Back button navigation out of the cases view (#145358)](https://github.com/elastic/kibana/pull/145358) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T11:29:55Z","message":"[ResponseOps][Cases] Back button navigation out of the cases view (#145358)\n\n## Summary\r\n\r\nFixes #145110 \r\n\r\nBesides our changes in the `useAllCasesQueryParams` I noticed that the\r\n`DatePickerContextProvider` was causing a similar issue.\r\n\r\nSome pages in Observability get the `dateFrom` and `dateTo` URL\r\nparameters even if there is no date picker on the page. The\r\n`DatePickerContextProvider` was adding these parameters were being added\r\non mount with `history.push` which caused us to have to click as many as\r\n3/4(!) times backspace to navigate out of a page we just visited.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4e26f09276aa595900b9ddfdea105ee0c5ddbd9e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Cases","backport:prev-minor","v8.6.0","v8.7.0"],"number":145358,"url":"https://github.com/elastic/kibana/pull/145358","mergeCommit":{"message":"[ResponseOps][Cases] Back button navigation out of the cases view (#145358)\n\n## Summary\r\n\r\nFixes #145110 \r\n\r\nBesides our changes in the `useAllCasesQueryParams` I noticed that the\r\n`DatePickerContextProvider` was causing a similar issue.\r\n\r\nSome pages in Observability get the `dateFrom` and `dateTo` URL\r\nparameters even if there is no date picker on the page. The\r\n`DatePickerContextProvider` was adding these parameters were being added\r\non mount with `history.push` which caused us to have to click as many as\r\n3/4(!) times backspace to navigate out of a page we just visited.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4e26f09276aa595900b9ddfdea105ee0c5ddbd9e"}},"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/145358","number":145358,"mergeCommit":{"message":"[ResponseOps][Cases] Back button navigation out of the cases view (#145358)\n\n## Summary\r\n\r\nFixes #145110 \r\n\r\nBesides our changes in the `useAllCasesQueryParams` I noticed that the\r\n`DatePickerContextProvider` was causing a similar issue.\r\n\r\nSome pages in Observability get the `dateFrom` and `dateTo` URL\r\nparameters even if there is no date picker on the page. The\r\n`DatePickerContextProvider` was adding these parameters were being added\r\non mount with `history.push` which caused us to have to click as many as\r\n3/4(!) times backspace to navigate out of a page we just visited.\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"4e26f09276aa595900b9ddfdea105ee0c5ddbd9e"}}]}] BACKPORT--> Co-authored-by: Antonio <antonio.coelho@elastic.co> |
||
|
Kibana Machine
|
68bd9a95e7
|
[8.6] [Security Solution] [Exceptions] Fix edit the exception while adding new comment. (#145575) (#145724)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution] [Exceptions] Fix edit the exception while adding new comment. (#145575)](https://github.com/elastic/kibana/pull/145575) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Wafaa Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T13:35:03Z","message":"[Security Solution] [Exceptions] Fix edit the exception while adding new comment. (#145575)\n\n## Summary\r\n\r\nAddress https://github.com/elastic/kibana/issues/144523\r\n\r\n1. Fix type schema check to use `updateExceptionListItemSchema` instead\r\nof `exceptionListItemSchema` as the comments array could be empty when\r\nthe user adds the Exceptions and in Editing with adding a new comment(s)\r\nit will contain only (comment and id) in the newly created comment\r\n\r\n2. Add `removeCreatedAtCreatedByFromCommentsOnUpdate` to remove the\r\n`createdAt`, and `createdBy` from the updated exception Item if a\r\ncomment was added before to fix the `400 Schema validations` as per the\r\nbelow Schema\r\n\r\nThe\r\n`packages/kbn-securitysolution-io-ts-list-types/src/common/update_comment/index.ts`\r\n \r\n ```\r\n export const updateComment = t.intersection([\r\n t.exact(\r\n t.type({\r\n comment: NonEmptyString,\r\n })\r\n ),\r\n t.exact(\r\n t.partial({\r\n id,\r\n })\r\n ),\r\n ]);\r\n ```\r\n3. Moving tests and mocks to the `hooks` package as well add new tests\r\nfor the new `removeCreatedAtCreatedByFromCommentsOnUpdate`\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2bd2226cb259312b90ad32b1cd5618a0cc2e8b49","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Security Solution Platform","v8.6.0","v8.7.0"],"number":145575,"url":"https://github.com/elastic/kibana/pull/145575","mergeCommit":{"message":"[Security Solution] [Exceptions] Fix edit the exception while adding new comment. (#145575)\n\n## Summary\r\n\r\nAddress https://github.com/elastic/kibana/issues/144523\r\n\r\n1. Fix type schema check to use `updateExceptionListItemSchema` instead\r\nof `exceptionListItemSchema` as the comments array could be empty when\r\nthe user adds the Exceptions and in Editing with adding a new comment(s)\r\nit will contain only (comment and id) in the newly created comment\r\n\r\n2. Add `removeCreatedAtCreatedByFromCommentsOnUpdate` to remove the\r\n`createdAt`, and `createdBy` from the updated exception Item if a\r\ncomment was added before to fix the `400 Schema validations` as per the\r\nbelow Schema\r\n\r\nThe\r\n`packages/kbn-securitysolution-io-ts-list-types/src/common/update_comment/index.ts`\r\n \r\n ```\r\n export const updateComment = t.intersection([\r\n t.exact(\r\n t.type({\r\n comment: NonEmptyString,\r\n })\r\n ),\r\n t.exact(\r\n t.partial({\r\n id,\r\n })\r\n ),\r\n ]);\r\n ```\r\n3. Moving tests and mocks to the `hooks` package as well add new tests\r\nfor the new `removeCreatedAtCreatedByFromCommentsOnUpdate`\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2bd2226cb259312b90ad32b1cd5618a0cc2e8b49"}},"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/145575","number":145575,"mergeCommit":{"message":"[Security Solution] [Exceptions] Fix edit the exception while adding new comment. (#145575)\n\n## Summary\r\n\r\nAddress https://github.com/elastic/kibana/issues/144523\r\n\r\n1. Fix type schema check to use `updateExceptionListItemSchema` instead\r\nof `exceptionListItemSchema` as the comments array could be empty when\r\nthe user adds the Exceptions and in Editing with adding a new comment(s)\r\nit will contain only (comment and id) in the newly created comment\r\n\r\n2. Add `removeCreatedAtCreatedByFromCommentsOnUpdate` to remove the\r\n`createdAt`, and `createdBy` from the updated exception Item if a\r\ncomment was added before to fix the `400 Schema validations` as per the\r\nbelow Schema\r\n\r\nThe\r\n`packages/kbn-securitysolution-io-ts-list-types/src/common/update_comment/index.ts`\r\n \r\n ```\r\n export const updateComment = t.intersection([\r\n t.exact(\r\n t.type({\r\n comment: NonEmptyString,\r\n })\r\n ),\r\n t.exact(\r\n t.partial({\r\n id,\r\n })\r\n ),\r\n ]);\r\n ```\r\n3. Moving tests and mocks to the `hooks` package as well add new tests\r\nfor the new `removeCreatedAtCreatedByFromCommentsOnUpdate`\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"2bd2226cb259312b90ad32b1cd5618a0cc2e8b49"}}]}] BACKPORT--> Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co> |
||
|
Kibana Machine
|
bc3f322a3c
|
[8.6] [ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699) (#145716)
# Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)](https://github.com/elastic/kibana/pull/145699) <!--- 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-18T11:49:06Z","message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260","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":145699,"url":"https://github.com/elastic/kibana/pull/145699","mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260"}},"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/145699","number":145699,"mergeCommit":{"message":"[ML] Explain Log Rate Spikes: Use bulk indexing for dummy data. (#145699)\n\nThe functional tests added 100 docs with individual requests. This\r\nupdate uses bulk indexing to speed up preparing the data.","sha":"65a9b0950548c2b3cac302f6bdad1532cd032260"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co> |
||
|
Kibana Machine
|
f994ea63f9
|
[8.6] [Osquery] Fix osquery attachment rerender (#145511) (#145709)
# Backport This will backport the following commits from `main` to `8.6`: - [[Osquery] Fix osquery attachment rerender (#145511)](https://github.com/elastic/kibana/pull/145511) <!--- 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-18T10:52:11Z","message":"[Osquery] Fix osquery attachment rerender (#145511)","sha":"4ba6d1dfaa11f8e68367783605403a312aed2002","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":145511,"url":"https://github.com/elastic/kibana/pull/145511","mergeCommit":{"message":"[Osquery] Fix osquery attachment rerender (#145511)","sha":"4ba6d1dfaa11f8e68367783605403a312aed2002"}},"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/145511","number":145511,"mergeCommit":{"message":"[Osquery] Fix osquery attachment rerender (#145511)","sha":"4ba6d1dfaa11f8e68367783605403a312aed2002"}}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
|
Kibana Machine
|
57318d2d7e
|
[8.6] [Actionable observability] Validate alert search bar query parameters (#145369) (#145702)
# Backport This will backport the following commits from `main` to `8.6`: - [[Actionable observability] Validate alert search bar query parameters (#145369)](https://github.com/elastic/kibana/pull/145369) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2022-11-18T10:08:03Z","message":"[Actionable observability] Validate alert search bar query parameters (#145369)\n\nFixes #144911, #143640\r\n\r\n## 📝 Summary\r\n\r\n- Validate alert search bar query params using io-ts\r\n- Make sure that we only enter one history for changes related to the\r\nalert search bar\r\n- Make sure to not save tab changes on the rule details page in the\r\nhistory\r\n- Use `DatePickerContextProvider` only for `overview` page to fix 143640\r\n\r\n## 🧪 How to test\r\n- In the alerts page URL, you should not see\r\n`rangeFrom=now-15m&rangeTo=now` query parameters anymore\r\n- Changing the alerts' page URL to an invalid one should not break the\r\npage anymore\r\n - Example: `_a=(kuery:%27%27,rangeFrom:now-15m,rangeTo:12)`\r\n- By changing alert search bar information, you should not see new\r\nrecords added to the history\r\n- Same for rule details page (either changing tab or alert search bar\r\nparameters)","sha":"42a1062000ca4dd5e827a97aac0134a8ad8f895a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team: Actionable Observability","v8.6.0","v8.7.0"],"number":145369,"url":"https://github.com/elastic/kibana/pull/145369","mergeCommit":{"message":"[Actionable observability] Validate alert search bar query parameters (#145369)\n\nFixes #144911, #143640\r\n\r\n## 📝 Summary\r\n\r\n- Validate alert search bar query params using io-ts\r\n- Make sure that we only enter one history for changes related to the\r\nalert search bar\r\n- Make sure to not save tab changes on the rule details page in the\r\nhistory\r\n- Use `DatePickerContextProvider` only for `overview` page to fix 143640\r\n\r\n## 🧪 How to test\r\n- In the alerts page URL, you should not see\r\n`rangeFrom=now-15m&rangeTo=now` query parameters anymore\r\n- Changing the alerts' page URL to an invalid one should not break the\r\npage anymore\r\n - Example: `_a=(kuery:%27%27,rangeFrom:now-15m,rangeTo:12)`\r\n- By changing alert search bar information, you should not see new\r\nrecords added to the history\r\n- Same for rule details page (either changing tab or alert search bar\r\nparameters)","sha":"42a1062000ca4dd5e827a97aac0134a8ad8f895a"}},"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/145369","number":145369,"mergeCommit":{"message":"[Actionable observability] Validate alert search bar query parameters (#145369)\n\nFixes #144911, #143640\r\n\r\n## 📝 Summary\r\n\r\n- Validate alert search bar query params using io-ts\r\n- Make sure that we only enter one history for changes related to the\r\nalert search bar\r\n- Make sure to not save tab changes on the rule details page in the\r\nhistory\r\n- Use `DatePickerContextProvider` only for `overview` page to fix 143640\r\n\r\n## 🧪 How to test\r\n- In the alerts page URL, you should not see\r\n`rangeFrom=now-15m&rangeTo=now` query parameters anymore\r\n- Changing the alerts' page URL to an invalid one should not break the\r\npage anymore\r\n - Example: `_a=(kuery:%27%27,rangeFrom:now-15m,rangeTo:12)`\r\n- By changing alert search bar information, you should not see new\r\nrecords added to the history\r\n- Same for rule details page (either changing tab or alert search bar\r\nparameters)","sha":"42a1062000ca4dd5e827a97aac0134a8ad8f895a"}}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> |
||
|
Kibana Machine
|
d9d8b15a90
|
[8.6] [Security Solution][Alerts] improves performance of new terms multi fields (#145167) (#145697)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security Solution][Alerts] improves performance of new terms multi fields (#145167)](https://github.com/elastic/kibana/pull/145167) <!--- 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-18T09:02:15Z","message":"[Security Solution][Alerts] improves performance of new terms multi fields (#145167)\n\n## Summary\r\n\r\nThis PR improves performance of new terms multiple fields implementation\r\nreleased in https://github.com/elastic/kibana/pull/143943\r\nIn comparison with single value fields it's faster in 2-2.5 times\r\nIn comparison with array field the win even more significant: 3-4 times\r\n\r\n### Technical implementation:\r\nValue for runtime field is emitted only if any of new terms fields\r\npresent in `include` clause of terms aggregation. It's achieved by\r\npassing a values map of new terms fields to the runtime script and\r\nchecking new terms values in it. So, there is a significant performance\r\nwins if runtime field is not matched with includes values:\r\n - new terms fields are not encoded in base64 within runtime script\r\n - runtime script doesn't emit any values\r\n- runtime field doesn't have any value to be compared against during\r\naggregation, as its empty\r\n- it eliminates possible unyielding execution branches early: if one of\r\nitems in array of first new terms field is not present in values map, no\r\nneed to run through the rest of combinations\r\n\r\nAs a result, this implementation overcomes the issue with non exhaustive\r\nresults due to the large number of emitted fields.\r\nES doesn't allow emitting more than 100 values in the runtime script, so\r\nif the number of all combinations in new terms fields is greater than\r\n100, only the first 100 combinations will be used for terms aggregation.\r\nWith this new implementation only matched fields will be emitting. Even\r\nif its number is greater than 100, we will hit circuit breaker in\r\nSecurity Solution: as rule run can't generate more than 100 alerts\r\n\r\n### Performance measurements\r\n\r\n\r\nImplementation | Shards | Docs per shard | Simultaneous Rule Executions\r\n| Fields cardinality | Rule Execution Time (improved) | Rule Execution\r\nTime (old)\r\n-- | -- | -- | -- | -- | -- | --\r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 17s | 33s\r\nTerms 2 fields | 10 | 900,000 | 2 | 100,000 | 19s | \r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 18s | 46s\r\nTerms 3 fields | 10 | 900,000 | 2 | 100,000 | 20s | \r\n | | | | | | \r\nTerms 1 field | 20 | 900,000 | 1 | 100,000 | 10.5s | \r\nTerms 2 fields | 20 | 900,000 | 1 | 100,000 | 28s | 55s\r\nTerms 2 fields | 20 | 900,000 | 2 | 100,000 | 28.5s | 56s\r\nTerms 3 fields | 20 | 900,000 | 1 | 100,000 | 30s | 75s\r\nTerms 3 fields | 20 | 900,000 | 2 | 100,000 | 31s | 75s\r\n | | | | | | \r\nTerms 1 field | 10 | 1,800,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 1,800,000 | 1 | 100,000 | 24s | 50s\r\nTerms 3 fields | 10 | 1,800,000 | 1 | 100,000 | 26s | 68s\r\n | | | | | | \r\narray of unique values length 10 | | | | | | \r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 9.5s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 75s | 3.5m\r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 83s | 6m\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com>","sha":"b985ec1735d432bf4cf13fb4a4610dabb5c987c6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["performance","release_note:skip","Team: SecuritySolution","Team:Detection Alerts","backport:prev-minor","v8.6.0","v8.7.0"],"number":145167,"url":"https://github.com/elastic/kibana/pull/145167","mergeCommit":{"message":"[Security Solution][Alerts] improves performance of new terms multi fields (#145167)\n\n## Summary\r\n\r\nThis PR improves performance of new terms multiple fields implementation\r\nreleased in https://github.com/elastic/kibana/pull/143943\r\nIn comparison with single value fields it's faster in 2-2.5 times\r\nIn comparison with array field the win even more significant: 3-4 times\r\n\r\n### Technical implementation:\r\nValue for runtime field is emitted only if any of new terms fields\r\npresent in `include` clause of terms aggregation. It's achieved by\r\npassing a values map of new terms fields to the runtime script and\r\nchecking new terms values in it. So, there is a significant performance\r\nwins if runtime field is not matched with includes values:\r\n - new terms fields are not encoded in base64 within runtime script\r\n - runtime script doesn't emit any values\r\n- runtime field doesn't have any value to be compared against during\r\naggregation, as its empty\r\n- it eliminates possible unyielding execution branches early: if one of\r\nitems in array of first new terms field is not present in values map, no\r\nneed to run through the rest of combinations\r\n\r\nAs a result, this implementation overcomes the issue with non exhaustive\r\nresults due to the large number of emitted fields.\r\nES doesn't allow emitting more than 100 values in the runtime script, so\r\nif the number of all combinations in new terms fields is greater than\r\n100, only the first 100 combinations will be used for terms aggregation.\r\nWith this new implementation only matched fields will be emitting. Even\r\nif its number is greater than 100, we will hit circuit breaker in\r\nSecurity Solution: as rule run can't generate more than 100 alerts\r\n\r\n### Performance measurements\r\n\r\n\r\nImplementation | Shards | Docs per shard | Simultaneous Rule Executions\r\n| Fields cardinality | Rule Execution Time (improved) | Rule Execution\r\nTime (old)\r\n-- | -- | -- | -- | -- | -- | --\r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 17s | 33s\r\nTerms 2 fields | 10 | 900,000 | 2 | 100,000 | 19s | \r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 18s | 46s\r\nTerms 3 fields | 10 | 900,000 | 2 | 100,000 | 20s | \r\n | | | | | | \r\nTerms 1 field | 20 | 900,000 | 1 | 100,000 | 10.5s | \r\nTerms 2 fields | 20 | 900,000 | 1 | 100,000 | 28s | 55s\r\nTerms 2 fields | 20 | 900,000 | 2 | 100,000 | 28.5s | 56s\r\nTerms 3 fields | 20 | 900,000 | 1 | 100,000 | 30s | 75s\r\nTerms 3 fields | 20 | 900,000 | 2 | 100,000 | 31s | 75s\r\n | | | | | | \r\nTerms 1 field | 10 | 1,800,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 1,800,000 | 1 | 100,000 | 24s | 50s\r\nTerms 3 fields | 10 | 1,800,000 | 1 | 100,000 | 26s | 68s\r\n | | | | | | \r\narray of unique values length 10 | | | | | | \r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 9.5s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 75s | 3.5m\r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 83s | 6m\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com>","sha":"b985ec1735d432bf4cf13fb4a4610dabb5c987c6"}},"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/145167","number":145167,"mergeCommit":{"message":"[Security Solution][Alerts] improves performance of new terms multi fields (#145167)\n\n## Summary\r\n\r\nThis PR improves performance of new terms multiple fields implementation\r\nreleased in https://github.com/elastic/kibana/pull/143943\r\nIn comparison with single value fields it's faster in 2-2.5 times\r\nIn comparison with array field the win even more significant: 3-4 times\r\n\r\n### Technical implementation:\r\nValue for runtime field is emitted only if any of new terms fields\r\npresent in `include` clause of terms aggregation. It's achieved by\r\npassing a values map of new terms fields to the runtime script and\r\nchecking new terms values in it. So, there is a significant performance\r\nwins if runtime field is not matched with includes values:\r\n - new terms fields are not encoded in base64 within runtime script\r\n - runtime script doesn't emit any values\r\n- runtime field doesn't have any value to be compared against during\r\naggregation, as its empty\r\n- it eliminates possible unyielding execution branches early: if one of\r\nitems in array of first new terms field is not present in values map, no\r\nneed to run through the rest of combinations\r\n\r\nAs a result, this implementation overcomes the issue with non exhaustive\r\nresults due to the large number of emitted fields.\r\nES doesn't allow emitting more than 100 values in the runtime script, so\r\nif the number of all combinations in new terms fields is greater than\r\n100, only the first 100 combinations will be used for terms aggregation.\r\nWith this new implementation only matched fields will be emitting. Even\r\nif its number is greater than 100, we will hit circuit breaker in\r\nSecurity Solution: as rule run can't generate more than 100 alerts\r\n\r\n### Performance measurements\r\n\r\n\r\nImplementation | Shards | Docs per shard | Simultaneous Rule Executions\r\n| Fields cardinality | Rule Execution Time (improved) | Rule Execution\r\nTime (old)\r\n-- | -- | -- | -- | -- | -- | --\r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 17s | 33s\r\nTerms 2 fields | 10 | 900,000 | 2 | 100,000 | 19s | \r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 18s | 46s\r\nTerms 3 fields | 10 | 900,000 | 2 | 100,000 | 20s | \r\n | | | | | | \r\nTerms 1 field | 20 | 900,000 | 1 | 100,000 | 10.5s | \r\nTerms 2 fields | 20 | 900,000 | 1 | 100,000 | 28s | 55s\r\nTerms 2 fields | 20 | 900,000 | 2 | 100,000 | 28.5s | 56s\r\nTerms 3 fields | 20 | 900,000 | 1 | 100,000 | 30s | 75s\r\nTerms 3 fields | 20 | 900,000 | 2 | 100,000 | 31s | 75s\r\n | | | | | | \r\nTerms 1 field | 10 | 1,800,000 | 1 | 100,000 | 7s | \r\nTerms 2 fields | 10 | 1,800,000 | 1 | 100,000 | 24s | 50s\r\nTerms 3 fields | 10 | 1,800,000 | 1 | 100,000 | 26s | 68s\r\n | | | | | | \r\narray of unique values length 10 | | | | | | \r\nTerms 1 field | 10 | 900,000 | 1 | 100,000 | 9.5s | \r\nTerms 2 fields | 10 | 900,000 | 1 | 100,000 | 75s | 3.5m\r\nTerms 3 fields | 10 | 900,000 | 1 | 100,000 | 83s | 6m\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com>","sha":"b985ec1735d432bf4cf13fb4a4610dabb5c987c6"}}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
423d5a58ed
|
[8.6] [Lens][Visualize][Embeddable] Optimize Lens embeddables on error (#144015) (#145695)
# Backport This will backport the following commits from `main` to `8.6`: - [[Lens][Visualize][Embeddable] Optimize Lens embeddables on error (#144015)](https://github.com/elastic/kibana/pull/144015) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-18T08:55:45Z","message":"[Lens][Visualize][Embeddable] Optimize Lens embeddables on error (#144015)\n\n## Summary\r\n\r\nFixes #143552\r\n\r\nIn this PR there are some embeddable rendering optimizations for the\r\nerror case.\r\nLens handles error states internally without passing to default\r\n`EmbeddablePanel` flows - this has been made explicit in the Lens\r\n`Embeddable` component. The embeddable was triggering multiple time the\r\n`render` method in both successful and failure case: while the\r\nexpression component renderer had some debouncing/memoize optimization\r\nto reduce the effective rerenders, the error route had none leading to a\r\ntotal of 3 rerenderings (loading + some changes detected).\r\n\r\nIn this PR I've managed to reduce the rerenders to 2 (loading + final\r\nstate) with some gatekeeping on the internal state reporting.\r\nAs for the `data-rendering-complete` the logic has changed to set it to\r\n`true` also in Error state, but I would collect some feedback from\r\n@elastic/kibana-app-services on this side to better understand the\r\nimpact. Before this change the `data-error` attribute could be checked\r\nto detect the final state of the panel, but that introduces some\r\nproblems for Lens panels for the error reporting, hence the need to have\r\nthe `complete` flag changed.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87c7b3940b2774c36b94243e325a8f49a2094329","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","Team:AppServicesSv","release_note:skip","Feature:Lens","backport:prev-minor","v8.6.0","v8.7.0"],"number":144015,"url":"https://github.com/elastic/kibana/pull/144015","mergeCommit":{"message":"[Lens][Visualize][Embeddable] Optimize Lens embeddables on error (#144015)\n\n## Summary\r\n\r\nFixes #143552\r\n\r\nIn this PR there are some embeddable rendering optimizations for the\r\nerror case.\r\nLens handles error states internally without passing to default\r\n`EmbeddablePanel` flows - this has been made explicit in the Lens\r\n`Embeddable` component. The embeddable was triggering multiple time the\r\n`render` method in both successful and failure case: while the\r\nexpression component renderer had some debouncing/memoize optimization\r\nto reduce the effective rerenders, the error route had none leading to a\r\ntotal of 3 rerenderings (loading + some changes detected).\r\n\r\nIn this PR I've managed to reduce the rerenders to 2 (loading + final\r\nstate) with some gatekeeping on the internal state reporting.\r\nAs for the `data-rendering-complete` the logic has changed to set it to\r\n`true` also in Error state, but I would collect some feedback from\r\n@elastic/kibana-app-services on this side to better understand the\r\nimpact. Before this change the `data-error` attribute could be checked\r\nto detect the final state of the panel, but that introduces some\r\nproblems for Lens panels for the error reporting, hence the need to have\r\nthe `complete` flag changed.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87c7b3940b2774c36b94243e325a8f49a2094329"}},"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/144015","number":144015,"mergeCommit":{"message":"[Lens][Visualize][Embeddable] Optimize Lens embeddables on error (#144015)\n\n## Summary\r\n\r\nFixes #143552\r\n\r\nIn this PR there are some embeddable rendering optimizations for the\r\nerror case.\r\nLens handles error states internally without passing to default\r\n`EmbeddablePanel` flows - this has been made explicit in the Lens\r\n`Embeddable` component. The embeddable was triggering multiple time the\r\n`render` method in both successful and failure case: while the\r\nexpression component renderer had some debouncing/memoize optimization\r\nto reduce the effective rerenders, the error route had none leading to a\r\ntotal of 3 rerenderings (loading + some changes detected).\r\n\r\nIn this PR I've managed to reduce the rerenders to 2 (loading + final\r\nstate) with some gatekeeping on the internal state reporting.\r\nAs for the `data-rendering-complete` the logic has changed to set it to\r\n`true` also in Error state, but I would collect some feedback from\r\n@elastic/kibana-app-services on this side to better understand the\r\nimpact. Before this change the `data-error` attribute could be checked\r\nto detect the final state of the panel, but that introduces some\r\nproblems for Lens panels for the error reporting, hence the need to have\r\nthe `complete` flag changed.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87c7b3940b2774c36b94243e325a8f49a2094329"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Kibana Machine
|
a8164ed83c
|
[8.6] [DOCS] Automate connector-listing.png (#143605) (#145659)
# Backport This will backport the following commits from `main` to `8.6`: - [[DOCS] Automate connector-listing.png (#143605)](https://github.com/elastic/kibana/pull/143605) <!--- 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-18T01:08:41Z","message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","v8.6.0","v8.5.1","v8.7.0"],"number":143605,"url":"https://github.com/elastic/kibana/pull/143605","mergeCommit":{"message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7"}},"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":"8.5","label":"v8.5.1","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/143605","number":143605,"mergeCommit":{"message":"[DOCS] Automate connector-listing.png (#143605)\n\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>","sha":"31ca6447332e52e502f0ed3645ebb02f054807c7"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
89a27f2d2e
|
[8.6] [Security solution] [Explore] Alerts/cases guided onboarding cypress tests (#145312) (#145647)
# Backport This will backport the following commits from `main` to `8.6`: - [[Security solution] [Explore] Alerts/cases guided onboarding cypress tests (#145312)](https://github.com/elastic/kibana/pull/145312) <!--- 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-17T23:02:10Z","message":"[Security solution] [Explore] Alerts/cases guided onboarding cypress tests (#145312)","sha":"39bacae9bceb53b9f53863bc4f7b36fea9c299fb","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting","Team: SecuritySolution","Team:Threat Hunting:Explore","v8.6.0","v8.7.0"],"number":145312,"url":"https://github.com/elastic/kibana/pull/145312","mergeCommit":{"message":"[Security solution] [Explore] Alerts/cases guided onboarding cypress tests (#145312)","sha":"39bacae9bceb53b9f53863bc4f7b36fea9c299fb"}},"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/145312","number":145312,"mergeCommit":{"message":"[Security solution] [Explore] Alerts/cases guided onboarding cypress tests (#145312)","sha":"39bacae9bceb53b9f53863bc4f7b36fea9c299fb"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Constance
|
fa3a62e5a5
|
Upgrade EUI to v67.1.9 (#145490)
## Summary `eui@67.1.8` ⏩ `eui@67.1.9` This backport fixes bugs affecting Maps that were found in the latest EUI upgrade (https://github.com/elastic/kibana/pull/144845#issuecomment-1317653081). It is meant to go directly into 8.6 ## [`67.1.9`](https://github.com/elastic/eui/tree/v67.1.9) - `EuiButton` now accepts `minWidth={false}` ([#6373](https://github.com/elastic/eui/pull/6373)) **Bug fixes** - Fixed the shadow sizes of `.eui-yScrollWithShadows` and `.eui-xScrollWithShadows` ([#6374](https://github.com/elastic/eui/pull/6374)) - `EuiButton` no longer outputs unnecessary inline styles for `minWidth={0}` or `minWidth={false}` ([#6373](https://github.com/elastic/eui/pull/6373)) - `EuiFacetButton` no longer reports type issues when passing props accepted by `EuiButton` ([#6373](https://github.com/elastic/eui/pull/6373)) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3ea72a641d
|
[8.6] basic smoke test for Fleet installation package (#145475) (#145634)
# Backport This will backport the following commits from `main` to `8.6`: - [basic smoke test for Fleet installation package (#145475)](https://github.com/elastic/kibana/pull/145475) <!--- 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-17T21:53:54Z","message":"basic smoke test for Fleet installation package (#145475)\n\ncovers https://github.com/elastic/kibana/pull/144899\r\n\r\nchecks `Elastic Synthetics` shows up when navigated to Installed\r\nIntegrations\r\n<img width=\"1616\" alt=\"Screen Shot 2022-11-16 at 3 16 32 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11466284/202315280-d5b1d730-df82-4dbb-9da1-35b001683b27.png\">","sha":"6d4cadaeac4c68fc1e023f97e2ce0968af47e024","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:xpack_main","test_xpack_functional","release_note:skip","Team:Fleet","backport:prev-minor","v8.6.0","v8.7.0"],"number":145475,"url":"https://github.com/elastic/kibana/pull/145475","mergeCommit":{"message":"basic smoke test for Fleet installation package (#145475)\n\ncovers https://github.com/elastic/kibana/pull/144899\r\n\r\nchecks `Elastic Synthetics` shows up when navigated to Installed\r\nIntegrations\r\n<img width=\"1616\" alt=\"Screen Shot 2022-11-16 at 3 16 32 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11466284/202315280-d5b1d730-df82-4dbb-9da1-35b001683b27.png\">","sha":"6d4cadaeac4c68fc1e023f97e2ce0968af47e024"}},"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/145475","number":145475,"mergeCommit":{"message":"basic smoke test for Fleet installation package (#145475)\n\ncovers https://github.com/elastic/kibana/pull/144899\r\n\r\nchecks `Elastic Synthetics` shows up when navigated to Installed\r\nIntegrations\r\n<img width=\"1616\" alt=\"Screen Shot 2022-11-16 at 3 16 32 PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11466284/202315280-d5b1d730-df82-4dbb-9da1-35b001683b27.png\">","sha":"6d4cadaeac4c68fc1e023f97e2ce0968af47e024"}}]}] BACKPORT--> Co-authored-by: Rashmi Kulkarni <rashmi.kulkarni@elastic.co> |
\r\n\r\nAfter\r\n\r\n
