Commit graph

64885 commits

Author SHA1 Message Date
Bruno Mercier Costa
a85d46cc4d
Update settings.asciidoc
Add `[ ]` brackets to the `server.ssl.cipherSuites` since it's unclear on both OpenSSL & Kibana docs that these are needed
2023-09-01 15:20:15 +02:00
jennypavlova
7bb86679fe
[Infra UI] Process tab flaky test fix- Wait for page loading (#165440)
Closes #160796 

## Summary

As we see in the picture from the failed build we are trying to check
the values when there are still spinners on the screen (so the data is
still loading).

<img width="1791" alt="image"
src="94608e6b-21b1-4435-9cee-efbf5a57f4ac">


To fix that I am now waiting for the page to load. This PR will be
backported to fix the issue in 8.9 and I will add a follow-up PR
(https://github.com/elastic/kibana/pull/165303) for the same fix in node
details tests.


[Build](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3035)
2023-09-01 15:06:58 +02:00
Kibana Machine
21f3ebd6e9
[8.9] [Flaky #98240] Unskip test (#165197) (#165249)
# Backport

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

<!--- 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-30T15:04:22Z","message":"[Flaky
#98240] Unskip test
(#165197)","sha":"0236516351e89ce1591d916c24d45a406bef714d","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","technical
debt","release_note:skip","backport:all-open","v8.11.0"],"number":165197,"url":"https://github.com/elastic/kibana/pull/165197","mergeCommit":{"message":"[Flaky
#98240] Unskip test
(#165197)","sha":"0236516351e89ce1591d916c24d45a406bef714d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165197","number":165197,"mergeCommit":{"message":"[Flaky
#98240] Unskip test
(#165197)","sha":"0236516351e89ce1591d916c24d45a406bef714d"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
2023-08-30 09:10:33 -07:00
Kibana Machine
4f33e26474
[8.9] Do not enforce app authorization for features that have opted out of RBAC. (#165190) (#165230)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Do not enforce app authorization for features that have opted out of
RBAC. (#165190)](https://github.com/elastic/kibana/pull/165190)

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

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

<!--BACKPORT [{"author":{"name":"Aleh
Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2023-08-30T12:38:13Z","message":"Do
not enforce app authorization for features that have opted out of RBAC.
(#165190)\n\n## Summary\r\n\r\nThe title says it all, we shouldn't
enforce app authorization for\r\nfeatures that have opted out of RBAC.
Currently we have just two such\r\nfeatures: Enterprise Search and
Monitoring.","sha":"f1cc1eb53879a21f0eaf13ef900e0fd872bd7038","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Security","release_note:skip","Feature:Security/Authorization","backport:all-open","Project:Serverless","ci:build-serverless-image","v8.11.0"],"number":165190,"url":"https://github.com/elastic/kibana/pull/165190","mergeCommit":{"message":"Do
not enforce app authorization for features that have opted out of RBAC.
(#165190)\n\n## Summary\r\n\r\nThe title says it all, we shouldn't
enforce app authorization for\r\nfeatures that have opted out of RBAC.
Currently we have just two such\r\nfeatures: Enterprise Search and
Monitoring.","sha":"f1cc1eb53879a21f0eaf13ef900e0fd872bd7038"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165190","number":165190,"mergeCommit":{"message":"Do
not enforce app authorization for features that have opted out of RBAC.
(#165190)\n\n## Summary\r\n\r\nThe title says it all, we shouldn't
enforce app authorization for\r\nfeatures that have opted out of RBAC.
Currently we have just two such\r\nfeatures: Enterprise Search and
Monitoring.","sha":"f1cc1eb53879a21f0eaf13ef900e0fd872bd7038"}}]}]
BACKPORT-->

Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co>
2023-08-30 07:18:42 -07:00
Jon
3256376c69
[8.9] Provide glibc <3.4.20 compatible version of re2 ARM64 binary (#165151)
This updates the download for our arm64 re2 binary to one with support
for older glibc versions, fixing an issue where Kibana does not start on
CentOS/RHEL 7.

The binary is built from our pipeline at
https://github.com/elastic/kibana-custom-nodejs-builds/, where re2 is
now built in a CentOS 7 container. A download redirect will be updated
in parallel with this pull request.

This is only targeting 8.9. 8.10+ was already updated to use the new
pipeline during the upgrade to Node 18.
2023-08-30 09:01:37 -05:00
Kibana Machine
7b337dea96
[8.9] [Flaky #116059] Unskip test (#165125) (#165201)
# Backport

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

<!--- 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-30T09:16:11Z","message":"[Flaky
#116059] Unskip test
(#165125)","sha":"cc728f6f2bcfeabec55b54a6c7bcfd5fee3661f0","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:all-open","v8.11.0"],"number":165125,"url":"https://github.com/elastic/kibana/pull/165125","mergeCommit":{"message":"[Flaky
#116059] Unskip test
(#165125)","sha":"cc728f6f2bcfeabec55b54a6c7bcfd5fee3661f0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165125","number":165125,"mergeCommit":{"message":"[Flaky
#116059] Unskip test
(#165125)","sha":"cc728f6f2bcfeabec55b54a6c7bcfd5fee3661f0"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
2023-08-30 03:18:31 -07:00
Kibana Machine
b89e9eeab0
[8.9] [ML] Anomaly detection wizard: ensure custom urls test functionality works as expected (#165055) (#165178)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[ML] Anomaly detection wizard: ensure custom urls test functionality
works as expected
(#165055)](https://github.com/elastic/kibana/pull/165055)

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

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

<!--BACKPORT [{"author":{"name":"Melissa
Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2023-08-29T22:24:01Z","message":"[ML]
Anomaly detection wizard: ensure custom urls test functionality works as
expected (#165055)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/165051, ensuring the\r\ncorrect
time range is used in the target Dashboard or Discover pages\r\nwhen
testing custom URLs created in the Anomaly Detection job
wizards.\r\nPreviously on subsequent tests the page would always open to
show `Last\r\n15 minutes` rather than a time range for which there are
documents in\r\nthe data view used by the datafeed.\r\n\r\nThis PR
ensures the original job object is not affected when the\r\ndatafeed is
removed for sending off to the
endpoint.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"501e9bda2a6c17732c525d557b97f12c48dfe345","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:Anomaly
Detection","v8.10.0","v8.11.0","v8.9.2"],"number":165055,"url":"https://github.com/elastic/kibana/pull/165055","mergeCommit":{"message":"[ML]
Anomaly detection wizard: ensure custom urls test functionality works as
expected (#165055)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/165051, ensuring the\r\ncorrect
time range is used in the target Dashboard or Discover pages\r\nwhen
testing custom URLs created in the Anomaly Detection job
wizards.\r\nPreviously on subsequent tests the page would always open to
show `Last\r\n15 minutes` rather than a time range for which there are
documents in\r\nthe data view used by the datafeed.\r\n\r\nThis PR
ensures the original job object is not affected when the\r\ndatafeed is
removed for sending off to the
endpoint.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"501e9bda2a6c17732c525d557b97f12c48dfe345"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165055","number":165055,"mergeCommit":{"message":"[ML]
Anomaly detection wizard: ensure custom urls test functionality works as
expected (#165055)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/165051, ensuring the\r\ncorrect
time range is used in the target Dashboard or Discover pages\r\nwhen
testing custom URLs created in the Anomaly Detection job
wizards.\r\nPreviously on subsequent tests the page would always open to
show `Last\r\n15 minutes` rather than a time range for which there are
documents in\r\nthe data view used by the datafeed.\r\n\r\nThis PR
ensures the original job object is not affected when the\r\ndatafeed is
removed for sending off to the
endpoint.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"501e9bda2a6c17732c525d557b97f12c48dfe345"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co>
2023-08-29 16:48:57 -07:00
Kibana Machine
e3110ec557
[8.9] [DOCS] Add examples for proxyBypassHosts and proxyOnlyHosts settings (#164981) (#165164)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Add examples for `proxyBypassHosts` and `proxyOnlyHosts`
settings (#164981)](https://github.com/elastic/kibana/pull/164981)

<!--- 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-29T20:13:27Z","message":"[DOCS]
Add examples for `proxyBypassHosts` and `proxyOnlyHosts` settings
(#164981)\n\nAdds example values for the
`xpack.actions.proxyBypassHosts` and `xpack.actions.proxyOnlyHosts`
settings.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/139560","sha":"00853534c8be36feebb4eac05039a73074268025","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorsManagement","v8.10.0","v7.17.13","v8.11.0","v8.9.2"],"number":164981,"url":"https://github.com/elastic/kibana/pull/164981","mergeCommit":{"message":"[DOCS]
Add examples for `proxyBypassHosts` and `proxyOnlyHosts` settings
(#164981)\n\nAdds example values for the
`xpack.actions.proxyBypassHosts` and `xpack.actions.proxyOnlyHosts`
settings.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/139560","sha":"00853534c8be36feebb4eac05039a73074268025"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","7.17","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.13","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164981","number":164981,"mergeCommit":{"message":"[DOCS]
Add examples for `proxyBypassHosts` and `proxyOnlyHosts` settings
(#164981)\n\nAdds example values for the
`xpack.actions.proxyBypassHosts` and `xpack.actions.proxyOnlyHosts`
settings.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/139560","sha":"00853534c8be36feebb4eac05039a73074268025"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
2023-08-29 16:37:59 -04:00
Kibana Machine
30f9bafa7f
[8.9] [DOCS] Update GitHub links in dev docs (#164503) (#165153)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Update GitHub links in dev docs
(#164503)](https://github.com/elastic/kibana/pull/164503)

<!--- 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-29T18:43:41Z","message":"[DOCS]
Update GitHub links in dev docs
(#164503)","sha":"6fdfefe4ffb452d29c203fcba975aa844c5d5dac","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Feature:ExpressionLanguage","release_note:skip","docs","v8.10.0","v8.11.0","v8.9.2"],"number":164503,"url":"https://github.com/elastic/kibana/pull/164503","mergeCommit":{"message":"[DOCS]
Update GitHub links in dev docs
(#164503)","sha":"6fdfefe4ffb452d29c203fcba975aa844c5d5dac"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164503","number":164503,"mergeCommit":{"message":"[DOCS]
Update GitHub links in dev docs
(#164503)","sha":"6fdfefe4ffb452d29c203fcba975aa844c5d5dac"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
2023-08-29 12:59:15 -07:00
Kibana Machine
1547c63cc9
[8.9] [Security Solution][Bug] Fix legacy showTopN popover actions (#165099) (#165119)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Bug] Fix legacy showTopN popover actions
(#165099)](https://github.com/elastic/kibana/pull/165099)

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

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

<!--BACKPORT [{"author":{"name":"Sergi
Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2023-08-29T15:16:09Z","message":"[Security
Solution][Bug] Fix legacy showTopN popover actions (#165099)\n\n##
Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/164800\r\n\r\nThe bug was
caused by the popover closing before the actions were able\r\nto
execute.\r\nSince all action executions are async, closing the popover
at the end of\r\nthe event loop (using `setTimeout`) is enough to allow
the action to\r\nexecute properly before the showTopN popover is
closed.\r\n\r\n###
Demo\r\n\r\n\r\ne427a81f-17ed-436c-89b3-903a94632d70","sha":"625b6f752e26b141bbaa8b48caa298d4c76177b3","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Threat
Hunting","Team:Threat
Hunting:Explore","v8.10.0","v8.11.0","v8.9.2"],"number":165099,"url":"https://github.com/elastic/kibana/pull/165099","mergeCommit":{"message":"[Security
Solution][Bug] Fix legacy showTopN popover actions (#165099)\n\n##
Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/164800\r\n\r\nThe bug was
caused by the popover closing before the actions were able\r\nto
execute.\r\nSince all action executions are async, closing the popover
at the end of\r\nthe event loop (using `setTimeout`) is enough to allow
the action to\r\nexecute properly before the showTopN popover is
closed.\r\n\r\n###
Demo\r\n\r\n\r\ne427a81f-17ed-436c-89b3-903a94632d70","sha":"625b6f752e26b141bbaa8b48caa298d4c76177b3"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165099","number":165099,"mergeCommit":{"message":"[Security
Solution][Bug] Fix legacy showTopN popover actions (#165099)\n\n##
Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/164800\r\n\r\nThe bug was
caused by the popover closing before the actions were able\r\nto
execute.\r\nSince all action executions are async, closing the popover
at the end of\r\nthe event loop (using `setTimeout`) is enough to allow
the action to\r\nexecute properly before the showTopN popover is
closed.\r\n\r\n###
Demo\r\n\r\n\r\ne427a81f-17ed-436c-89b3-903a94632d70","sha":"625b6f752e26b141bbaa8b48caa298d4c76177b3"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
2023-08-29 09:33:31 -07:00
Kibana Machine
d098dee68c
[8.9] [APM] Swallow unhandled exceptions (#164251) (#165111)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[APM] Swallow unhandled exceptions
(#164251)](https://github.com/elastic/kibana/pull/164251)

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

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

<!--BACKPORT [{"author":{"name":"Søren
Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2023-08-21T18:10:30Z","message":"[APM]
Swallow unhandled exceptions (#164251)\n\nIf an unhandled error occurs,
it will break the diagnostics bundle. This\r\nchange will log errors and
then swallow them.\r\nThis should go out in 8.10 since it is already
affecting
users.","sha":"654de7b7285ad5748dc9ff1e19156e753d68d568","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","auto-backport","backport:prev-minor","apm:cypress-record","v8.9.0","v8.10.0","v8.11.0"],"number":164251,"url":"https://github.com/elastic/kibana/pull/164251","mergeCommit":{"message":"[APM]
Swallow unhandled exceptions (#164251)\n\nIf an unhandled error occurs,
it will break the diagnostics bundle. This\r\nchange will log errors and
then swallow them.\r\nThis should go out in 8.10 since it is already
affecting
users.","sha":"654de7b7285ad5748dc9ff1e19156e753d68d568"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/164342","number":164342,"state":"MERGED","mergeCommit":{"sha":"481e6d5a9a7cd9bd89dbe6ef7bb821d556e7793f","message":"[8.10]
[APM] Swallow unhandled exceptions (#164251) (#164342)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.10`:\n- [[APM] Swallow unhandled
exceptions\n(#164251)](https://github.com/elastic/kibana/pull/164251)\n\n<!---
Backport version: 8.9.7 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Søren\nLouv-Jansen\",\"email\":\"soren.louv@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2023-08-21T18:10:30Z\",\"message\":\"[APM]\nSwallow
unhandled exceptions (#164251)\\n\\nIf an unhandled error occurs,\nit
will break the diagnostics bundle. This\\r\\nchange will log errors
and\nthen swallow them.\\r\\nThis should go out in 8.10 since it is
already\naffecting\nusers.\",\"sha\":\"654de7b7285ad5748dc9ff1e19156e753d68d568\",\"branchLabelMapping\":{\"^v8.11.0$\":\"main\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:APM\",\"release_note:skip\",\"backport:prev-minor\",\"apm:cypress-record\",\"v8.10.0\",\"v8.11.0\"],\"number\":164251,\"url\":\"https://github.com/elastic/kibana/pull/164251\",\"mergeCommit\":{\"message\":\"[APM]\nSwallow
unhandled exceptions (#164251)\\n\\nIf an unhandled error occurs,\nit
will break the diagnostics bundle. This\\r\\nchange will log errors
and\nthen swallow them.\\r\\nThis should go out in 8.10 since it is
already\naffecting\nusers.\",\"sha\":\"654de7b7285ad5748dc9ff1e19156e753d68d568\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.10\"],\"targetPullRequestStates\":[{\"branch\":\"8.10\",\"label\":\"v8.10.0\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v8.11.0\",\"labelRegex\":\"^v8.11.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/164251\",\"number\":164251,\"mergeCommit\":{\"message\":\"[APM]\nSwallow
unhandled exceptions (#164251)\\n\\nIf an unhandled error occurs,\nit
will break the diagnostics bundle. This\\r\\nchange will log errors
and\nthen swallow them.\\r\\nThis should go out in 8.10 since it is
already\naffecting
users.\",\"sha\":\"654de7b7285ad5748dc9ff1e19156e753d68d568\"}}]}]\nBACKPORT-->\n\nCo-authored-by:
Søren Louv-Jansen
<soren.louv@elastic.co>"}},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164251","number":164251,"mergeCommit":{"message":"[APM]
Swallow unhandled exceptions (#164251)\n\nIf an unhandled error occurs,
it will break the diagnostics bundle. This\r\nchange will log errors and
then swallow them.\r\nThis should go out in 8.10 since it is already
affecting users.","sha":"654de7b7285ad5748dc9ff1e19156e753d68d568"}}]}]
BACKPORT-->

Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co>
2023-08-29 09:04:07 -07:00
Kibana Machine
89220a48cb
[8.9] [FTR] Implement scrollIntoView util (#165080) (#165097)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[FTR] Implement scrollIntoView util
(#165080)](https://github.com/elastic/kibana/pull/165080)

<!--- 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-29T13:31:27Z","message":"[FTR]
Implement scrollIntoView util (#165080)\n\n## 📓 Summary\r\n\r\nBased on
the need for
[this\r\ntest](https://github.com/elastic/kibana/pull/164493/files#diff-e0bb824023eef20a7b3742da023e25744a6c20406f59ae8400455c579153faeaR262)\r\nto
scroll into the element independently of its existence in view,
this\r\nPR exposes a new `scrollIntoView` method that replicates the
behaviour\r\nof the native
[Element\r\n.scrollIntoView](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView)\r\nmethod.\r\n\r\n---------\r\n\r\nCo-authored-by:
Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56c04d88872bb22d4c941fda6262746e198c5505","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v7.17.13","v8.11.0"],"number":165080,"url":"https://github.com/elastic/kibana/pull/165080","mergeCommit":{"message":"[FTR]
Implement scrollIntoView util (#165080)\n\n## 📓 Summary\r\n\r\nBased on
the need for
[this\r\ntest](https://github.com/elastic/kibana/pull/164493/files#diff-e0bb824023eef20a7b3742da023e25744a6c20406f59ae8400455c579153faeaR262)\r\nto
scroll into the element independently of its existence in view,
this\r\nPR exposes a new `scrollIntoView` method that replicates the
behaviour\r\nof the native
[Element\r\n.scrollIntoView](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView)\r\nmethod.\r\n\r\n---------\r\n\r\nCo-authored-by:
Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56c04d88872bb22d4c941fda6262746e198c5505"}},"sourceBranch":"main","suggestedTargetBranches":["7.17"],"targetPullRequestStates":[{"branch":"7.17","label":"v7.17.13","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165080","number":165080,"mergeCommit":{"message":"[FTR]
Implement scrollIntoView util (#165080)\n\n## 📓 Summary\r\n\r\nBased on
the need for
[this\r\ntest](https://github.com/elastic/kibana/pull/164493/files#diff-e0bb824023eef20a7b3742da023e25744a6c20406f59ae8400455c579153faeaR262)\r\nto
scroll into the element independently of its existence in view,
this\r\nPR exposes a new `scrollIntoView` method that replicates the
behaviour\r\nof the native
[Element\r\n.scrollIntoView](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView)\r\nmethod.\r\n\r\n---------\r\n\r\nCo-authored-by:
Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56c04d88872bb22d4c941fda6262746e198c5505"}}]}]
BACKPORT-->

Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani01@gmail.com>
2023-08-29 07:36:56 -07:00
Kibana Machine
4b6192435e
[8.9] [DOCS] Add cross-link for other encryption key settings (#165014) (#165035)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Add cross-link for other encryption key settings
(#165014)](https://github.com/elastic/kibana/pull/165014)

<!--- 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-28T19:02:22Z","message":"[DOCS]
Add cross-link for other encryption key settings (#165014)\n\nProblem:
The [Configure security in
Kibana](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html)
docs page only covers the `xpack.security.encryptionKey` setting for
session encryption. Users may not know that encryption for Kibana's
reporting and saved objects features also require encryption
keys.\r\n\r\nSolution: Add a cross-link to the respective encryption key
settings for reporting and saved
objects","sha":"8ac82e38d79c0031d76de472d1b1e0f2f7b9fef2","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Feature:Reporting","Feature:Saved
Objects","release_note:skip","docs","Feature:Security/Session
Management","v8.10.0","v8.11.0","v8.9.2"],"number":165014,"url":"https://github.com/elastic/kibana/pull/165014","mergeCommit":{"message":"[DOCS]
Add cross-link for other encryption key settings (#165014)\n\nProblem:
The [Configure security in
Kibana](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html)
docs page only covers the `xpack.security.encryptionKey` setting for
session encryption. Users may not know that encryption for Kibana's
reporting and saved objects features also require encryption
keys.\r\n\r\nSolution: Add a cross-link to the respective encryption key
settings for reporting and saved
objects","sha":"8ac82e38d79c0031d76de472d1b1e0f2f7b9fef2"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/165014","number":165014,"mergeCommit":{"message":"[DOCS]
Add cross-link for other encryption key settings (#165014)\n\nProblem:
The [Configure security in
Kibana](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html)
docs page only covers the `xpack.security.encryptionKey` setting for
session encryption. Users may not know that encryption for Kibana's
reporting and saved objects features also require encryption
keys.\r\n\r\nSolution: Add a cross-link to the respective encryption key
settings for reporting and saved
objects","sha":"8ac82e38d79c0031d76de472d1b1e0f2f7b9fef2"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
2023-08-28 15:26:55 -04:00
Nikita Indik
098c0aa3a8
[8.9] [Rule Details] - Update rule details data view id text (#164494) (#165021)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Rule Details] - Update rule details data view id text
(#164494)](https://github.com/elastic/kibana/pull/164494)

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

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

<!--BACKPORT [{"author":{"name":"Yara
Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-28T16:29:00Z","message":"[Rule
Details] - Update rule details data view id text
(#164494)\n\n**Resolves:
https://github.com/elastic/kibana/issues/164828**\r\n**Related UX
writing
issue:\r\nhttps://github.com/elastic/ux-writing/issues/46**\r\n\r\n##
Summary\r\n\r\nIn rule details page, when a rule has a data view
selected, two labels\r\nshow up as \"Data View\". This appears to be a
bug, as one of those labels\r\nshould be \"Data view ID\" and another
should be \"Data view index\r\npattern\".\r\n\r\nThanks to @MadameSheema
@nikitaindik for finding this. \r\n\r\n### Before
\r\n\r\n![image](8ac8b6d4-1005-4c03-a71a-31216a1287c5)\r\n\r\n###
After\r\n<img width=\"808\" alt=\"Screenshot 2023-08-26 at 19 30
54\"\r\nsrc=\"b511bf92-0e90-4455-834c-36b8e75b2a58\">\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n\r\n---------\r\n\r\nCo-authored-by:
Nikita Indik
<nikita.indik@elastic.co>","sha":"31e95574ae6d8cfa9e0ba4595e1068e9391b423d","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detection
Rule Management","ui-copy","Feature:Rule Details","Team:Detection
Engine","v8.10.0","v8.11.0","v8.9.2"],"number":164494,"url":"https://github.com/elastic/kibana/pull/164494","mergeCommit":{"message":"[Rule
Details] - Update rule details data view id text
(#164494)\n\n**Resolves:
https://github.com/elastic/kibana/issues/164828**\r\n**Related UX
writing
issue:\r\nhttps://github.com/elastic/ux-writing/issues/46**\r\n\r\n##
Summary\r\n\r\nIn rule details page, when a rule has a data view
selected, two labels\r\nshow up as \"Data View\". This appears to be a
bug, as one of those labels\r\nshould be \"Data view ID\" and another
should be \"Data view index\r\npattern\".\r\n\r\nThanks to @MadameSheema
@nikitaindik for finding this. \r\n\r\n### Before
\r\n\r\n![image](8ac8b6d4-1005-4c03-a71a-31216a1287c5)\r\n\r\n###
After\r\n<img width=\"808\" alt=\"Screenshot 2023-08-26 at 19 30
54\"\r\nsrc=\"b511bf92-0e90-4455-834c-36b8e75b2a58\">\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n\r\n---------\r\n\r\nCo-authored-by:
Nikita Indik
<nikita.indik@elastic.co>","sha":"31e95574ae6d8cfa9e0ba4595e1068e9391b423d"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/165015","number":165015,"state":"OPEN"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164494","number":164494,"mergeCommit":{"message":"[Rule
Details] - Update rule details data view id text
(#164494)\n\n**Resolves:
https://github.com/elastic/kibana/issues/164828**\r\n**Related UX
writing
issue:\r\nhttps://github.com/elastic/ux-writing/issues/46**\r\n\r\n##
Summary\r\n\r\nIn rule details page, when a rule has a data view
selected, two labels\r\nshow up as \"Data View\". This appears to be a
bug, as one of those labels\r\nshould be \"Data view ID\" and another
should be \"Data view index\r\npattern\".\r\n\r\nThanks to @MadameSheema
@nikitaindik for finding this. \r\n\r\n### Before
\r\n\r\n![image](8ac8b6d4-1005-4c03-a71a-31216a1287c5)\r\n\r\n###
After\r\n<img width=\"808\" alt=\"Screenshot 2023-08-26 at 19 30
54\"\r\nsrc=\"b511bf92-0e90-4455-834c-36b8e75b2a58\">\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n\r\n---------\r\n\r\nCo-authored-by:
Nikita Indik
<nikita.indik@elastic.co>","sha":"31e95574ae6d8cfa9e0ba4595e1068e9391b423d"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
2023-08-28 11:31:21 -07:00
Juan Pablo Djeredjian
41f6c48aa7
[8.9] [Security Solution] Fix flakiness in: prebuilt_rules_management.cy.ts - Deletes and recovers more than one rule (#164824)
**NOTE: This is a manual backport of
https://github.com/elastic/kibana/pull/164694**


Relates to: https://github.com/elastic/kibana/issues/161507

## Summary

- Solves flakiness in following test:
- Filename:
`x-pack/plugins/security_solution/cypress/e2e/detection_rules/prebuilt_rules_management.cy.ts`
- Test name: **Prebuilt rules Actions with prebuilt rules Rules table
Deletes and recovers more than one rule**

- Test was failing because of already observed issue of `autoRefresh`
taking place while the rule selection is happening, causing Cypress to
lose focus and preventing the checkbox from being checked. This PR
disables autorefresh from the table to prevent that from happening.

## Flaky test runner

350 iters:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2976
🟢
2023-08-28 13:02:39 +02:00
Kibana Machine
a6a08714e1
[8.9] [DOCS] Trying to fix broken links, or removing them (#162844) (#162924)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Trying to fix broken links, or removing them
(#162844)](https://github.com/elastic/kibana/pull/162844)

<!--- 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-01T17:40:47Z","message":"[DOCS]
Trying to fix broken links, or removing them (#162844)\n\n##
Summary\r\n\r\nRelates to #162551\r\n\r\nLinks returning 404 on
[Elasticsearch
service\r\npage](https://www.elastic.co/guide/en/kibana/current/elasticsearch-service.html)\r\nin
the Developer guide.\r\n\r\nReplaced the link to the data plug in and
one to the global search\r\nplugin (though I'm not sure keeping the
sentence and the link to the\r\nglobal search plugin is useful - maybe
we should just remove both\r\ncompletely). Removed the link
'Elasticsearch service API
docs'\r\naltogether.","sha":"6666ed46351a4b2c4fa0b3e4fab9b7a1a5f9a928","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Team:Core","release_note:skip","docs","v7.17.0","v8.9.0","v8.10.0"],"number":162844,"url":"https://github.com/elastic/kibana/pull/162844","mergeCommit":{"message":"[DOCS]
Trying to fix broken links, or removing them (#162844)\n\n##
Summary\r\n\r\nRelates to #162551\r\n\r\nLinks returning 404 on
[Elasticsearch
service\r\npage](https://www.elastic.co/guide/en/kibana/current/elasticsearch-service.html)\r\nin
the Developer guide.\r\n\r\nReplaced the link to the data plug in and
one to the global search\r\nplugin (though I'm not sure keeping the
sentence and the link to the\r\nglobal search plugin is useful - maybe
we should just remove both\r\ncompletely). Removed the link
'Elasticsearch service API
docs'\r\naltogether.","sha":"6666ed46351a4b2c4fa0b3e4fab9b7a1a5f9a928"}},"sourceBranch":"main","suggestedTargetBranches":["7.17","8.9"],"targetPullRequestStates":[{"branch":"7.17","label":"v7.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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/162844","number":162844,"mergeCommit":{"message":"[DOCS]
Trying to fix broken links, or removing them (#162844)\n\n##
Summary\r\n\r\nRelates to #162551\r\n\r\nLinks returning 404 on
[Elasticsearch
service\r\npage](https://www.elastic.co/guide/en/kibana/current/elasticsearch-service.html)\r\nin
the Developer guide.\r\n\r\nReplaced the link to the data plug in and
one to the global search\r\nplugin (though I'm not sure keeping the
sentence and the link to the\r\nglobal search plugin is useful - maybe
we should just remove both\r\ncompletely). Removed the link
'Elasticsearch service API
docs'\r\naltogether.","sha":"6666ed46351a4b2c4fa0b3e4fab9b7a1a5f9a928"}}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
2023-08-26 17:27:30 -04:00
Kibana Machine
651db1fd10
[8.9] [Ops] Fix @kbn/imports/no_unused_imports rule (#164870) (#164907)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Ops] Fix @kbn/imports/no_unused_imports rule
(#164870)](https://github.com/elastic/kibana/pull/164870)

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

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

<!--BACKPORT [{"author":{"name":"Alex
Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2023-08-25T23:13:57Z","message":"[Ops]
Fix @kbn/imports/no_unused_imports rule (#164870)\n\n##
Summary\r\n@jloleysens reported that ESLint breaks (probably in IDEs
only) because\r\nof this bug. When there's an unused import, linting
stops for the whole\r\nfile.\r\n\r\nBy adding this flag, it no longer
breaks on my machine, however,\r\nauto-fixing still doesn't work from
the CLI. The IDE auto-fixes because\r\nit also recognizes it as a
non-unsed variable.\r\n\r\n- add `meta.hasSuggestions` to
`@kbn/imports/no_unused_imports` prevent\r\nESLint from
breaking","sha":"d8d355dd7b4184127a760261178daf0f8a94af86","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.11.0"],"number":164870,"url":"https://github.com/elastic/kibana/pull/164870","mergeCommit":{"message":"[Ops]
Fix @kbn/imports/no_unused_imports rule (#164870)\n\n##
Summary\r\n@jloleysens reported that ESLint breaks (probably in IDEs
only) because\r\nof this bug. When there's an unused import, linting
stops for the whole\r\nfile.\r\n\r\nBy adding this flag, it no longer
breaks on my machine, however,\r\nauto-fixing still doesn't work from
the CLI. The IDE auto-fixes because\r\nit also recognizes it as a
non-unsed variable.\r\n\r\n- add `meta.hasSuggestions` to
`@kbn/imports/no_unused_imports` prevent\r\nESLint from
breaking","sha":"d8d355dd7b4184127a760261178daf0f8a94af86"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164870","number":164870,"mergeCommit":{"message":"[Ops]
Fix @kbn/imports/no_unused_imports rule (#164870)\n\n##
Summary\r\n@jloleysens reported that ESLint breaks (probably in IDEs
only) because\r\nof this bug. When there's an unused import, linting
stops for the whole\r\nfile.\r\n\r\nBy adding this flag, it no longer
breaks on my machine, however,\r\nauto-fixing still doesn't work from
the CLI. The IDE auto-fixes because\r\nit also recognizes it as a
non-unsed variable.\r\n\r\n- add `meta.hasSuggestions` to
`@kbn/imports/no_unused_imports` prevent\r\nESLint from
breaking","sha":"d8d355dd7b4184127a760261178daf0f8a94af86"}}]}]
BACKPORT-->

Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
2023-08-25 17:24:42 -07:00
Kibana Machine
79ce19767b
[8.9] [Security Solution][Detection Engine] Exceptions auto-populate not working for numeric filed values (#164713) (#164834)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Detection Engine] Exceptions auto-populate not
working for numeric filed values
(#164713)](https://github.com/elastic/kibana/pull/164713)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2023-08-25T11:42:53Z","message":"[Security
Solution][Detection Engine] Exceptions auto-populate not working for
numeric filed values (#164713)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/163924\r\n\r\nAs we utilize
either the
[\r\nMatch](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L384)\r\nor\r\n[Match_Any](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L402),\r\noperator,
the anticipated values should be limited to either strings or\r\narrays
containing
strings.","sha":"e8127e275faa5ff27cfef8d9c534a69bfd9fba14","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:cloud-deploy","Team:Detection
Engine","v8.11.0","v8.9.2"],"number":164713,"url":"https://github.com/elastic/kibana/pull/164713","mergeCommit":{"message":"[Security
Solution][Detection Engine] Exceptions auto-populate not working for
numeric filed values (#164713)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/163924\r\n\r\nAs we utilize
either the
[\r\nMatch](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L384)\r\nor\r\n[Match_Any](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L402),\r\noperator,
the anticipated values should be limited to either strings or\r\narrays
containing
strings.","sha":"e8127e275faa5ff27cfef8d9c534a69bfd9fba14"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164713","number":164713,"mergeCommit":{"message":"[Security
Solution][Detection Engine] Exceptions auto-populate not working for
numeric filed values (#164713)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/163924\r\n\r\nAs we utilize
either the
[\r\nMatch](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L384)\r\nor\r\n[Match_Any](https://github.com/WafaaNasr/kibana/blob/main/x-pack/plugins/lists/public/exceptions/components/builder/entry_renderer.tsx#L402),\r\noperator,
the anticipated values should be limited to either strings or\r\narrays
containing
strings.","sha":"e8127e275faa5ff27cfef8d9c534a69bfd9fba14"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co>
2023-08-25 06:17:15 -07:00
Pete Harverson
6387bc2a3f
[8.9] [ML] Unskips outlier creation functional tests (#164835)
## Summary

Unskips the outlier detection creation functional tests for 8.9 that
were skipped in
https://github.com/elastic/kibana/issues/142093#issuecomment-1683009827.

The failing test on `8.9.2` was caused by the incomplete version bump
that was done in https://github.com/elastic/kibana/pull/164192, and
since rectified in https://github.com/elastic/kibana/pull/164230.

### Checklist

- [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-25 14:12:26 +01:00
Tiago Costa
ebf21b6fa7
[8.9] chore(NA): upgrade typescript into v4.7.4 (#162738) (#164761)
# Backport

This will backport the following commits from `main` to `8.9`:
- [chore(NA): upgrade typescript into v4.7.4
(#162738)](https://github.com/elastic/kibana/pull/162738)

<!--- 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-24T16:27:13Z","message":"chore(NA):
upgrade typescript into v4.7.4 (#162738)\n\nThis PR bumps the Typescript
version used on Kibana into v4.7.4.\r\n\r\nDuring the upgrade I got the
impression the majority of the failures\r\nwere too specific to the
codebase so instead of making assumptions I\r\nchoose to marked a lot of
them with `@ts-expect-error` and let each team\r\ndecide how to handle
it.\r\n\r\nNext you can find a list of files with those comments and the
teams to\r\nwho they belong to. I would appreciate the collaboration
from each team\r\non fixing those. I'm not opposed on fixing those in
subsequent PRs after\r\nthis one have been merged, just wanted to
elaborate that list for a good\r\nfollow up:\r\n\r\n@elastic/kibana-core
\r\n-
[x]\r\n[packages/core/http/core-http-router-server-internal/src/request.ts](https://github.com/elastic/kibana/pull/162738/files#diff-c1f4a8c013c6ff9c5170803322414cb002f70331b23e45c55f075258c678410a)\r\n\r\n@elastic/kibana-data-discovery
\r\n-
[x]\r\n[src/plugins/discover/public/components/doc_table/components/table_row.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9106b254a57e73fc6f0b2e01f9aff1abbd26f1a0999e6fa998f1b45d3013038f)\r\n\r\n@elastic/kibana-visualizations
\r\n-
[x]\r\n[src/plugins/expressions/common/execution/execution.ts](https://github.com/elastic/kibana/pull/162738/files#diff-47bf3af7472c08ede90f86575ee7db4b8a2c949b1fb61400410ed16a8d819667)\r\n-
[x]\r\n[src/plugins/expressions/common/expression_functions/expression_function_parameter.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3bcaa3c50f2297ff990c7ac83a1c2d36a79e6706a09082c3c48a911713afe950)\r\n-
[x]\r\n[src/plugins/vis_types/heatmap/public/editor/components/labels_panel.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-345db24d53f4158414480b890fa43d1f8a454b67313de79602fda081279cbc4f)\r\n-
[x]\r\n[src/plugins/vis_types/xy/public/editor/components/options/metrics_axes/label_options.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-1c346b41cf025ff4f4e07b6d6dcdd1451cbaa758f9a9e8c72a9801d3fbbdfda2)\r\n\r\n@elastic/kibana-presentation
\r\n-
[x]\r\n[x-pack/plugins/canvas/public/components/workpad_page/workpad_interactive_page/event_handlers.ts](https://github.com/elastic/kibana/pull/162738/files#diff-56858ed9be77830ab218eab1960337240926609c5a1593b3960b35660ef81359)\r\n\r\n@elastic/response-ops
\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/create/form.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-c5c415f1f56ca986f4bb59e65490b5e0fc77a86092240c0c1a26c141dba07818)\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/markdown_editor/editable_markdown_renderer.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-ab038916f6fed59e18b0a72ce8e823e88d115afdb2704010d0fa8656b66702df)\r\n-
[x]\r\n[x-pack/plugins/rule_registry/server/alert_data_client/browser_fields/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3f91aa93f7e6514c0479a37a76d6e9a53646d4eaf5dcd0db64437eadf1eee6b6)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/.storybook/decorator.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-fbf1d6d0104c11c3f3690d29edf06000b5a63a858bb22b7d04d1f96a45133b07)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/public/common/get_experimental_features.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n\r\n@elastic/fleet
\r\n-
[x]\r\n[x-pack/plugins/fleet/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-a852b157b5ff1d6dbf321ea8a25f0020d8f88cd458378cc9de8ef25ce28c9414)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/components/agent_policy_advanced_fields/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9eea0be0f9341dd6369720ce7b11bff69dda51230337ebbae921f6abde187bd2)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-844d5f9707b739d25f2b73bd34c45c21e2e5d573b3238c13130a0d1c1db092dc)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agents/agent_list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-f88d92abbc549ddc95d693bf3a3bc9752613cf74f1e859a01ca61d572e031b11)\r\n-
[x]\r\n[x-pack/plugins/fleet/server/mocks/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-d3f3e436b158ac2d877b7be9d57642855f89b0149cc28735811443da45bb079f)\r\n\r\n@elastic/security-detection-engine\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/extension_point_storage_client.ts](https://github.com/elastic/kibana/pull/162738/files#diff-dbbf5a8541e06fd977c66e44d9ef59f738d953bdfda679ac838e098742c92f50)\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/types.ts](https://github.com/elastic/kibana/pull/162738/files#diff-31186826bea8fdb286a25878fa06eeacad8f7a6c384d617fed905d4625821eef)\r\n\r\n@elastic/security-defend-workflows
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/detection_engine/rule_response_actions/osquery/osquery_response_action.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-049eeedef2a403ade7c636418e17fc9a3ffc7030eec2f3e013f459721c076470)\r\n\r\n@elastic/infra-monitoring-ui
\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/apm/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-4ab4fa150247d8f522741ae5ea1ea71c102c72f5439410ea869ec1c9dc9878ad)\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/enterprise_search/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-285a67d9ec93651206608d308e5d1d20ccc98ccccb9bcbf3ee31fe35c1844b42)\r\n\r\n@elastic/kibana-security
\r\n-
[x]\r\n[x-pack/plugins/security/server/authentication/authenticator.ts](https://github.com/elastic/kibana/pull/162738/files#diff-bd369002fdfd0986f1ce3bf16263fb8b765e01a86832ccf5b4e521811d502038)\r\n-
[x]\r\n[x-pack/plugins/security/server/session_management/session_index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-10b76eb52a0e17564ad864def8270bb84a4eb87eb35851309bc36601086cbcd7)\r\n\r\n@elastic/security-threat-hunting-explore
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/common/mock/endpoint/app_context_render.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-7f130bdc9a954330d188aa25324910cf2f72baf76d1329bd36584f5bb153856b)\r\n\r\n@elastic/security-solution
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/components/page_overlay/page_overlay.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-e68a2799df17238257a86ce965369c525be901f6f882e518bde9e8c9bd7cd2c8)\r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/pages/policy/view/policy_settings_form/components/event_collection_card.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-edc756f655792f7dcaca0c707f35c6c022981be1873712f460ccb1d611e42568)\r\n-
[x]\r\n[x-pack/plugins/security_solution/tsconfig.json](https://github.com/elastic/kibana/pull/162738/files#diff-844dde79a96b9e6c2bfdf21f8c80feb8b687577e21326da6bd15c6b95d8ec918)\r\n\r\n@elastic/uptime
\r\n-
[x]\r\n[x-pack/plugins/uptime/server/legacy_uptime/lib/alerts/duration_anomaly.test.ts](https://github.com/elastic/kibana/pull/162738/files#diff-6c7b63ce65aa17a2fe3219e1747ae051be88fb02edbe2f198ad6fd418a2bcc57)\r\n\r\n@elastic/security-detections-response-alerts
@gergoabraham \r\n-
[x]\r\n[x-pack/test/detection_engine_api_integration/security_and_spaces/group8/exception_operators_data_types/keyword_array.ts](https://github.com/elastic/kibana/pull/162738/files#diff-472ba2c7fe43448c8a4d04406703f755f71f6e60146bb2f090b4ca0f19ad0a0f)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Michael Dokolin <dokmic@gmail.com>\r\nCo-authored-by: Stratoula
Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Rudolf Meijering
<skaapgif@gmail.com>\r\nCo-authored-by: Devon Thomson
<devon.thomson@elastic.co>","sha":"2d652e1313a64f55bae994833324ad8116738254","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","Feature:ExpressionLanguage","release_note:skip","Team:Fleet","auto-backport","v8.10.0","v7.17.13","v8.11.0","v8.9.2"],"number":162738,"url":"https://github.com/elastic/kibana/pull/162738","mergeCommit":{"message":"chore(NA):
upgrade typescript into v4.7.4 (#162738)\n\nThis PR bumps the Typescript
version used on Kibana into v4.7.4.\r\n\r\nDuring the upgrade I got the
impression the majority of the failures\r\nwere too specific to the
codebase so instead of making assumptions I\r\nchoose to marked a lot of
them with `@ts-expect-error` and let each team\r\ndecide how to handle
it.\r\n\r\nNext you can find a list of files with those comments and the
teams to\r\nwho they belong to. I would appreciate the collaboration
from each team\r\non fixing those. I'm not opposed on fixing those in
subsequent PRs after\r\nthis one have been merged, just wanted to
elaborate that list for a good\r\nfollow up:\r\n\r\n@elastic/kibana-core
\r\n-
[x]\r\n[packages/core/http/core-http-router-server-internal/src/request.ts](https://github.com/elastic/kibana/pull/162738/files#diff-c1f4a8c013c6ff9c5170803322414cb002f70331b23e45c55f075258c678410a)\r\n\r\n@elastic/kibana-data-discovery
\r\n-
[x]\r\n[src/plugins/discover/public/components/doc_table/components/table_row.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9106b254a57e73fc6f0b2e01f9aff1abbd26f1a0999e6fa998f1b45d3013038f)\r\n\r\n@elastic/kibana-visualizations
\r\n-
[x]\r\n[src/plugins/expressions/common/execution/execution.ts](https://github.com/elastic/kibana/pull/162738/files#diff-47bf3af7472c08ede90f86575ee7db4b8a2c949b1fb61400410ed16a8d819667)\r\n-
[x]\r\n[src/plugins/expressions/common/expression_functions/expression_function_parameter.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3bcaa3c50f2297ff990c7ac83a1c2d36a79e6706a09082c3c48a911713afe950)\r\n-
[x]\r\n[src/plugins/vis_types/heatmap/public/editor/components/labels_panel.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-345db24d53f4158414480b890fa43d1f8a454b67313de79602fda081279cbc4f)\r\n-
[x]\r\n[src/plugins/vis_types/xy/public/editor/components/options/metrics_axes/label_options.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-1c346b41cf025ff4f4e07b6d6dcdd1451cbaa758f9a9e8c72a9801d3fbbdfda2)\r\n\r\n@elastic/kibana-presentation
\r\n-
[x]\r\n[x-pack/plugins/canvas/public/components/workpad_page/workpad_interactive_page/event_handlers.ts](https://github.com/elastic/kibana/pull/162738/files#diff-56858ed9be77830ab218eab1960337240926609c5a1593b3960b35660ef81359)\r\n\r\n@elastic/response-ops
\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/create/form.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-c5c415f1f56ca986f4bb59e65490b5e0fc77a86092240c0c1a26c141dba07818)\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/markdown_editor/editable_markdown_renderer.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-ab038916f6fed59e18b0a72ce8e823e88d115afdb2704010d0fa8656b66702df)\r\n-
[x]\r\n[x-pack/plugins/rule_registry/server/alert_data_client/browser_fields/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3f91aa93f7e6514c0479a37a76d6e9a53646d4eaf5dcd0db64437eadf1eee6b6)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/.storybook/decorator.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-fbf1d6d0104c11c3f3690d29edf06000b5a63a858bb22b7d04d1f96a45133b07)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/public/common/get_experimental_features.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n\r\n@elastic/fleet
\r\n-
[x]\r\n[x-pack/plugins/fleet/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-a852b157b5ff1d6dbf321ea8a25f0020d8f88cd458378cc9de8ef25ce28c9414)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/components/agent_policy_advanced_fields/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9eea0be0f9341dd6369720ce7b11bff69dda51230337ebbae921f6abde187bd2)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-844d5f9707b739d25f2b73bd34c45c21e2e5d573b3238c13130a0d1c1db092dc)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agents/agent_list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-f88d92abbc549ddc95d693bf3a3bc9752613cf74f1e859a01ca61d572e031b11)\r\n-
[x]\r\n[x-pack/plugins/fleet/server/mocks/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-d3f3e436b158ac2d877b7be9d57642855f89b0149cc28735811443da45bb079f)\r\n\r\n@elastic/security-detection-engine\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/extension_point_storage_client.ts](https://github.com/elastic/kibana/pull/162738/files#diff-dbbf5a8541e06fd977c66e44d9ef59f738d953bdfda679ac838e098742c92f50)\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/types.ts](https://github.com/elastic/kibana/pull/162738/files#diff-31186826bea8fdb286a25878fa06eeacad8f7a6c384d617fed905d4625821eef)\r\n\r\n@elastic/security-defend-workflows
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/detection_engine/rule_response_actions/osquery/osquery_response_action.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-049eeedef2a403ade7c636418e17fc9a3ffc7030eec2f3e013f459721c076470)\r\n\r\n@elastic/infra-monitoring-ui
\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/apm/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-4ab4fa150247d8f522741ae5ea1ea71c102c72f5439410ea869ec1c9dc9878ad)\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/enterprise_search/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-285a67d9ec93651206608d308e5d1d20ccc98ccccb9bcbf3ee31fe35c1844b42)\r\n\r\n@elastic/kibana-security
\r\n-
[x]\r\n[x-pack/plugins/security/server/authentication/authenticator.ts](https://github.com/elastic/kibana/pull/162738/files#diff-bd369002fdfd0986f1ce3bf16263fb8b765e01a86832ccf5b4e521811d502038)\r\n-
[x]\r\n[x-pack/plugins/security/server/session_management/session_index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-10b76eb52a0e17564ad864def8270bb84a4eb87eb35851309bc36601086cbcd7)\r\n\r\n@elastic/security-threat-hunting-explore
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/common/mock/endpoint/app_context_render.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-7f130bdc9a954330d188aa25324910cf2f72baf76d1329bd36584f5bb153856b)\r\n\r\n@elastic/security-solution
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/components/page_overlay/page_overlay.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-e68a2799df17238257a86ce965369c525be901f6f882e518bde9e8c9bd7cd2c8)\r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/pages/policy/view/policy_settings_form/components/event_collection_card.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-edc756f655792f7dcaca0c707f35c6c022981be1873712f460ccb1d611e42568)\r\n-
[x]\r\n[x-pack/plugins/security_solution/tsconfig.json](https://github.com/elastic/kibana/pull/162738/files#diff-844dde79a96b9e6c2bfdf21f8c80feb8b687577e21326da6bd15c6b95d8ec918)\r\n\r\n@elastic/uptime
\r\n-
[x]\r\n[x-pack/plugins/uptime/server/legacy_uptime/lib/alerts/duration_anomaly.test.ts](https://github.com/elastic/kibana/pull/162738/files#diff-6c7b63ce65aa17a2fe3219e1747ae051be88fb02edbe2f198ad6fd418a2bcc57)\r\n\r\n@elastic/security-detections-response-alerts
@gergoabraham \r\n-
[x]\r\n[x-pack/test/detection_engine_api_integration/security_and_spaces/group8/exception_operators_data_types/keyword_array.ts](https://github.com/elastic/kibana/pull/162738/files#diff-472ba2c7fe43448c8a4d04406703f755f71f6e60146bb2f090b4ca0f19ad0a0f)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Michael Dokolin <dokmic@gmail.com>\r\nCo-authored-by: Stratoula
Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Rudolf Meijering
<skaapgif@gmail.com>\r\nCo-authored-by: Devon Thomson
<devon.thomson@elastic.co>","sha":"2d652e1313a64f55bae994833324ad8116738254"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","7.17","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.13","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/162738","number":162738,"mergeCommit":{"message":"chore(NA):
upgrade typescript into v4.7.4 (#162738)\n\nThis PR bumps the Typescript
version used on Kibana into v4.7.4.\r\n\r\nDuring the upgrade I got the
impression the majority of the failures\r\nwere too specific to the
codebase so instead of making assumptions I\r\nchoose to marked a lot of
them with `@ts-expect-error` and let each team\r\ndecide how to handle
it.\r\n\r\nNext you can find a list of files with those comments and the
teams to\r\nwho they belong to. I would appreciate the collaboration
from each team\r\non fixing those. I'm not opposed on fixing those in
subsequent PRs after\r\nthis one have been merged, just wanted to
elaborate that list for a good\r\nfollow up:\r\n\r\n@elastic/kibana-core
\r\n-
[x]\r\n[packages/core/http/core-http-router-server-internal/src/request.ts](https://github.com/elastic/kibana/pull/162738/files#diff-c1f4a8c013c6ff9c5170803322414cb002f70331b23e45c55f075258c678410a)\r\n\r\n@elastic/kibana-data-discovery
\r\n-
[x]\r\n[src/plugins/discover/public/components/doc_table/components/table_row.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9106b254a57e73fc6f0b2e01f9aff1abbd26f1a0999e6fa998f1b45d3013038f)\r\n\r\n@elastic/kibana-visualizations
\r\n-
[x]\r\n[src/plugins/expressions/common/execution/execution.ts](https://github.com/elastic/kibana/pull/162738/files#diff-47bf3af7472c08ede90f86575ee7db4b8a2c949b1fb61400410ed16a8d819667)\r\n-
[x]\r\n[src/plugins/expressions/common/expression_functions/expression_function_parameter.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3bcaa3c50f2297ff990c7ac83a1c2d36a79e6706a09082c3c48a911713afe950)\r\n-
[x]\r\n[src/plugins/vis_types/heatmap/public/editor/components/labels_panel.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-345db24d53f4158414480b890fa43d1f8a454b67313de79602fda081279cbc4f)\r\n-
[x]\r\n[src/plugins/vis_types/xy/public/editor/components/options/metrics_axes/label_options.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-1c346b41cf025ff4f4e07b6d6dcdd1451cbaa758f9a9e8c72a9801d3fbbdfda2)\r\n\r\n@elastic/kibana-presentation
\r\n-
[x]\r\n[x-pack/plugins/canvas/public/components/workpad_page/workpad_interactive_page/event_handlers.ts](https://github.com/elastic/kibana/pull/162738/files#diff-56858ed9be77830ab218eab1960337240926609c5a1593b3960b35660ef81359)\r\n\r\n@elastic/response-ops
\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/create/form.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-c5c415f1f56ca986f4bb59e65490b5e0fc77a86092240c0c1a26c141dba07818)\r\n-
[x]\r\n[x-pack/plugins/cases/public/components/markdown_editor/editable_markdown_renderer.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-ab038916f6fed59e18b0a72ce8e823e88d115afdb2704010d0fa8656b66702df)\r\n-
[x]\r\n[x-pack/plugins/rule_registry/server/alert_data_client/browser_fields/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-3f91aa93f7e6514c0479a37a76d6e9a53646d4eaf5dcd0db64437eadf1eee6b6)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/.storybook/decorator.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-fbf1d6d0104c11c3f3690d29edf06000b5a63a858bb22b7d04d1f96a45133b07)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n-
[x]\r\n[x-pack/plugins/triggers_actions_ui/public/common/get_experimental_features.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-8e2ca70700895b17125532779945a1d0ab9076b4d4db304c065b47f82b6628a5)\r\n\r\n@elastic/fleet
\r\n-
[x]\r\n[x-pack/plugins/fleet/common/experimental_features.ts](https://github.com/elastic/kibana/pull/162738/files#diff-a852b157b5ff1d6dbf321ea8a25f0020d8f88cd458378cc9de8ef25ce28c9414)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/components/agent_policy_advanced_fields/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-9eea0be0f9341dd6369720ce7b11bff69dda51230337ebbae921f6abde187bd2)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-844d5f9707b739d25f2b73bd34c45c21e2e5d573b3238c13130a0d1c1db092dc)\r\n-
[x]\r\n[x-pack/plugins/fleet/public/applications/fleet/sections/agents/agent_list_page/index.test.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-f88d92abbc549ddc95d693bf3a3bc9752613cf74f1e859a01ca61d572e031b11)\r\n-
[x]\r\n[x-pack/plugins/fleet/server/mocks/index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-d3f3e436b158ac2d877b7be9d57642855f89b0149cc28735811443da45bb079f)\r\n\r\n@elastic/security-detection-engine\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/extension_point_storage_client.ts](https://github.com/elastic/kibana/pull/162738/files#diff-dbbf5a8541e06fd977c66e44d9ef59f738d953bdfda679ac838e098742c92f50)\r\n-
[x]\r\n[x-pack/plugins/lists/server/services/extension_points/types.ts](https://github.com/elastic/kibana/pull/162738/files#diff-31186826bea8fdb286a25878fa06eeacad8f7a6c384d617fed905d4625821eef)\r\n\r\n@elastic/security-defend-workflows
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/detection_engine/rule_response_actions/osquery/osquery_response_action.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-049eeedef2a403ade7c636418e17fc9a3ffc7030eec2f3e013f459721c076470)\r\n\r\n@elastic/infra-monitoring-ui
\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/apm/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-4ab4fa150247d8f522741ae5ea1ea71c102c72f5439410ea869ec1c9dc9878ad)\r\n-
[x]\r\n[x-pack/plugins/monitoring/public/application/pages/enterprise_search/overview.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-285a67d9ec93651206608d308e5d1d20ccc98ccccb9bcbf3ee31fe35c1844b42)\r\n\r\n@elastic/kibana-security
\r\n-
[x]\r\n[x-pack/plugins/security/server/authentication/authenticator.ts](https://github.com/elastic/kibana/pull/162738/files#diff-bd369002fdfd0986f1ce3bf16263fb8b765e01a86832ccf5b4e521811d502038)\r\n-
[x]\r\n[x-pack/plugins/security/server/session_management/session_index.ts](https://github.com/elastic/kibana/pull/162738/files#diff-10b76eb52a0e17564ad864def8270bb84a4eb87eb35851309bc36601086cbcd7)\r\n\r\n@elastic/security-threat-hunting-explore
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/common/mock/endpoint/app_context_render.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-7f130bdc9a954330d188aa25324910cf2f72baf76d1329bd36584f5bb153856b)\r\n\r\n@elastic/security-solution
@gergoabraham \r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/components/page_overlay/page_overlay.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-e68a2799df17238257a86ce965369c525be901f6f882e518bde9e8c9bd7cd2c8)\r\n-
[x]\r\n[x-pack/plugins/security_solution/public/management/pages/policy/view/policy_settings_form/components/event_collection_card.tsx](https://github.com/elastic/kibana/pull/162738/files#diff-edc756f655792f7dcaca0c707f35c6c022981be1873712f460ccb1d611e42568)\r\n-
[x]\r\n[x-pack/plugins/security_solution/tsconfig.json](https://github.com/elastic/kibana/pull/162738/files#diff-844dde79a96b9e6c2bfdf21f8c80feb8b687577e21326da6bd15c6b95d8ec918)\r\n\r\n@elastic/uptime
\r\n-
[x]\r\n[x-pack/plugins/uptime/server/legacy_uptime/lib/alerts/duration_anomaly.test.ts](https://github.com/elastic/kibana/pull/162738/files#diff-6c7b63ce65aa17a2fe3219e1747ae051be88fb02edbe2f198ad6fd418a2bcc57)\r\n\r\n@elastic/security-detections-response-alerts
@gergoabraham \r\n-
[x]\r\n[x-pack/test/detection_engine_api_integration/security_and_spaces/group8/exception_operators_data_types/keyword_array.ts](https://github.com/elastic/kibana/pull/162738/files#diff-472ba2c7fe43448c8a4d04406703f755f71f6e60146bb2f090b4ca0f19ad0a0f)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Michael Dokolin <dokmic@gmail.com>\r\nCo-authored-by: Stratoula
Kalafateli <stratoula1@gmail.com>\r\nCo-authored-by: Rudolf Meijering
<skaapgif@gmail.com>\r\nCo-authored-by: Devon Thomson
<devon.thomson@elastic.co>","sha":"2d652e1313a64f55bae994833324ad8116738254"}},{"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-25 13:20:54 +01:00
David Sánchez
7e708300f6
[8.9] [Security Solution][Endpoint] Split blocklist entry in multiple entries when different hash types (#164599) (#164725)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Endpoint] Split blocklist entry in multiple
entries when different hash types
(#164599)](https://github.com/elastic/kibana/pull/164599)

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

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

<!--BACKPORT [{"author":{"name":"David
Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2023-08-24T12:10:23Z","message":"[Security
Solution][Endpoint] Split blocklist entry in multiple entries when
different hash types (#164599)\n\nFixes:
https://github.com/elastic/kibana/issues/164374\r\n##
Summary\r\n\r\nDuring fleet artifact generation, we split those
blocklist entries that\r\ncontains multiple hash types in it, so the
resulting artifact contains\r\nan entry for each hash type. This is done
for each blocklist if they\r\ncontain multiple hash types in
it.\r\n\r\nIt also updates ftr test to ensure the resulting artifact is
generated\r\ncorrectly.\r\n\r\nFor a blocklist containing these hashes:
\r\n```\r\n['741462ab431a22233c787baab9b653c7',
'aedb279e378bed6c2db3c9dc9e12ba635e0b391c',
'a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476']\r\n```\r\n\r\nThe
artifact generated is:\r\n\r\n```\r\n{\r\n entries: [\r\n {\r\n type:
'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.md5',\r\n operator:
'included',\r\n type: 'exact_cased_any',\r\n value:
['741462ab431a22233c787baab9b653c7'],\r\n },\r\n ],\r\n },\r\n {\r\n
type: 'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.sha1',\r\n
operator: 'included',\r\n type: 'exact_cased_any',\r\n value:
['aedb279e378bed6c2db3c9dc9e12ba635e0b391c'],\r\n },\r\n ],\r\n },\r\n
{\r\n type: 'simple',\r\n entries: [\r\n {\r\n field:
'file.hash.sha256',\r\n operator: 'included',\r\n type:
'exact_cased_any',\r\n value:
['a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476'],\r\n
},\r\n ],\r\n },\r\n ]\r\n}\r\n```\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"665937683845322e6c75b18b14041854dcb761c9","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","v8.10.0","v8.11.0","v8.9.2"],"number":164599,"url":"https://github.com/elastic/kibana/pull/164599","mergeCommit":{"message":"[Security
Solution][Endpoint] Split blocklist entry in multiple entries when
different hash types (#164599)\n\nFixes:
https://github.com/elastic/kibana/issues/164374\r\n##
Summary\r\n\r\nDuring fleet artifact generation, we split those
blocklist entries that\r\ncontains multiple hash types in it, so the
resulting artifact contains\r\nan entry for each hash type. This is done
for each blocklist if they\r\ncontain multiple hash types in
it.\r\n\r\nIt also updates ftr test to ensure the resulting artifact is
generated\r\ncorrectly.\r\n\r\nFor a blocklist containing these hashes:
\r\n```\r\n['741462ab431a22233c787baab9b653c7',
'aedb279e378bed6c2db3c9dc9e12ba635e0b391c',
'a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476']\r\n```\r\n\r\nThe
artifact generated is:\r\n\r\n```\r\n{\r\n entries: [\r\n {\r\n type:
'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.md5',\r\n operator:
'included',\r\n type: 'exact_cased_any',\r\n value:
['741462ab431a22233c787baab9b653c7'],\r\n },\r\n ],\r\n },\r\n {\r\n
type: 'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.sha1',\r\n
operator: 'included',\r\n type: 'exact_cased_any',\r\n value:
['aedb279e378bed6c2db3c9dc9e12ba635e0b391c'],\r\n },\r\n ],\r\n },\r\n
{\r\n type: 'simple',\r\n entries: [\r\n {\r\n field:
'file.hash.sha256',\r\n operator: 'included',\r\n type:
'exact_cased_any',\r\n value:
['a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476'],\r\n
},\r\n ],\r\n },\r\n ]\r\n}\r\n```\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"665937683845322e6c75b18b14041854dcb761c9"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/164700","number":164700,"state":"OPEN"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164599","number":164599,"mergeCommit":{"message":"[Security
Solution][Endpoint] Split blocklist entry in multiple entries when
different hash types (#164599)\n\nFixes:
https://github.com/elastic/kibana/issues/164374\r\n##
Summary\r\n\r\nDuring fleet artifact generation, we split those
blocklist entries that\r\ncontains multiple hash types in it, so the
resulting artifact contains\r\nan entry for each hash type. This is done
for each blocklist if they\r\ncontain multiple hash types in
it.\r\n\r\nIt also updates ftr test to ensure the resulting artifact is
generated\r\ncorrectly.\r\n\r\nFor a blocklist containing these hashes:
\r\n```\r\n['741462ab431a22233c787baab9b653c7',
'aedb279e378bed6c2db3c9dc9e12ba635e0b391c',
'a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476']\r\n```\r\n\r\nThe
artifact generated is:\r\n\r\n```\r\n{\r\n entries: [\r\n {\r\n type:
'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.md5',\r\n operator:
'included',\r\n type: 'exact_cased_any',\r\n value:
['741462ab431a22233c787baab9b653c7'],\r\n },\r\n ],\r\n },\r\n {\r\n
type: 'simple',\r\n entries: [\r\n {\r\n field: 'file.hash.sha1',\r\n
operator: 'included',\r\n type: 'exact_cased_any',\r\n value:
['aedb279e378bed6c2db3c9dc9e12ba635e0b391c'],\r\n },\r\n ],\r\n },\r\n
{\r\n type: 'simple',\r\n entries: [\r\n {\r\n field:
'file.hash.sha256',\r\n operator: 'included',\r\n type:
'exact_cased_any',\r\n value:
['a4370c0cf81686c0b696fa6261c9d3e0d810ae704ab8301839dffd5d5112f476'],\r\n
},\r\n ],\r\n },\r\n ]\r\n}\r\n```\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"665937683845322e6c75b18b14041854dcb761c9"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2023-08-24 13:17:27 -04:00
Kibana Machine
8548581da9
[8.9] [Fleet] set typeMigrationVersion instead of migrationVersion (#164712) (#164728)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Fleet] set typeMigrationVersion instead of migrationVersion
(#164712)](https://github.com/elastic/kibana/pull/164712)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-24T14:37:58Z","message":"[Fleet]
set typeMigrationVersion instead of migrationVersion (#164712)\n\n##
Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/164690\r\n\r\n`migrationVersion`
was removed from es mapping in
8.8:\r\nhttps://github.com/elastic/kibana/issues/154246\r\nReplacing it
with `typeMigrationVersion` using the same logic as in\r\nkibana
core:\r\n\r\nba843882a7/packages/core/saved-objects/core-saved-objects-migration-server-internal/src/document_migrator/migrations/transform_migration_version.ts (L17)\r\n\r\n\r\nTo
verify:\r\n- add Kubernetes integration to a new policy\r\n- verify that
it is added successfully\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"0146dc87e8db9ed085295ad63d5863f2964d4eb6","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.10.0","v8.11.0","v8.9.2"],"number":164712,"url":"https://github.com/elastic/kibana/pull/164712","mergeCommit":{"message":"[Fleet]
set typeMigrationVersion instead of migrationVersion (#164712)\n\n##
Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/164690\r\n\r\n`migrationVersion`
was removed from es mapping in
8.8:\r\nhttps://github.com/elastic/kibana/issues/154246\r\nReplacing it
with `typeMigrationVersion` using the same logic as in\r\nkibana
core:\r\n\r\nba843882a7/packages/core/saved-objects/core-saved-objects-migration-server-internal/src/document_migrator/migrations/transform_migration_version.ts (L17)\r\n\r\n\r\nTo
verify:\r\n- add Kubernetes integration to a new policy\r\n- verify that
it is added successfully\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"0146dc87e8db9ed085295ad63d5863f2964d4eb6"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164712","number":164712,"mergeCommit":{"message":"[Fleet]
set typeMigrationVersion instead of migrationVersion (#164712)\n\n##
Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/164690\r\n\r\n`migrationVersion`
was removed from es mapping in
8.8:\r\nhttps://github.com/elastic/kibana/issues/154246\r\nReplacing it
with `typeMigrationVersion` using the same logic as in\r\nkibana
core:\r\n\r\nba843882a7/packages/core/saved-objects/core-saved-objects-migration-server-internal/src/document_migrator/migrations/transform_migration_version.ts (L17)\r\n\r\n\r\nTo
verify:\r\n- add Kubernetes integration to a new policy\r\n- verify that
it is added successfully\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"0146dc87e8db9ed085295ad63d5863f2964d4eb6"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
2023-08-24 09:03:25 -07:00
Georgii Gorbachev
128fde2748
[8.9] [Security Solution] Modal says "duplicating 0 rules" when you duplicate an individual rule (#163908) (#164687)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Modal says "duplicating 0 rules" when you
duplicate an individual rule
(#163908)](https://github.com/elastic/kibana/pull/163908)

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

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

<!--BACKPORT
[{"author":{"name":"GitStart","email":"1501599+gitstart@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-24T07:13:17Z","message":"[Security
Solution] Modal says \"duplicating 0 rules\" when you duplicate an
individual rule (#163908)\n\n ## What does this PR do?\r\n * It fixes
the count on the duplicate modal when duplicating an individual
rule.\r\n \r\n ## Issue References\r\nFixes #162035\r\n \r\n ##
Video/Screenshot Demo\r\n ##### Steps to reproduce &
Fix:\r\nhttps://www.loom.com/share/931e42c1490d4483958b8f98dc0ba534?sid=07c67df5-b380-41a5-90f1-f64f326a12d9\r\n\r\n___\r\n
\r\n This code was written and reviewed by GitStart Community. Growing
future engineers, one PR at a
time.","sha":"59f20582605d5dcb489b6534b027ec19475e7136","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","💝community","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection Rule
Management","v8.10.0","v8.9.2"],"number":163908,"url":"https://github.com/elastic/kibana/pull/163908","mergeCommit":{"message":"[Security
Solution] Modal says \"duplicating 0 rules\" when you duplicate an
individual rule (#163908)\n\n ## What does this PR do?\r\n * It fixes
the count on the duplicate modal when duplicating an individual
rule.\r\n \r\n ## Issue References\r\nFixes #162035\r\n \r\n ##
Video/Screenshot Demo\r\n ##### Steps to reproduce &
Fix:\r\nhttps://www.loom.com/share/931e42c1490d4483958b8f98dc0ba534?sid=07c67df5-b380-41a5-90f1-f64f326a12d9\r\n\r\n___\r\n
\r\n This code was written and reviewed by GitStart Community. Growing
future engineers, one PR at a
time.","sha":"59f20582605d5dcb489b6534b027ec19475e7136"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","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: GitStart <1501599+gitstart@users.noreply.github.com>
2023-08-24 16:11:43 +02:00
Juan Pablo Djeredjian
993447864a
[8.9] [Security Solution] Fix flaky test: detection_rules/bulk_edit_rules_actions.cy.ts (#164569)
**NOTE: This is a manual backport of
https://github.com/elastic/kibana/pull/163698**

**Original PR description:**

Fixes: https://github.com/elastic/kibana/issues/154721

## Summary

- Fixes flaky test:
`x-pack/plugins/security_solution/cypress/e2e/detection_response/rule_management/rule_actions/bulk_actions/bulk_edit_rules_actions.cy.ts`
- Test title: `Detection rules, bulk edit of rule actions`


## Details

For: `Detection rules, bulk edit of rule actions - Restricted action
privileges - User with no privileges can't add rule actions`
- Since this test logs in with a user with missing privileges, the
"Missing privileges" callout is shown at the top of the Rules Table. The
`selectNumberOfRules();` command selects rules one by one by clicking on
their checkboxes. However, flakiness was caused when the callout was
rendered while the selection of the rules was happening, causing a
layout shift that caused the selection of a checkbox to lose focus, and
not being able to be checked. This was solved by waiting the callout to
be rendered before the selection of rules start, with the new
`waitForCallOutToBeShown`method.

For: `Detection rules, bulk edit of rule actions - All actions
privileges - before/beforeEach Clause`
- Tests were failing in the `beforeEach` clause because the first test,
mentioned above, would be logged in with a `ROLES.hunter_no_actions`
role, and logging in with a user with permissions happened in a `before`
clause instead of a `beforeEach` clause. This caused the rest of the
suite to continue with a role without permissions, and the setup of the
second test would fail as the API requests done would fail with `401`.
Moving the initial logging-in from a `before` clause to a `beforeEach`
clause solved this issue.

For: `Detection rules, bulk edit of rule actions - All actions
privileges - Add a rule action to rules (existing connector)`
- This flakiness was extremely rare, but could be reproduced after about
400 iterations. It was caused by a similar reason as the first case
above: while rules were being selected one by one, the table would auto
refresh and focus would be lost from the checkbox that was about to be
selected. This aws fixed by disabling autorefresh in the setup.

### Other changes
- Prevents the installation of `security_detection_engine` package and
creates mock rules instead.
- Creates the `waitForCallOutToBeShown` method and moves the callout IDs
spread across different files to a a single file where they are exported
from.
2023-08-24 14:15:50 +02:00
Juan Pablo Djeredjian
7b2b4a4b61
[8.9] [Security Solution] Flaky Cypress test: Detection rules, Prebuilt Rules Installation and Update workflow - Installation of prebuilt rules package via Fleet should install package from Fleet in the background (#164566)
**NOTE: This is a manual backport of
https://github.com/elastic/kibana/pull/163468 to 8.9.**

**Original PR description:**

Fixes: https://github.com/elastic/kibana/issues/163447
Fixes: https://github.com/elastic/kibana/issues/163586

## Summary

- Fixes flaky test:
`x-pack/plugins/security_solution/cypress/e2e/detection_response/prebuilt_rules/prebuilt_rules_install_update_workflows.cy.ts`
- Test title: `Detection rules, Prebuilt Rules Installation and Update
workflow - Installation of prebuilt rules package via Fleet should
install package from Fleet in the background`

## Details

- Initially ran the flaky test runner with multiple iterations and all
gave succesful results, i.e. no flakiness or failed tests.
- But: after checking the logs for the failed tests in the original
failed build, discovered that the reason the test failed is because:
- when checking Fleet's response for the installation of the
`security_detection_engine`, the API response was not as expected from
the API spec:
```
**Expected:** [{ name: 'security_detection_engine', installSource: 'registry' }]
**Actual:** [{ name: 'security_detection_engine', installSource: undefined }]
```
Since we cannot rely 100% that the Fleet API will return the correct
value for the installSource, this PR deletes this part of the test to
prevent any type of flakiness caused by external factors such as this.
2023-08-24 14:15:09 +02:00
Juan Pablo Djeredjian
949e6630fc
[8.9] [Security Solution] Fix flaky test: x-pack/test/detection_engine_api_integration/security_and_spaces/update_prebuilt_rules_package/update_prebuilt_rules_package·ts - update_prebuilt_rules_package should allow user to install prebuilt rules from scratch, then install new rules and upgrade existing rules from the new package (#164558)
**NOTE: This is a manual backport of
https://github.com/elastic/kibana/pull/163241. It had to be done
manually because of changes that happened from 8.9 -> 8.10 like the
common folder restructuring and some type changes because of the OpenAPI
effort, but it is mostly the changes to the same files as that PR.**

**Original PR description follows:**

Fixes: https://github.com/elastic/kibana/issues/162658

## Summary

- Fixes flaky test:
`x-pack/test/detection_engine_api_integration/security_and_spaces/update_prebuilt_rules_package/update_prebuilt_rules_package·ts`
- Test title: `update_prebuilt_rules_package should allow user to
install prebuilt rules from scratch, then install new rules and upgrade
existing rules from the new package`

## Passing flaky test runner

300 runs:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2799

## Root cause and what this PR does

- On initial investigation, the flaky test runner was executed for this
test with 300 iterations and all of them succeeded. This gives us great
confidence that the test is not actually flaky.
- Further investigation showed that @kibanamachine reported this tests
as failing when running the CI for two backport PRs to `8.9`:
-
https://buildkite.com/elastic/kibana-on-merge/builds/33282#0189987d-3a80-49c2-8332-3105ec3c2109
-
https://buildkite.com/elastic/kibana-on-merge/builds/33444#0189b1fa-4bc4-4422-9ce9-5c9a24f11ad5
- These flakiness was caused **by a race condition** between the writing
of rules into indeces, and them being made available for reading. This
is a known issue, already and solved for other integration test, by
manually refreshing ES's indeces.
- In order to reduce the probability of flakiness in a similar scenario,
this PR adds code to refresh the indices after each rule installation or
upgrade during the test.

## Refactor

- Moves the refreshing of the indexes within the utility function that
write to indexes:
    - `installPrebuiltRules`
    - `upgradePrebuiltRules`
    - `installPrebuiltRulesAndTimelines` (legacy, but still used)
    - `installPrebuiltRulesFleetPackage`
- Creates 2 new utils:
- `installPrebuiltRulesPackageByVersion`, which installs
`security_detection_engine` package via Fleet API, with its version
passed in as param
- `getInstalledRules`, reusable function to fetch all installed rules
    -
2023-08-24 14:14:48 +02:00
Wafaa Nasr
63985f2fba
[8.9] [Security Solution] [Detection Engine] Fix exception comment flakiness (#162807) (#164621)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Detection Engine] Fix exception comment
flakiness (#162807)](https://github.com/elastic/kibana/pull/162807)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2023-08-01T13:58:40Z","message":"[Security
Solution] [Detection Engine] Fix exception comment flakiness
(#162807)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/162565 \r\n- Converting the
`Comments` related Cypress test to a FTR test according\r\nto
these\r\n[observations](https://github.com/elastic/kibana/issues/162565#issuecomment-1653410937)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a2275dd346b027db0224e7afa5df58158eb9b641","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["WIP","release_note:skip","test-failure-flaky","Team:Detection
Engine","v8.10.0","v8.9.2"],"number":162807,"url":"https://github.com/elastic/kibana/pull/162807","mergeCommit":{"message":"[Security
Solution] [Detection Engine] Fix exception comment flakiness
(#162807)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/162565 \r\n- Converting the
`Comments` related Cypress test to a FTR test according\r\nto
these\r\n[observations](https://github.com/elastic/kibana/issues/162565#issuecomment-1653410937)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a2275dd346b027db0224e7afa5df58158eb9b641"}},"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/162807","number":162807,"mergeCommit":{"message":"[Security
Solution] [Detection Engine] Fix exception comment flakiness
(#162807)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/162565 \r\n- Converting the
`Comments` related Cypress test to a FTR test according\r\nto
these\r\n[observations](https://github.com/elastic/kibana/issues/162565#issuecomment-1653410937)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a2275dd346b027db0224e7afa5df58158eb9b641"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2023-08-24 10:37:11 +02:00
Wafaa Nasr
4c62619b31
[8.9] [Security Solution] [Flaky test] Fix double ftr test flakiness (#162990) (#164616)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Flaky test] Fix double ftr test flakiness
(#162990)](https://github.com/elastic/kibana/pull/162990)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2023-08-09T14:40:55Z","message":"[Security
Solution] [Flaky test] Fix double ftr test flakiness (#162990)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/155122 \r\n\r\n\r\n##
Investigations\r\n\r\n\r\n *First attempt*\r\n\r\n> While investigating
the three failing pipelines and examining the\r\nArtifacts, specifically
target/test_failures/*.log, I discovered the\r\nroot cause to be\r\n>
Did not get an expected 200 \"ok\" when waiting for a list
item\r\n(waitForListItem) yet. Retrying until we get a 200 \"ok\".
body:\r\n{\"message\":\"list_id: \\\"list_items.txt\\\" item of 1.0 does
not\r\nexist\",\"status_code\":404}, status: 404\r\n>
\r\n>\r\n![image](ad3c4db9-e340-42c0-8a61-63e5387b9b83)\r\n>
\r\n\r\n*Second attempt*\r\n\r\n\r\n> Upon incorporating additional logs
to pinpoint the underlying issue,\r\nit was realized that the test will
persist in its attempts until the\r\npreceding error is rectified, and
it was determined that the\r\nlist_items.txt file contains the correct
item once located.\r\n> \r\n> The problem seemed to be associated with
incomplete indexing of all\r\nindices signalsOpen.hits.hits when the
test verifies against the\r\nanticipated value.\r\n> \r\n> To
investigate the matter, two iterations were conducted, totaling
490\r\nattempts. During these iterations, logs, and warnings were
deliberately\r\ninserted to facilitate the tracing of the issue.\r\n>
\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2770#0189bb29-c258-4586-986a-2ac5e128eb52\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2768#0189baeb-8f09-488e-936f-69e72d089787\r\n>
\r\n> In
this\r\n[Atifact](0189bb29-c258-4586-986a-2ac5e128eb52_d98d35afa0abd1ad03e28a68882291c4.log?response-content-type=text%2Fplain&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAQPCP3C7LXS7MSJGH%2F20230808%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230808T102039Z&X-Amz-Expires=600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEOH%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJHMEUCIQDYG9De6RYDlVNcO0JGqO6Qc4dpzCQG1s%2BgaXTSimWc9QIgfkZgXlnVcScJCO56vz2VQx1buVTNEDEaVYhYmDgupEgq%2BgMIiv%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FARAAGgwwMzIzNzk3MDUzMDMiDOz2Gl2kfcuTHVaWyirOA4iHfkFBI7KBoy%2F97CuLMAxGLNIR8h4FtLCsY664lMhgDGd%2FBVi82zu%2B2Y5DAGEboOmb7C1q%2FX6CyesjDKP7sknXdfT7q8B4jBRK4QcVw2AAvC9%2BqMeN37eCfRXWT%2FrQAEdaWzxkJxk4BtFcATds3LJmmAlbYOT2L7vItmGzGs%2FnkRYevX%2Fq6hwxWqmOKNNot9hZ9sMJ3TZvGsA3045459BfyfObwIlzb13Pj6V7%2FMyTb87RjQazFiK%2Bb7qOXB%2B7ItaVAcpG7diXzPAif%2F%2FEiJedTHtBVh4LsMIKQtiASbcTh4X90kYtVMUcH%2BSG0B41WjWYPok0C3tHfQnGhGBIbSnqvMGmWgwGlhHNF1G7nIDYyWs32PQ3M3WmTGQuLIwp2hPzk4wFtgH%2FDQPWevRFRT%2FhzYJf05hyBT9BMcST9eeKTqEqs52PhCHDlCgo7K5bGjT86OO16MzEKdA77HRro8GqIh6mgTMyQ5gKpH38ueUWvQZnLix4T5HYw0EyJgRLRfiVIpKcH0jRobaFwKSfSYc%2FZ2FPHsAK31weedhy6tafwU7elNYiAaMRv4AQhB%2FlrGWYd6IjOrdgSFowlkd1m5%2FrYTY3k7%2F8D0vsxgjUETDX9semBjqlAWkLq%2FLaRV5KokMNXfT3lCVNJzpYeN1%2FdnInE%2BQn3Ub86kRgMOfTN2OgDHkuYSKsQ95tFHH49NfRn6rTw8tI2Tjs3pToqp65gCYh9MzUKTd2EWsgqdNn6y%2BbHRGFJxd7cacrX9Ghr4XyNme5aAeWAVYNXSqJ1KIbtWmRcwwhThAJHxWk5%2FoBwScZRUSYGWmkhaxnZXDjXg6LBuH7uZOJjf%2FLuFVdtQ%3D%3D&X-Amz-SignedHeaders=host&X-Amz-Signature=8a44c3a5e3b88b632097dc344ecec1ba6d6cb8e80e10d9058e96883e43d925b5)\r\n>
\r\n>\r\n![image](bc58d389-3586-4343-a9f9-9577331d4876)\r\n>
\r\n> \r\n\r\n## Solution \r\n\r\nBy modifying the third parameter of
the `await\r\nwaitForSignalsToBePresent(supertest, log, 1, [id]);`
function to a value\r\nof 3 instead of the initial 1, we signify the
number of alerts we need\r\nto await before conducting assertions. This
change is made to\r\naccommodate the assertion of three alerts being
generated, accounting\r\nfor the exclusion of a single 1.0
value.","sha":"f48d422a2e5114e899df5697a18de10918beb779","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-failure-flaky","Feature:Rule
Exceptions","v8.9.0","Team:Detection
Engine","v8.10.0","v8.11.0"],"number":162990,"url":"https://github.com/elastic/kibana/pull/162990","mergeCommit":{"message":"[Security
Solution] [Flaky test] Fix double ftr test flakiness (#162990)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/155122 \r\n\r\n\r\n##
Investigations\r\n\r\n\r\n *First attempt*\r\n\r\n> While investigating
the three failing pipelines and examining the\r\nArtifacts, specifically
target/test_failures/*.log, I discovered the\r\nroot cause to be\r\n>
Did not get an expected 200 \"ok\" when waiting for a list
item\r\n(waitForListItem) yet. Retrying until we get a 200 \"ok\".
body:\r\n{\"message\":\"list_id: \\\"list_items.txt\\\" item of 1.0 does
not\r\nexist\",\"status_code\":404}, status: 404\r\n>
\r\n>\r\n![image](ad3c4db9-e340-42c0-8a61-63e5387b9b83)\r\n>
\r\n\r\n*Second attempt*\r\n\r\n\r\n> Upon incorporating additional logs
to pinpoint the underlying issue,\r\nit was realized that the test will
persist in its attempts until the\r\npreceding error is rectified, and
it was determined that the\r\nlist_items.txt file contains the correct
item once located.\r\n> \r\n> The problem seemed to be associated with
incomplete indexing of all\r\nindices signalsOpen.hits.hits when the
test verifies against the\r\nanticipated value.\r\n> \r\n> To
investigate the matter, two iterations were conducted, totaling
490\r\nattempts. During these iterations, logs, and warnings were
deliberately\r\ninserted to facilitate the tracing of the issue.\r\n>
\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2770#0189bb29-c258-4586-986a-2ac5e128eb52\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2768#0189baeb-8f09-488e-936f-69e72d089787\r\n>
\r\n> In
this\r\n[Atifact](0189bb29-c258-4586-986a-2ac5e128eb52_d98d35afa0abd1ad03e28a68882291c4.log?response-content-type=text%2Fplain&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAQPCP3C7LXS7MSJGH%2F20230808%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230808T102039Z&X-Amz-Expires=600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEOH%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJHMEUCIQDYG9De6RYDlVNcO0JGqO6Qc4dpzCQG1s%2BgaXTSimWc9QIgfkZgXlnVcScJCO56vz2VQx1buVTNEDEaVYhYmDgupEgq%2BgMIiv%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FARAAGgwwMzIzNzk3MDUzMDMiDOz2Gl2kfcuTHVaWyirOA4iHfkFBI7KBoy%2F97CuLMAxGLNIR8h4FtLCsY664lMhgDGd%2FBVi82zu%2B2Y5DAGEboOmb7C1q%2FX6CyesjDKP7sknXdfT7q8B4jBRK4QcVw2AAvC9%2BqMeN37eCfRXWT%2FrQAEdaWzxkJxk4BtFcATds3LJmmAlbYOT2L7vItmGzGs%2FnkRYevX%2Fq6hwxWqmOKNNot9hZ9sMJ3TZvGsA3045459BfyfObwIlzb13Pj6V7%2FMyTb87RjQazFiK%2Bb7qOXB%2B7ItaVAcpG7diXzPAif%2F%2FEiJedTHtBVh4LsMIKQtiASbcTh4X90kYtVMUcH%2BSG0B41WjWYPok0C3tHfQnGhGBIbSnqvMGmWgwGlhHNF1G7nIDYyWs32PQ3M3WmTGQuLIwp2hPzk4wFtgH%2FDQPWevRFRT%2FhzYJf05hyBT9BMcST9eeKTqEqs52PhCHDlCgo7K5bGjT86OO16MzEKdA77HRro8GqIh6mgTMyQ5gKpH38ueUWvQZnLix4T5HYw0EyJgRLRfiVIpKcH0jRobaFwKSfSYc%2FZ2FPHsAK31weedhy6tafwU7elNYiAaMRv4AQhB%2FlrGWYd6IjOrdgSFowlkd1m5%2FrYTY3k7%2F8D0vsxgjUETDX9semBjqlAWkLq%2FLaRV5KokMNXfT3lCVNJzpYeN1%2FdnInE%2BQn3Ub86kRgMOfTN2OgDHkuYSKsQ95tFHH49NfRn6rTw8tI2Tjs3pToqp65gCYh9MzUKTd2EWsgqdNn6y%2BbHRGFJxd7cacrX9Ghr4XyNme5aAeWAVYNXSqJ1KIbtWmRcwwhThAJHxWk5%2FoBwScZRUSYGWmkhaxnZXDjXg6LBuH7uZOJjf%2FLuFVdtQ%3D%3D&X-Amz-SignedHeaders=host&X-Amz-Signature=8a44c3a5e3b88b632097dc344ecec1ba6d6cb8e80e10d9058e96883e43d925b5)\r\n>
\r\n>\r\n![image](bc58d389-3586-4343-a9f9-9577331d4876)\r\n>
\r\n> \r\n\r\n## Solution \r\n\r\nBy modifying the third parameter of
the `await\r\nwaitForSignalsToBePresent(supertest, log, 1, [id]);`
function to a value\r\nof 3 instead of the initial 1, we signify the
number of alerts we need\r\nto await before conducting assertions. This
change is made to\r\naccommodate the assertion of three alerts being
generated, accounting\r\nfor the exclusion of a single 1.0
value.","sha":"f48d422a2e5114e899df5697a18de10918beb779"}},"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/162990","number":162990,"mergeCommit":{"message":"[Security
Solution] [Flaky test] Fix double ftr test flakiness (#162990)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/155122 \r\n\r\n\r\n##
Investigations\r\n\r\n\r\n *First attempt*\r\n\r\n> While investigating
the three failing pipelines and examining the\r\nArtifacts, specifically
target/test_failures/*.log, I discovered the\r\nroot cause to be\r\n>
Did not get an expected 200 \"ok\" when waiting for a list
item\r\n(waitForListItem) yet. Retrying until we get a 200 \"ok\".
body:\r\n{\"message\":\"list_id: \\\"list_items.txt\\\" item of 1.0 does
not\r\nexist\",\"status_code\":404}, status: 404\r\n>
\r\n>\r\n![image](ad3c4db9-e340-42c0-8a61-63e5387b9b83)\r\n>
\r\n\r\n*Second attempt*\r\n\r\n\r\n> Upon incorporating additional logs
to pinpoint the underlying issue,\r\nit was realized that the test will
persist in its attempts until the\r\npreceding error is rectified, and
it was determined that the\r\nlist_items.txt file contains the correct
item once located.\r\n> \r\n> The problem seemed to be associated with
incomplete indexing of all\r\nindices signalsOpen.hits.hits when the
test verifies against the\r\nanticipated value.\r\n> \r\n> To
investigate the matter, two iterations were conducted, totaling
490\r\nattempts. During these iterations, logs, and warnings were
deliberately\r\ninserted to facilitate the tracing of the issue.\r\n>
\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2770#0189bb29-c258-4586-986a-2ac5e128eb52\r\n>\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2768#0189baeb-8f09-488e-936f-69e72d089787\r\n>
\r\n> In
this\r\n[Atifact](0189bb29-c258-4586-986a-2ac5e128eb52_d98d35afa0abd1ad03e28a68882291c4.log?response-content-type=text%2Fplain&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAQPCP3C7LXS7MSJGH%2F20230808%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230808T102039Z&X-Amz-Expires=600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEOH%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJHMEUCIQDYG9De6RYDlVNcO0JGqO6Qc4dpzCQG1s%2BgaXTSimWc9QIgfkZgXlnVcScJCO56vz2VQx1buVTNEDEaVYhYmDgupEgq%2BgMIiv%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FARAAGgwwMzIzNzk3MDUzMDMiDOz2Gl2kfcuTHVaWyirOA4iHfkFBI7KBoy%2F97CuLMAxGLNIR8h4FtLCsY664lMhgDGd%2FBVi82zu%2B2Y5DAGEboOmb7C1q%2FX6CyesjDKP7sknXdfT7q8B4jBRK4QcVw2AAvC9%2BqMeN37eCfRXWT%2FrQAEdaWzxkJxk4BtFcATds3LJmmAlbYOT2L7vItmGzGs%2FnkRYevX%2Fq6hwxWqmOKNNot9hZ9sMJ3TZvGsA3045459BfyfObwIlzb13Pj6V7%2FMyTb87RjQazFiK%2Bb7qOXB%2B7ItaVAcpG7diXzPAif%2F%2FEiJedTHtBVh4LsMIKQtiASbcTh4X90kYtVMUcH%2BSG0B41WjWYPok0C3tHfQnGhGBIbSnqvMGmWgwGlhHNF1G7nIDYyWs32PQ3M3WmTGQuLIwp2hPzk4wFtgH%2FDQPWevRFRT%2FhzYJf05hyBT9BMcST9eeKTqEqs52PhCHDlCgo7K5bGjT86OO16MzEKdA77HRro8GqIh6mgTMyQ5gKpH38ueUWvQZnLix4T5HYw0EyJgRLRfiVIpKcH0jRobaFwKSfSYc%2FZ2FPHsAK31weedhy6tafwU7elNYiAaMRv4AQhB%2FlrGWYd6IjOrdgSFowlkd1m5%2FrYTY3k7%2F8D0vsxgjUETDX9semBjqlAWkLq%2FLaRV5KokMNXfT3lCVNJzpYeN1%2FdnInE%2BQn3Ub86kRgMOfTN2OgDHkuYSKsQ95tFHH49NfRn6rTw8tI2Tjs3pToqp65gCYh9MzUKTd2EWsgqdNn6y%2BbHRGFJxd7cacrX9Ghr4XyNme5aAeWAVYNXSqJ1KIbtWmRcwwhThAJHxWk5%2FoBwScZRUSYGWmkhaxnZXDjXg6LBuH7uZOJjf%2FLuFVdtQ%3D%3D&X-Amz-SignedHeaders=host&X-Amz-Signature=8a44c3a5e3b88b632097dc344ecec1ba6d6cb8e80e10d9058e96883e43d925b5)\r\n>
\r\n>\r\n![image](bc58d389-3586-4343-a9f9-9577331d4876)\r\n>
\r\n> \r\n\r\n## Solution \r\n\r\nBy modifying the third parameter of
the `await\r\nwaitForSignalsToBePresent(supertest, log, 1, [id]);`
function to a value\r\nof 3 instead of the initial 1, we signify the
number of alerts we need\r\nto await before conducting assertions. This
change is made to\r\naccommodate the assertion of three alerts being
generated, accounting\r\nfor the exclusion of a single 1.0
value.","sha":"f48d422a2e5114e899df5697a18de10918beb779"}},{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2023-08-24 10:34:21 +02:00
Kibana Machine
5a890ddfae
[8.9] [Security Solution] [Endpoint] Convert hash values to lower case for Blocklist (#164472) (#164578)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Endpoint] Convert hash values to lower case for
Blocklist (#164472)](https://github.com/elastic/kibana/pull/164472)

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

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

<!--BACKPORT [{"author":{"name":"David
Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2023-08-23T12:11:18Z","message":"[Security
Solution] [Endpoint] Convert hash values to lower case for Blocklist
(#164472)\n\nFixes:
https://github.com/elastic/kibana/issues/164373\r\n## Summary\r\n\r\n-
Converts Blocklist hash values to lower case in UI (same thing
we\r\nalready do for Trusted Apps).\r\n- Fixes test cases (FTR and
Cypress).","sha":"1cdcb84591b82f3fdc3094eee70d60b4ea878212","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","v8.10.0","v8.11.0","v8.9.2"],"number":164472,"url":"https://github.com/elastic/kibana/pull/164472","mergeCommit":{"message":"[Security
Solution] [Endpoint] Convert hash values to lower case for Blocklist
(#164472)\n\nFixes:
https://github.com/elastic/kibana/issues/164373\r\n## Summary\r\n\r\n-
Converts Blocklist hash values to lower case in UI (same thing
we\r\nalready do for Trusted Apps).\r\n- Fixes test cases (FTR and
Cypress).","sha":"1cdcb84591b82f3fdc3094eee70d60b4ea878212"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164472","number":164472,"mergeCommit":{"message":"[Security
Solution] [Endpoint] Convert hash values to lower case for Blocklist
(#164472)\n\nFixes:
https://github.com/elastic/kibana/issues/164373\r\n## Summary\r\n\r\n-
Converts Blocklist hash values to lower case in UI (same thing
we\r\nalready do for Trusted Apps).\r\n- Fixes test cases (FTR and
Cypress).","sha":"1cdcb84591b82f3fdc3094eee70d60b4ea878212"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: David Sánchez <david.sanchezsoler@elastic.co>
2023-08-23 07:06:11 -07:00
Kibana Machine
06368c20aa
[8.9] [Security Solution][Endpoint] Fixes kibana crash when going back to policy details page (#164329) (#164556)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Endpoint] Fixes kibana crash when going back to
policy details page
(#164329)](https://github.com/elastic/kibana/pull/164329)

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

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

<!--BACKPORT [{"author":{"name":"David
Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2023-08-23T10:44:11Z","message":"[Security
Solution][Endpoint] Fixes kibana crash when going back to policy details
page (#164329)\n\nFixes:
https://github.com/elastic/kibana/issues/164295\r\nFixes:
https://github.com/elastic/kibana/issues/164190\r\n\r\n##
Summary\r\nThere was a Kibana crash when using back link buttons to go
back to the\r\npolicy details page from Trusted Apps / Event Filters /
Host Isolation\r\nexceptions / Blocklists page. Route state can be null
depending on the\r\nprevious action so it has to be
conditional.\r\n\r\nThe error occurs when it tries to access the
`backLink` prop on\r\n`routeState` when it's not
defined.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fb79e3e86430418c8a10d1cb9041c5e4f901a436","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","v8.10.0","v8.11.0","v8.9.2"],"number":164329,"url":"https://github.com/elastic/kibana/pull/164329","mergeCommit":{"message":"[Security
Solution][Endpoint] Fixes kibana crash when going back to policy details
page (#164329)\n\nFixes:
https://github.com/elastic/kibana/issues/164295\r\nFixes:
https://github.com/elastic/kibana/issues/164190\r\n\r\n##
Summary\r\nThere was a Kibana crash when using back link buttons to go
back to the\r\npolicy details page from Trusted Apps / Event Filters /
Host Isolation\r\nexceptions / Blocklists page. Route state can be null
depending on the\r\nprevious action so it has to be
conditional.\r\n\r\nThe error occurs when it tries to access the
`backLink` prop on\r\n`routeState` when it's not
defined.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fb79e3e86430418c8a10d1cb9041c5e4f901a436"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164329","number":164329,"mergeCommit":{"message":"[Security
Solution][Endpoint] Fixes kibana crash when going back to policy details
page (#164329)\n\nFixes:
https://github.com/elastic/kibana/issues/164295\r\nFixes:
https://github.com/elastic/kibana/issues/164190\r\n\r\n##
Summary\r\nThere was a Kibana crash when using back link buttons to go
back to the\r\npolicy details page from Trusted Apps / Event Filters /
Host Isolation\r\nexceptions / Blocklists page. Route state can be null
depending on the\r\nprevious action so it has to be
conditional.\r\n\r\nThe error occurs when it tries to access the
`backLink` prop on\r\n`routeState` when it's not
defined.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fb79e3e86430418c8a10d1cb9041c5e4f901a436"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: David Sánchez <david.sanchezsoler@elastic.co>
2023-08-23 04:59:27 -07:00
Julia Bardi
b3a4723498
[8.9][Fleet] Fix index patterns being recreated in default space, fix migr… (#164531)
Backport https://github.com/elastic/kibana/pull/164456 to 8.9 (only
index pattern fix)
2023-08-23 12:21:11 +01:00
Elastic Machine
5e65000375
[8.9] Sync bundled packages with Package Storage (#164526)
Automated by
https://internal-ci.elastic.co/job/package_storage/job/sync-bundled-packages-job/job/main/6480/

Co-authored-by: apmmachine <infra-root+apmmachine@elastic.co>
2023-08-23 01:42:23 -07:00
Kibana Machine
e164e8ab59
[8.9] [Security Selection][Detection engine] fixes rule preview performance issues (#164207) (#164487)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Selection][Detection engine] fixes rule preview performance
issues (#164207)](https://github.com/elastic/kibana/pull/164207)

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

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

<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-22T17:05:15Z","message":"[Security
Selection][Detection engine] fixes rule preview performance issues
(#164207)\n\n## Summary\r\n\r\nOn every single keyboard type on query
input, the whole preview part was\r\nre-rendering. If there are too many
alerts, it could take ~150ms-200ms,\r\nfor its re-render. Ultimately,
making form almost unusable\r\nSo, in this PR I'm adding memoization for
2 Preview components, to\r\nresolve this issue\r\n\r\n\r\n###
Before\r\n\r\n<img width=\"2529\" alt=\"Screenshot 2023-08-17 at 17 13
07\"\r\nsrc=\"c0b137e6-828b-4068-b061-85a5b5ca99f1\">\r\n\r\n###
After\r\n\r\n<img width=\"2523\" alt=\"Screenshot 2023-08-17 at 17 07
56\"\r\nsrc=\"06a0983c-d8e0-40c1-9b48-fd4bc106e922\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cd8a94ba3203022a7791e85a8dd8a6c16ae381ab","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","backport:prev-minor","Team:Detection
Engine","v8.10.0","v8.11.0","v8.9.2"],"number":164207,"url":"https://github.com/elastic/kibana/pull/164207","mergeCommit":{"message":"[Security
Selection][Detection engine] fixes rule preview performance issues
(#164207)\n\n## Summary\r\n\r\nOn every single keyboard type on query
input, the whole preview part was\r\nre-rendering. If there are too many
alerts, it could take ~150ms-200ms,\r\nfor its re-render. Ultimately,
making form almost unusable\r\nSo, in this PR I'm adding memoization for
2 Preview components, to\r\nresolve this issue\r\n\r\n\r\n###
Before\r\n\r\n<img width=\"2529\" alt=\"Screenshot 2023-08-17 at 17 13
07\"\r\nsrc=\"c0b137e6-828b-4068-b061-85a5b5ca99f1\">\r\n\r\n###
After\r\n\r\n<img width=\"2523\" alt=\"Screenshot 2023-08-17 at 17 07
56\"\r\nsrc=\"06a0983c-d8e0-40c1-9b48-fd4bc106e922\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cd8a94ba3203022a7791e85a8dd8a6c16ae381ab"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164207","number":164207,"mergeCommit":{"message":"[Security
Selection][Detection engine] fixes rule preview performance issues
(#164207)\n\n## Summary\r\n\r\nOn every single keyboard type on query
input, the whole preview part was\r\nre-rendering. If there are too many
alerts, it could take ~150ms-200ms,\r\nfor its re-render. Ultimately,
making form almost unusable\r\nSo, in this PR I'm adding memoization for
2 Preview components, to\r\nresolve this issue\r\n\r\n\r\n###
Before\r\n\r\n<img width=\"2529\" alt=\"Screenshot 2023-08-17 at 17 13
07\"\r\nsrc=\"c0b137e6-828b-4068-b061-85a5b5ca99f1\">\r\n\r\n###
After\r\n\r\n<img width=\"2523\" alt=\"Screenshot 2023-08-17 at 17 07
56\"\r\nsrc=\"06a0983c-d8e0-40c1-9b48-fd4bc106e922\">\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"cd8a94ba3203022a7791e85a8dd8a6c16ae381ab"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
2023-08-22 11:32:48 -07:00
Kibana Machine
2ac7591d36
[8.9] [Security Solution] File paths for Blocklist Windows and Mac should be case insensitive (#164200) (#164319)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] File paths for Blocklist Windows and Mac should
be case insensitive
(#164200)](https://github.com/elastic/kibana/pull/164200)

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

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

<!--BACKPORT [{"author":{"name":"Kevin
Logan","email":"56395104+kevinlog@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-21T14:00:53Z","message":"[Security
Solution] File paths for Blocklist Windows and Mac should be case
insensitive (#164200)\n\n## Summary\r\n\r\nThis fixes a bug where
Windows and Mac Blocklist file path entries\r\nshould be passed as case
insensitive. This is because Mac and Windows\r\nare caseless for most
use cases.\r\n\r\nBug ticket:
https://github.com/elastic/kibana/issues/158581\r\n\r\nHere is how it
will be displayed in the UI:\r\n<img width=\"1728\"
alt=\"image\"\r\nsrc=\"a3006397-f49e-4de0-818d-94e2de20dba3\">\r\n\r\nHere
are the breakdown of the artifacts after the
fix:\r\n\r\nLinux:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-linux-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-linux-v1/f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n
Encoded SHA256:
a907835be40af89b8b7aa23a6efc66c01ceaa5a19622edd378139319f3ca5fa0\r\n
Decoded SHA256:
f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_cased_any\",\r\n \"value\": [\r\n
\"/opt/bin/bin.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\nMac:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-macos-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-macos-v1/b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n
Encoded SHA256:
4f3e80d688f5cae4bf6a88b0704e37909f9fa4f47fe8325b7b154cddd46a2db9\r\n
Decoded SHA256:
b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"/opt/exe.exe\"\r\n ]\r\n }\r\n ]\r\n
}\r\n```\r\n\r\nWindows:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-windows-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-windows-v1/2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n
Encoded SHA256:
c6e045fce97651336eeb400f0123541475b940e3aa38ce721f299585683da288\r\n
Decoded SHA256:
2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"C:\\\\path\\\\path.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"88bd71c0773d158ed1e6312075633ed85abc575e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Defend
Workflows","v8.10.0","v8.11.0","v8.9.2"],"number":164200,"url":"https://github.com/elastic/kibana/pull/164200","mergeCommit":{"message":"[Security
Solution] File paths for Blocklist Windows and Mac should be case
insensitive (#164200)\n\n## Summary\r\n\r\nThis fixes a bug where
Windows and Mac Blocklist file path entries\r\nshould be passed as case
insensitive. This is because Mac and Windows\r\nare caseless for most
use cases.\r\n\r\nBug ticket:
https://github.com/elastic/kibana/issues/158581\r\n\r\nHere is how it
will be displayed in the UI:\r\n<img width=\"1728\"
alt=\"image\"\r\nsrc=\"a3006397-f49e-4de0-818d-94e2de20dba3\">\r\n\r\nHere
are the breakdown of the artifacts after the
fix:\r\n\r\nLinux:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-linux-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-linux-v1/f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n
Encoded SHA256:
a907835be40af89b8b7aa23a6efc66c01ceaa5a19622edd378139319f3ca5fa0\r\n
Decoded SHA256:
f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_cased_any\",\r\n \"value\": [\r\n
\"/opt/bin/bin.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\nMac:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-macos-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-macos-v1/b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n
Encoded SHA256:
4f3e80d688f5cae4bf6a88b0704e37909f9fa4f47fe8325b7b154cddd46a2db9\r\n
Decoded SHA256:
b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"/opt/exe.exe\"\r\n ]\r\n }\r\n ]\r\n
}\r\n```\r\n\r\nWindows:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-windows-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-windows-v1/2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n
Encoded SHA256:
c6e045fce97651336eeb400f0123541475b940e3aa38ce721f299585683da288\r\n
Decoded SHA256:
2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"C:\\\\path\\\\path.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"88bd71c0773d158ed1e6312075633ed85abc575e"}},"sourceBranch":"main","suggestedTargetBranches":["8.11","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164200","number":164200,"mergeCommit":{"message":"[Security
Solution] File paths for Blocklist Windows and Mac should be case
insensitive (#164200)\n\n## Summary\r\n\r\nThis fixes a bug where
Windows and Mac Blocklist file path entries\r\nshould be passed as case
insensitive. This is because Mac and Windows\r\nare caseless for most
use cases.\r\n\r\nBug ticket:
https://github.com/elastic/kibana/issues/158581\r\n\r\nHere is how it
will be displayed in the UI:\r\n<img width=\"1728\"
alt=\"image\"\r\nsrc=\"a3006397-f49e-4de0-818d-94e2de20dba3\">\r\n\r\nHere
are the breakdown of the artifacts after the
fix:\r\n\r\nLinux:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-linux-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-linux-v1/f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n
Encoded SHA256:
a907835be40af89b8b7aa23a6efc66c01ceaa5a19622edd378139319f3ca5fa0\r\n
Decoded SHA256:
f33e6890aeced00861c26a08121dd42d2d29ba08abfeb3c065d0447e32e18640\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_cased_any\",\r\n \"value\": [\r\n
\"/opt/bin/bin.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\nMac:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-macos-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-macos-v1/b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n
Encoded SHA256:
4f3e80d688f5cae4bf6a88b0704e37909f9fa4f47fe8325b7b154cddd46a2db9\r\n
Decoded SHA256:
b28e7978da4314ebc2c94770e0638fc4b2270f9dc17a11d6d32b8634b1fbec0f\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"/opt/exe.exe\"\r\n ]\r\n }\r\n ]\r\n
}\r\n```\r\n\r\nWindows:\r\n```\r\n-------------------------------------------------------------------\r\nPolicy:
Protect\r\nManifest: 1.0.6 | v1\r\nArtifact:
endpoint-blocklist-windows-v1\r\n Relative URL:
/api/fleet/artifacts/endpoint-blocklist-windows-v1/2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n
Encoded SHA256:
c6e045fce97651336eeb400f0123541475b940e3aa38ce721f299585683da288\r\n
Decoded SHA256:
2a6fcc67c696ad4e29d91f8b685bff46977198cd34b9a61e8003d55b78dff6ac\r\n-------------------------------------------------------------------\r\n\r\n{\r\n
\"entries\": [\r\n {\r\n \"type\": \"simple\",\r\n \"entries\": [\r\n
{\r\n \"field\": \"file.path\",\r\n \"operator\": \"included\",\r\n
\"type\": \"exact_caseless_any\",\r\n \"value\": [\r\n
\"C:\\\\path\\\\path.exe\"\r\n ]\r\n }\r\n ]\r\n }\r\n
]\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"88bd71c0773d158ed1e6312075633ed85abc575e"}},{"branch":"8.11","label":"v8.11.0","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: Kevin Logan <56395104+kevinlog@users.noreply.github.com>
Co-authored-by: Kevin Logan <kevin.logan@elastic.co>
2023-08-22 11:27:57 -07:00
Wafaa Nasr
fd35b9a928
[8.9] [Security Solution] [Detection Engine] Fix rule_exception cypress test flakiness (#161751) (#163688)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Detection Engine] Fix `rule_exception` cypress
test flakiness (#161751)](https://github.com/elastic/kibana/pull/161751)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2023-08-01T11:28:46Z","message":"[Security
Solution] [Detection Engine] Fix `rule_exception` cypress test flakiness
(#161751)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/159341 \r\n\r\n**Steps to
insure the flakiness** \r\n\r\n- Run the test through Flaky test runner
by modifying the\r\n`x-pack/plugins/security_solution/package.json` to
only run the\r\n`Rule_exceptions` as the following
=>\r\n`./cypress/e2e/exceptions/**/rule_exception.cy.ts`\r\n- Run the
test locally multiple times by wrapping the test suite by \r\n
`Cypress._.times(50, () => {});`\r\n\r\n**Failing steps**\r\n\r\n- The
test only failed in the step mentioned when executed through
the\r\nFlaky test runner.\r\n\r\n```\r\n 1) Rule Exceptions workflows
from Alert\r\n --\r\n | Should create a Rule exception item from the
alert actions overflow menu and close all matching alerts:\r\n |
AssertionError: Timed out retrying after 150000ms: Expected to find
element: `[data-test-subj=\"alertsStateTableEmptyState\"]`, but never
found it.\r\n```\r\n\r\n- By executing it locally multiple times, the
test failed at different\r\nsteps on each occasion.\r\n \r\n-
Immediately after creating an Exception with the Closing all
matching\r\nalerts option, the Alert table was not found empty,
indicating
a\r\nfailure.\r\n\r\n![image](492aa552-f721-493b-b0b7-fa3e91dc4e63)\r\n\r\n-
After removing the exception, the expected number of alerts was
not\r\nfound in the Alerts table, resulting in a
failure.\r\n\r\n![image](c291d630-8775-4a5b-9a6b-feb30a169757)\r\n\r\n-
Unrelated to this test, but concerning exceptions, the
failure\r\noccurred when attempting to click on \"Submit exception\" due
to an error\r\ntoast obstructing the button, similar to the 2nd
screenshot
provided\r\nbelow.\r\n\r\n![image](758cbb3e-9b95-439a-a5d1-49de8d84518e)\r\n\r\n**Steps
to mitigate test flakiness:**\r\n\r\n- **Splitting Test Cases:** The
rule_exceptions test currently covers\r\nmultiple areas using different
Rule types. To improve stability, we\r\nshould divide it into separate
test files. For example,\r\n`closing_all_matching_alerts.cy.ts`
and\r\n`auto_populate_with_alert_data.cy.ts`. Additionally, we should
ensure\r\nthat each test file cleans up any previous data to maintain
test\r\nisolation.\r\n\r\n- **Handling Async Calls:** Test flakiness can
occur when Cypress\r\nexecutes faster than async calls, leading to
errors when alerts don't\r\nmove to the closed tab in time. To address
this, we should avoid\r\nimmediate validation after creating an
exception. Instead, refresh the\r\n`Alerts table` to allow time for the
alerts to be moved to the\r\nappropriate tab before asserting the
conditions.\r\n\r\n For example ` waitForAlerts();` method\r\n\r\n-
**Avoiding Specific Alert Counts:** Relying on a specific number
of\r\ngenerated or closed alerts for validation is not a robust
approach.\r\nDuring test execution, the Rule might generate more alerts
than\r\nexpected, leading to test failures. To overcome this, we should
focus on\r\nvalidating the expected behavior rather than a fixed alert
count.\r\n \r\n For example\r\n ```\r\n
goToClosedAlertsOnRuleDetailsPage(); \r\n
cy.get(ALERTS_COUNT).should('exist');\r\n ```\r\n\r\n- In the test, when
utilizing `cy.task('esArchiverLoad',\r\n'exceptions');`, it can be
beneficial to check if the exception list is\r\nnot present in the
environment by calling `cy.task('esArchiverUnload',\r\n'exceptions');`
beforehand. This cleanup step ensures that any existing\r\nexception
list is removed, mitigating the occurrence of the following\r\nerror:
`resource_already_exists_exception:
index\r\n[.lists-default-000001/U_3_TShzRY-WZD_XqhSBnw] already exists
(400).`\r\n\r\n- It does not provide a value at the end of
the\r\n`closing_all_matching_alerts.cy.ts` test to verify if alerts
are\r\ngenerated again after the `Exception` that closes all matching
alerts is\r\ndeleted because the test already begins with the rule
generating alerts\r\nuntil the exception is created. Therefore, this
part has been excluded.\r\n\r\nBy following these steps for the test,
running the new files multiple\r\ntimes locally proved to be
beneficial:\r\n\r\n\r\n![image](8a0250a0-274f-442b-b94c-86e4c815afd1)\r\n
successfully
\r\n\r\n![image](4e9562f3-506e-4f13-ab1f-c084d2613eb8)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8f8c51a2d6c960007a9dc5f8fb4abd9fad7ec5aa","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":161751,"url":"https://github.com/elastic/kibana/pull/161751","mergeCommit":{"message":"[Security
Solution] [Detection Engine] Fix `rule_exception` cypress test flakiness
(#161751)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/159341 \r\n\r\n**Steps to
insure the flakiness** \r\n\r\n- Run the test through Flaky test runner
by modifying the\r\n`x-pack/plugins/security_solution/package.json` to
only run the\r\n`Rule_exceptions` as the following
=>\r\n`./cypress/e2e/exceptions/**/rule_exception.cy.ts`\r\n- Run the
test locally multiple times by wrapping the test suite by \r\n
`Cypress._.times(50, () => {});`\r\n\r\n**Failing steps**\r\n\r\n- The
test only failed in the step mentioned when executed through
the\r\nFlaky test runner.\r\n\r\n```\r\n 1) Rule Exceptions workflows
from Alert\r\n --\r\n | Should create a Rule exception item from the
alert actions overflow menu and close all matching alerts:\r\n |
AssertionError: Timed out retrying after 150000ms: Expected to find
element: `[data-test-subj=\"alertsStateTableEmptyState\"]`, but never
found it.\r\n```\r\n\r\n- By executing it locally multiple times, the
test failed at different\r\nsteps on each occasion.\r\n \r\n-
Immediately after creating an Exception with the Closing all
matching\r\nalerts option, the Alert table was not found empty,
indicating
a\r\nfailure.\r\n\r\n![image](492aa552-f721-493b-b0b7-fa3e91dc4e63)\r\n\r\n-
After removing the exception, the expected number of alerts was
not\r\nfound in the Alerts table, resulting in a
failure.\r\n\r\n![image](c291d630-8775-4a5b-9a6b-feb30a169757)\r\n\r\n-
Unrelated to this test, but concerning exceptions, the
failure\r\noccurred when attempting to click on \"Submit exception\" due
to an error\r\ntoast obstructing the button, similar to the 2nd
screenshot
provided\r\nbelow.\r\n\r\n![image](758cbb3e-9b95-439a-a5d1-49de8d84518e)\r\n\r\n**Steps
to mitigate test flakiness:**\r\n\r\n- **Splitting Test Cases:** The
rule_exceptions test currently covers\r\nmultiple areas using different
Rule types. To improve stability, we\r\nshould divide it into separate
test files. For example,\r\n`closing_all_matching_alerts.cy.ts`
and\r\n`auto_populate_with_alert_data.cy.ts`. Additionally, we should
ensure\r\nthat each test file cleans up any previous data to maintain
test\r\nisolation.\r\n\r\n- **Handling Async Calls:** Test flakiness can
occur when Cypress\r\nexecutes faster than async calls, leading to
errors when alerts don't\r\nmove to the closed tab in time. To address
this, we should avoid\r\nimmediate validation after creating an
exception. Instead, refresh the\r\n`Alerts table` to allow time for the
alerts to be moved to the\r\nappropriate tab before asserting the
conditions.\r\n\r\n For example ` waitForAlerts();` method\r\n\r\n-
**Avoiding Specific Alert Counts:** Relying on a specific number
of\r\ngenerated or closed alerts for validation is not a robust
approach.\r\nDuring test execution, the Rule might generate more alerts
than\r\nexpected, leading to test failures. To overcome this, we should
focus on\r\nvalidating the expected behavior rather than a fixed alert
count.\r\n \r\n For example\r\n ```\r\n
goToClosedAlertsOnRuleDetailsPage(); \r\n
cy.get(ALERTS_COUNT).should('exist');\r\n ```\r\n\r\n- In the test, when
utilizing `cy.task('esArchiverLoad',\r\n'exceptions');`, it can be
beneficial to check if the exception list is\r\nnot present in the
environment by calling `cy.task('esArchiverUnload',\r\n'exceptions');`
beforehand. This cleanup step ensures that any existing\r\nexception
list is removed, mitigating the occurrence of the following\r\nerror:
`resource_already_exists_exception:
index\r\n[.lists-default-000001/U_3_TShzRY-WZD_XqhSBnw] already exists
(400).`\r\n\r\n- It does not provide a value at the end of
the\r\n`closing_all_matching_alerts.cy.ts` test to verify if alerts
are\r\ngenerated again after the `Exception` that closes all matching
alerts is\r\ndeleted because the test already begins with the rule
generating alerts\r\nuntil the exception is created. Therefore, this
part has been excluded.\r\n\r\nBy following these steps for the test,
running the new files multiple\r\ntimes locally proved to be
beneficial:\r\n\r\n\r\n![image](8a0250a0-274f-442b-b94c-86e4c815afd1)\r\n
successfully
\r\n\r\n![image](4e9562f3-506e-4f13-ab1f-c084d2613eb8)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8f8c51a2d6c960007a9dc5f8fb4abd9fad7ec5aa"}},"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/161751","number":161751,"mergeCommit":{"message":"[Security
Solution] [Detection Engine] Fix `rule_exception` cypress test flakiness
(#161751)\n\n## Summary\r\n\r\n- Fixes
https://github.com/elastic/kibana/issues/159341 \r\n\r\n**Steps to
insure the flakiness** \r\n\r\n- Run the test through Flaky test runner
by modifying the\r\n`x-pack/plugins/security_solution/package.json` to
only run the\r\n`Rule_exceptions` as the following
=>\r\n`./cypress/e2e/exceptions/**/rule_exception.cy.ts`\r\n- Run the
test locally multiple times by wrapping the test suite by \r\n
`Cypress._.times(50, () => {});`\r\n\r\n**Failing steps**\r\n\r\n- The
test only failed in the step mentioned when executed through
the\r\nFlaky test runner.\r\n\r\n```\r\n 1) Rule Exceptions workflows
from Alert\r\n --\r\n | Should create a Rule exception item from the
alert actions overflow menu and close all matching alerts:\r\n |
AssertionError: Timed out retrying after 150000ms: Expected to find
element: `[data-test-subj=\"alertsStateTableEmptyState\"]`, but never
found it.\r\n```\r\n\r\n- By executing it locally multiple times, the
test failed at different\r\nsteps on each occasion.\r\n \r\n-
Immediately after creating an Exception with the Closing all
matching\r\nalerts option, the Alert table was not found empty,
indicating
a\r\nfailure.\r\n\r\n![image](492aa552-f721-493b-b0b7-fa3e91dc4e63)\r\n\r\n-
After removing the exception, the expected number of alerts was
not\r\nfound in the Alerts table, resulting in a
failure.\r\n\r\n![image](c291d630-8775-4a5b-9a6b-feb30a169757)\r\n\r\n-
Unrelated to this test, but concerning exceptions, the
failure\r\noccurred when attempting to click on \"Submit exception\" due
to an error\r\ntoast obstructing the button, similar to the 2nd
screenshot
provided\r\nbelow.\r\n\r\n![image](758cbb3e-9b95-439a-a5d1-49de8d84518e)\r\n\r\n**Steps
to mitigate test flakiness:**\r\n\r\n- **Splitting Test Cases:** The
rule_exceptions test currently covers\r\nmultiple areas using different
Rule types. To improve stability, we\r\nshould divide it into separate
test files. For example,\r\n`closing_all_matching_alerts.cy.ts`
and\r\n`auto_populate_with_alert_data.cy.ts`. Additionally, we should
ensure\r\nthat each test file cleans up any previous data to maintain
test\r\nisolation.\r\n\r\n- **Handling Async Calls:** Test flakiness can
occur when Cypress\r\nexecutes faster than async calls, leading to
errors when alerts don't\r\nmove to the closed tab in time. To address
this, we should avoid\r\nimmediate validation after creating an
exception. Instead, refresh the\r\n`Alerts table` to allow time for the
alerts to be moved to the\r\nappropriate tab before asserting the
conditions.\r\n\r\n For example ` waitForAlerts();` method\r\n\r\n-
**Avoiding Specific Alert Counts:** Relying on a specific number
of\r\ngenerated or closed alerts for validation is not a robust
approach.\r\nDuring test execution, the Rule might generate more alerts
than\r\nexpected, leading to test failures. To overcome this, we should
focus on\r\nvalidating the expected behavior rather than a fixed alert
count.\r\n \r\n For example\r\n ```\r\n
goToClosedAlertsOnRuleDetailsPage(); \r\n
cy.get(ALERTS_COUNT).should('exist');\r\n ```\r\n\r\n- In the test, when
utilizing `cy.task('esArchiverLoad',\r\n'exceptions');`, it can be
beneficial to check if the exception list is\r\nnot present in the
environment by calling `cy.task('esArchiverUnload',\r\n'exceptions');`
beforehand. This cleanup step ensures that any existing\r\nexception
list is removed, mitigating the occurrence of the following\r\nerror:
`resource_already_exists_exception:
index\r\n[.lists-default-000001/U_3_TShzRY-WZD_XqhSBnw] already exists
(400).`\r\n\r\n- It does not provide a value at the end of
the\r\n`closing_all_matching_alerts.cy.ts` test to verify if alerts
are\r\ngenerated again after the `Exception` that closes all matching
alerts is\r\ndeleted because the test already begins with the rule
generating alerts\r\nuntil the exception is created. Therefore, this
part has been excluded.\r\n\r\nBy following these steps for the test,
running the new files multiple\r\ntimes locally proved to be
beneficial:\r\n\r\n\r\n![image](8a0250a0-274f-442b-b94c-86e4c815afd1)\r\n
successfully
\r\n\r\n![image](4e9562f3-506e-4f13-ab1f-c084d2613eb8)\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"8f8c51a2d6c960007a9dc5f8fb4abd9fad7ec5aa"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-08-22 08:41:56 -07:00
Kibana Machine
072be8c23f
[8.9] [ML] Fix anomaly detection module manifest queries for kibana sample data sets (#164332) (#164458)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[ML] Fix anomaly detection module manifest queries for kibana sample
data sets (#164332)](https://github.com/elastic/kibana/pull/164332)

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

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

<!--BACKPORT [{"author":{"name":"James
Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2023-08-22T13:39:58Z","message":"[ML]
Fix anomaly detection module manifest queries for kibana sample data
sets (#164332)\n\nFollow up to
https://github.com/elastic/kibana/pull/119635\r\nAll modules which
contain a query in their manifest file should have a\r\nfilter to avoid
querying cold and frozen tiers.\r\nThe original PR did not include the
sample data sets as it was assumed\r\nit was not necessary due to these
data sets never being added to cold or\r\nfrozen tiers.\r\nHowever it
was overlooked that these queries will be run on any index\r\npattern
passed to the `/internal/ml/modules/recognize` endpoint and so\r\nhas
the potential to negatively impact the speed of all calls to
this\r\nendpoint, especially if the index pattern contains multiple
indices
and\r\nwildcards.","sha":"cd219942d12083897d7c56723f83da2a2f3c2586","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","v8.10.0","v8.11.0","v8.9.2"],"number":164332,"url":"https://github.com/elastic/kibana/pull/164332","mergeCommit":{"message":"[ML]
Fix anomaly detection module manifest queries for kibana sample data
sets (#164332)\n\nFollow up to
https://github.com/elastic/kibana/pull/119635\r\nAll modules which
contain a query in their manifest file should have a\r\nfilter to avoid
querying cold and frozen tiers.\r\nThe original PR did not include the
sample data sets as it was assumed\r\nit was not necessary due to these
data sets never being added to cold or\r\nfrozen tiers.\r\nHowever it
was overlooked that these queries will be run on any index\r\npattern
passed to the `/internal/ml/modules/recognize` endpoint and so\r\nhas
the potential to negatively impact the speed of all calls to
this\r\nendpoint, especially if the index pattern contains multiple
indices
and\r\nwildcards.","sha":"cd219942d12083897d7c56723f83da2a2f3c2586"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164332","number":164332,"mergeCommit":{"message":"[ML]
Fix anomaly detection module manifest queries for kibana sample data
sets (#164332)\n\nFollow up to
https://github.com/elastic/kibana/pull/119635\r\nAll modules which
contain a query in their manifest file should have a\r\nfilter to avoid
querying cold and frozen tiers.\r\nThe original PR did not include the
sample data sets as it was assumed\r\nit was not necessary due to these
data sets never being added to cold or\r\nfrozen tiers.\r\nHowever it
was overlooked that these queries will be run on any index\r\npattern
passed to the `/internal/ml/modules/recognize` endpoint and so\r\nhas
the potential to negatively impact the speed of all calls to
this\r\nendpoint, especially if the index pattern contains multiple
indices
and\r\nwildcards.","sha":"cd219942d12083897d7c56723f83da2a2f3c2586"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: James Gowdy <jgowdy@elastic.co>
2023-08-22 08:08:11 -07:00
Ievgen Sorokopud
e059c8434a
[8.9] [Security Solution] formatAlertForNotificationActions fails to merge dot and object notations correctly (#164075) (#164267)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] formatAlertForNotificationActions fails to merge
dot and object notations correctly
(#164075)](https://github.com/elastic/kibana/pull/164075)

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

### 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-08-17T08:39:24Z","message":"[Security
Solution] formatAlertForNotificationActions fails to merge dot and
object notations correctly (#164075)\n\n## Summary\r\n\r\nOriginal
ticket: #163844\r\n\r\nThese changes fix the issue with the incorrect
`expandDottedObject`\r\nfunctionality which instead of merging objects
would replace with the\r\nlatest version of
it.","sha":"a50b33032359410e7ee93e65a6cff58e00205856","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","ci:cloud-deploy","Team:Detection
Engine","v8.10.0","v8.11.0","v8.9.2"],"number":164075,"url":"https://github.com/elastic/kibana/pull/164075","mergeCommit":{"message":"[Security
Solution] formatAlertForNotificationActions fails to merge dot and
object notations correctly (#164075)\n\n## Summary\r\n\r\nOriginal
ticket: #163844\r\n\r\nThese changes fix the issue with the incorrect
`expandDottedObject`\r\nfunctionality which instead of merging objects
would replace with the\r\nlatest version of
it.","sha":"a50b33032359410e7ee93e65a6cff58e00205856"}},"sourceBranch":"main","suggestedTargetBranches":["8.11","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164075","number":164075,"mergeCommit":{"message":"[Security
Solution] formatAlertForNotificationActions fails to merge dot and
object notations correctly (#164075)\n\n## Summary\r\n\r\nOriginal
ticket: #163844\r\n\r\nThese changes fix the issue with the incorrect
`expandDottedObject`\r\nfunctionality which instead of merging objects
would replace with the\r\nlatest version of
it.","sha":"a50b33032359410e7ee93e65a6cff58e00205856"}},{"branch":"8.11","label":"v8.11.0","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"},{"url":"https://github.com/elastic/kibana/pull/164140","number":164140,"branch":"8.10","state":"MERGED","mergeCommit":{"sha":"7d8b808d8acf6d8f8824cafea649f23556347edf","message":"[8.10]
[Security Solution] formatAlertForNotificationActions fails to merge dot
and object notations correctly (#164075) (#164140)\n\n# Backport\n\nThis
will backport the following commits from `main` to `8.10`:\n- [[Security
Solution] formatAlertForNotificationActions fails to merge\ndot and
object notations
correctly\n(#164075)](https://github.com/elastic/kibana/pull/164075)\n\n<!---
Backport version: 8.9.7 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Ievgen\nSorokopud\",\"email\":\"ievgen.sorokopud@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2023-08-17T08:39:24Z\",\"message\":\"[Security\nSolution]
formatAlertForNotificationActions fails to merge dot and\nobject
notations correctly (#164075)\\n\\n##
Summary\\r\\n\\r\\nOriginal\nticket: #163844\\r\\n\\r\\nThese changes
fix the issue with the
incorrect\n`expandDottedObject`\\r\\nfunctionality which instead of
merging objects\nwould replace with the\\r\\nlatest version
of\nit.\",\"sha\":\"a50b33032359410e7ee93e65a6cff58e00205856\",\"branchLabelMapping\":{\"^v8.10.0$\":\"main\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"Team:\nSecuritySolution\",\"ci:cloud-deploy\",\"Team:Detection\nEngine\",\"v8.10.0\",\"v8.11.0\"],\"number\":164075,\"url\":\"https://github.com/elastic/kibana/pull/164075\",\"mergeCommit\":{\"message\":\"[Security\nSolution]
formatAlertForNotificationActions fails to merge dot and\nobject
notations correctly (#164075)\\n\\n##
Summary\\r\\n\\r\\nOriginal\nticket: #163844\\r\\n\\r\\nThese changes
fix the issue with the
incorrect\n`expandDottedObject`\\r\\nfunctionality which instead of
merging objects\nwould replace with the\\r\\nlatest version
of\nit.\",\"sha\":\"a50b33032359410e7ee93e65a6cff58e00205856\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.11\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v8.10.0\",\"labelRegex\":\"^v8.10.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/164075\",\"number\":164075,\"mergeCommit\":{\"message\":\"[Security\nSolution]
formatAlertForNotificationActions fails to merge dot and\nobject
notations correctly (#164075)\\n\\n##
Summary\\r\\n\\r\\nOriginal\nticket: #163844\\r\\n\\r\\nThese changes
fix the issue with the
incorrect\n`expandDottedObject`\\r\\nfunctionality which instead of
merging objects\nwould replace with the\\r\\nlatest version
of\nit.\",\"sha\":\"a50b33032359410e7ee93e65a6cff58e00205856\"}},{\"branch\":\"8.11\",\"label\":\"v8.11.0\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by:
Ievgen Sorokopud <ievgen.sorokopud@elastic.co>"}}]}] BACKPORT-->
2023-08-22 09:33:57 -04:00
Kibana Machine
499993f892
[8.9] [AO] Fix add_to_case functional test (#163155) (#164436)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[AO] Fix add_to_case functional test
(#163155)](https://github.com/elastic/kibana/pull/163155)

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

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

Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co>
2023-08-22 06:20:40 -07:00
Mike Côté
59b16e06dd
[8.9] Add warning for max alerts circuit breaker (#164217) (#164422)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Add warning for max alerts circuit breaker
(#164217)](https://github.com/elastic/kibana/pull/164217)

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

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

<!--BACKPORT [{"author":{"name":"Mike
Côté","email":"mikecote@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-22T11:01:29Z","message":"Add
warning for max alerts circuit breaker (#164217)\n\nIn this PR, I'm
adding a warning message to the docs for
the\r\n`xpack.alerting.rules.run.alerts.max` setting that indicates
the\r\nconsequences when setting a value higher than the default, while
also\r\nindicating it's not supported.\r\n\r\n<img width=\"862\"
alt=\"Screenshot 2023-08-21 at 5 03 52
PM\"\r\nsrc=\"46a7f5d6-f6d5-475a-ab93-edf256eb9141\">\r\n\r\ncc
@lcawl\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"327af6ca2e92ad57a99d18b06a0bf03e8f08b59b","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","backport:prev-minor","v8.11.0"],"number":164217,"url":"https://github.com/elastic/kibana/pull/164217","mergeCommit":{"message":"Add
warning for max alerts circuit breaker (#164217)\n\nIn this PR, I'm
adding a warning message to the docs for
the\r\n`xpack.alerting.rules.run.alerts.max` setting that indicates
the\r\nconsequences when setting a value higher than the default, while
also\r\nindicating it's not supported.\r\n\r\n<img width=\"862\"
alt=\"Screenshot 2023-08-21 at 5 03 52
PM\"\r\nsrc=\"46a7f5d6-f6d5-475a-ab93-edf256eb9141\">\r\n\r\ncc
@lcawl\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"327af6ca2e92ad57a99d18b06a0bf03e8f08b59b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164217","number":164217,"mergeCommit":{"message":"Add
warning for max alerts circuit breaker (#164217)\n\nIn this PR, I'm
adding a warning message to the docs for
the\r\n`xpack.alerting.rules.run.alerts.max` setting that indicates
the\r\nconsequences when setting a value higher than the default, while
also\r\nindicating it's not supported.\r\n\r\n<img width=\"862\"
alt=\"Screenshot 2023-08-21 at 5 03 52
PM\"\r\nsrc=\"46a7f5d6-f6d5-475a-ab93-edf256eb9141\">\r\n\r\ncc
@lcawl\r\n\r\n---------\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"327af6ca2e92ad57a99d18b06a0bf03e8f08b59b"}}]}]
BACKPORT-->
2023-08-22 09:04:02 -04:00
amyjtechwriter
9a6c2979f3
[DOCS] Fix accessibility language in 8.9 what's new page (#164298)
## Summary

Accessibility feedback added to [whats-new page for
8.9.](https://www.elastic.co/guide/en/kibana/8.9/whats-new.html)

Based on feedback from: #163938

---------

Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
2023-08-22 13:47:26 +01:00
Kibana Machine
843482c7ad
[8.9] Fleet - Turn some error messages in info (#164333) (#164430)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Fleet - Turn some error messages in info
(#164333)](https://github.com/elastic/kibana/pull/164333)

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

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

<!--BACKPORT [{"author":{"name":"Luca
Belluccini","email":"luca.belluccini@elastic.co"},"sourceCommit":{"committedDate":"2023-08-22T11:03:22Z","message":"Fleet
- Turn some error messages in info (#164333)\n\n##
Summary\r\n\r\nProposal to fix
https://github.com/elastic/kibana/issues/164270\r\n\r\n###
Checklist\r\n\r\n- [ ] Possibly evaluate the \"verbosity\" vs
\"troubleshoot-ability\"\r\n- [ ] Backport\r\n\r\nCo-authored-by: Julia
Bardi
<90178898+juliaElastic@users.noreply.github.com>","sha":"79f8dcd90ceaddd0a0f9cc32440a954ae12b5357","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.10.0","v8.11.0","v8.9.2"],"number":164333,"url":"https://github.com/elastic/kibana/pull/164333","mergeCommit":{"message":"Fleet
- Turn some error messages in info (#164333)\n\n##
Summary\r\n\r\nProposal to fix
https://github.com/elastic/kibana/issues/164270\r\n\r\n###
Checklist\r\n\r\n- [ ] Possibly evaluate the \"verbosity\" vs
\"troubleshoot-ability\"\r\n- [ ] Backport\r\n\r\nCo-authored-by: Julia
Bardi
<90178898+juliaElastic@users.noreply.github.com>","sha":"79f8dcd90ceaddd0a0f9cc32440a954ae12b5357"}},"sourceBranch":"main","suggestedTargetBranches":["8.10","8.9"],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164333","number":164333,"mergeCommit":{"message":"Fleet
- Turn some error messages in info (#164333)\n\n##
Summary\r\n\r\nProposal to fix
https://github.com/elastic/kibana/issues/164270\r\n\r\n###
Checklist\r\n\r\n- [ ] Possibly evaluate the \"verbosity\" vs
\"troubleshoot-ability\"\r\n- [ ] Backport\r\n\r\nCo-authored-by: Julia
Bardi
<90178898+juliaElastic@users.noreply.github.com>","sha":"79f8dcd90ceaddd0a0f9cc32440a954ae12b5357"}},{"branch":"8.9","label":"v8.9.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
2023-08-22 05:22:16 -07:00
Ievgen Sorokopud
653a0d73e8
[8.9] [Security Solution] [Detections] Fixes flakey exceptions read-only viewer cypress test (#164283) (#164352)
# Backport

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

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

### 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-08-21T18:40:14Z","message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#164283)\n\n## Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/162569\r\nFixes:
https://github.com/elastic/kibana/issues/164061\r\nFixes:
https://github.com/elastic/kibana/issues/164058\r\nFixes:
https://github.com/elastic/kibana/issues/163546\r\nFixes:
https://github.com/elastic/kibana/issues/162669\r\n\r\nWe tried to fix
the issue with this PR\r\nhttps://github.com/elastic/kibana/pull/162839
but test failed again.\r\n\r\nThis is another attempt to fix it using
the @jpdjere's approach where we\r\ndisable rule's table
refreshing\r\n(https://github.com/elastic/kibana/pull/163698).","sha":"4477f642e3297355ef676dcf485efb0cb49c4fcb","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Detection
Engine","v8.10.0","v8.11.0"],"number":164283,"url":"https://github.com/elastic/kibana/pull/164283","mergeCommit":{"message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#164283)\n\n## Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/162569\r\nFixes:
https://github.com/elastic/kibana/issues/164061\r\nFixes:
https://github.com/elastic/kibana/issues/164058\r\nFixes:
https://github.com/elastic/kibana/issues/163546\r\nFixes:
https://github.com/elastic/kibana/issues/162669\r\n\r\nWe tried to fix
the issue with this PR\r\nhttps://github.com/elastic/kibana/pull/162839
but test failed again.\r\n\r\nThis is another attempt to fix it using
the @jpdjere's approach where we\r\ndisable rule's table
refreshing\r\n(https://github.com/elastic/kibana/pull/163698).","sha":"4477f642e3297355ef676dcf485efb0cb49c4fcb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/164346","number":164346,"state":"MERGED","mergeCommit":{"sha":"bdbc3e7e0e7cf59397af3653ed2f8ba86bd3ea93","message":"[8.10]
[Security Solution] [Detections] Fixes flakey exceptions read-only
viewer cypress test (#164283) (#164346)\n\n# Backport\n\nThis will
backport the following commits from `main` to `8.10`:\n- [[Security
Solution] [Detections] Fixes flakey exceptions read-only\nviewer cypress
test\n(#164283)](https://github.com/elastic/kibana/pull/164283)\n\n<!---
Backport version: 8.9.7 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Ievgen\nSorokopud\",\"email\":\"ievgen.sorokopud@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2023-08-21T18:40:14Z\",\"message\":\"[Security\nSolution]
[Detections] Fixes flakey exceptions read-only viewer cypress\ntest
(#164283)\\n\\n##
Summary\\r\\n\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162569\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164061\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164058\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/163546\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162669\\r\\n\\r\\nWe
tried to fix\nthe issue with this
PR\\r\\nhttps://github.com/elastic/kibana/pull/162839\nbut test failed
again.\\r\\n\\r\\nThis is another attempt to fix it using\nthe
@jpdjere's approach where we\\r\\ndisable rule's
table\nrefreshing\\r\\n(https://github.com/elastic/kibana/pull/163698).\",\"sha\":\"4477f642e3297355ef676dcf485efb0cb49c4fcb\",\"branchLabelMapping\":{\"^v8.11.0$\":\"main\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:\nSecuritySolution\",\"Team:Detection\nEngine\",\"v8.10.0\",\"v8.11.0\"],\"number\":164283,\"url\":\"https://github.com/elastic/kibana/pull/164283\",\"mergeCommit\":{\"message\":\"[Security\nSolution]
[Detections] Fixes flakey exceptions read-only viewer cypress\ntest
(#164283)\\n\\n##
Summary\\r\\n\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162569\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164061\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164058\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/163546\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162669\\r\\n\\r\\nWe
tried to fix\nthe issue with this
PR\\r\\nhttps://github.com/elastic/kibana/pull/162839\nbut test failed
again.\\r\\n\\r\\nThis is another attempt to fix it using\nthe
@jpdjere's approach where we\\r\\ndisable rule's
table\nrefreshing\\r\\n(https://github.com/elastic/kibana/pull/163698).\",\"sha\":\"4477f642e3297355ef676dcf485efb0cb49c4fcb\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.10\"],\"targetPullRequestStates\":[{\"branch\":\"8.10\",\"label\":\"v8.10.0\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v8.11.0\",\"labelRegex\":\"^v8.11.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/164283\",\"number\":164283,\"mergeCommit\":{\"message\":\"[Security\nSolution]
[Detections] Fixes flakey exceptions read-only viewer cypress\ntest
(#164283)\\n\\n##
Summary\\r\\n\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162569\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164061\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/164058\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/163546\\r\\nFixes:\nhttps://github.com/elastic/kibana/issues/162669\\r\\n\\r\\nWe
tried to fix\nthe issue with this
PR\\r\\nhttps://github.com/elastic/kibana/pull/162839\nbut test failed
again.\\r\\n\\r\\nThis is another attempt to fix it using\nthe
@jpdjere's approach where we\\r\\ndisable rule's
table\nrefreshing\\r\\n(https://github.com/elastic/kibana/pull/163698).\",\"sha\":\"4477f642e3297355ef676dcf485efb0cb49c4fcb\"}}]}]\nBACKPORT-->\n\nCo-authored-by:
Ievgen Sorokopud
<ievgen.sorokopud@elastic.co>"}},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164283","number":164283,"mergeCommit":{"message":"[Security
Solution] [Detections] Fixes flakey exceptions read-only viewer cypress
test (#164283)\n\n## Summary\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/162569\r\nFixes:
https://github.com/elastic/kibana/issues/164061\r\nFixes:
https://github.com/elastic/kibana/issues/164058\r\nFixes:
https://github.com/elastic/kibana/issues/163546\r\nFixes:
https://github.com/elastic/kibana/issues/162669\r\n\r\nWe tried to fix
the issue with this PR\r\nhttps://github.com/elastic/kibana/pull/162839
but test failed again.\r\n\r\nThis is another attempt to fix it using
the @jpdjere's approach where we\r\ndisable rule's table
refreshing\r\n(https://github.com/elastic/kibana/pull/163698).","sha":"4477f642e3297355ef676dcf485efb0cb49c4fcb"}}]}]
BACKPORT-->
2023-08-22 10:28:20 +02:00
Lisa Cawley
a2f5eb720c
[8.9] [OAS] Remove redundant connector properties (#163987) (#164360)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[OAS] Remove redundant connector properties
(#163987)](https://github.com/elastic/kibana/pull/163987)

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

### 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-21T16:29:08Z","message":"[OAS]
Remove redundant connector properties
(#163987)","sha":"c1d2834f1aa675f2682793d83ac9ad07c3854990","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorTypes","backport:prev-minor","v8.10.0","v8.11.0"],"number":163987,"url":"https://github.com/elastic/kibana/pull/163987","mergeCommit":{"message":"[OAS]
Remove redundant connector properties
(#163987)","sha":"c1d2834f1aa675f2682793d83ac9ad07c3854990"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/164338","number":164338,"state":"MERGED","mergeCommit":{"sha":"df9b17fb7ce2b90db9d954f17432a8906faee3b7","message":"[8.10]
[OAS] Remove redundant connector properties (#163987) (#164338)\n\n#
Backport\n\nThis will backport the following commits from `main` to
`8.10`:\n- [[OAS] Remove redundant connector
properties\n(#163987)](https://github.com/elastic/kibana/pull/163987)\n\n<!---
Backport version: 8.9.7 -->\n\n### Questions ?\nPlease refer to the
[Backport
tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT
[{\"author\":{\"name\":\"Lisa\nCawley\",\"email\":\"lcawley@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2023-08-21T16:29:08Z\",\"message\":\"[OAS]\nRemove
redundant connector
properties\n(#163987)\",\"sha\":\"c1d2834f1aa675f2682793d83ac9ad07c3854990\",\"branchLabelMapping\":{\"^v8.11.0$\":\"main\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:ResponseOps\",\"docs\",\"Feature:Actions/ConnectorTypes\",\"backport:prev-minor\",\"v8.10.0\",\"v8.11.0\"],\"number\":163987,\"url\":\"https://github.com/elastic/kibana/pull/163987\",\"mergeCommit\":{\"message\":\"[OAS]\nRemove
redundant connector
properties\n(#163987)\",\"sha\":\"c1d2834f1aa675f2682793d83ac9ad07c3854990\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.10\"],\"targetPullRequestStates\":[{\"branch\":\"8.10\",\"label\":\"v8.10.0\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v8.11.0\",\"labelRegex\":\"^v8.11.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/163987\",\"number\":163987,\"mergeCommit\":{\"message\":\"[OAS]\nRemove
redundant connector
properties\n(#163987)\",\"sha\":\"c1d2834f1aa675f2682793d83ac9ad07c3854990\"}}]}]\nBACKPORT-->\n\nCo-authored-by:
Lisa Cawley
<lcawley@elastic.co>"}},{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163987","number":163987,"mergeCommit":{"message":"[OAS]
Remove redundant connector properties
(#163987)","sha":"c1d2834f1aa675f2682793d83ac9ad07c3854990"}}]}]
BACKPORT-->
2023-08-21 14:01:11 -07:00
Jatin Kathuria
bea10503e9
[8.9] [Security Solution][Fix] Event Summary columns is not visible in Event Rendered View of Alert Table (#162635) (#163561)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Fix] Event Summary columns is not visible in
Event Rendered View of Alert Table
(#162635)](https://github.com/elastic/kibana/pull/162635)

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

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

<!--BACKPORT [{"author":{"name":"Jatin
Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2023-08-03T10:56:25Z","message":"[Security
Solution][Fix] Event Summary columns is not visible in Event Rendered
View of Alert Table (#162635)\n\n## Summary\r\n\r\nHandles.
#162471\r\n\r\nThis PR fixes the stability of visibleColumns in the
alert Table. Below\r\nvideos shows the difference between before and
after the change.\r\n\r\n| Before | After
|\r\n|--|--|\r\n|<video\r\nsrc=\"06d8616b-9708-40ed-814f-5899d6158551\"\r\n/>
|
<video\r\nsrc=\"12c86e11-fccb-4b6f-88cf-1ba2bd96ea52\"\r\n/>
|\r\n\r\n\r\n## Existing issues.\r\n\r\n1. If you noticed in the after
video, there remains an existing issue\r\nwhich is the event rendered
view is coming without alternating color\r\nrows as shown in screenshot
below. (  Fixed in this PR )\r\n\r\n2. Additionally, this bug was also
found which also being separately\r\ntracked :
https://github.com/elastic/kibana/issues/162684\r\n\r\n\r\n\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fcfabcdcd10f1cba284dd6876edf8bc583dea1bc","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","Team:Threat
Hunting:Investigations","v8.9.0","v8.10.0"],"number":162635,"url":"https://github.com/elastic/kibana/pull/162635","mergeCommit":{"message":"[Security
Solution][Fix] Event Summary columns is not visible in Event Rendered
View of Alert Table (#162635)\n\n## Summary\r\n\r\nHandles.
#162471\r\n\r\nThis PR fixes the stability of visibleColumns in the
alert Table. Below\r\nvideos shows the difference between before and
after the change.\r\n\r\n| Before | After
|\r\n|--|--|\r\n|<video\r\nsrc=\"06d8616b-9708-40ed-814f-5899d6158551\"\r\n/>
|
<video\r\nsrc=\"12c86e11-fccb-4b6f-88cf-1ba2bd96ea52\"\r\n/>
|\r\n\r\n\r\n## Existing issues.\r\n\r\n1. If you noticed in the after
video, there remains an existing issue\r\nwhich is the event rendered
view is coming without alternating color\r\nrows as shown in screenshot
below. (  Fixed in this PR )\r\n\r\n2. Additionally, this bug was also
found which also being separately\r\ntracked :
https://github.com/elastic/kibana/issues/162684\r\n\r\n\r\n\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fcfabcdcd10f1cba284dd6876edf8bc583dea1bc"}},"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/162635","number":162635,"mergeCommit":{"message":"[Security
Solution][Fix] Event Summary columns is not visible in Event Rendered
View of Alert Table (#162635)\n\n## Summary\r\n\r\nHandles.
#162471\r\n\r\nThis PR fixes the stability of visibleColumns in the
alert Table. Below\r\nvideos shows the difference between before and
after the change.\r\n\r\n| Before | After
|\r\n|--|--|\r\n|<video\r\nsrc=\"06d8616b-9708-40ed-814f-5899d6158551\"\r\n/>
|
<video\r\nsrc=\"12c86e11-fccb-4b6f-88cf-1ba2bd96ea52\"\r\n/>
|\r\n\r\n\r\n## Existing issues.\r\n\r\n1. If you noticed in the after
video, there remains an existing issue\r\nwhich is the event rendered
view is coming without alternating color\r\nrows as shown in screenshot
below. (  Fixed in this PR )\r\n\r\n2. Additionally, this bug was also
found which also being separately\r\ntracked :
https://github.com/elastic/kibana/issues/162684\r\n\r\n\r\n\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fcfabcdcd10f1cba284dd6876edf8bc583dea1bc"}}]}]
BACKPORT-->
2023-08-21 12:53:37 -07:00
Kibana Machine
6f149e8764 skip failing test suite (#164334) 2023-08-21 12:54:38 -04:00
Kibana Machine
e680546dcd skip failing test suite (#164318) 2023-08-21 11:08:46 -04:00
Maxim Palenov
6a21870c4e
[8.9] [Security Solution] Unskip rules table auto-refresh Cypress tests (#163451) (#164062)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Unskip rules table auto-refresh Cypress tests
(#163451)](https://github.com/elastic/kibana/pull/163451)

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

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

<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2023-08-11T12:07:35Z","message":"[Security
Solution] Unskip rules table auto-refresh Cypress tests
(#163451)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/154694\r\n\r\n##
Summary\r\n\r\nThis PR unskips rules table auto-refresh tests.\r\n\r\n##
Details\r\n\r\nRules table auto-refresh Cypress tests were outdated so
it was hard to determine the original flakiness reason. To make it
working the following has been done\r\n\r\n- `mockGlobalClock()` moved
above `visit()` to mock the time before visiting the page. It didn't
look like working so the test had to wait for 60 seconds (our refresh
interval)\r\n- removed unnecessary waiting
`waitForRulesTableToBeLoaded()` as the test should work without it\r\n-
removed `setRowsPerPageTo(5)` as the test doesn't look related to the
page size\r\n- `AutoRefreshButtonComponent ` was refactored in attempt
to fix popover closing related flakiness but it doesn't seem to help but
the refactoring looks improving readability so leaving as a part of this
PR\r\n- auto-refresh popover's behavior has been changed. The trigger
button gets disabled if there is a rule selected. Clicking the disabled
button won't make the auto-refresh popover to appear so this part was
changed.\r\n\r\n### Encountered issues\r\n\r\n- `EuiPopover` should
close by clicking the trigger button, clicking outside or pressing `Esc`
button. The latter two cause flakiness for some reason. I spent quite
some time to investigate the reason but without success. It looks like
there is a race condition related to
[EuiFocusTrap](https://github.com/elastic/eui/blob/main/src/components/focus_trap/focus_trap.tsx)
but it doesn't look to be an issue outside Cypress.\r\n-
`waitForRulesTableToBeLoaded()` basically does nothing after changes in
the rules table. Looking at tis contents\r\n\r\n```ts\r\nexport const
waitForRulesTableToBeLoaded = () => {\r\n // Wait up to 5 minutes for
the rules to load as in CI containers this can be very slow\r\n
cy.get(RULES_TABLE_INITIAL_LOADING_INDICATOR, { timeout: 300000
}).should('not.exist');\r\n};\r\n```\r\n\r\nreveals that
`RULES_TABLE_INITIAL_LOADING_INDICATOR` defined as
`[data-test-subj=\"initialLoadingPanelAllRulesTable\"]` doesn't exist
anymore in our codebase so this function instantly returns. The selector
will be fixed in a separate PR.\r\n\r\n- invoking `mockGlobalClock()`
during the test leads to appearing a lot of `Executing a cancelled
action` error messages.\r\n\r\n\r\n### Flaky test runner\r\n\r\n[50 runs
succeeded](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2842)","sha":"589ef228fb9c2525a49d6abc5db64eb98b2c381e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","skipped-test","release_note:skip","impact:high","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection Rule
Management","backport:prev-minor","v8.10.0"],"number":163451,"url":"https://github.com/elastic/kibana/pull/163451","mergeCommit":{"message":"[Security
Solution] Unskip rules table auto-refresh Cypress tests
(#163451)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/154694\r\n\r\n##
Summary\r\n\r\nThis PR unskips rules table auto-refresh tests.\r\n\r\n##
Details\r\n\r\nRules table auto-refresh Cypress tests were outdated so
it was hard to determine the original flakiness reason. To make it
working the following has been done\r\n\r\n- `mockGlobalClock()` moved
above `visit()` to mock the time before visiting the page. It didn't
look like working so the test had to wait for 60 seconds (our refresh
interval)\r\n- removed unnecessary waiting
`waitForRulesTableToBeLoaded()` as the test should work without it\r\n-
removed `setRowsPerPageTo(5)` as the test doesn't look related to the
page size\r\n- `AutoRefreshButtonComponent ` was refactored in attempt
to fix popover closing related flakiness but it doesn't seem to help but
the refactoring looks improving readability so leaving as a part of this
PR\r\n- auto-refresh popover's behavior has been changed. The trigger
button gets disabled if there is a rule selected. Clicking the disabled
button won't make the auto-refresh popover to appear so this part was
changed.\r\n\r\n### Encountered issues\r\n\r\n- `EuiPopover` should
close by clicking the trigger button, clicking outside or pressing `Esc`
button. The latter two cause flakiness for some reason. I spent quite
some time to investigate the reason but without success. It looks like
there is a race condition related to
[EuiFocusTrap](https://github.com/elastic/eui/blob/main/src/components/focus_trap/focus_trap.tsx)
but it doesn't look to be an issue outside Cypress.\r\n-
`waitForRulesTableToBeLoaded()` basically does nothing after changes in
the rules table. Looking at tis contents\r\n\r\n```ts\r\nexport const
waitForRulesTableToBeLoaded = () => {\r\n // Wait up to 5 minutes for
the rules to load as in CI containers this can be very slow\r\n
cy.get(RULES_TABLE_INITIAL_LOADING_INDICATOR, { timeout: 300000
}).should('not.exist');\r\n};\r\n```\r\n\r\nreveals that
`RULES_TABLE_INITIAL_LOADING_INDICATOR` defined as
`[data-test-subj=\"initialLoadingPanelAllRulesTable\"]` doesn't exist
anymore in our codebase so this function instantly returns. The selector
will be fixed in a separate PR.\r\n\r\n- invoking `mockGlobalClock()`
during the test leads to appearing a lot of `Executing a cancelled
action` error messages.\r\n\r\n\r\n### Flaky test runner\r\n\r\n[50 runs
succeeded](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2842)","sha":"589ef228fb9c2525a49d6abc5db64eb98b2c381e"}},"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/163451","number":163451,"mergeCommit":{"message":"[Security
Solution] Unskip rules table auto-refresh Cypress tests
(#163451)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/154694\r\n\r\n##
Summary\r\n\r\nThis PR unskips rules table auto-refresh tests.\r\n\r\n##
Details\r\n\r\nRules table auto-refresh Cypress tests were outdated so
it was hard to determine the original flakiness reason. To make it
working the following has been done\r\n\r\n- `mockGlobalClock()` moved
above `visit()` to mock the time before visiting the page. It didn't
look like working so the test had to wait for 60 seconds (our refresh
interval)\r\n- removed unnecessary waiting
`waitForRulesTableToBeLoaded()` as the test should work without it\r\n-
removed `setRowsPerPageTo(5)` as the test doesn't look related to the
page size\r\n- `AutoRefreshButtonComponent ` was refactored in attempt
to fix popover closing related flakiness but it doesn't seem to help but
the refactoring looks improving readability so leaving as a part of this
PR\r\n- auto-refresh popover's behavior has been changed. The trigger
button gets disabled if there is a rule selected. Clicking the disabled
button won't make the auto-refresh popover to appear so this part was
changed.\r\n\r\n### Encountered issues\r\n\r\n- `EuiPopover` should
close by clicking the trigger button, clicking outside or pressing `Esc`
button. The latter two cause flakiness for some reason. I spent quite
some time to investigate the reason but without success. It looks like
there is a race condition related to
[EuiFocusTrap](https://github.com/elastic/eui/blob/main/src/components/focus_trap/focus_trap.tsx)
but it doesn't look to be an issue outside Cypress.\r\n-
`waitForRulesTableToBeLoaded()` basically does nothing after changes in
the rules table. Looking at tis contents\r\n\r\n```ts\r\nexport const
waitForRulesTableToBeLoaded = () => {\r\n // Wait up to 5 minutes for
the rules to load as in CI containers this can be very slow\r\n
cy.get(RULES_TABLE_INITIAL_LOADING_INDICATOR, { timeout: 300000
}).should('not.exist');\r\n};\r\n```\r\n\r\nreveals that
`RULES_TABLE_INITIAL_LOADING_INDICATOR` defined as
`[data-test-subj=\"initialLoadingPanelAllRulesTable\"]` doesn't exist
anymore in our codebase so this function instantly returns. The selector
will be fixed in a separate PR.\r\n\r\n- invoking `mockGlobalClock()`
during the test leads to appearing a lot of `Executing a cancelled
action` error messages.\r\n\r\n\r\n### Flaky test runner\r\n\r\n[50 runs
succeeded](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2842)","sha":"589ef228fb9c2525a49d6abc5db64eb98b2c381e"}}]}]
BACKPORT-->

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-08-21 17:08:33 +02:00
Kibana Machine
ad228feeb1
[8.9] [DOCS] Removes 8.9.1 coming tag. (#164302) (#164311)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Removes 8.9.1 coming tag.
(#164302)](https://github.com/elastic/kibana/pull/164302)

<!--- 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-21T13:24:48Z","message":"[DOCS]
Removes 8.9.1 coming tag. (#164302)\n\nRemoves `coming` tag from the
8.9.1 release
notes.","sha":"90b6e4dbe01219d5af51a93943338043bfdd773a","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v8.9.0","v8.10.0","v8.9.1","v8.11.0"],"number":164302,"url":"https://github.com/elastic/kibana/pull/164302","mergeCommit":{"message":"[DOCS]
Removes 8.9.1 coming tag. (#164302)\n\nRemoves `coming` tag from the
8.9.1 release
notes.","sha":"90b6e4dbe01219d5af51a93943338043bfdd773a"}},"sourceBranch":"main","suggestedTargetBranches":["8.9","8.11"],"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/164302","number":164302,"mergeCommit":{"message":"[DOCS]
Removes 8.9.1 coming tag. (#164302)\n\nRemoves `coming` tag from the
8.9.1 release
notes.","sha":"90b6e4dbe01219d5af51a93943338043bfdd773a"}},{"branch":"8.11","label":"v8.11.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
2023-08-21 09:49:40 -04:00
Marco Liberati
01f486e0d8
[8.9] [Lens] Relax counter field checks for saved visualizations with unsupported operations (#163515) - manual backport (#164191)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Lens] Relax counter field checks for saved visualizations with
unsupported operations
(#163515)](https://github.com/elastic/kibana/pull/163515)

This is a manual backport which adds a missing mock function, not
available in the automated backport cherry-pick of the PR.
The extra code is here:
`x-pack/plugins/lens/public/datasources/form_based/mocks.ts`

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-08-11T09:52:17Z","message":"[Lens]
Relax counter field checks for saved visualizations with unsupported
operations (#163515)\n\n## Summary\r\n\r\nFix #163473\r\n\r\nThis PR
relaxes a bit the checks on the Lens side for
old/saved\r\nvisualizations with unsupported operations for the
`counter` field type,\r\nwhile preserving those checks for newer
visualizations.\r\n\r\nDashboards with \"meaningless\" operations will
now show a warning\r\nmessage:\r\n<img width=\"556\" alt=\"Screenshot
2023-08-09 at 18 31
21\"\r\nsrc=\"7c8f3739-4957-4d1d-8aaa-e9457b8a4426\">\r\n\r\nWhen
in editor the warning is shown at the top-right corner as well:\r\n<img
width=\"845\" alt=\"Screenshot 2023-08-09 at 18 30
31\"\r\nsrc=\"c52a7823-d4b9-4efd-9c5d-ca654f3f03a0\">\r\n\r\nNew
visualizations still prevent the user from using the
unsupported\r\noperations:\r\n<img width=\"410\" alt=\"Screenshot
2023-08-09 at 18 30
55\"\r\nsrc=\"d2364a01-0dc3-409a-9c0b-3e3a77cb2566\">\r\n<img
width=\"848\" alt=\"Screenshot 2023-08-09 at 18 31
48\"\r\nsrc=\"086a7360-6b1a-40a2-90d9-f4e8c7bf3f3a\">\r\n\r\nThere's
theoretically a last case where users in old SOs might create a\r\nnew
metric dimension trying to force to use a unsupported operation for\r\na
counter field: in this case the logic for a \"new\" visualization
will\r\nkick-in, clean the data in the workspace and show a full
error.\r\nCancelling such metric dimension will lead to the previous
\"relaxed\"\r\nstate.\r\n\r\nMessages are grouped by field and by top
referencing column (i.e. a\r\nformula): this means that if a formula
uses the same `counter` field\r\nwith two different dimensions (i.e.
`sum(counter_field) +\r\nmedian(counter_field)` as `myFormula`) will
show up as a single column\r\n(`myFormula`).\r\n\r\nThe wording of the
message mimics the same documentation copy provided\r\nin the ES
documentation.
Ref:\r\nhttps://github.com/elastic/elasticsearch/pull/97974\r\n\r\nTesting
SO:\r\n\r\n\r\n[export.ndjson.txt](12304924/export.ndjson.txt)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x]\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\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli
<efstratia.kalafateli@elastic.co>","sha":"4c812e3b6d1a4e477768dae04047e79bbdc940ff","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","v8.10.0"],"number":163515,"url":"https://github.com/elastic/kibana/pull/163515","mergeCommit":{"message":"[Lens]
Relax counter field checks for saved visualizations with unsupported
operations (#163515)\n\n## Summary\r\n\r\nFix #163473\r\n\r\nThis PR
relaxes a bit the checks on the Lens side for
old/saved\r\nvisualizations with unsupported operations for the
`counter` field type,\r\nwhile preserving those checks for newer
visualizations.\r\n\r\nDashboards with \"meaningless\" operations will
now show a warning\r\nmessage:\r\n<img width=\"556\" alt=\"Screenshot
2023-08-09 at 18 31
21\"\r\nsrc=\"7c8f3739-4957-4d1d-8aaa-e9457b8a4426\">\r\n\r\nWhen
in editor the warning is shown at the top-right corner as well:\r\n<img
width=\"845\" alt=\"Screenshot 2023-08-09 at 18 30
31\"\r\nsrc=\"c52a7823-d4b9-4efd-9c5d-ca654f3f03a0\">\r\n\r\nNew
visualizations still prevent the user from using the
unsupported\r\noperations:\r\n<img width=\"410\" alt=\"Screenshot
2023-08-09 at 18 30
55\"\r\nsrc=\"d2364a01-0dc3-409a-9c0b-3e3a77cb2566\">\r\n<img
width=\"848\" alt=\"Screenshot 2023-08-09 at 18 31
48\"\r\nsrc=\"086a7360-6b1a-40a2-90d9-f4e8c7bf3f3a\">\r\n\r\nThere's
theoretically a last case where users in old SOs might create a\r\nnew
metric dimension trying to force to use a unsupported operation for\r\na
counter field: in this case the logic for a \"new\" visualization
will\r\nkick-in, clean the data in the workspace and show a full
error.\r\nCancelling such metric dimension will lead to the previous
\"relaxed\"\r\nstate.\r\n\r\nMessages are grouped by field and by top
referencing column (i.e. a\r\nformula): this means that if a formula
uses the same `counter` field\r\nwith two different dimensions (i.e.
`sum(counter_field) +\r\nmedian(counter_field)` as `myFormula`) will
show up as a single column\r\n(`myFormula`).\r\n\r\nThe wording of the
message mimics the same documentation copy provided\r\nin the ES
documentation.
Ref:\r\nhttps://github.com/elastic/elasticsearch/pull/97974\r\n\r\nTesting
SO:\r\n\r\n\r\n[export.ndjson.txt](12304924/export.ndjson.txt)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x]\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\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli
<efstratia.kalafateli@elastic.co>","sha":"4c812e3b6d1a4e477768dae04047e79bbdc940ff"}},"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/163515","number":163515,"mergeCommit":{"message":"[Lens]
Relax counter field checks for saved visualizations with unsupported
operations (#163515)\n\n## Summary\r\n\r\nFix #163473\r\n\r\nThis PR
relaxes a bit the checks on the Lens side for
old/saved\r\nvisualizations with unsupported operations for the
`counter` field type,\r\nwhile preserving those checks for newer
visualizations.\r\n\r\nDashboards with \"meaningless\" operations will
now show a warning\r\nmessage:\r\n<img width=\"556\" alt=\"Screenshot
2023-08-09 at 18 31
21\"\r\nsrc=\"7c8f3739-4957-4d1d-8aaa-e9457b8a4426\">\r\n\r\nWhen
in editor the warning is shown at the top-right corner as well:\r\n<img
width=\"845\" alt=\"Screenshot 2023-08-09 at 18 30
31\"\r\nsrc=\"c52a7823-d4b9-4efd-9c5d-ca654f3f03a0\">\r\n\r\nNew
visualizations still prevent the user from using the
unsupported\r\noperations:\r\n<img width=\"410\" alt=\"Screenshot
2023-08-09 at 18 30
55\"\r\nsrc=\"d2364a01-0dc3-409a-9c0b-3e3a77cb2566\">\r\n<img
width=\"848\" alt=\"Screenshot 2023-08-09 at 18 31
48\"\r\nsrc=\"086a7360-6b1a-40a2-90d9-f4e8c7bf3f3a\">\r\n\r\nThere's
theoretically a last case where users in old SOs might create a\r\nnew
metric dimension trying to force to use a unsupported operation for\r\na
counter field: in this case the logic for a \"new\" visualization
will\r\nkick-in, clean the data in the workspace and show a full
error.\r\nCancelling such metric dimension will lead to the previous
\"relaxed\"\r\nstate.\r\n\r\nMessages are grouped by field and by top
referencing column (i.e. a\r\nformula): this means that if a formula
uses the same `counter` field\r\nwith two different dimensions (i.e.
`sum(counter_field) +\r\nmedian(counter_field)` as `myFormula`) will
show up as a single column\r\n(`myFormula`).\r\n\r\nThe wording of the
message mimics the same documentation copy provided\r\nin the ES
documentation.
Ref:\r\nhttps://github.com/elastic/elasticsearch/pull/97974\r\n\r\nTesting
SO:\r\n\r\n\r\n[export.ndjson.txt](12304924/export.ndjson.txt)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x]\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\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli
<efstratia.kalafateli@elastic.co>","sha":"4c812e3b6d1a4e477768dae04047e79bbdc940ff"}}]}]
BACKPORT-->

---------

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
2023-08-21 15:24:25 +02:00
Kibana Machine
2774922290
[8.9] fix 'Download CSV' returns no data when panel has custom time range outside timerange of global time picker (#163887) (#164238)
# Backport

This will backport the following commits from `main` to `8.9`:
- [fix 'Download CSV' returns no data when panel has custom time range
outside timerange of global time picker
(#163887)](https://github.com/elastic/kibana/pull/163887)

<!--- 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-17T22:37:12Z","message":"fix
'Download CSV' returns no data when panel has custom time range outside
timerange of global time picker (#163887)\n\nCloses
https://github.com/elastic/kibana/issues/163614\r\n\r\nPR resolves issue
by only adding global time filter to CSV export body\r\nwhen saved
search embeddable does not have time
range.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"53e803e42c5c9de73e60ae95cff13d17bab09f26","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","Team:DataDiscovery","Team:SharedUX","v8.10.0","v8.11.0","v8.9.2"],"number":163887,"url":"https://github.com/elastic/kibana/pull/163887","mergeCommit":{"message":"fix
'Download CSV' returns no data when panel has custom time range outside
timerange of global time picker (#163887)\n\nCloses
https://github.com/elastic/kibana/issues/163614\r\n\r\nPR resolves issue
by only adding global time filter to CSV export body\r\nwhen saved
search embeddable does not have time
range.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"53e803e42c5c9de73e60ae95cff13d17bab09f26"}},"sourceBranch":"main","suggestedTargetBranches":["8.11","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163887","number":163887,"mergeCommit":{"message":"fix
'Download CSV' returns no data when panel has custom time range outside
timerange of global time picker (#163887)\n\nCloses
https://github.com/elastic/kibana/issues/163614\r\n\r\nPR resolves issue
by only adding global time filter to CSV export body\r\nwhen saved
search embeddable does not have time
range.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"53e803e42c5c9de73e60ae95cff13d17bab09f26"}},{"branch":"8.11","label":"v8.11.0","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: Nathan Reese <reese.nathan@elastic.co>
2023-08-17 20:59:25 -07:00