github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-21 00:13:52 -04:00
Code Issues Projects Releases Packages Wiki Activity
64916 commits 431 branches 495 tags 22 GiB
Commit graph

64916 commits

This branch
This branch
All branches
Author SHA1 Message Date
Devin W. Hurley
93797e65b4
[8.9] [Security Solution] [Detections] Fixes flakey exceptions read-only viewer cypress test (#162839) (#163766) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Detections] Fixes flakey exceptions read-only
viewer cypress test
(#162839)](https://github.com/elastic/kibana/pull/162839)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Devin W.
Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2023-08-12T03:35:20Z","message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#162839)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/162569\r\n\r\nThe test was
trying to load the exceptions tab before the rule details\r\npage
loaded. Now we wait for the rule tab to load before
continuing.\r\nSomething I was unaware of was that `cy.url()` will
[automatically\r\nretry](https://docs.cypress.io/api/commands/url#Assertions)
until all\r\nchained assertions have passed, which I think can be an
easy way to fix\r\nfuture flake issues where cypress tries to click on
an element before\r\nthe new page
loads.","sha":"7b3cc8f5735306d13113b0f75499f386fc0aec48","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Team:Detection
Engine","v8.10.0","v8.9.2"],"number":162839,"url":"https://github.com/elastic/kibana/pull/162839","mergeCommit":{"message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#162839)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/162569\r\n\r\nThe test was
trying to load the exceptions tab before the rule details\r\npage
loaded. Now we wait for the rule tab to load before
continuing.\r\nSomething I was unaware of was that `cy.url()` will
[automatically\r\nretry](https://docs.cypress.io/api/commands/url#Assertions)
until all\r\nchained assertions have passed, which I think can be an
easy way to fix\r\nfuture flake issues where cypress tries to click on
an element before\r\nthe new page
loads.","sha":"7b3cc8f5735306d13113b0f75499f386fc0aec48"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162839","number":162839,"mergeCommit":{"message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#162839)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/162569\r\n\r\nThe test was
trying to load the exceptions tab before the rule details\r\npage
loaded. Now we wait for the rule tab to load before
continuing.\r\nSomething I was unaware of was that `cy.url()` will
[automatically\r\nretry](https://docs.cypress.io/api/commands/url#Assertions)
until all\r\nchained assertions have passed, which I think can be an
easy way to fix\r\nfuture flake issues where cypress tries to click on
an element before\r\nthe new page
loads.","sha":"7b3cc8f5735306d13113b0f75499f386fc0aec48"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2023-08-12 16:09:42 -07:00
Kibana Machine
075824034c
[8.9] [controls] fix Dashboard getting stuck at loading in Kibana when Controls is used and mapping changed from integer to keyword (#163529) (#163750) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[controls] fix Dashboard getting stuck at loading in Kibana when
Controls is used and mapping changed from integer to keyword
(#163529)](https://github.com/elastic/kibana/pull/163529)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T19:58:19Z","message":"[controls]
fix Dashboard getting stuck at loading in Kibana when Controls is used
and mapping changed from integer to keyword (#163529)\n\nCloses
https://github.com/elastic/kibana/issues/162474\r\n\r\n### Changes\r\n*
RangeSliderEmbeddable - call setInitializationFinished
when\r\nrunRangeSliderQuery throws. This fixes the issue\r\n*
Investigated if OptionsListEmbeddable is vulnerable to the same
issue.\r\nIt's not because it uses its own REST API that has a service
wrapper\r\n`OptionsListService`. `OptionsListService` handles REST API
errors.\r\n* Add unit test verifying
OptionsListService.runOptionsListRequest does\r\nnot throw when there
are REST API errors and always returns a response.\r\n* Add unit tests
ensuring setInitializationFinished is called for
both\r\nRangeSliderEmbeddable and OptionsListEmbeddable in all
cases\r\n* Other clean up\r\n* Fix uses of `dataViewsService.get`.
`dataViewsService.get` throws when\r\ndata view is not found. It does
not return undefined. PR updates\r\nOptionsListEmbeddable,
RangeSliderEmbeddable, and mocked data service\r\n* Fix uses of
`dataView.getFieldByName`. `dataView.getFieldByName`\r\nreturns
undefined when field is not found and never throws. PR
updates\r\nOptionsListEmbeddable and RangeSliderEmbeddable\r\n * Remove
`resp` wrapper around mocked `fetch` results.\r\n\r\n### Test
instructions\r\n1) In console run \r\n ```\r\n PUT test1\r\n\r\n PUT
test1/_mapping\r\n {\r\n \"properties\": {\r\n \"value\": {\r\n
\"type\": \"integer\"\r\n }\r\n }\r\n }\r\n\r\n PUT test1/_doc/1\r\n
{\r\n \"value\" : 1\r\n }\r\n\r\n PUT test1/_doc/2\r\n {\r\n \"value\" :
10\r\n }\r\n ```\r\n2) create data view `test*`\r\n3) create dashboard
with range slider control on test*.value.\r\n4) select a range in the
range slider\r\n5) save dashboard\r\n6) run the following in console\r\n
```\r\n PUT test2\r\n\r\n PUT test2/_mapping\r\n {\r\n \"properties\":
{\r\n \"value\": {\r\n \"type\": \"keyword\"\r\n }\r\n }\r\n }\r\n\r\n
PUT test2/_doc/1\r\n {\r\n \"value\" : \"foo\"\r\n }\r\n\r\n DELETE
test1\r\n ```\r\n7) Open dashboard saved above. Verify dashboard opens
and control\r\ndisplays an error message about being unable to run
aggregation on\r\nkeyword field.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Devon Thomson
<devon.thomson@elastic.co>","sha":"0a74fa03a028e7002b5fdebdbfa7dc0c7283aa75","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Input
Control","Team:Presentation","v8.10.0","v8.9.2"],"number":163529,"url":"https://github.com/elastic/kibana/pull/163529","mergeCommit":{"message":"[controls]
fix Dashboard getting stuck at loading in Kibana when Controls is used
and mapping changed from integer to keyword (#163529)\n\nCloses
https://github.com/elastic/kibana/issues/162474\r\n\r\n### Changes\r\n*
RangeSliderEmbeddable - call setInitializationFinished
when\r\nrunRangeSliderQuery throws. This fixes the issue\r\n*
Investigated if OptionsListEmbeddable is vulnerable to the same
issue.\r\nIt's not because it uses its own REST API that has a service
wrapper\r\n`OptionsListService`. `OptionsListService` handles REST API
errors.\r\n* Add unit test verifying
OptionsListService.runOptionsListRequest does\r\nnot throw when there
are REST API errors and always returns a response.\r\n* Add unit tests
ensuring setInitializationFinished is called for
both\r\nRangeSliderEmbeddable and OptionsListEmbeddable in all
cases\r\n* Other clean up\r\n* Fix uses of `dataViewsService.get`.
`dataViewsService.get` throws when\r\ndata view is not found. It does
not return undefined. PR updates\r\nOptionsListEmbeddable,
RangeSliderEmbeddable, and mocked data service\r\n* Fix uses of
`dataView.getFieldByName`. `dataView.getFieldByName`\r\nreturns
undefined when field is not found and never throws. PR
updates\r\nOptionsListEmbeddable and RangeSliderEmbeddable\r\n * Remove
`resp` wrapper around mocked `fetch` results.\r\n\r\n### Test
instructions\r\n1) In console run \r\n ```\r\n PUT test1\r\n\r\n PUT
test1/_mapping\r\n {\r\n \"properties\": {\r\n \"value\": {\r\n
\"type\": \"integer\"\r\n }\r\n }\r\n }\r\n\r\n PUT test1/_doc/1\r\n
{\r\n \"value\" : 1\r\n }\r\n\r\n PUT test1/_doc/2\r\n {\r\n \"value\" :
10\r\n }\r\n ```\r\n2) create data view `test*`\r\n3) create dashboard
with range slider control on test*.value.\r\n4) select a range in the
range slider\r\n5) save dashboard\r\n6) run the following in console\r\n
```\r\n PUT test2\r\n\r\n PUT test2/_mapping\r\n {\r\n \"properties\":
{\r\n \"value\": {\r\n \"type\": \"keyword\"\r\n }\r\n }\r\n }\r\n\r\n
PUT test2/_doc/1\r\n {\r\n \"value\" : \"foo\"\r\n }\r\n\r\n DELETE
test1\r\n ```\r\n7) Open dashboard saved above. Verify dashboard opens
and control\r\ndisplays an error message about being unable to run
aggregation on\r\nkeyword field.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Devon Thomson
<devon.thomson@elastic.co>","sha":"0a74fa03a028e7002b5fdebdbfa7dc0c7283aa75"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163529","number":163529,"mergeCommit":{"message":"[controls]
fix Dashboard getting stuck at loading in Kibana when Controls is used
and mapping changed from integer to keyword (#163529)\n\nCloses
https://github.com/elastic/kibana/issues/162474\r\n\r\n### Changes\r\n*
RangeSliderEmbeddable - call setInitializationFinished
when\r\nrunRangeSliderQuery throws. This fixes the issue\r\n*
Investigated if OptionsListEmbeddable is vulnerable to the same
issue.\r\nIt's not because it uses its own REST API that has a service
wrapper\r\n`OptionsListService`. `OptionsListService` handles REST API
errors.\r\n* Add unit test verifying
OptionsListService.runOptionsListRequest does\r\nnot throw when there
are REST API errors and always returns a response.\r\n* Add unit tests
ensuring setInitializationFinished is called for
both\r\nRangeSliderEmbeddable and OptionsListEmbeddable in all
cases\r\n* Other clean up\r\n* Fix uses of `dataViewsService.get`.
`dataViewsService.get` throws when\r\ndata view is not found. It does
not return undefined. PR updates\r\nOptionsListEmbeddable,
RangeSliderEmbeddable, and mocked data service\r\n* Fix uses of
`dataView.getFieldByName`. `dataView.getFieldByName`\r\nreturns
undefined when field is not found and never throws. PR
updates\r\nOptionsListEmbeddable and RangeSliderEmbeddable\r\n * Remove
`resp` wrapper around mocked `fetch` results.\r\n\r\n### Test
instructions\r\n1) In console run \r\n ```\r\n PUT test1\r\n\r\n PUT
test1/_mapping\r\n {\r\n \"properties\": {\r\n \"value\": {\r\n
\"type\": \"integer\"\r\n }\r\n }\r\n }\r\n\r\n PUT test1/_doc/1\r\n
{\r\n \"value\" : 1\r\n }\r\n\r\n PUT test1/_doc/2\r\n {\r\n \"value\" :
10\r\n }\r\n ```\r\n2) create data view `test*`\r\n3) create dashboard
with range slider control on test*.value.\r\n4) select a range in the
range slider\r\n5) save dashboard\r\n6) run the following in console\r\n
```\r\n PUT test2\r\n\r\n PUT test2/_mapping\r\n {\r\n \"properties\":
{\r\n \"value\": {\r\n \"type\": \"keyword\"\r\n }\r\n }\r\n }\r\n\r\n
PUT test2/_doc/1\r\n {\r\n \"value\" : \"foo\"\r\n }\r\n\r\n DELETE
test1\r\n ```\r\n7) Open dashboard saved above. Verify dashboard opens
and control\r\ndisplays an error message about being unable to run
aggregation on\r\nkeyword field.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Devon Thomson
<devon.thomson@elastic.co>","sha":"0a74fa03a028e7002b5fdebdbfa7dc0c7283aa75"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
 2023-08-11 14:17:05 -07:00
Devon Thomson
b17767646a
[8.9] [Dashboard] Fix missing state on short URL alias match redirect (#163658) (#163746) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Dashboard] Fix missing state on short URL alias match redirect
(#163658)](https://github.com/elastic/kibana/pull/163658)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Devon
Thomson","email":"devon.thomson@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T16:15:18Z","message":"[Dashboard]
Fix missing state on short URL alias match redirect (#163658)\n\nFixes
an issue where URL state from short URLs could be lost on an alias match
redirect.","sha":"4de61111b14b59d2b57758a35ef47618c3a9ba46","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","release_note:fix","Team:Presentation","loe:hours","impact:high","backport:prev-minor","v8.10.0","v8.9.2"],"number":163658,"url":"https://github.com/elastic/kibana/pull/163658","mergeCommit":{"message":"[Dashboard]
Fix missing state on short URL alias match redirect (#163658)\n\nFixes
an issue where URL state from short URLs could be lost on an alias match
redirect.","sha":"4de61111b14b59d2b57758a35ef47618c3a9ba46"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163658","number":163658,"mergeCommit":{"message":"[Dashboard]
Fix missing state on short URL alias match redirect (#163658)\n\nFixes
an issue where URL state from short URLs could be lost on an alias match
redirect.","sha":"4de61111b14b59d2b57758a35ef47618c3a9ba46"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2023-08-11 13:41:35 -06:00
Kibana Machine
f237760b79
[8.9] Adjust global loading indicator data-test-subj for projects (#163697) (#163745) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [Adjust global loading indicator data-test-subj for projects
(#163697)](https://github.com/elastic/kibana/pull/163697)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T17:40:26Z","message":"Adjust
global loading indicator data-test-subj for projects (#163697)\n\n##
Summary\r\n\r\nThis PR adjusts the `data-test-subj` for the global
loading indicator in\r\nserverless projects such that at matches the
stateful version. This\r\nmakes sure that functional tests and
corresponding test helper methods\r\ncontinue to work the same in
stateful and serverless environments when\r\ncomes to waiting for global
loading to finish, which is a key mechanism\r\nto avoid test
flakiness.\r\n\r\n### Additional information\r\n\r\n- The serverless
project specific global loading indicator was\r\nintroduced with
#158523\r\n- The stateful loading indicator `data-test-subj` naming is
implemented\r\nhere:\r\nhttps://github.com/elastic/kibana/blob/main/packages/core/chrome/core-chrome-browser-internal/src/ui/loading_indicator.tsx#L61\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"fd08c62f052d065e677b670a381840ae80dc9724","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.10.0","v8.9.1"],"number":163697,"url":"https://github.com/elastic/kibana/pull/163697","mergeCommit":{"message":"Adjust
global loading indicator data-test-subj for projects (#163697)\n\n##
Summary\r\n\r\nThis PR adjusts the `data-test-subj` for the global
loading indicator in\r\nserverless projects such that at matches the
stateful version. This\r\nmakes sure that functional tests and
corresponding test helper methods\r\ncontinue to work the same in
stateful and serverless environments when\r\ncomes to waiting for global
loading to finish, which is a key mechanism\r\nto avoid test
flakiness.\r\n\r\n### Additional information\r\n\r\n- The serverless
project specific global loading indicator was\r\nintroduced with
#158523\r\n- The stateful loading indicator `data-test-subj` naming is
implemented\r\nhere:\r\nhttps://github.com/elastic/kibana/blob/main/packages/core/chrome/core-chrome-browser-internal/src/ui/loading_indicator.tsx#L61\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"fd08c62f052d065e677b670a381840ae80dc9724"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163697","number":163697,"mergeCommit":{"message":"Adjust
global loading indicator data-test-subj for projects (#163697)\n\n##
Summary\r\n\r\nThis PR adjusts the `data-test-subj` for the global
loading indicator in\r\nserverless projects such that at matches the
stateful version. This\r\nmakes sure that functional tests and
corresponding test helper methods\r\ncontinue to work the same in
stateful and serverless environments when\r\ncomes to waiting for global
loading to finish, which is a key mechanism\r\nto avoid test
flakiness.\r\n\r\n### Additional information\r\n\r\n- The serverless
project specific global loading indicator was\r\nintroduced with
#158523\r\n- The stateful loading indicator `data-test-subj` naming is
implemented\r\nhere:\r\nhttps://github.com/elastic/kibana/blob/main/packages/core/chrome/core-chrome-browser-internal/src/ui/loading_indicator.tsx#L61\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"fd08c62f052d065e677b670a381840ae80dc9724"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
 2023-08-11 11:53:44 -07:00
Walter Rafelsberger
6cfb565d5b
[8.9] [ML] Transforms: Fix privileges check. (#163687) (#163725) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[ML] Transforms: Fix privileges check.
(#163687)](https://github.com/elastic/kibana/pull/163687)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T13:46:56Z","message":"[ML]
Transforms: Fix privileges check. (#163687)\n\nFixes a regression
introduced in #154007.\r\n\r\nWhen security is disabled, the check for
transform\r\nprivileges/capabilities would fail and the transform page
would not\r\nrender.\r\n\r\n- This fixes the endpoint to return data in
the correct format should\r\nsecurity be disabled.\r\n- The endpoint's
TypeScript has been updated to catch malformed\r\nresponses.\r\n- The
client side custom `useRequest` is replaced with `useQuery`
from\r\n`'@tanstack/react-query'` which also fixes TypeScript support on
the\r\nclient
side.","sha":"ecaa8a73707f97c99ef2d57574ac3dcbac3096df","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Transforms","v8.10.0","v8.9.2"],"number":163687,"url":"https://github.com/elastic/kibana/pull/163687","mergeCommit":{"message":"[ML]
Transforms: Fix privileges check. (#163687)\n\nFixes a regression
introduced in #154007.\r\n\r\nWhen security is disabled, the check for
transform\r\nprivileges/capabilities would fail and the transform page
would not\r\nrender.\r\n\r\n- This fixes the endpoint to return data in
the correct format should\r\nsecurity be disabled.\r\n- The endpoint's
TypeScript has been updated to catch malformed\r\nresponses.\r\n- The
client side custom `useRequest` is replaced with `useQuery`
from\r\n`'@tanstack/react-query'` which also fixes TypeScript support on
the\r\nclient
side.","sha":"ecaa8a73707f97c99ef2d57574ac3dcbac3096df"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163687","number":163687,"mergeCommit":{"message":"[ML]
Transforms: Fix privileges check. (#163687)\n\nFixes a regression
introduced in #154007.\r\n\r\nWhen security is disabled, the check for
transform\r\nprivileges/capabilities would fail and the transform page
would not\r\nrender.\r\n\r\n- This fixes the endpoint to return data in
the correct format should\r\nsecurity be disabled.\r\n- The endpoint's
TypeScript has been updated to catch malformed\r\nresponses.\r\n- The
client side custom `useRequest` is replaced with `useQuery`
from\r\n`'@tanstack/react-query'` which also fixes TypeScript support on
the\r\nclient
side.","sha":"ecaa8a73707f97c99ef2d57574ac3dcbac3096df"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2023-08-11 08:34:19 -07:00
Kibana Machine
5c5c2daa00
[8.9] [FTR] Implement browser network condition utils (#163633) (#163703) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[FTR] Implement browser network condition utils
(#163633)](https://github.com/elastic/kibana/pull/163633)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Marco Antonio
Ghiani","email":"marcoantonio.ghiani01@gmail.com"},"sourceCommit":{"committedDate":"2023-08-11T12:24:06Z","message":"[FTR]
Implement browser network condition utils (#163633)\n\n## 📓
Summary\r\n\r\nThe PR implements some utilities into the `browser`
service to allow\r\ncontrolling the network conditions during the
execution of a functional\r\ntest.\r\n\r\n###
`getNetworkConditions`\r\n\r\nReturns the current network simulation
options. If none conditions are\r\npreviously set, it returns
`undefined`\r\n\r\n**N.B.**: _if the testing environment is not a
Chromium browser, it\r\nthrows an error that can be easily caught to
manually skip the test or\r\nhandle a fallback
scenario._\r\n\r\n\r\n```ts\r\nit('should display a loading skeleton
while loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n const networkConditions
= await browser.getNetworkConditions(); // undefined\r\n\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n\r\n const networkConditions
= await browser.getNetworkConditions();\r\n // {\r\n // offline:
false,\r\n // latency: 2000,\r\n // download_throughput: 50000,\r\n //
upload_throughput: 50000,\r\n // }\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
`setNetworkConditions`\r\n\r\nSet the desired network conditions.\r\nIt
supports different presets that match the [network profiles
provided\r\nby
Chrome\r\ndebugger](da276a3fae/front_end/core/sdk/NetworkManager.ts (L363-L393)):\r\n-
`NO_THROTTLING`\r\n- `FAST_3G`\r\n- `SLOW_3G`\r\n- `OFFLINE`\r\n-
`CLOUD_USER` (pre-existing)\r\nIt also accepts ad-hoc options to
configure more specifically the\r\nnetwork conditions.\r\n\r\n**N.B.**:
_if the testing environment is not a Chromium browser, it\r\nthrows an
error that can be easily caught to manually skip the test or\r\nhandle a
fallback scenario._\r\n\r\n```ts\r\nit('should display a loading
skeleton while loading', async function () {\r\n // Skip the test in
case network condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('NO_THROTTLING');\r\n await
browser.setNetworkConditions('FAST_3G');\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n await
browser.setNetworkConditions('OFFLINE');\r\n await
browser.setNetworkConditions('CLOUD_USER');\r\n await
browser.setNetworkConditions({\r\n offline: false,\r\n latency: 5, //
Additional latency (ms).\r\n download_throughput: 500 * 1024, // Maximal
aggregated download throughput.\r\n upload_throughput: 500 * 1024, //
Maximal aggregated upload throughput.\r\n });\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
restoreNetworkConditions\r\n\r\nRestore the original network conditions,
setting to `NO_THROTTLING`.\r\nThe native implementation of
`deleteNetworkConditions` exposed by\r\nselenium is unofficial and
didn't consistently work, the recommended\r\napproach by the google dev
tools team is to restore the connection\r\nsetting the no throttling
profile.\r\n\r\n**N.B.**: _if the testing environment is not a Chromium
browser, it\r\nthrows an error that can be easily caught to manually
skip the test or\r\nhandle a fallback
scenario._\r\n\r\n```ts\r\nit('should display a loading skeleton while
loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('SLOW_3G'); // Slow down network
conditions\r\n \r\n // Do your assertions\r\n\r\n await
browser.restoreNetworkConditions(); // Restore network conditions\r\n }
catch (error) {\r\n this.skip();\r\n
}\r\n});\r\n```\r\n\r\nCo-authored-by: Marco Antonio Ghiani
<marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"aa45152a4e787f36014675b864fcc0fce7bd6758","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.10.0","v7.17.13","v8.9.2"],"number":163633,"url":"https://github.com/elastic/kibana/pull/163633","mergeCommit":{"message":"[FTR]
Implement browser network condition utils (#163633)\n\n## 📓
Summary\r\n\r\nThe PR implements some utilities into the `browser`
service to allow\r\ncontrolling the network conditions during the
execution of a functional\r\ntest.\r\n\r\n###
`getNetworkConditions`\r\n\r\nReturns the current network simulation
options. If none conditions are\r\npreviously set, it returns
`undefined`\r\n\r\n**N.B.**: _if the testing environment is not a
Chromium browser, it\r\nthrows an error that can be easily caught to
manually skip the test or\r\nhandle a fallback
scenario._\r\n\r\n\r\n```ts\r\nit('should display a loading skeleton
while loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n const networkConditions
= await browser.getNetworkConditions(); // undefined\r\n\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n\r\n const networkConditions
= await browser.getNetworkConditions();\r\n // {\r\n // offline:
false,\r\n // latency: 2000,\r\n // download_throughput: 50000,\r\n //
upload_throughput: 50000,\r\n // }\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
`setNetworkConditions`\r\n\r\nSet the desired network conditions.\r\nIt
supports different presets that match the [network profiles
provided\r\nby
Chrome\r\ndebugger](da276a3fae/front_end/core/sdk/NetworkManager.ts (L363-L393)):\r\n-
`NO_THROTTLING`\r\n- `FAST_3G`\r\n- `SLOW_3G`\r\n- `OFFLINE`\r\n-
`CLOUD_USER` (pre-existing)\r\nIt also accepts ad-hoc options to
configure more specifically the\r\nnetwork conditions.\r\n\r\n**N.B.**:
_if the testing environment is not a Chromium browser, it\r\nthrows an
error that can be easily caught to manually skip the test or\r\nhandle a
fallback scenario._\r\n\r\n```ts\r\nit('should display a loading
skeleton while loading', async function () {\r\n // Skip the test in
case network condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('NO_THROTTLING');\r\n await
browser.setNetworkConditions('FAST_3G');\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n await
browser.setNetworkConditions('OFFLINE');\r\n await
browser.setNetworkConditions('CLOUD_USER');\r\n await
browser.setNetworkConditions({\r\n offline: false,\r\n latency: 5, //
Additional latency (ms).\r\n download_throughput: 500 * 1024, // Maximal
aggregated download throughput.\r\n upload_throughput: 500 * 1024, //
Maximal aggregated upload throughput.\r\n });\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
restoreNetworkConditions\r\n\r\nRestore the original network conditions,
setting to `NO_THROTTLING`.\r\nThe native implementation of
`deleteNetworkConditions` exposed by\r\nselenium is unofficial and
didn't consistently work, the recommended\r\napproach by the google dev
tools team is to restore the connection\r\nsetting the no throttling
profile.\r\n\r\n**N.B.**: _if the testing environment is not a Chromium
browser, it\r\nthrows an error that can be easily caught to manually
skip the test or\r\nhandle a fallback
scenario._\r\n\r\n```ts\r\nit('should display a loading skeleton while
loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('SLOW_3G'); // Slow down network
conditions\r\n \r\n // Do your assertions\r\n\r\n await
browser.restoreNetworkConditions(); // Restore network conditions\r\n }
catch (error) {\r\n this.skip();\r\n
}\r\n});\r\n```\r\n\r\nCo-authored-by: Marco Antonio Ghiani
<marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"aa45152a4e787f36014675b864fcc0fce7bd6758"}},"sourceBranch":"main","suggestedTargetBranches":["7.17","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163633","number":163633,"mergeCommit":{"message":"[FTR]
Implement browser network condition utils (#163633)\n\n## 📓
Summary\r\n\r\nThe PR implements some utilities into the `browser`
service to allow\r\ncontrolling the network conditions during the
execution of a functional\r\ntest.\r\n\r\n###
`getNetworkConditions`\r\n\r\nReturns the current network simulation
options. If none conditions are\r\npreviously set, it returns
`undefined`\r\n\r\n**N.B.**: _if the testing environment is not a
Chromium browser, it\r\nthrows an error that can be easily caught to
manually skip the test or\r\nhandle a fallback
scenario._\r\n\r\n\r\n```ts\r\nit('should display a loading skeleton
while loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n const networkConditions
= await browser.getNetworkConditions(); // undefined\r\n\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n\r\n const networkConditions
= await browser.getNetworkConditions();\r\n // {\r\n // offline:
false,\r\n // latency: 2000,\r\n // download_throughput: 50000,\r\n //
upload_throughput: 50000,\r\n // }\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
`setNetworkConditions`\r\n\r\nSet the desired network conditions.\r\nIt
supports different presets that match the [network profiles
provided\r\nby
Chrome\r\ndebugger](da276a3fae/front_end/core/sdk/NetworkManager.ts (L363-L393)):\r\n-
`NO_THROTTLING`\r\n- `FAST_3G`\r\n- `SLOW_3G`\r\n- `OFFLINE`\r\n-
`CLOUD_USER` (pre-existing)\r\nIt also accepts ad-hoc options to
configure more specifically the\r\nnetwork conditions.\r\n\r\n**N.B.**:
_if the testing environment is not a Chromium browser, it\r\nthrows an
error that can be easily caught to manually skip the test or\r\nhandle a
fallback scenario._\r\n\r\n```ts\r\nit('should display a loading
skeleton while loading', async function () {\r\n // Skip the test in
case network condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('NO_THROTTLING');\r\n await
browser.setNetworkConditions('FAST_3G');\r\n await
browser.setNetworkConditions('SLOW_3G');\r\n await
browser.setNetworkConditions('OFFLINE');\r\n await
browser.setNetworkConditions('CLOUD_USER');\r\n await
browser.setNetworkConditions({\r\n offline: false,\r\n latency: 5, //
Additional latency (ms).\r\n download_throughput: 500 * 1024, // Maximal
aggregated download throughput.\r\n upload_throughput: 500 * 1024, //
Maximal aggregated upload throughput.\r\n });\r\n } catch (error) {\r\n
this.skip();\r\n }\r\n});\r\n```\r\n\r\n###
restoreNetworkConditions\r\n\r\nRestore the original network conditions,
setting to `NO_THROTTLING`.\r\nThe native implementation of
`deleteNetworkConditions` exposed by\r\nselenium is unofficial and
didn't consistently work, the recommended\r\napproach by the google dev
tools team is to restore the connection\r\nsetting the no throttling
profile.\r\n\r\n**N.B.**: _if the testing environment is not a Chromium
browser, it\r\nthrows an error that can be easily caught to manually
skip the test or\r\nhandle a fallback
scenario._\r\n\r\n```ts\r\nit('should display a loading skeleton while
loading', async function () {\r\n // Skip the test in case network
condition utils are not available\r\n try {\r\n await
browser.setNetworkConditions('SLOW_3G'); // Slow down network
conditions\r\n \r\n // Do your assertions\r\n\r\n await
browser.restoreNetworkConditions(); // Restore network conditions\r\n }
catch (error) {\r\n this.skip();\r\n
}\r\n});\r\n```\r\n\r\nCo-authored-by: Marco Antonio Ghiani
<marcoantonio.ghiani@elastic.co>\r\nCo-authored-by: Dzmitry Lemechko
<dzmitry.lemechko@elastic.co>","sha":"aa45152a4e787f36014675b864fcc0fce7bd6758"}},{"branch":"7.17","label":"v7.17.13","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com>
 2023-08-11 06:36:38 -07:00
Kibana Machine
2bc538692a
[8.9] [DOCS] Adds the release notes for the 8.9.1 release. (#163578) (#163708) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Adds the release notes for the 8.9.1 release.
(#163578)](https://github.com/elastic/kibana/pull/163578)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-11T13:03:10Z","message":"[DOCS]
Adds the release notes for the 8.9.1 release. (#163578)\n\n##
Summary\r\n\r\nAdds the release notes for the 8.9.1
release.\r\n\r\nCloses:#163565","sha":"9bc2150c789fef4f8ddf5c3ee329a971e4e0c8cb","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v8.10.0","v8.9.1"],"number":163578,"url":"https://github.com/elastic/kibana/pull/163578","mergeCommit":{"message":"[DOCS]
Adds the release notes for the 8.9.1 release. (#163578)\n\n##
Summary\r\n\r\nAdds the release notes for the 8.9.1
release.\r\n\r\nCloses:#163565","sha":"9bc2150c789fef4f8ddf5c3ee329a971e4e0c8cb"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163578","number":163578,"mergeCommit":{"message":"[DOCS]
Adds the release notes for the 8.9.1 release. (#163578)\n\n##
Summary\r\n\r\nAdds the release notes for the 8.9.1
release.\r\n\r\nCloses:#163565","sha":"9bc2150c789fef4f8ddf5c3ee329a971e4e0c8cb"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
 2023-08-11 09:25:52 -04:00
Jatin Kathuria
c375c78160
[8.9] [Security Solution][Investigations] - skip failing tests (#163322) (#163584) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Investigations] - skip failing tests
(#163322)](https://github.com/elastic/kibana/pull/163322)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Michael
Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T16:19:23Z","message":"[Security
Solution][Investigations] - skip failing tests (#163322)\n\n##
Summary\r\n\r\nTests have been failing intermittently on CI. Skipping
for now while we\r\ninvestigate the issue\r\n\r\nFailure
example:\r\nhttps://buildkite.com/elastic/kibana-pull-request/builds/147846#0189cfa6-5aa6-44af-a3ae-2314b16007f9\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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)","sha":"2231d7c1328238fb71fa501aaf6dc69111c79a1c","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-failure-flaky","Team:Threat
Hunting:Investigations","backport:prev-minor","v8.10.0","v8.9.1"],"number":163322,"url":"https://github.com/elastic/kibana/pull/163322","mergeCommit":{"message":"[Security
Solution][Investigations] - skip failing tests (#163322)\n\n##
Summary\r\n\r\nTests have been failing intermittently on CI. Skipping
for now while we\r\ninvestigate the issue\r\n\r\nFailure
example:\r\nhttps://buildkite.com/elastic/kibana-pull-request/builds/147846#0189cfa6-5aa6-44af-a3ae-2314b16007f9\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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)","sha":"2231d7c1328238fb71fa501aaf6dc69111c79a1c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163322","number":163322,"mergeCommit":{"message":"[Security
Solution][Investigations] - skip failing tests (#163322)\n\n##
Summary\r\n\r\nTests have been failing intermittently on CI. Skipping
for now while we\r\ninvestigate the issue\r\n\r\nFailure
example:\r\nhttps://buildkite.com/elastic/kibana-pull-request/builds/147846#0189cfa6-5aa6-44af-a3ae-2314b16007f9\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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)","sha":"2231d7c1328238fb71fa501aaf6dc69111c79a1c"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/163396","number":163396,"state":"OPEN"}]}]
BACKPORT-->

---------

Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co>
 2023-08-11 08:20:57 -04:00
Kibana Machine
55f90c095e
[8.9] [Enterprise Search] Update Workplace Search connectors doclink (#163676) (#163686) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Enterprise Search] Update Workplace Search connectors doclink
(#163676)](https://github.com/elastic/kibana/pull/163676)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Liam
Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-11T09:27:26Z","message":"[Enterprise
Search] Update Workplace Search connectors doclink (#163676)\n\nSmall
URL
update.","sha":"c8e5741a0b4722d1adb8e532ab2997b30d664fc1","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.10.0"],"number":163676,"url":"https://github.com/elastic/kibana/pull/163676","mergeCommit":{"message":"[Enterprise
Search] Update Workplace Search connectors doclink (#163676)\n\nSmall
URL
update.","sha":"c8e5741a0b4722d1adb8e532ab2997b30d664fc1"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163676","number":163676,"mergeCommit":{"message":"[Enterprise
Search] Update Workplace Search connectors doclink (#163676)\n\nSmall
URL update.","sha":"c8e5741a0b4722d1adb8e532ab2997b30d664fc1"}}]}]
BACKPORT-->

Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
 2023-08-11 03:42:36 -07:00
Kibana Machine
fd28e1182d
[8.9] [Flaky #118272] Unskip tests (#163319) (#163680) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Flaky #118272] Unskip tests
(#163319)](https://github.com/elastic/kibana/pull/163319)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T08:32:32Z","message":"[Flaky
#118272] Unskip tests
(#163319)","sha":"5de69cb567e8f6fde93f09b839710e1ee8a3cc72","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","technical
debt","release_note:skip","backport:all-open","v8.10.0"],"number":163319,"url":"https://github.com/elastic/kibana/pull/163319","mergeCommit":{"message":"[Flaky
#118272] Unskip tests
(#163319)","sha":"5de69cb567e8f6fde93f09b839710e1ee8a3cc72"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163319","number":163319,"mergeCommit":{"message":"[Flaky
#118272] Unskip tests
(#163319)","sha":"5de69cb567e8f6fde93f09b839710e1ee8a3cc72"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
 2023-08-11 02:32:26 -07:00
Kibana Machine
0d8ff48975
[8.9] Flaky test: Detection rule telemetry #162407 (#162681) (#163675) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [Flaky test: Detection rule telemetry #162407
(#162681)](https://github.com/elastic/kibana/pull/162681)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Ievgen
Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2023-07-31T09:43:54Z","message":"Flaky
test: Detection rule telemetry #162407 (#162681)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156088\r\n\r\nIt looks like
flakiness happens due to another rule from previous test\r\ncase being
scheduled by alerting framework and running even after we\r\ndeleted it
(since we called delete rule after it was scheduled). That\r\nrule
scheduled earlier produces some unexpected artifacts in
metrics,\r\nspecifically `stats.detection_rules.detection_rule_status`
where\r\noccasionally see\r\n\r\n<img width=\"1255\" alt=\"Screenshot
2023-07-25 at 15 13
29\"\r\nsrc=\"5d1cc334-25b5-4bf2-8822-c9858a0b72bf\">\r\n\r\nSince,
in this test case the rule is disabled, we should not see
this\r\ndata.\r\n\r\nAs a fix, we decided to test against specific
metrics attributes\r\n`stats.detection_rules.detection_rule_usage` which
we expect
being\r\nupdated.","sha":"9036b15be0c75e3541738d6d121bc2583affd447","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-failure-flaky","backport:prev-minor","Team:Detection
Engine","v8.10.0"],"number":162681,"url":"https://github.com/elastic/kibana/pull/162681","mergeCommit":{"message":"Flaky
test: Detection rule telemetry #162407 (#162681)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156088\r\n\r\nIt looks like
flakiness happens due to another rule from previous test\r\ncase being
scheduled by alerting framework and running even after we\r\ndeleted it
(since we called delete rule after it was scheduled). That\r\nrule
scheduled earlier produces some unexpected artifacts in
metrics,\r\nspecifically `stats.detection_rules.detection_rule_status`
where\r\noccasionally see\r\n\r\n<img width=\"1255\" alt=\"Screenshot
2023-07-25 at 15 13
29\"\r\nsrc=\"5d1cc334-25b5-4bf2-8822-c9858a0b72bf\">\r\n\r\nSince,
in this test case the rule is disabled, we should not see
this\r\ndata.\r\n\r\nAs a fix, we decided to test against specific
metrics attributes\r\n`stats.detection_rules.detection_rule_usage` which
we expect
being\r\nupdated.","sha":"9036b15be0c75e3541738d6d121bc2583affd447"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162681","number":162681,"mergeCommit":{"message":"Flaky
test: Detection rule telemetry #162407 (#162681)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156088\r\n\r\nIt looks like
flakiness happens due to another rule from previous test\r\ncase being
scheduled by alerting framework and running even after we\r\ndeleted it
(since we called delete rule after it was scheduled). That\r\nrule
scheduled earlier produces some unexpected artifacts in
metrics,\r\nspecifically `stats.detection_rules.detection_rule_status`
where\r\noccasionally see\r\n\r\n<img width=\"1255\" alt=\"Screenshot
2023-07-25 at 15 13
29\"\r\nsrc=\"5d1cc334-25b5-4bf2-8822-c9858a0b72bf\">\r\n\r\nSince,
in this test case the rule is disabled, we should not see
this\r\ndata.\r\n\r\nAs a fix, we decided to test against specific
metrics attributes\r\n`stats.detection_rules.detection_rule_usage` which
we expect
being\r\nupdated.","sha":"9036b15be0c75e3541738d6d121bc2583affd447"}}]}]
BACKPORT-->

Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
 2023-08-11 01:13:51 -07:00
Kibana Machine
393b4e318b
[8.9] [DOCS] Fix event.values URL template var desc (#163507) (#163651) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Fix `event.values` URL template var desc
(#163507)](https://github.com/elastic/kibana/pull/163507)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"James
Rodewig","email":"james.rodewig@elastic.co"},"sourceCommit":{"committedDate":"2023-08-10T18:32:55Z","message":"[DOCS]
Fix `event.values` URL template var desc
(#163507)","sha":"37a53b69cfbce11344103199bb4b751d2313dde8","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","docs","v8.3.0","v8.4.0","v8.5.0","v8.6.0","v8.7.0","v8.8.0","v8.10.0","v8.9.1"],"number":163507,"url":"https://github.com/elastic/kibana/pull/163507","mergeCommit":{"message":"[DOCS]
Fix `event.values` URL template var desc
(#163507)","sha":"37a53b69cfbce11344103199bb4b751d2313dde8"}},"sourceBranch":"main","suggestedTargetBranches":["8.3","8.4","8.5","8.6","8.7","8.8","8.9"],"targetPullRequestStates":[{"branch":"8.3","label":"v8.3.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.4","label":"v8.4.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.5","label":"v8.5.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163507","number":163507,"mergeCommit":{"message":"[DOCS]
Fix `event.values` URL template var desc
(#163507)","sha":"37a53b69cfbce11344103199bb4b751d2313dde8"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
 2023-08-10 15:07:39 -04:00
Kibana Machine
fc94811899
[8.9] fix(NA): yarn env vars for node_modules mirrors (#163549) (#163617) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [fix(NA): yarn env vars for node_modules mirrors
(#163549)](https://github.com/elastic/kibana/pull/163549)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2023-08-10T14:35:34Z","message":"fix(NA):
yarn env vars for node_modules mirrors (#163549)\n\nThis PR fixes the
setup we have for the node_module mirrors vars that\r\nare overriding
and pointing into our middle cache. The previous\r\nconfiguration was
not working as intended as the env vars set globally\r\non CI never
ended up in the bazel managed yarn install.\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"17936ffd21d4b4b274d2cda90902764ed0d4ae07","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.10.0"],"number":163549,"url":"https://github.com/elastic/kibana/pull/163549","mergeCommit":{"message":"fix(NA):
yarn env vars for node_modules mirrors (#163549)\n\nThis PR fixes the
setup we have for the node_module mirrors vars that\r\nare overriding
and pointing into our middle cache. The previous\r\nconfiguration was
not working as intended as the env vars set globally\r\non CI never
ended up in the bazel managed yarn install.\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"17936ffd21d4b4b274d2cda90902764ed0d4ae07"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163549","number":163549,"mergeCommit":{"message":"fix(NA):
yarn env vars for node_modules mirrors (#163549)\n\nThis PR fixes the
setup we have for the node_module mirrors vars that\r\nare overriding
and pointing into our middle cache. The previous\r\nconfiguration was
not working as intended as the env vars set globally\r\non CI never
ended up in the bazel managed yarn install.\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"17936ffd21d4b4b274d2cda90902764ed0d4ae07"}}]}]
BACKPORT-->

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
 2023-08-10 08:54:50 -07:00
Jeramy Soucy
0559e6636e
[8.9] Bump elastic-apm-node 3.49.0 -> 3.49.1 (#163522) (#163541) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [Bump elastic-apm-node 3.49.0 -> 3.49.1
(#163522)](https://github.com/elastic/kibana/pull/163522)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-08-09T20:39:34Z","message":"Bump
elastic-apm-node 3.49.0 -> 3.49.1 (#163522)\n\n##
Summary\r\n\r\nUpgrades `elastic-apm-node` from 3.49.0 to
3.49.1","sha":"53965c97a1176127916870d2ac01f2ec2fdb95bb","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:all-open","v8.10.0"],"number":163522,"url":"https://github.com/elastic/kibana/pull/163522","mergeCommit":{"message":"Bump
elastic-apm-node 3.49.0 -> 3.49.1 (#163522)\n\n##
Summary\r\n\r\nUpgrades `elastic-apm-node` from 3.49.0 to
3.49.1","sha":"53965c97a1176127916870d2ac01f2ec2fdb95bb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163522","number":163522,"mergeCommit":{"message":"Bump
elastic-apm-node 3.49.0 -> 3.49.1 (#163522)\n\n##
Summary\r\n\r\nUpgrades `elastic-apm-node` from 3.49.0 to
3.49.1","sha":"53965c97a1176127916870d2ac01f2ec2fdb95bb"}}]}]
BACKPORT-->
 2023-08-10 16:37:51 +01:00
Shahzad
6c664aeb22
[8.9] [Synthetics] Fix 404 not found monitor view (#163501) (#163534) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Fix 404 not found monitor view
(#163501)](https://github.com/elastic/kibana/pull/163501)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-08-09T16:21:37Z","message":"[Synthetics]
Fix 404 not found monitor view
(#163501)","sha":"9d6ebdda4e630f0973ab6ece2803a878cea09227","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:uptime","v8.10.0","v8.9.1"],"number":163501,"url":"https://github.com/elastic/kibana/pull/163501","mergeCommit":{"message":"[Synthetics]
Fix 404 not found monitor view
(#163501)","sha":"9d6ebdda4e630f0973ab6ece2803a878cea09227"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163501","number":163501,"mergeCommit":{"message":"[Synthetics]
Fix 404 not found monitor view
(#163501)","sha":"9d6ebdda4e630f0973ab6ece2803a878cea09227"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2023-08-10 10:39:45 +02:00
Kibana Machine
86f579d9e3
[8.9] [FTR] unskip tsvb time series tests for Chrome (#163510) (#163555) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[FTR] unskip tsvb time series tests for Chrome
(#163510)](https://github.com/elastic/kibana/pull/163510)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-08-10T07:17:12Z","message":"[FTR]
unskip tsvb time series tests for Chrome (#163510)\n\n##
Summary\r\n\r\nRelated to #162995\r\n\r\nThis PR unskip TSVB tests for
Chrome browser since it is proved to
be\r\nstable\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2836\r\n100x
passed\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2835\r\n100x
passed\r\nOn Firefox the flakiness is related to Terms 2nd aggregation
field\r\nsometimes is not selected. I tested it manually in Firefox 116
and was\r\nable to set fields, though I have a feeling that values are
not always\r\nselected on click in the drop-down. But I didn't see any
errors in\r\nconsole.\r\n\r\nI also returned back retry for dropdown
selection I removed in #161202\r\nthough flaky-test-runner proves there
is no need. Let's have just to\r\nkeep logic as before my
PR.","sha":"072ad967fc04e2b79bf75fd9e6618f3bf0e46b9f","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.10.0","v8.9.1"],"number":163510,"url":"https://github.com/elastic/kibana/pull/163510","mergeCommit":{"message":"[FTR]
unskip tsvb time series tests for Chrome (#163510)\n\n##
Summary\r\n\r\nRelated to #162995\r\n\r\nThis PR unskip TSVB tests for
Chrome browser since it is proved to
be\r\nstable\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2836\r\n100x
passed\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2835\r\n100x
passed\r\nOn Firefox the flakiness is related to Terms 2nd aggregation
field\r\nsometimes is not selected. I tested it manually in Firefox 116
and was\r\nable to set fields, though I have a feeling that values are
not always\r\nselected on click in the drop-down. But I didn't see any
errors in\r\nconsole.\r\n\r\nI also returned back retry for dropdown
selection I removed in #161202\r\nthough flaky-test-runner proves there
is no need. Let's have just to\r\nkeep logic as before my
PR.","sha":"072ad967fc04e2b79bf75fd9e6618f3bf0e46b9f"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163510","number":163510,"mergeCommit":{"message":"[FTR]
unskip tsvb time series tests for Chrome (#163510)\n\n##
Summary\r\n\r\nRelated to #162995\r\n\r\nThis PR unskip TSVB tests for
Chrome browser since it is proved to
be\r\nstable\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2836\r\n100x
passed\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2835\r\n100x
passed\r\nOn Firefox the flakiness is related to Terms 2nd aggregation
field\r\nsometimes is not selected. I tested it manually in Firefox 116
and was\r\nable to set fields, though I have a feeling that values are
not always\r\nselected on click in the drop-down. But I didn't see any
errors in\r\nconsole.\r\n\r\nI also returned back retry for dropdown
selection I removed in #161202\r\nthough flaky-test-runner proves there
is no need. Let's have just to\r\nkeep logic as before my
PR.","sha":"072ad967fc04e2b79bf75fd9e6618f3bf0e46b9f"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2023-08-10 01:30:27 -07:00
Stratoula Kalafateli
f343ff6a54
[8.9] [TSVB] Unskip tsdb tests (#163471) (#163553) 
# Backport

Closes https://github.com/elastic/kibana/issues/163454

This will backport the following commits from `main` to `8.9`:
- [[TSVB] Unskip tsdb tests
(#163471)](https://github.com/elastic/kibana/pull/163471)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2023-08-09T11:16:02Z","message":"[TSVB]
Unskip tsdb tests (#163471)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/163454\r\n\r\nNow ES doesnt
error out for average aggregation in counter fields. So we\r\ncan remove
the test for this
scenario","sha":"4fc9906c17206a67426e743984d8d628f7b14321","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:TSVB","Team:Visualizations","failed-test","release_note:skip","backport:skip","v8.10.0"],"number":163471,"url":"https://github.com/elastic/kibana/pull/163471","mergeCommit":{"message":"[TSVB]
Unskip tsdb tests (#163471)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/163454\r\n\r\nNow ES doesnt
error out for average aggregation in counter fields. So we\r\ncan remove
the test for this
scenario","sha":"4fc9906c17206a67426e743984d8d628f7b14321"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163471","number":163471,"mergeCommit":{"message":"[TSVB]
Unskip tsdb tests (#163471)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/163454\r\n\r\nNow ES doesnt
error out for average aggregation in counter fields. So we\r\ncan remove
the test for this
scenario","sha":"4fc9906c17206a67426e743984d8d628f7b14321"}}]}]
BACKPORT-->
 2023-08-10 09:53:14 +02:00
Jon
ee7361032e
[8.9] Upgrade Node.js to 16.20.2 (#163539) 
https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V16.md#16.20.2
 2023-08-09 14:19:54 -07:00
Kibana Machine
9c97e5bfc4
[8.9] chore(NA): upgrade chromedriver to v115 (#163520) (#163536) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [chore(NA): upgrade chromedriver to v115
(#163520)](https://github.com/elastic/kibana/pull/163520)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2023-08-09T19:28:41Z","message":"chore(NA):
upgrade chromedriver to v115 (#163520)\n\nThis PR upgrades chromedriver
into the latest version
available.","sha":"924b8e90742f6899a54e123149513fdc3b00b1bb","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.10.0"],"number":163520,"url":"https://github.com/elastic/kibana/pull/163520","mergeCommit":{"message":"chore(NA):
upgrade chromedriver to v115 (#163520)\n\nThis PR upgrades chromedriver
into the latest version
available.","sha":"924b8e90742f6899a54e123149513fdc3b00b1bb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163520","number":163520,"mergeCommit":{"message":"chore(NA):
upgrade chromedriver to v115 (#163520)\n\nThis PR upgrades chromedriver
into the latest version
available.","sha":"924b8e90742f6899a54e123149513fdc3b00b1bb"}}]}]
BACKPORT-->

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
 2023-08-09 20:37:23 +01:00
Tiago Costa
d781e42193
[8.9] fix(NA): apply ipv4 first dns result order for worker threads (#163484) (#163512) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [fix(NA): apply ipv4 first dns result order for worker threads
(#163484)](https://github.com/elastic/kibana/pull/163484)

<!--- Backport version: 8.9.8 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2023-08-09T15:49:57Z","message":"fix(NA):
apply ipv4 first dns result order for worker threads (#163484)\n\nThis
PR is a follow up of https://github.com/elastic/kibana/pull/163025\r\nas
we discover the initial fix doesn't apply correctly to
working\r\nthreads during
development.","sha":"f4856f74784cf5ca2094f2f54a6d86f2aff3335a","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.10.0"],"number":163484,"url":"https://github.com/elastic/kibana/pull/163484","mergeCommit":{"message":"fix(NA):
apply ipv4 first dns result order for worker threads (#163484)\n\nThis
PR is a follow up of https://github.com/elastic/kibana/pull/163025\r\nas
we discover the initial fix doesn't apply correctly to
working\r\nthreads during
development.","sha":"f4856f74784cf5ca2094f2f54a6d86f2aff3335a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163484","number":163484,"mergeCommit":{"message":"fix(NA):
apply ipv4 first dns result order for worker threads (#163484)\n\nThis
PR is a follow up of https://github.com/elastic/kibana/pull/163025\r\nas
we discover the initial fix doesn't apply correctly to
working\r\nthreads during
development.","sha":"f4856f74784cf5ca2094f2f54a6d86f2aff3335a"}}]}]
BACKPORT-->
 2023-08-09 19:50:29 +01:00
Tiago Costa
7413e8a21a
skip failing es promotion suite (#163454) 2023-08-09 17:32:44 +01:00
Kibana Machine
fb16a55e78 skip failing test suite (#162995) 2023-08-08 14:29:24 -04:00
Kibana Machine
29f9a8453e
[8.9] [OAS] Clarify rule action descriptions (#162199) (#163418) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[OAS] Clarify rule action descriptions
(#162199)](https://github.com/elastic/kibana/pull/162199)

<!--- 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":"2023-08-08T14:31:46Z","message":"[OAS]
Clarify rule action descriptions
(#162199)","sha":"bc9d601febb56c19a677dbed3312a2012bdedc97","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:prev-minor","v8.10.0"],"number":162199,"url":"https://github.com/elastic/kibana/pull/162199","mergeCommit":{"message":"[OAS]
Clarify rule action descriptions
(#162199)","sha":"bc9d601febb56c19a677dbed3312a2012bdedc97"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162199","number":162199,"mergeCommit":{"message":"[OAS]
Clarify rule action descriptions
(#162199)","sha":"bc9d601febb56c19a677dbed3312a2012bdedc97"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2023-08-08 08:57:24 -07:00
Sander Philipse
95fe4905a9
[Search] Remove Google Cloud Storage as native connector (#163310) 
## Summary

Removing Google Cloud Storage as a native connector.


### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces&mdash;unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes&mdash;Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
 2023-08-08 09:59:26 +01:00
Kibana Machine
2608fd9046
[8.9] chore(NA): skip failing suite on osquery/cypress/e2e/all/alerts.cy.ts (#163366) (#163375) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [chore(NA): skip failing suite on osquery/cypress/e2e/all/alerts.cy.ts
(#163366)](https://github.com/elastic/kibana/pull/163366)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2023-08-08T07:33:31Z","message":"chore(NA):
skip failing suite on osquery/cypress/e2e/all/alerts.cy.ts
(#163366)\n\nRecreation of
https://github.com/elastic/kibana/pull/163360\r\n\r\nThis PR intends to
skip a failing suite to unblock the unsupported FTRs\r\npipeline along
the same lines of what was done
at\r\nhttps://github.com/elastic/kibana/pull/163322","sha":"0d49c8a21490f9a7d6f3c14e8582a584b3155ce9","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","test-failure-flaky","backport:prev-minor","v8.10.0"],"number":163366,"url":"https://github.com/elastic/kibana/pull/163366","mergeCommit":{"message":"chore(NA):
skip failing suite on osquery/cypress/e2e/all/alerts.cy.ts
(#163366)\n\nRecreation of
https://github.com/elastic/kibana/pull/163360\r\n\r\nThis PR intends to
skip a failing suite to unblock the unsupported FTRs\r\npipeline along
the same lines of what was done
at\r\nhttps://github.com/elastic/kibana/pull/163322","sha":"0d49c8a21490f9a7d6f3c14e8582a584b3155ce9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163366","number":163366,"mergeCommit":{"message":"chore(NA):
skip failing suite on osquery/cypress/e2e/all/alerts.cy.ts
(#163366)\n\nRecreation of
https://github.com/elastic/kibana/pull/163360\r\n\r\nThis PR intends to
skip a failing suite to unblock the unsupported FTRs\r\npipeline along
the same lines of what was done
at\r\nhttps://github.com/elastic/kibana/pull/163322","sha":"0d49c8a21490f9a7d6f3c14e8582a584b3155ce9"}}]}]
BACKPORT-->

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
 2023-08-08 01:45:09 -07:00
Kibana Machine
0fe9603705
[8.9] [docs] Improve Node.js upgrade docs (#163268) (#163353) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[docs] Improve Node.js upgrade docs
(#163268)](https://github.com/elastic/kibana/pull/163268)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Thomas
Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T20:08:18Z","message":"[docs]
Improve Node.js upgrade docs
(#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.10.0"],"number":163268,"url":"https://github.com/elastic/kibana/pull/163268","mergeCommit":{"message":"[docs]
Improve Node.js upgrade docs
(#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163268","number":163268,"mergeCommit":{"message":"[docs]
Improve Node.js upgrade docs
(#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808"}}]}]
BACKPORT-->

Co-authored-by: Thomas Watson <watson@elastic.co>
 2023-08-07 16:29:46 -04:00
Kibana Machine
dcca7c8054
[8.9] [Canvas] Fix embeddables not rendering (#163013) (#163349) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Canvas] Fix embeddables not rendering
(#163013)](https://github.com/elastic/kibana/pull/163013)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T18:19:30Z","message":"[Canvas]
Fix embeddables not rendering (#163013)\n\n## Summary\r\n\r\nCloses
#158948.\r\n\r\nThis removes the debounce on a redux action that was
causing the\r\nembeddables to not load in Canvas. It was introduced in
#132831 which\r\nfixed https://github.com/elastic/kibana/issues/123557
where changes to\r\nthe datasource settings weren't synced with the
expression properly.\r\n\r\nAfter extensive testing with this debounce
removed, I was still unable\r\nto reproduce the datasource/expression
sync issues, so this change\r\nshouldn't cause any regression
there.\r\n\r\nI added a smoke test that checks that embeddables render
correctly after\r\na page change, and I added debounces to the handlers
for any settings\r\nchanges in the sidebar both in the `display` tab and
the `data` tab to\r\nprevent too many updates.\r\n\r\nWhile I was in
here, I noticed that the corners of the dashed border\r\nwere slightly
showing after switching from `border` to `outline` styles\r\non the
embeddable panel, so I fixed the CSS here to hide them
correctly\r\nagain.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f64ba2a4fcddb9e8605c7d9b41a6fe57ce511a61","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","loe:days","impact:high","Feature:Canvas","v8.10.0","v8.9.1"],"number":163013,"url":"https://github.com/elastic/kibana/pull/163013","mergeCommit":{"message":"[Canvas]
Fix embeddables not rendering (#163013)\n\n## Summary\r\n\r\nCloses
#158948.\r\n\r\nThis removes the debounce on a redux action that was
causing the\r\nembeddables to not load in Canvas. It was introduced in
#132831 which\r\nfixed https://github.com/elastic/kibana/issues/123557
where changes to\r\nthe datasource settings weren't synced with the
expression properly.\r\n\r\nAfter extensive testing with this debounce
removed, I was still unable\r\nto reproduce the datasource/expression
sync issues, so this change\r\nshouldn't cause any regression
there.\r\n\r\nI added a smoke test that checks that embeddables render
correctly after\r\na page change, and I added debounces to the handlers
for any settings\r\nchanges in the sidebar both in the `display` tab and
the `data` tab to\r\nprevent too many updates.\r\n\r\nWhile I was in
here, I noticed that the corners of the dashed border\r\nwere slightly
showing after switching from `border` to `outline` styles\r\non the
embeddable panel, so I fixed the CSS here to hide them
correctly\r\nagain.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f64ba2a4fcddb9e8605c7d9b41a6fe57ce511a61"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163013","number":163013,"mergeCommit":{"message":"[Canvas]
Fix embeddables not rendering (#163013)\n\n## Summary\r\n\r\nCloses
#158948.\r\n\r\nThis removes the debounce on a redux action that was
causing the\r\nembeddables to not load in Canvas. It was introduced in
#132831 which\r\nfixed https://github.com/elastic/kibana/issues/123557
where changes to\r\nthe datasource settings weren't synced with the
expression properly.\r\n\r\nAfter extensive testing with this debounce
removed, I was still unable\r\nto reproduce the datasource/expression
sync issues, so this change\r\nshouldn't cause any regression
there.\r\n\r\nI added a smoke test that checks that embeddables render
correctly after\r\na page change, and I added debounces to the handlers
for any settings\r\nchanges in the sidebar both in the `display` tab and
the `data` tab to\r\nprevent too many updates.\r\n\r\nWhile I was in
here, I noticed that the corners of the dashed border\r\nwere slightly
showing after switching from `border` to `outline` styles\r\non the
embeddable panel, so I fixed the CSS here to hide them
correctly\r\nagain.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] 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&mdash;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&mdash;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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f64ba2a4fcddb9e8605c7d9b41a6fe57ce511a61"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
 2023-08-07 12:35:44 -07:00
Kibana Machine
e1a00f0377
[8.9] [FTR] use xpath locator to find particular element in group by index (#161202) (#163291) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[FTR] use xpath locator to find particular element in group by index
(#161202)](https://github.com/elastic/kibana/pull/161202)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T11:39:29Z","message":"[FTR]
use xpath locator to find particular element in group by index
(#161202)\n\nRelated to #158972\r\n\r\nI was able to reproduce the
failure locally on the latest main with a\r\nsmall code
change:\r\n\r\n\r\nb3d7b71076/test/functional/page_objects/visual_builder_page.ts (L867-L869)\r\n\r\n```\r\n
| debg comboBox.isOptionSelected, value: machine.os.raw\r\n │ info
Taking screenshot
\"/Users/dmle/github/kibana/test/functional/screenshots/failure/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.png\"\r\n
│ info Current URL is:
http://localhost:5620/app/visualize#/create?type=metrics&_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:%272015-09-19T06:31:44.000Z%27,to:%272015-09-22T18:31:44.000Z%27))&_a=(filters:!(),linked:!f,query:(language:kuery,query:%27%27),uiState:(),vis:(aggs:!(),params:(axis_formatter:number,axis_position:left,axis_scale:normal,drop_last_bucket:1,id:b6ee5181-addb-436f-8190-4f2a178fee7b,index_pattern:(id:%27logstash-*%27),interval:%27%27,isModelInvalid:!f,max_lines_legend:1,series:!((axis_position:right,chart_type:line,color:%2368BC00,fill:0.5,formatter:default,id:%2724f639d7-d16e-44d1-ac0d-f2b590e94e8e%27,line_width:1,metrics:!((id:d4f68ace-b844-4e00-933f-8c3b49e19067,type:count)),override_index_pattern:0,palette:(name:default,type:palette),point_size:1,separate_axis:0,series_drop_last_bucket:0,split_mode:terms,stacked:none,terms_field:!(bytes,machine.os.raw),time_range_mode:entire_time_range)),show_grid:1,show_legend:1,time_field:%27%27,time_range_mode:entire_time_range,tooltip_mode:show_all,truncate_legend:1,type:timeseries,use_kibana_indexes:!t),title:%27%27,type:metrics))\r\n
│ info Saving page source to:
/Users/dmle/github/kibana/test/functional/failure_debug/html/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.html\r\n
└- ✖ fail: visualize app visual builder Time Series basics Clicking on
the chart should create a filter for series with multiple split by terms
fields one of which has formatting\r\n │ StaleElementReferenceError:
stale element reference: stale element not found\r\n │ (Session info:
chrome=114.0.5735.198)\r\n │ at Object.throwDecodedError
(node_modules/selenium-webdriver/lib/error.js:524:15)\r\n │ at
parseHttpResponse
(node_modules/selenium-webdriver/lib/http.js:601:13)\r\n │ at
Executor.execute
(node_modules/selenium-webdriver/lib/http.js:529:28)\r\n │ at
runMicrotasks (<anonymous>)\r\n │ at processTicksAndRejections
(node:internal/process/task_queues:96:5)\r\n │ at Task.exec
(prevent_parallel_calls.ts:28:20)\r\n```\r\n\r\n### Do we have any
service to help with StaleElementReferenceError\r\nhandling in
FTR?\r\n\r\nWe do. `WebElementWrapper` object have internal mechanism to
handle it:\r\nwe wrap most of the actions (click, type, getAttribute,
etc.) with\r\n`retryCall` function, which execute command up to
RETRY_MAX_ATTEMPTS\r\ntimes (3 by default) and check for errors. So if
we try to click element\r\nthat is no longer in the DOM, this mechanism
will try to find the\r\nelement in the DOM again, assuming it is still
there but referenceId was\r\nchanged due to page updates. And repeat the
click.\r\n\r\nhttps://github.com/elastic/kibana/blob/main/test/functional/services/lib/web_element_wrapper/web_element_wrapper.ts#L107-L140\r\n\r\nYou
might notice a warning during timePicker dates selection\r\n```\r\n │
debg
Find.findByCssSelector('[data-test-subj=\"superDatePickerAbsoluteTab\"]')
with timeout=10000\r\n │ warn WebElementWrapper.click:
StaleElementReferenceError: stale element reference: stale element not
found\r\n │ (Session info: chrome=114.0.5735.198)\r\n │ debg Searching
again for the element 'By(css selector,
[data-test-subj=\"superDatePickerAbsoluteTab\"])',\r\n | 2 attempts
left\r\n```\r\nIt is helping a lot to minimize the flakiness.\r\n\r\n###
Why does FTR still fails with StaleElementReferenceError in\r\nVisualize
tests?\r\nBecause most methods use the same pattern for searching
elements in the\r\nDOM: get all elements and then pick one by
index.\r\n\r\n```\r\nconst byFields = await
this.testSubjects.findAll('fieldSelectItem');\r\nconst selectedByField =
byFields[byFields.length - 1];\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThe
problem is that WebElementWrapper retry mechanism relies on
having\r\n`locator` property defined and it is _only_ defined if you
search for a\r\nsingle element, e.g. `testSubjects.find` or
`by.byCssSelector`. This\r\nproperty is set to `null` for each
`WebElementWrapper` object in array\r\nyou get from `await
this.testSubjects.findAll('fieldSelectItem')`;\r\nSo when we pass this
object in `this.comboBox.setElement` and go through\r\na list of
actions, it will fail on the first
StaleElementReferenceError\r\noccurrence.\r\n\r\nThe devil is in the
detail: usually searching for multiple elements and\r\ndoing actions on
some of it is totally fine. But comboBox selection has\r\nquite many
actions with different child elements, that can be updated in\r\nDOM and
lead to the error. Wrapping things with classical `retry`\r\nservice
only hides the issue, but does not actually solve it.\r\n\r\n###
Proposed solution\r\nAfaik CSS locators does not support searching for
elements and picking\r\nup one by index (I looked at `:nth-child()\r\n`,
but it is not what we need).\r\nBut we can use xpath locators for this
purpose. \r\n```\r\nconst selectedByField = await
this.find.byXPath(`(//*[@data-test-subj='fieldSelectItem'])[last()]`);\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThis way
`selectedByField` has locator property defined and internal\r\nmechanism
will be able to retry actions.\r\n\r\n#### Why don't we store `locator`
for multiple elements search.\r\nWe can, but it means every element in
array has the same locator and\r\nwhile retrying to find it WebDriver
will return the first one in the DOM\r\nignoring the element index.
Using xpath locator is basically the simpler\r\nversion of storing
element index in WebElementWrapper object.\r\n\r\nFlaky test runner: 50x
for
visualize/group1..5/config.ts\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2554\r\n\r\n100x
for
group5\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2596#0189403c-ccd2-4186-a83e-af21fe88018c\r\n\r\n100x
flaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2794","sha":"8e1d66fab6d09ec01946672911e874dc8a9d2050","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test_ui_functional","release_note:skip","v8.10.0","v8.9.1"],"number":161202,"url":"https://github.com/elastic/kibana/pull/161202","mergeCommit":{"message":"[FTR]
use xpath locator to find particular element in group by index
(#161202)\n\nRelated to #158972\r\n\r\nI was able to reproduce the
failure locally on the latest main with a\r\nsmall code
change:\r\n\r\n\r\nb3d7b71076/test/functional/page_objects/visual_builder_page.ts (L867-L869)\r\n\r\n```\r\n
| debg comboBox.isOptionSelected, value: machine.os.raw\r\n │ info
Taking screenshot
\"/Users/dmle/github/kibana/test/functional/screenshots/failure/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.png\"\r\n
│ info Current URL is:
http://localhost:5620/app/visualize#/create?type=metrics&_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:%272015-09-19T06:31:44.000Z%27,to:%272015-09-22T18:31:44.000Z%27))&_a=(filters:!(),linked:!f,query:(language:kuery,query:%27%27),uiState:(),vis:(aggs:!(),params:(axis_formatter:number,axis_position:left,axis_scale:normal,drop_last_bucket:1,id:b6ee5181-addb-436f-8190-4f2a178fee7b,index_pattern:(id:%27logstash-*%27),interval:%27%27,isModelInvalid:!f,max_lines_legend:1,series:!((axis_position:right,chart_type:line,color:%2368BC00,fill:0.5,formatter:default,id:%2724f639d7-d16e-44d1-ac0d-f2b590e94e8e%27,line_width:1,metrics:!((id:d4f68ace-b844-4e00-933f-8c3b49e19067,type:count)),override_index_pattern:0,palette:(name:default,type:palette),point_size:1,separate_axis:0,series_drop_last_bucket:0,split_mode:terms,stacked:none,terms_field:!(bytes,machine.os.raw),time_range_mode:entire_time_range)),show_grid:1,show_legend:1,time_field:%27%27,time_range_mode:entire_time_range,tooltip_mode:show_all,truncate_legend:1,type:timeseries,use_kibana_indexes:!t),title:%27%27,type:metrics))\r\n
│ info Saving page source to:
/Users/dmle/github/kibana/test/functional/failure_debug/html/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.html\r\n
└- ✖ fail: visualize app visual builder Time Series basics Clicking on
the chart should create a filter for series with multiple split by terms
fields one of which has formatting\r\n │ StaleElementReferenceError:
stale element reference: stale element not found\r\n │ (Session info:
chrome=114.0.5735.198)\r\n │ at Object.throwDecodedError
(node_modules/selenium-webdriver/lib/error.js:524:15)\r\n │ at
parseHttpResponse
(node_modules/selenium-webdriver/lib/http.js:601:13)\r\n │ at
Executor.execute
(node_modules/selenium-webdriver/lib/http.js:529:28)\r\n │ at
runMicrotasks (<anonymous>)\r\n │ at processTicksAndRejections
(node:internal/process/task_queues:96:5)\r\n │ at Task.exec
(prevent_parallel_calls.ts:28:20)\r\n```\r\n\r\n### Do we have any
service to help with StaleElementReferenceError\r\nhandling in
FTR?\r\n\r\nWe do. `WebElementWrapper` object have internal mechanism to
handle it:\r\nwe wrap most of the actions (click, type, getAttribute,
etc.) with\r\n`retryCall` function, which execute command up to
RETRY_MAX_ATTEMPTS\r\ntimes (3 by default) and check for errors. So if
we try to click element\r\nthat is no longer in the DOM, this mechanism
will try to find the\r\nelement in the DOM again, assuming it is still
there but referenceId was\r\nchanged due to page updates. And repeat the
click.\r\n\r\nhttps://github.com/elastic/kibana/blob/main/test/functional/services/lib/web_element_wrapper/web_element_wrapper.ts#L107-L140\r\n\r\nYou
might notice a warning during timePicker dates selection\r\n```\r\n │
debg
Find.findByCssSelector('[data-test-subj=\"superDatePickerAbsoluteTab\"]')
with timeout=10000\r\n │ warn WebElementWrapper.click:
StaleElementReferenceError: stale element reference: stale element not
found\r\n │ (Session info: chrome=114.0.5735.198)\r\n │ debg Searching
again for the element 'By(css selector,
[data-test-subj=\"superDatePickerAbsoluteTab\"])',\r\n | 2 attempts
left\r\n```\r\nIt is helping a lot to minimize the flakiness.\r\n\r\n###
Why does FTR still fails with StaleElementReferenceError in\r\nVisualize
tests?\r\nBecause most methods use the same pattern for searching
elements in the\r\nDOM: get all elements and then pick one by
index.\r\n\r\n```\r\nconst byFields = await
this.testSubjects.findAll('fieldSelectItem');\r\nconst selectedByField =
byFields[byFields.length - 1];\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThe
problem is that WebElementWrapper retry mechanism relies on
having\r\n`locator` property defined and it is _only_ defined if you
search for a\r\nsingle element, e.g. `testSubjects.find` or
`by.byCssSelector`. This\r\nproperty is set to `null` for each
`WebElementWrapper` object in array\r\nyou get from `await
this.testSubjects.findAll('fieldSelectItem')`;\r\nSo when we pass this
object in `this.comboBox.setElement` and go through\r\na list of
actions, it will fail on the first
StaleElementReferenceError\r\noccurrence.\r\n\r\nThe devil is in the
detail: usually searching for multiple elements and\r\ndoing actions on
some of it is totally fine. But comboBox selection has\r\nquite many
actions with different child elements, that can be updated in\r\nDOM and
lead to the error. Wrapping things with classical `retry`\r\nservice
only hides the issue, but does not actually solve it.\r\n\r\n###
Proposed solution\r\nAfaik CSS locators does not support searching for
elements and picking\r\nup one by index (I looked at `:nth-child()\r\n`,
but it is not what we need).\r\nBut we can use xpath locators for this
purpose. \r\n```\r\nconst selectedByField = await
this.find.byXPath(`(//*[@data-test-subj='fieldSelectItem'])[last()]`);\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThis way
`selectedByField` has locator property defined and internal\r\nmechanism
will be able to retry actions.\r\n\r\n#### Why don't we store `locator`
for multiple elements search.\r\nWe can, but it means every element in
array has the same locator and\r\nwhile retrying to find it WebDriver
will return the first one in the DOM\r\nignoring the element index.
Using xpath locator is basically the simpler\r\nversion of storing
element index in WebElementWrapper object.\r\n\r\nFlaky test runner: 50x
for
visualize/group1..5/config.ts\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2554\r\n\r\n100x
for
group5\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2596#0189403c-ccd2-4186-a83e-af21fe88018c\r\n\r\n100x
flaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2794","sha":"8e1d66fab6d09ec01946672911e874dc8a9d2050"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161202","number":161202,"mergeCommit":{"message":"[FTR]
use xpath locator to find particular element in group by index
(#161202)\n\nRelated to #158972\r\n\r\nI was able to reproduce the
failure locally on the latest main with a\r\nsmall code
change:\r\n\r\n\r\nb3d7b71076/test/functional/page_objects/visual_builder_page.ts (L867-L869)\r\n\r\n```\r\n
| debg comboBox.isOptionSelected, value: machine.os.raw\r\n │ info
Taking screenshot
\"/Users/dmle/github/kibana/test/functional/screenshots/failure/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.png\"\r\n
│ info Current URL is:
http://localhost:5620/app/visualize#/create?type=metrics&_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:%272015-09-19T06:31:44.000Z%27,to:%272015-09-22T18:31:44.000Z%27))&_a=(filters:!(),linked:!f,query:(language:kuery,query:%27%27),uiState:(),vis:(aggs:!(),params:(axis_formatter:number,axis_position:left,axis_scale:normal,drop_last_bucket:1,id:b6ee5181-addb-436f-8190-4f2a178fee7b,index_pattern:(id:%27logstash-*%27),interval:%27%27,isModelInvalid:!f,max_lines_legend:1,series:!((axis_position:right,chart_type:line,color:%2368BC00,fill:0.5,formatter:default,id:%2724f639d7-d16e-44d1-ac0d-f2b590e94e8e%27,line_width:1,metrics:!((id:d4f68ace-b844-4e00-933f-8c3b49e19067,type:count)),override_index_pattern:0,palette:(name:default,type:palette),point_size:1,separate_axis:0,series_drop_last_bucket:0,split_mode:terms,stacked:none,terms_field:!(bytes,machine.os.raw),time_range_mode:entire_time_range)),show_grid:1,show_legend:1,time_field:%27%27,time_range_mode:entire_time_range,tooltip_mode:show_all,truncate_legend:1,type:timeseries,use_kibana_indexes:!t),title:%27%27,type:metrics))\r\n
│ info Saving page source to:
/Users/dmle/github/kibana/test/functional/failure_debug/html/visualize
app visual builder Time Series basics Clicking on the chart should
cre-a71516dab48cdb296c45e2b439ed3965cfd400204827bba7ce3cf4719afb093b.html\r\n
└- ✖ fail: visualize app visual builder Time Series basics Clicking on
the chart should create a filter for series with multiple split by terms
fields one of which has formatting\r\n │ StaleElementReferenceError:
stale element reference: stale element not found\r\n │ (Session info:
chrome=114.0.5735.198)\r\n │ at Object.throwDecodedError
(node_modules/selenium-webdriver/lib/error.js:524:15)\r\n │ at
parseHttpResponse
(node_modules/selenium-webdriver/lib/http.js:601:13)\r\n │ at
Executor.execute
(node_modules/selenium-webdriver/lib/http.js:529:28)\r\n │ at
runMicrotasks (<anonymous>)\r\n │ at processTicksAndRejections
(node:internal/process/task_queues:96:5)\r\n │ at Task.exec
(prevent_parallel_calls.ts:28:20)\r\n```\r\n\r\n### Do we have any
service to help with StaleElementReferenceError\r\nhandling in
FTR?\r\n\r\nWe do. `WebElementWrapper` object have internal mechanism to
handle it:\r\nwe wrap most of the actions (click, type, getAttribute,
etc.) with\r\n`retryCall` function, which execute command up to
RETRY_MAX_ATTEMPTS\r\ntimes (3 by default) and check for errors. So if
we try to click element\r\nthat is no longer in the DOM, this mechanism
will try to find the\r\nelement in the DOM again, assuming it is still
there but referenceId was\r\nchanged due to page updates. And repeat the
click.\r\n\r\nhttps://github.com/elastic/kibana/blob/main/test/functional/services/lib/web_element_wrapper/web_element_wrapper.ts#L107-L140\r\n\r\nYou
might notice a warning during timePicker dates selection\r\n```\r\n │
debg
Find.findByCssSelector('[data-test-subj=\"superDatePickerAbsoluteTab\"]')
with timeout=10000\r\n │ warn WebElementWrapper.click:
StaleElementReferenceError: stale element reference: stale element not
found\r\n │ (Session info: chrome=114.0.5735.198)\r\n │ debg Searching
again for the element 'By(css selector,
[data-test-subj=\"superDatePickerAbsoluteTab\"])',\r\n | 2 attempts
left\r\n```\r\nIt is helping a lot to minimize the flakiness.\r\n\r\n###
Why does FTR still fails with StaleElementReferenceError in\r\nVisualize
tests?\r\nBecause most methods use the same pattern for searching
elements in the\r\nDOM: get all elements and then pick one by
index.\r\n\r\n```\r\nconst byFields = await
this.testSubjects.findAll('fieldSelectItem');\r\nconst selectedByField =
byFields[byFields.length - 1];\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThe
problem is that WebElementWrapper retry mechanism relies on
having\r\n`locator` property defined and it is _only_ defined if you
search for a\r\nsingle element, e.g. `testSubjects.find` or
`by.byCssSelector`. This\r\nproperty is set to `null` for each
`WebElementWrapper` object in array\r\nyou get from `await
this.testSubjects.findAll('fieldSelectItem')`;\r\nSo when we pass this
object in `this.comboBox.setElement` and go through\r\na list of
actions, it will fail on the first
StaleElementReferenceError\r\noccurrence.\r\n\r\nThe devil is in the
detail: usually searching for multiple elements and\r\ndoing actions on
some of it is totally fine. But comboBox selection has\r\nquite many
actions with different child elements, that can be updated in\r\nDOM and
lead to the error. Wrapping things with classical `retry`\r\nservice
only hides the issue, but does not actually solve it.\r\n\r\n###
Proposed solution\r\nAfaik CSS locators does not support searching for
elements and picking\r\nup one by index (I looked at `:nth-child()\r\n`,
but it is not what we need).\r\nBut we can use xpath locators for this
purpose. \r\n```\r\nconst selectedByField = await
this.find.byXPath(`(//*[@data-test-subj='fieldSelectItem'])[last()]`);\r\nawait
this.comboBox.setElement(selectedByField, field);\r\n```\r\n\r\nThis way
`selectedByField` has locator property defined and internal\r\nmechanism
will be able to retry actions.\r\n\r\n#### Why don't we store `locator`
for multiple elements search.\r\nWe can, but it means every element in
array has the same locator and\r\nwhile retrying to find it WebDriver
will return the first one in the DOM\r\nignoring the element index.
Using xpath locator is basically the simpler\r\nversion of storing
element index in WebElementWrapper object.\r\n\r\nFlaky test runner: 50x
for
visualize/group1..5/config.ts\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2554\r\n\r\n100x
for
group5\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2596#0189403c-ccd2-4186-a83e-af21fe88018c\r\n\r\n100x
flaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2794","sha":"8e1d66fab6d09ec01946672911e874dc8a9d2050"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2023-08-07 05:53:47 -07:00
Kibana Machine
1906969726
[8.9] [ftr/WebElementWrapper] workaround for chromedriver incorrect error response (#163231) (#163285) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[ftr/WebElementWrapper] workaround for chromedriver incorrect error
response (#163231)](https://github.com/elastic/kibana/pull/163231)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T10:32:02Z","message":"[ftr/WebElementWrapper]
workaround for chromedriver incorrect error response
(#163231)\n\nRelated to #156821\r\n\r\nIt seems like Chromedriver 115
has regression again: sometimes it\r\nreturns NoSuchElementError instead
of
StaleElementReferenceError.\r\n[chromedriver/issues#534](https://bugs.chromium.org/p/chromedriver/issues/detail?id=4534)\r\n\r\nThe
fix on our side is by adding error message to retry list. The
list\r\nreferences the errors we would like to retry command on. It only
work\r\nfor single element search where we store locator.\r\nE.g. it
will help with retrying on\r\n\r\n```\r\nawait
testSubjects.click('...');\r\n```\r\n\r\nbut still fail when you
do\r\n\r\n```\r\nconst elements = await
testSubjects.findAll('...');\r\nawait
elements[1].click();\r\n```\r\n\r\nFor viz tests stability I suggest
reviewing
#161202","sha":"585d108db7dc2239c274453964bc04ce2993f7a3","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.10.0","v8.9.1"],"number":163231,"url":"https://github.com/elastic/kibana/pull/163231","mergeCommit":{"message":"[ftr/WebElementWrapper]
workaround for chromedriver incorrect error response
(#163231)\n\nRelated to #156821\r\n\r\nIt seems like Chromedriver 115
has regression again: sometimes it\r\nreturns NoSuchElementError instead
of
StaleElementReferenceError.\r\n[chromedriver/issues#534](https://bugs.chromium.org/p/chromedriver/issues/detail?id=4534)\r\n\r\nThe
fix on our side is by adding error message to retry list. The
list\r\nreferences the errors we would like to retry command on. It only
work\r\nfor single element search where we store locator.\r\nE.g. it
will help with retrying on\r\n\r\n```\r\nawait
testSubjects.click('...');\r\n```\r\n\r\nbut still fail when you
do\r\n\r\n```\r\nconst elements = await
testSubjects.findAll('...');\r\nawait
elements[1].click();\r\n```\r\n\r\nFor viz tests stability I suggest
reviewing
#161202","sha":"585d108db7dc2239c274453964bc04ce2993f7a3"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163231","number":163231,"mergeCommit":{"message":"[ftr/WebElementWrapper]
workaround for chromedriver incorrect error response
(#163231)\n\nRelated to #156821\r\n\r\nIt seems like Chromedriver 115
has regression again: sometimes it\r\nreturns NoSuchElementError instead
of
StaleElementReferenceError.\r\n[chromedriver/issues#534](https://bugs.chromium.org/p/chromedriver/issues/detail?id=4534)\r\n\r\nThe
fix on our side is by adding error message to retry list. The
list\r\nreferences the errors we would like to retry command on. It only
work\r\nfor single element search where we store locator.\r\nE.g. it
will help with retrying on\r\n\r\n```\r\nawait
testSubjects.click('...');\r\n```\r\n\r\nbut still fail when you
do\r\n\r\n```\r\nconst elements = await
testSubjects.findAll('...');\r\nawait
elements[1].click();\r\n```\r\n\r\nFor viz tests stability I suggest
reviewing
#161202","sha":"585d108db7dc2239c274453964bc04ce2993f7a3"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2023-08-07 04:35:27 -07:00
Julia Bardi
40743390be
[8.9][Fleet] added agent logs top errors from 100 hits (#162135) (#163278) 
Backport https://github.com/elastic/kibana/pull/162135
 2023-08-07 13:07:49 +02:00
Kibana Machine
99b0b1dfa1
[8.9] [Synthetics] Normalize monitor before mixing params. (#163176) (#163191) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Normalize monitor before mixing params.
(#163176)](https://github.com/elastic/kibana/pull/163176)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Abdul Wahab
Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2023-08-04T17:25:10Z","message":"[Synthetics]
Normalize monitor before mixing params. (#163176)\n\nFixes #163042
\r\n\r\n## Summary\r\n\r\nNormalize the monitor object before mixing
global and
project-wide\r\nparams.","sha":"339eb28861e56a465cc9ce6f458d792d39414706","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":163176,"url":"https://github.com/elastic/kibana/pull/163176","mergeCommit":{"message":"[Synthetics]
Normalize monitor before mixing params. (#163176)\n\nFixes #163042
\r\n\r\n## Summary\r\n\r\nNormalize the monitor object before mixing
global and
project-wide\r\nparams.","sha":"339eb28861e56a465cc9ce6f458d792d39414706"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163176","number":163176,"mergeCommit":{"message":"[Synthetics]
Normalize monitor before mixing params. (#163176)\n\nFixes #163042
\r\n\r\n## Summary\r\n\r\nNormalize the monitor object before mixing
global and
project-wide\r\nparams.","sha":"339eb28861e56a465cc9ce6f458d792d39414706"}}]}]
BACKPORT-->

Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>
 2023-08-04 13:13:15 -07:00
Kibana Machine
2540167153
[8.9] chore(NA): exposes the new CHROMEDRIVER_CDNBINARIESURL env var to the new chromedriver version (#163010) (#163201) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [chore(NA): exposes the new CHROMEDRIVER_CDNBINARIESURL env var to the
new chromedriver version
(#163010)](https://github.com/elastic/kibana/pull/163010)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Tiago
Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2023-08-04T18:12:16Z","message":"chore(NA):
exposes the new CHROMEDRIVER_CDNBINARIESURL env var to the new
chromedriver version (#163010)\n\nThis PR exposes the new
`CHROMEDRIVER_CDNBINARIESURL` which was\r\nintroduced in the
chromedriver version we are now using.\r\n\r\nMore info on this can be
found
at\r\nhttps://github.com/giggio/node-chromedriver#custom-binaries-url
and\r\nhttps://developer.chrome.com/blog/chrome-for-testing/\r\n\r\nThis
should be merged after the changes in the ci proxy
cache.","sha":"ac66353a393c34f6b0fe256311be35112de14e20","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.10.0"],"number":163010,"url":"https://github.com/elastic/kibana/pull/163010","mergeCommit":{"message":"chore(NA):
exposes the new CHROMEDRIVER_CDNBINARIESURL env var to the new
chromedriver version (#163010)\n\nThis PR exposes the new
`CHROMEDRIVER_CDNBINARIESURL` which was\r\nintroduced in the
chromedriver version we are now using.\r\n\r\nMore info on this can be
found
at\r\nhttps://github.com/giggio/node-chromedriver#custom-binaries-url
and\r\nhttps://developer.chrome.com/blog/chrome-for-testing/\r\n\r\nThis
should be merged after the changes in the ci proxy
cache.","sha":"ac66353a393c34f6b0fe256311be35112de14e20"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163010","number":163010,"mergeCommit":{"message":"chore(NA):
exposes the new CHROMEDRIVER_CDNBINARIESURL env var to the new
chromedriver version (#163010)\n\nThis PR exposes the new
`CHROMEDRIVER_CDNBINARIESURL` which was\r\nintroduced in the
chromedriver version we are now using.\r\n\r\nMore info on this can be
found
at\r\nhttps://github.com/giggio/node-chromedriver#custom-binaries-url
and\r\nhttps://developer.chrome.com/blog/chrome-for-testing/\r\n\r\nThis
should be merged after the changes in the ci proxy
cache.","sha":"ac66353a393c34f6b0fe256311be35112de14e20"}}]}]
BACKPORT-->

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
 2023-08-04 12:21:00 -07:00
Kibana Machine
df6b25ed8b
[8.9] [APM] check if the doc is missing span.name (#162899) (#163171) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[APM] check if the doc is missing `span.name`
(#162899)](https://github.com/elastic/kibana/pull/162899)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Katerina","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2023-08-04T13:12:38Z","message":"[APM]
check if the doc is missing `span.name` (#162899)\n\n##
Summary\r\nfixes:
https://github.com/elastic/kibana/issues/154998\r\neven though name is
required in span spec it seems to be missed in some\r\ndocuments causing
the runtime
error.\r\n\r\n\r\n35854feb-2df0-4b59-af2e-b79a6f997497","sha":"b7a38984bd8e16e804f19b6e2ed9dcbe8887fe71","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:APM","backport:prev-minor","v8.10.0"],"number":162899,"url":"https://github.com/elastic/kibana/pull/162899","mergeCommit":{"message":"[APM]
check if the doc is missing `span.name` (#162899)\n\n##
Summary\r\nfixes:
https://github.com/elastic/kibana/issues/154998\r\neven though name is
required in span spec it seems to be missed in some\r\ndocuments causing
the runtime
error.\r\n\r\n\r\n35854feb-2df0-4b59-af2e-b79a6f997497","sha":"b7a38984bd8e16e804f19b6e2ed9dcbe8887fe71"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162899","number":162899,"mergeCommit":{"message":"[APM]
check if the doc is missing `span.name` (#162899)\n\n##
Summary\r\nfixes:
https://github.com/elastic/kibana/issues/154998\r\neven though name is
required in span spec it seems to be missed in some\r\ndocuments causing
the runtime
error.\r\n\r\n\r\n35854feb-2df0-4b59-af2e-b79a6f997497","sha":"b7a38984bd8e16e804f19b6e2ed9dcbe8887fe71"}}]}]
BACKPORT-->

Co-authored-by: Katerina <aikaterini.patticha@elastic.co>
 2023-08-04 07:21:33 -07:00
Kibana Machine
60a41625bf
[8.9] [DOCS] Updates the quick start guide (#163165) (#163175) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Updates the quick start guide
(#163165)](https://github.com/elastic/kibana/pull/163165)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"István Zoltán
Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2023-08-04T13:55:25Z","message":"[DOCS]
Updates the quick start guide (#163165)\n\n## Summary\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/161040\r\nThis PR deletes a
line from the quick start guide to make it
up-to-date.","sha":"fc2fbe345ac700a802a3e102ed3c10b18ebae282","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","docs","v8.8.2","v8.10.0","v8.9.1"],"number":163165,"url":"https://github.com/elastic/kibana/pull/163165","mergeCommit":{"message":"[DOCS]
Updates the quick start guide (#163165)\n\n## Summary\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/161040\r\nThis PR deletes a
line from the quick start guide to make it
up-to-date.","sha":"fc2fbe345ac700a802a3e102ed3c10b18ebae282"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163165","number":163165,"mergeCommit":{"message":"[DOCS]
Updates the quick start guide (#163165)\n\n## Summary\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/161040\r\nThis PR deletes a
line from the quick start guide to make it
up-to-date.","sha":"fc2fbe345ac700a802a3e102ed3c10b18ebae282"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
 2023-08-04 10:16:59 -04:00
Julia Rechkunova
694e83780c
[8.9] [Discover] Make share links and search session info shorter for ad-hoc data views (#161180) (#163101) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Discover] Make share links and search session info shorter for
ad-hoc data views
(#161180)](https://github.com/elastic/kibana/pull/161180)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Julia
Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2023-07-25T19:49:13Z","message":"[Discover]
Make share links and search session info shorter for ad-hoc data views
(#161180)\n\n- Closes
https://github.com/elastic/kibana/issues/160993\r\n\r\n##
Summary\r\n\r\nThis PR introduces `dataView.toMinimalSpec()` which is
used now in 3\r\ncases:\r\n- when constructing an alert link\r\n- when
constructing a share URL for ad-hoc data views\r\n- when constructing
search session info for ad-hoc data
views\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8b42e0f79b1dfd6ce81b9f89846eee4d9df21b75","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:DataDiscovery","backport:prev-minor","v8.10.0"],"number":161180,"url":"https://github.com/elastic/kibana/pull/161180","mergeCommit":{"message":"[Discover]
Make share links and search session info shorter for ad-hoc data views
(#161180)\n\n- Closes
https://github.com/elastic/kibana/issues/160993\r\n\r\n##
Summary\r\n\r\nThis PR introduces `dataView.toMinimalSpec()` which is
used now in 3\r\ncases:\r\n- when constructing an alert link\r\n- when
constructing a share URL for ad-hoc data views\r\n- when constructing
search session info for ad-hoc data
views\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8b42e0f79b1dfd6ce81b9f89846eee4d9df21b75"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161180","number":161180,"mergeCommit":{"message":"[Discover]
Make share links and search session info shorter for ad-hoc data views
(#161180)\n\n- Closes
https://github.com/elastic/kibana/issues/160993\r\n\r\n##
Summary\r\n\r\nThis PR introduces `dataView.toMinimalSpec()` which is
used now in 3\r\ncases:\r\n- when constructing an alert link\r\n- when
constructing a share URL for ad-hoc data views\r\n- when constructing
search session info for ad-hoc data
views\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8b42e0f79b1dfd6ce81b9f89846eee4d9df21b75"}}]}]
BACKPORT-->
 2023-08-04 10:18:31 +02:00
Kibana Machine
7b61ce382a
[8.9] Flaky test: rolling file appender (#162851) (#163124) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [Flaky test: rolling file appender
(#162851)](https://github.com/elastic/kibana/pull/162851)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Christiane (Tina)
Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2023-08-03T20:46:14Z","message":"Flaky
test: rolling file appender (#162851)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Ahmad Bamieh
<ahmad.bamyeh@elastic.co>","sha":"b443c0cb9dfd6e34850b2403c8a45f655130e03d","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Feature:Logging","v8.10.0","v8.9.1"],"number":162851,"url":"https://github.com/elastic/kibana/pull/162851","mergeCommit":{"message":"Flaky
test: rolling file appender (#162851)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Ahmad Bamieh
<ahmad.bamyeh@elastic.co>","sha":"b443c0cb9dfd6e34850b2403c8a45f655130e03d"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162851","number":162851,"mergeCommit":{"message":"Flaky
test: rolling file appender (#162851)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Ahmad Bamieh
<ahmad.bamyeh@elastic.co>","sha":"b443c0cb9dfd6e34850b2403c8a45f655130e03d"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
 2023-08-03 14:41:03 -07:00
Kibana Machine
26eb89a395
[8.9] [Security Solution] Fix rounding in top alerts chart on alerts page (#162647) (#162741) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Fix rounding in top alerts chart on alerts page
(#162647)](https://github.com/elastic/kibana/pull/162647)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-28T20:04:37Z","message":"[Security
Solution] Fix rounding in top alerts chart on alerts page
(#162647)\n\n## Summary\r\n\r\nThis PR addresses
(https://github.com/elastic/kibana/issues/162521). In\r\nextreme cases
when there are a lot of alerts without user names, entries\r\nin top
alerts chart disappear. This is due to entries being rounded to
3\r\ndecimal places, when denominator grows too big, the percentages
are\r\nrounded to zero.\r\n\r\nThis PR removed the rounding and added a
label `<1%` when top alerts\r\ngrouping drops below 1%. User should
always see entries if they
are\r\navailable.\r\n\r\n\r\n![image](42ae8453-ccc7-4c71-8bd0-27a79b9b8318)\r\n\r\n**How
to test**\r\nFirst generate a few alerts with user name:\r\n- Go to
`security_solution` folder:
`cd\r\nx-pack/plugins/security_solution`\r\n- Run resolver generate data
script `yarn test:generate --ne 5\r\n--relAlerts 1` - this command will
generate 5 hosts each with 1 alert\r\n\r\nTo generate alerts without
user names, comment lines that populate user\r\nnames
in\r\n`x-pack/plugins/security_solution/common/endpoint/generate_data.ts`\r\n(there
are multiple places)\r\n```\r\nuser: {\r\n domain:
this.randomString(10),\r\n name: this.randomString(10),\r\n
},\r\n```\r\n- run the script again `yarn test:generate --ne 10
--relAlerts 50` -\r\nthis command will generate 50 alerts each for 10
hosts\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"af15cc19c429aa4dd318e21c74e47fb0f13bad8c","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat
Hunting:Investigations","v8.10.0","v8.9.1"],"number":162647,"url":"https://github.com/elastic/kibana/pull/162647","mergeCommit":{"message":"[Security
Solution] Fix rounding in top alerts chart on alerts page
(#162647)\n\n## Summary\r\n\r\nThis PR addresses
(https://github.com/elastic/kibana/issues/162521). In\r\nextreme cases
when there are a lot of alerts without user names, entries\r\nin top
alerts chart disappear. This is due to entries being rounded to
3\r\ndecimal places, when denominator grows too big, the percentages
are\r\nrounded to zero.\r\n\r\nThis PR removed the rounding and added a
label `<1%` when top alerts\r\ngrouping drops below 1%. User should
always see entries if they
are\r\navailable.\r\n\r\n\r\n![image](42ae8453-ccc7-4c71-8bd0-27a79b9b8318)\r\n\r\n**How
to test**\r\nFirst generate a few alerts with user name:\r\n- Go to
`security_solution` folder:
`cd\r\nx-pack/plugins/security_solution`\r\n- Run resolver generate data
script `yarn test:generate --ne 5\r\n--relAlerts 1` - this command will
generate 5 hosts each with 1 alert\r\n\r\nTo generate alerts without
user names, comment lines that populate user\r\nnames
in\r\n`x-pack/plugins/security_solution/common/endpoint/generate_data.ts`\r\n(there
are multiple places)\r\n```\r\nuser: {\r\n domain:
this.randomString(10),\r\n name: this.randomString(10),\r\n
},\r\n```\r\n- run the script again `yarn test:generate --ne 10
--relAlerts 50` -\r\nthis command will generate 50 alerts each for 10
hosts\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"af15cc19c429aa4dd318e21c74e47fb0f13bad8c"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162647","number":162647,"mergeCommit":{"message":"[Security
Solution] Fix rounding in top alerts chart on alerts page
(#162647)\n\n## Summary\r\n\r\nThis PR addresses
(https://github.com/elastic/kibana/issues/162521). In\r\nextreme cases
when there are a lot of alerts without user names, entries\r\nin top
alerts chart disappear. This is due to entries being rounded to
3\r\ndecimal places, when denominator grows too big, the percentages
are\r\nrounded to zero.\r\n\r\nThis PR removed the rounding and added a
label `<1%` when top alerts\r\ngrouping drops below 1%. User should
always see entries if they
are\r\navailable.\r\n\r\n\r\n![image](42ae8453-ccc7-4c71-8bd0-27a79b9b8318)\r\n\r\n**How
to test**\r\nFirst generate a few alerts with user name:\r\n- Go to
`security_solution` folder:
`cd\r\nx-pack/plugins/security_solution`\r\n- Run resolver generate data
script `yarn test:generate --ne 5\r\n--relAlerts 1` - this command will
generate 5 hosts each with 1 alert\r\n\r\nTo generate alerts without
user names, comment lines that populate user\r\nnames
in\r\n`x-pack/plugins/security_solution/common/endpoint/generate_data.ts`\r\n(there
are multiple places)\r\n```\r\nuser: {\r\n domain:
this.randomString(10),\r\n name: this.randomString(10),\r\n
},\r\n```\r\n- run the script again `yarn test:generate --ne 10
--relAlerts 50` -\r\nthis command will generate 50 alerts each for 10
hosts\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"af15cc19c429aa4dd318e21c74e47fb0f13bad8c"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
 2023-08-03 13:34:51 -07:00
Kibana Machine
4cb1cc2197
[8.9] [SecuritySolution] Update user metrics labels (#163097) (#163115) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[SecuritySolution] Update user metrics labels
(#163097)](https://github.com/elastic/kibana/pull/163097)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Angela
Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-03T18:44:00Z","message":"[SecuritySolution]
Update user metrics labels
(#163097)","sha":"53a7d0c97fb2bea73903a6c32217264c714d25d4","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Explore","Feature:Lens
Charts","v8.10.0","v8.9.1"],"number":163097,"url":"https://github.com/elastic/kibana/pull/163097","mergeCommit":{"message":"[SecuritySolution]
Update user metrics labels
(#163097)","sha":"53a7d0c97fb2bea73903a6c32217264c714d25d4"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163097","number":163097,"mergeCommit":{"message":"[SecuritySolution]
Update user metrics labels
(#163097)","sha":"53a7d0c97fb2bea73903a6c32217264c714d25d4"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>
 2023-08-03 13:08:40 -07:00
Julia Rechkunova
74604ca7c8
[8.9] [Discover] Fix search sessions using temporary data views (#161029) (#163087) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Discover] Fix search sessions using temporary data views
(#161029)](https://github.com/elastic/kibana/pull/161029)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Matthias
Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2023-07-03T12:10:25Z","message":"[Discover]
Fix search sessions using temporary data views (#161029)\n\nEnables
search sessions in Discover to work correctly with temporary data
view\r\n\r\nCo-authored-by: Julia Rechkunova
<julia.rechkunova@gmail.com>","sha":"25c6446711392fbc2a71b1a88a46edd9599a2c16","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","backport:skip","Team:DataDiscovery","v8.10.0"],"number":161029,"url":"https://github.com/elastic/kibana/pull/161029","mergeCommit":{"message":"[Discover]
Fix search sessions using temporary data views (#161029)\n\nEnables
search sessions in Discover to work correctly with temporary data
view\r\n\r\nCo-authored-by: Julia Rechkunova
<julia.rechkunova@gmail.com>","sha":"25c6446711392fbc2a71b1a88a46edd9599a2c16"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161029","number":161029,"mergeCommit":{"message":"[Discover]
Fix search sessions using temporary data views (#161029)\n\nEnables
search sessions in Discover to work correctly with temporary data
view\r\n\r\nCo-authored-by: Julia Rechkunova
<julia.rechkunova@gmail.com>","sha":"25c6446711392fbc2a71b1a88a46edd9599a2c16"}}]}]
BACKPORT-->

Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>
 2023-08-03 18:23:58 +02:00
Kibana Machine
b08ac7642c
[8.9] [Unified Histogram] Set legend width to extra large and enable text wrapping in legend labels (#163009) (#163060) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Unified Histogram] Set legend width to extra large and enable text
wrapping in legend labels
(#163009)](https://github.com/elastic/kibana/pull/163009)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Davis
McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2023-08-03T13:00:14Z","message":"[Unified
Histogram] Set legend width to extra large and enable text wrapping in
legend labels (#163009)\n\n## Summary\r\n\r\nThis PR sets the Unified
Histogram chart's legend width to extra large\r\nand enables text
wrapping in legend labels.\r\n\r\nNote that this means the legend will
always use the extra large size\r\n(230px) even if the screen size is
small or the labels do not fill the\r\navailable legend
space.\r\n\r\nWith long labels:\r\n<img width=\"1369\"
alt=\"long\"\r\nsrc=\"1f6f0d80-d924-48a4-b758-4cf72b99fc57\">\r\n\r\nWith
short labels:\r\n<img width=\"1369\"
alt=\"short\"\r\nsrc=\"704f2b75-a565-44a0-be1a-e27bdca00a8e\">\r\n\r\nResolves
#162932.\r\n\r\n### Checklist\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- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"79303c24f6ee395a3860947a691ff8da1df7c4d6","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Discover","Team:DataDiscovery","backport:prev-minor","Feature:UnifiedHistogram","v8.10.0"],"number":163009,"url":"https://github.com/elastic/kibana/pull/163009","mergeCommit":{"message":"[Unified
Histogram] Set legend width to extra large and enable text wrapping in
legend labels (#163009)\n\n## Summary\r\n\r\nThis PR sets the Unified
Histogram chart's legend width to extra large\r\nand enables text
wrapping in legend labels.\r\n\r\nNote that this means the legend will
always use the extra large size\r\n(230px) even if the screen size is
small or the labels do not fill the\r\navailable legend
space.\r\n\r\nWith long labels:\r\n<img width=\"1369\"
alt=\"long\"\r\nsrc=\"1f6f0d80-d924-48a4-b758-4cf72b99fc57\">\r\n\r\nWith
short labels:\r\n<img width=\"1369\"
alt=\"short\"\r\nsrc=\"704f2b75-a565-44a0-be1a-e27bdca00a8e\">\r\n\r\nResolves
#162932.\r\n\r\n### Checklist\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- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"79303c24f6ee395a3860947a691ff8da1df7c4d6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163009","number":163009,"mergeCommit":{"message":"[Unified
Histogram] Set legend width to extra large and enable text wrapping in
legend labels (#163009)\n\n## Summary\r\n\r\nThis PR sets the Unified
Histogram chart's legend width to extra large\r\nand enables text
wrapping in legend labels.\r\n\r\nNote that this means the legend will
always use the extra large size\r\n(230px) even if the screen size is
small or the labels do not fill the\r\navailable legend
space.\r\n\r\nWith long labels:\r\n<img width=\"1369\"
alt=\"long\"\r\nsrc=\"1f6f0d80-d924-48a4-b758-4cf72b99fc57\">\r\n\r\nWith
short labels:\r\n<img width=\"1369\"
alt=\"short\"\r\nsrc=\"704f2b75-a565-44a0-be1a-e27bdca00a8e\">\r\n\r\nResolves
#162932.\r\n\r\n### Checklist\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- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"79303c24f6ee395a3860947a691ff8da1df7c4d6"}}]}]
BACKPORT-->

Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>
 2023-08-03 07:11:27 -07:00
Kibana Machine
ad47e5faf8
[8.9] [data views] fix renamed field filters (#162860) (#163047) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[data views] fix renamed field filters
(#162860)](https://github.com/elastic/kibana/pull/162860)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Matthew
Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2023-08-03T10:48:40Z","message":"[data
views] fix renamed field filters (#162860)\n\n## Summary\r\n\r\nField
filters (aka source filters) are given a `clientId` when
they're\r\nchanged. Unfortunately this is missing from the schema which
can result\r\nin schema failures.\r\n\r\nThe schema has been fixed and a
functional test has been added that\r\nverifies field filter renaming
functionality.\r\n\r\nCloses:
https://github.com/elastic/kibana/issues/162611\r\n\r\n## Release
Note\r\n\r\nResolves potential errors present in v8.9.0 with data views
that contain\r\nfield filters that have been
edited.","sha":"d9f5223e2de3815da750cbb8ef6db8994fa087c5","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data
Views","Team:DataDiscovery","backport:prev-minor","v8.10.0"],"number":162860,"url":"https://github.com/elastic/kibana/pull/162860","mergeCommit":{"message":"[data
views] fix renamed field filters (#162860)\n\n## Summary\r\n\r\nField
filters (aka source filters) are given a `clientId` when
they're\r\nchanged. Unfortunately this is missing from the schema which
can result\r\nin schema failures.\r\n\r\nThe schema has been fixed and a
functional test has been added that\r\nverifies field filter renaming
functionality.\r\n\r\nCloses:
https://github.com/elastic/kibana/issues/162611\r\n\r\n## Release
Note\r\n\r\nResolves potential errors present in v8.9.0 with data views
that contain\r\nfield filters that have been
edited.","sha":"d9f5223e2de3815da750cbb8ef6db8994fa087c5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162860","number":162860,"mergeCommit":{"message":"[data
views] fix renamed field filters (#162860)\n\n## Summary\r\n\r\nField
filters (aka source filters) are given a `clientId` when
they're\r\nchanged. Unfortunately this is missing from the schema which
can result\r\nin schema failures.\r\n\r\nThe schema has been fixed and a
functional test has been added that\r\nverifies field filter renaming
functionality.\r\n\r\nCloses:
https://github.com/elastic/kibana/issues/162611\r\n\r\n## Release
Note\r\n\r\nResolves potential errors present in v8.9.0 with data views
that contain\r\nfield filters that have been
edited.","sha":"d9f5223e2de3815da750cbb8ef6db8994fa087c5"}}]}]
BACKPORT-->

Co-authored-by: Matthew Kime <matt@mattki.me>
 2023-08-03 04:59:10 -07:00
Kibana Machine
ac129046a0
[8.9] [Security Solution] Legacy actions are deleted when user tries to save a rule and the run action interval is slower than rule run interval (#160798) (#162779) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Legacy actions are deleted when user tries to
save a rule and the run action interval is slower than rule run interval
(#160798)](https://github.com/elastic/kibana/pull/160798)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Ievgen
Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2023-07-31T09:51:38Z","message":"[Security
Solution] Legacy actions are deleted when user tries to save a rule and
the run action interval is slower than rule run interval (#160798)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/157462\r\n\r\nWith these
changes we fix the legacy actions data loss (on migration)\r\nissue. One
of the first steps of the migration we retrieve legacy\r\nactions and
immediately delete them. Then we do validation which might\r\nthrow an
exception and all legacy actions will be lost in this case.\r\n\r\nAs a
solution we will do legacy actions validation before deleting
them\r\nand throwing exception in case those are broken. This means that
in case\r\nlegacy action is broken user will need to export the rule,
fix it\r\nmanually and import it again. Or just re-create it from
scratch.\r\n\r\n\r\na23f5d43-3758-4ab7-8e63-bd93016e338d","sha":"8ca90fbfc3f5f201e12053d9675c41b0906b8f9e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","Team:
SecuritySolution","ci:cloud-deploy","Team:Detection
Engine","v8.10.0","v8.9.1"],"number":160798,"url":"https://github.com/elastic/kibana/pull/160798","mergeCommit":{"message":"[Security
Solution] Legacy actions are deleted when user tries to save a rule and
the run action interval is slower than rule run interval (#160798)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/157462\r\n\r\nWith these
changes we fix the legacy actions data loss (on migration)\r\nissue. One
of the first steps of the migration we retrieve legacy\r\nactions and
immediately delete them. Then we do validation which might\r\nthrow an
exception and all legacy actions will be lost in this case.\r\n\r\nAs a
solution we will do legacy actions validation before deleting
them\r\nand throwing exception in case those are broken. This means that
in case\r\nlegacy action is broken user will need to export the rule,
fix it\r\nmanually and import it again. Or just re-create it from
scratch.\r\n\r\n\r\na23f5d43-3758-4ab7-8e63-bd93016e338d","sha":"8ca90fbfc3f5f201e12053d9675c41b0906b8f9e"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/160798","number":160798,"mergeCommit":{"message":"[Security
Solution] Legacy actions are deleted when user tries to save a rule and
the run action interval is slower than rule run interval (#160798)\n\n##
Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/157462\r\n\r\nWith these
changes we fix the legacy actions data loss (on migration)\r\nissue. One
of the first steps of the migration we retrieve legacy\r\nactions and
immediately delete them. Then we do validation which might\r\nthrow an
exception and all legacy actions will be lost in this case.\r\n\r\nAs a
solution we will do legacy actions validation before deleting
them\r\nand throwing exception in case those are broken. This means that
in case\r\nlegacy action is broken user will need to export the rule,
fix it\r\nmanually and import it again. Or just re-create it from
scratch.\r\n\r\n\r\na23f5d43-3758-4ab7-8e63-bd93016e338d","sha":"8ca90fbfc3f5f201e12053d9675c41b0906b8f9e"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
 2023-08-03 02:48:54 -07:00
Kibana Machine
e38b2c7f24
[8.9] [Ingest Pipelines] Fix bug in reroute processor (#162872) (#162991) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Ingest Pipelines] Fix bug in reroute processor
(#162872)](https://github.com/elastic/kibana/pull/162872)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Elena
Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-02T15:53:55Z","message":"[Ingest
Pipelines] Fix bug in reroute processor (#162872)\n\nFixes
https://github.com/elastic/kibana/issues/162823\r\n\r\n##
Summary\r\n\r\nThis PR fixes the bug in the Reroute processor form which
makes the page\r\ncrash when switching from another processor type to
reroute processor.\r\n\r\n**How to test:**\r\n\r\n1. Start Es with `yarn
es snapshot` and Kibana with `yarn start`.\r\n2. Go to Stack Management
> Ingest Pipeline.\r\n3. Click **Create pipeline**, and then select
**New pipeline**.\r\n4. Click **Add a processor**.\r\n5. In the
**Configure processor** form, open the Processor dropdown, and\r\nselect
Reroute.\r\n6. From the Processor dropdown, select Bytes (or any other
processor\r\ntype).\r\n7. From the Processor dropdown, select
Reroute.\r\n8. Verify that the form works as
expected.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"190a98f48734668d0c2a970348ca9852da086769","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Deployment
Management","release_note:skip","Feature:Ingest Node
Pipelines","backport:prev-minor","v8.10.0","v8.9.1"],"number":162872,"url":"https://github.com/elastic/kibana/pull/162872","mergeCommit":{"message":"[Ingest
Pipelines] Fix bug in reroute processor (#162872)\n\nFixes
https://github.com/elastic/kibana/issues/162823\r\n\r\n##
Summary\r\n\r\nThis PR fixes the bug in the Reroute processor form which
makes the page\r\ncrash when switching from another processor type to
reroute processor.\r\n\r\n**How to test:**\r\n\r\n1. Start Es with `yarn
es snapshot` and Kibana with `yarn start`.\r\n2. Go to Stack Management
> Ingest Pipeline.\r\n3. Click **Create pipeline**, and then select
**New pipeline**.\r\n4. Click **Add a processor**.\r\n5. In the
**Configure processor** form, open the Processor dropdown, and\r\nselect
Reroute.\r\n6. From the Processor dropdown, select Bytes (or any other
processor\r\ntype).\r\n7. From the Processor dropdown, select
Reroute.\r\n8. Verify that the form works as
expected.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"190a98f48734668d0c2a970348ca9852da086769"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162872","number":162872,"mergeCommit":{"message":"[Ingest
Pipelines] Fix bug in reroute processor (#162872)\n\nFixes
https://github.com/elastic/kibana/issues/162823\r\n\r\n##
Summary\r\n\r\nThis PR fixes the bug in the Reroute processor form which
makes the page\r\ncrash when switching from another processor type to
reroute processor.\r\n\r\n**How to test:**\r\n\r\n1. Start Es with `yarn
es snapshot` and Kibana with `yarn start`.\r\n2. Go to Stack Management
> Ingest Pipeline.\r\n3. Click **Create pipeline**, and then select
**New pipeline**.\r\n4. Click **Add a processor**.\r\n5. In the
**Configure processor** form, open the Processor dropdown, and\r\nselect
Reroute.\r\n6. From the Processor dropdown, select Bytes (or any other
processor\r\ntype).\r\n7. From the Processor dropdown, select
Reroute.\r\n8. Verify that the form works as
expected.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"190a98f48734668d0c2a970348ca9852da086769"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
 2023-08-02 10:02:55 -07:00
Tiago Costa
59aff4a6f2
skip flaky suite (#159123, #159124) 2023-08-02 17:05:29 +01:00
Kevin Logan
c5ad96469f
[8.9][Security Solution] Skip flaky CTI test (#162965) 
## Summary

Skip the CTI test on `8.9` that was skipped in this PR:
https://github.com/elastic/kibana/pull/162787

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
 2023-08-02 11:49:12 -04:00
Kibana Machine
08a8c73865
[8.9] [APM] Fix flamegraph rendering (#162968) (#162975) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[APM] Fix flamegraph rendering
(#162968)](https://github.com/elastic/kibana/pull/162968)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Katerina","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2023-08-02T13:27:48Z","message":"[APM]
Fix flamegraph rendering (#162968)\n\n## Summary\r\n\r\nclose:
#[158963](https://github.com/elastic/kibana/issues/162967)\r\n\r\n###
Before\r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 26
29\"\r\nsrc=\"669fe47f-94c0-4cff-b9a9-8a0f315eaab6\">\r\n\r\n###
After \r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 25
09\"\r\nsrc=\"b0976498-1680-45df-a9b8-0b0ae1666a0b\">","sha":"59a4e56c503e825785161cd2829ba5a942209371","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:APM","backport:prev-minor","v8.10.0"],"number":162968,"url":"https://github.com/elastic/kibana/pull/162968","mergeCommit":{"message":"[APM]
Fix flamegraph rendering (#162968)\n\n## Summary\r\n\r\nclose:
#[158963](https://github.com/elastic/kibana/issues/162967)\r\n\r\n###
Before\r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 26
29\"\r\nsrc=\"669fe47f-94c0-4cff-b9a9-8a0f315eaab6\">\r\n\r\n###
After \r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 25
09\"\r\nsrc=\"b0976498-1680-45df-a9b8-0b0ae1666a0b\">","sha":"59a4e56c503e825785161cd2829ba5a942209371"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162968","number":162968,"mergeCommit":{"message":"[APM]
Fix flamegraph rendering (#162968)\n\n## Summary\r\n\r\nclose:
#[158963](https://github.com/elastic/kibana/issues/162967)\r\n\r\n###
Before\r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 26
29\"\r\nsrc=\"669fe47f-94c0-4cff-b9a9-8a0f315eaab6\">\r\n\r\n###
After \r\n<img width=\"1775\" alt=\"Screenshot 2023-08-02 at 13 25
09\"\r\nsrc=\"b0976498-1680-45df-a9b8-0b0ae1666a0b\">","sha":"59a4e56c503e825785161cd2829ba5a942209371"}}]}]
BACKPORT-->

Co-authored-by: Katerina <aikaterini.patticha@elastic.co>
 2023-08-02 08:06:50 -07:00
Kibana Machine
01006e0b7e
[8.9] [DOCS] Remove breaking changes tags (#162928) (#162969) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Remove breaking changes tags
(#162928)](https://github.com/elastic/kibana/pull/162928)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"James
Rodewig","email":"james.rodewig@elastic.co"},"sourceCommit":{"committedDate":"2023-08-02T12:27:22Z","message":"[DOCS]
Remove breaking changes tags (#162928)\n\nWith
https://github.com/elastic/stack-docs/pull/2495 merged, we no longer
need tags to reuse breaking changes in the Stack Install/Upgrade
guide.","sha":"98fcc817766c8dfef628a476f78309cca6c6d618","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.10.0","v8.9.1"],"number":162928,"url":"https://github.com/elastic/kibana/pull/162928","mergeCommit":{"message":"[DOCS]
Remove breaking changes tags (#162928)\n\nWith
https://github.com/elastic/stack-docs/pull/2495 merged, we no longer
need tags to reuse breaking changes in the Stack Install/Upgrade
guide.","sha":"98fcc817766c8dfef628a476f78309cca6c6d618"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162928","number":162928,"mergeCommit":{"message":"[DOCS]
Remove breaking changes tags (#162928)\n\nWith
https://github.com/elastic/stack-docs/pull/2495 merged, we no longer
need tags to reuse breaking changes in the Stack Install/Upgrade
guide.","sha":"98fcc817766c8dfef628a476f78309cca6c6d618"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
 2023-08-02 08:50:17 -04:00
Kibana Machine
d941804915
[8.9] [Profiling] Remove profiling from apm-server in apm package policy (#162798) (#162960) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Profiling] Remove profiling from apm-server in apm package policy
(#162798)](https://github.com/elastic/kibana/pull/162798)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Cauê
Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-02T10:50:34Z","message":"[Profiling]
Remove profiling from apm-server in apm package policy (#162798)\n\nThis
PR does:\r\n\r\n- Verify if the APM package policy contains profiling
instructions\r\n- When it does, it show the set up instructions.\r\n-
When the setup profiling button is clicked, updates the apm
package\r\npolicy removing the profiling
instructions.\r\n\r\n---------\r\n\r\nCo-authored-by: Francesco Gualazzi
<inge4pres@users.noreply.github.com>","sha":"2fd6af9063ecd0b7719573dbd4571531911cc1b7","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","ci:build-cloud-image","v8.10.0","v8.9.1"],"number":162798,"url":"https://github.com/elastic/kibana/pull/162798","mergeCommit":{"message":"[Profiling]
Remove profiling from apm-server in apm package policy (#162798)\n\nThis
PR does:\r\n\r\n- Verify if the APM package policy contains profiling
instructions\r\n- When it does, it show the set up instructions.\r\n-
When the setup profiling button is clicked, updates the apm
package\r\npolicy removing the profiling
instructions.\r\n\r\n---------\r\n\r\nCo-authored-by: Francesco Gualazzi
<inge4pres@users.noreply.github.com>","sha":"2fd6af9063ecd0b7719573dbd4571531911cc1b7"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162798","number":162798,"mergeCommit":{"message":"[Profiling]
Remove profiling from apm-server in apm package policy (#162798)\n\nThis
PR does:\r\n\r\n- Verify if the APM package policy contains profiling
instructions\r\n- When it does, it show the set up instructions.\r\n-
When the setup profiling button is clicked, updates the apm
package\r\npolicy removing the profiling
instructions.\r\n\r\n---------\r\n\r\nCo-authored-by: Francesco Gualazzi
<inge4pres@users.noreply.github.com>","sha":"2fd6af9063ecd0b7719573dbd4571531911cc1b7"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>
 2023-08-02 05:04:11 -07:00
Kibana Machine
a1bc028122
[8.9] [Migrations] Unskip migration integration tests after fixing (#162648) (#162911) 
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Migrations] Unskip migration integration tests after fixing
(#162648)](https://github.com/elastic/kibana/pull/162648)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Michael
Dokolin","email":"mikhail.dokolin@elastic.co"},"sourceCommit":{"committedDate":"2023-08-01T15:16:07Z","message":"[Migrations]
Unskip migration integration tests after fixing
(#162648)","sha":"fcb592de8d88ad24eefc8783207738d7569db19d","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Feature:Migrations","8.10
candidate","v8.10.0","v8.8.3","v8.9.1"],"number":162648,"url":"https://github.com/elastic/kibana/pull/162648","mergeCommit":{"message":"[Migrations]
Unskip migration integration tests after fixing
(#162648)","sha":"fcb592de8d88ad24eefc8783207738d7569db19d"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162648","number":162648,"mergeCommit":{"message":"[Migrations]
Unskip migration integration tests after fixing
(#162648)","sha":"fcb592de8d88ad24eefc8783207738d7569db19d"}},{"branch":"8.8","label":"v8.8.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Michael Dokolin <mikhail.dokolin@elastic.co>
 2023-08-01 09:39:42 -07:00
Tiago Costa
c4bc8675e1
skip flaky suite (#156741) 2023-08-01 15:58:10 +01:00