Commit graph

64666 commits

Author SHA1 Message Date
Kibana Machine
098eee5d09
[8.9] [DOCv2] Temporarily disable Kibana Rules (#126869) (#161865)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCv2] Temporarily disable Kibana Rules
(#126869)](https://github.com/elastic/kibana/pull/126869)

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

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

<!--BACKPORT [{"author":{"name":"Stef
Nestor","email":"26751266+stefnestor@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-13T13:22:55Z","message":"[DOCv2]
Temporarily disable Kibana Rules (#126869)\n\n👋🏼 @gchaps asked me to
file a new PR since my
last\r\nhttps://github.com/elastic/kibana/pull/122573 got too far
behind.\r\n\r\n## Summary\r\n\r\n🙏🏼 per #116017, adds insight on how to
temporarily disable Kibana Rules\r\nfor clusters which need breathing
room.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Lisa Cawley
<lcawley@elastic.co>","sha":"b1d619617a0321617636c7c1bbcbf74e393a5d9e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","auto-backport","Feature:Alerting/RulesManagement","v8.9.0","v8.10.0"],"number":126869,"url":"https://github.com/elastic/kibana/pull/126869","mergeCommit":{"message":"[DOCv2]
Temporarily disable Kibana Rules (#126869)\n\n👋🏼 @gchaps asked me to
file a new PR since my
last\r\nhttps://github.com/elastic/kibana/pull/122573 got too far
behind.\r\n\r\n## Summary\r\n\r\n🙏🏼 per #116017, adds insight on how to
temporarily disable Kibana Rules\r\nfor clusters which need breathing
room.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Lisa Cawley
<lcawley@elastic.co>","sha":"b1d619617a0321617636c7c1bbcbf74e393a5d9e"}},"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/126869","number":126869,"mergeCommit":{"message":"[DOCv2]
Temporarily disable Kibana Rules (#126869)\n\n👋🏼 @gchaps asked me to
file a new PR since my
last\r\nhttps://github.com/elastic/kibana/pull/122573 got too far
behind.\r\n\r\n## Summary\r\n\r\n🙏🏼 per #116017, adds insight on how to
temporarily disable Kibana Rules\r\nfor clusters which need breathing
room.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Lisa Cawley
<lcawley@elastic.co>","sha":"b1d619617a0321617636c7c1bbcbf74e393a5d9e"}}]}]
BACKPORT-->

Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
2023-07-13 09:46:05 -04:00
Georgii Gorbachev
ee95a1159a
[8.9] [Security Solution] Move test plans from /cypress to /docs (#161517) (#161739)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Move test plans from /cypress to /docs
(#161517)](https://github.com/elastic/kibana/pull/161517)

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

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

<!--BACKPORT [{"author":{"name":"Georgii
Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T09:27:00Z","message":"[Security
Solution] Move test plans from /cypress to /docs (#161517)\n\n**Related
to:**
https://github.com/elastic/security-team/issues/6867\r\n(internal)\r\n\r\n##
Summary\r\n\r\nAs requested
in\r\nhttps://github.com/elastic/kibana/pull/160685#issuecomment-1621635262.\r\n\r\nIn
test plans, we mention how scenarios are going to be automated
--\r\nwhether a given scenario will be automated using Cypress for e2e
tests,\r\nJest for integration tests and unit tests, etc. But currently,
test\r\nplans are under
`x-pack/plugins/security_solution/cypress/`.\r\n\r\nSince test plans are
in fact technology agnostic, it does not make much\r\nsense to keep them
inside a specific framework technology folder. That's\r\nwhy we're
moving them to a
generic\r\n`x-pack/plugins/security_solution/docs/testing`
folder.","sha":"15a86c355a261ce11cad82f3b3c47dfeca814d1f","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","v8.9.0","v8.10.0"],"number":161517,"url":"https://github.com/elastic/kibana/pull/161517","mergeCommit":{"message":"[Security
Solution] Move test plans from /cypress to /docs (#161517)\n\n**Related
to:**
https://github.com/elastic/security-team/issues/6867\r\n(internal)\r\n\r\n##
Summary\r\n\r\nAs requested
in\r\nhttps://github.com/elastic/kibana/pull/160685#issuecomment-1621635262.\r\n\r\nIn
test plans, we mention how scenarios are going to be automated
--\r\nwhether a given scenario will be automated using Cypress for e2e
tests,\r\nJest for integration tests and unit tests, etc. But currently,
test\r\nplans are under
`x-pack/plugins/security_solution/cypress/`.\r\n\r\nSince test plans are
in fact technology agnostic, it does not make much\r\nsense to keep them
inside a specific framework technology folder. That's\r\nwhy we're
moving them to a
generic\r\n`x-pack/plugins/security_solution/docs/testing`
folder.","sha":"15a86c355a261ce11cad82f3b3c47dfeca814d1f"}},"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/161517","number":161517,"mergeCommit":{"message":"[Security
Solution] Move test plans from /cypress to /docs (#161517)\n\n**Related
to:**
https://github.com/elastic/security-team/issues/6867\r\n(internal)\r\n\r\n##
Summary\r\n\r\nAs requested
in\r\nhttps://github.com/elastic/kibana/pull/160685#issuecomment-1621635262.\r\n\r\nIn
test plans, we mention how scenarios are going to be automated
--\r\nwhether a given scenario will be automated using Cypress for e2e
tests,\r\nJest for integration tests and unit tests, etc. But currently,
test\r\nplans are under
`x-pack/plugins/security_solution/cypress/`.\r\n\r\nSince test plans are
in fact technology agnostic, it does not make much\r\nsense to keep them
inside a specific framework technology folder. That's\r\nwhy we're
moving them to a
generic\r\n`x-pack/plugins/security_solution/docs/testing`
folder.","sha":"15a86c355a261ce11cad82f3b3c47dfeca814d1f"}}]}]
BACKPORT-->
2023-07-13 15:11:18 +02:00
Kibana Machine
b9b161416e
[8.9] [Enterprise Search] Fix documents pagination (#161830) (#161850)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Enterprise Search] Fix documents pagination
(#161830)](https://github.com/elastic/kibana/pull/161830)

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

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

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-13T10:47:43Z","message":"[Enterprise
Search] Fix documents pagination (#161830)\n\n## Summary\r\n\r\nThis
fixes broken pagination in access control indices, by splitting
the\r\nfetching logic out and making it unique per index
name.","sha":"1727a5ed77dca39c3b8ae7090225323f6f3b340c","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.9.0","v8.10.0"],"number":161830,"url":"https://github.com/elastic/kibana/pull/161830","mergeCommit":{"message":"[Enterprise
Search] Fix documents pagination (#161830)\n\n## Summary\r\n\r\nThis
fixes broken pagination in access control indices, by splitting
the\r\nfetching logic out and making it unique per index
name.","sha":"1727a5ed77dca39c3b8ae7090225323f6f3b340c"}},"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/161830","number":161830,"mergeCommit":{"message":"[Enterprise
Search] Fix documents pagination (#161830)\n\n## Summary\r\n\r\nThis
fixes broken pagination in access control indices, by splitting
the\r\nfetching logic out and making it unique per index
name.","sha":"1727a5ed77dca39c3b8ae7090225323f6f3b340c"}}]}] BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
2023-07-13 04:53:44 -07:00
Kibana Machine
425faa5891
[8.9] [Security Solution] [Timeline] Add filter.meta.relation to timeline filters saved object mapping (#161722) (#161817)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Timeline] Add filter.meta.relation to timeline
filters saved object mapping
(#161722)](https://github.com/elastic/kibana/pull/161722)

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

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

<!--BACKPORT [{"author":{"name":"Kevin
Qualters","email":"56408403+kqualters-elastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-12T22:09:13Z","message":"[Security
Solution] [Timeline] Add filter.meta.relation to timeline filters saved
object mapping (#161722)\n\n## Summary\r\n\r\nWithout this mapping,
timelines that try to make use of a top level OR\r\nfilter from the
unified search filter builder cannot be saved,\r\neverything works as
expected with this change.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2caa973c61735002df5b9aaf444f1ca543c279c1","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting:Investigations","v8.9.0","v8.10.0"],"number":161722,"url":"https://github.com/elastic/kibana/pull/161722","mergeCommit":{"message":"[Security
Solution] [Timeline] Add filter.meta.relation to timeline filters saved
object mapping (#161722)\n\n## Summary\r\n\r\nWithout this mapping,
timelines that try to make use of a top level OR\r\nfilter from the
unified search filter builder cannot be saved,\r\neverything works as
expected with this change.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2caa973c61735002df5b9aaf444f1ca543c279c1"}},"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/161722","number":161722,"mergeCommit":{"message":"[Security
Solution] [Timeline] Add filter.meta.relation to timeline filters saved
object mapping (#161722)\n\n## Summary\r\n\r\nWithout this mapping,
timelines that try to make use of a top level OR\r\nfilter from the
unified search filter builder cannot be saved,\r\neverything works as
expected with this change.\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"2caa973c61735002df5b9aaf444f1ca543c279c1"}}]}]
BACKPORT-->

Co-authored-by: Kevin Qualters <56408403+kqualters-elastic@users.noreply.github.com>
2023-07-12 16:30:11 -07:00
Kibana Machine
98978c8a16
[8.9] [Observability] Add feedback buttons for prompts (#160351) (#161805)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Observability] Add feedback buttons for prompts
(#160351)](https://github.com/elastic/kibana/pull/160351)

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

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

<!--BACKPORT [{"author":{"name":"Dario
Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2023-07-12T19:58:13Z","message":"[Observability]
Add feedback buttons for prompts (#160351)\n\nCo-authored-by: Sean
Heelan
<sean@optimyze.cloud>","sha":"4ae94c35024f2037ee02502037b873d93256d200","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","v8.9.0","v8.10.0"],"number":160351,"url":"https://github.com/elastic/kibana/pull/160351","mergeCommit":{"message":"[Observability]
Add feedback buttons for prompts (#160351)\n\nCo-authored-by: Sean
Heelan
<sean@optimyze.cloud>","sha":"4ae94c35024f2037ee02502037b873d93256d200"}},"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/160351","number":160351,"mergeCommit":{"message":"[Observability]
Add feedback buttons for prompts (#160351)\n\nCo-authored-by: Sean
Heelan
<sean@optimyze.cloud>","sha":"4ae94c35024f2037ee02502037b873d93256d200"}}]}]
BACKPORT-->

Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
2023-07-12 14:22:26 -07:00
Nicolas Chaulet
ddf0c1972e
[8.9] [Fleet] Fix dupplicate unhealthy callout (#161755) (#161769)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Fleet] Fix dupplicate unhealthy callout
(#161755)](https://github.com/elastic/kibana/pull/161755)

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

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

<!--BACKPORT [{"author":{"name":"Nicolas
Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2023-07-12T13:21:43Z","message":"[Fleet]
Fix dupplicate unhealthy callout
(#161755)","sha":"c031900036b320dff64aebe14c0bf0ec9001ae84","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v8.9.0","v8.10.0"],"number":161755,"url":"https://github.com/elastic/kibana/pull/161755","mergeCommit":{"message":"[Fleet]
Fix dupplicate unhealthy callout
(#161755)","sha":"c031900036b320dff64aebe14c0bf0ec9001ae84"}},"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/161755","number":161755,"mergeCommit":{"message":"[Fleet]
Fix dupplicate unhealthy callout
(#161755)","sha":"c031900036b320dff64aebe14c0bf0ec9001ae84"}}]}]
BACKPORT-->

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-07-12 20:16:12 +02:00
Kibana Machine
d15bd0338e
[8.9] [Security Solution] Fixing exceptions flyout is not auto filled with all highlighted fields listed on Alert details page (#161673) (#161785)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Fixing exceptions flyout is not auto filled with
all highlighted fields listed on Alert details page
(#161673)](https://github.com/elastic/kibana/pull/161673)

<!--- 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-07-12T15:50:02Z","message":"[Security
Solution] Fixing exceptions flyout is not auto filled with all
highlighted fields listed on Alert details page (#161673)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/161460\r\n- Exclude `agent.id`
in case the Alert's `agent.type` is not `endpoint`\r\n- Handle Alert
`event.category` array field ex. `[process]`\r\n- For the `Threshold
Rule` there are two additional fields the Alert\r\nSummary populates the
`Event Count` and the `Event Cardinality` which\r\ncan be ignored as
they are not relevant to the Rule
exception\r\n\r\n\r\n![image](8972a647-6490-4d54-8af8-54f90d4ac438)\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"130e9deea59a326e1e0d40827ad7a0bc401a3d27","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Rule
Exceptions","backport:prev-minor","ci:cloud-deploy","8.9
candidate","Team:Detection
Engine","v8.10.0"],"number":161673,"url":"https://github.com/elastic/kibana/pull/161673","mergeCommit":{"message":"[Security
Solution] Fixing exceptions flyout is not auto filled with all
highlighted fields listed on Alert details page (#161673)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/161460\r\n- Exclude `agent.id`
in case the Alert's `agent.type` is not `endpoint`\r\n- Handle Alert
`event.category` array field ex. `[process]`\r\n- For the `Threshold
Rule` there are two additional fields the Alert\r\nSummary populates the
`Event Count` and the `Event Cardinality` which\r\ncan be ignored as
they are not relevant to the Rule
exception\r\n\r\n\r\n![image](8972a647-6490-4d54-8af8-54f90d4ac438)\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"130e9deea59a326e1e0d40827ad7a0bc401a3d27"}},"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/161673","number":161673,"mergeCommit":{"message":"[Security
Solution] Fixing exceptions flyout is not auto filled with all
highlighted fields listed on Alert details page (#161673)\n\n##
Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/161460\r\n- Exclude `agent.id`
in case the Alert's `agent.type` is not `endpoint`\r\n- Handle Alert
`event.category` array field ex. `[process]`\r\n- For the `Threshold
Rule` there are two additional fields the Alert\r\nSummary populates the
`Event Count` and the `Event Cardinality` which\r\ncan be ignored as
they are not relevant to the Rule
exception\r\n\r\n\r\n![image](8972a647-6490-4d54-8af8-54f90d4ac438)\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"130e9deea59a326e1e0d40827ad7a0bc401a3d27"}}]}]
BACKPORT-->

Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co>
2023-07-12 10:31:54 -07:00
Kibana Machine
1489f70e08
[8.9] [DOCS] Add rule.params to rule action variables (#161714) (#161792)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Add rule.params to rule action variables
(#161714)](https://github.com/elastic/kibana/pull/161714)

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

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-07-12T16:56:57Z","message":"[DOCS]
Add rule.params to rule action variables
(#161714)","sha":"7f3c9e8c811c0eff75a3d8d27ce337eeaddeded1","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Alerting/RuleActions","backport:prev-minor","v8.9.0","v8.10.0"],"number":161714,"url":"https://github.com/elastic/kibana/pull/161714","mergeCommit":{"message":"[DOCS]
Add rule.params to rule action variables
(#161714)","sha":"7f3c9e8c811c0eff75a3d8d27ce337eeaddeded1"}},"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/161714","number":161714,"mergeCommit":{"message":"[DOCS]
Add rule.params to rule action variables
(#161714)","sha":"7f3c9e8c811c0eff75a3d8d27ce337eeaddeded1"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-07-12 13:22:05 -04:00
Kibana Machine
5442b6b330
[8.9] [APM] Fix broken unit tests (#161636) (#161782)
# Backport

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

<!--- 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-07-12T15:19:00Z","message":"[APM]
Fix broken unit tests (#161636)\n\nA bunch of APM unit tests were
passing on CI but failing locally. This\r\nPR fixes the unit
tests\r\n\r\n**Why fail locally and pass on CI??**\r\nThe reason they
pass on CI is because `console.error` calls are omitted.\r\nIn the APM
jest config `console.error` is treated as a test
failure:\r\n\r\n\r\n7ea0dd6b11/x-pack/plugins/apm/jest_setup.js (L12-L15)","sha":"ccb36d929a2514dfce82534471455480e335e206","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","v8.9.0","v8.10.0"],"number":161636,"url":"https://github.com/elastic/kibana/pull/161636","mergeCommit":{"message":"[APM]
Fix broken unit tests (#161636)\n\nA bunch of APM unit tests were
passing on CI but failing locally. This\r\nPR fixes the unit
tests\r\n\r\n**Why fail locally and pass on CI??**\r\nThe reason they
pass on CI is because `console.error` calls are omitted.\r\nIn the APM
jest config `console.error` is treated as a test
failure:\r\n\r\n\r\n7ea0dd6b11/x-pack/plugins/apm/jest_setup.js (L12-L15)","sha":"ccb36d929a2514dfce82534471455480e335e206"}},"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/161636","number":161636,"mergeCommit":{"message":"[APM]
Fix broken unit tests (#161636)\n\nA bunch of APM unit tests were
passing on CI but failing locally. This\r\nPR fixes the unit
tests\r\n\r\n**Why fail locally and pass on CI??**\r\nThe reason they
pass on CI is because `console.error` calls are omitted.\r\nIn the APM
jest config `console.error` is treated as a test
failure:\r\n\r\n\r\n7ea0dd6b11/x-pack/plugins/apm/jest_setup.js (L12-L15)","sha":"ccb36d929a2514dfce82534471455480e335e206"}}]}]
BACKPORT-->

Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co>
2023-07-12 09:49:43 -07:00
Kibana Machine
19f406744f skip failing test suite (#161557) 2023-07-12 12:04:23 -04:00
Kibana Machine
7bbfb3cfa2
[8.9] [Synthetics] Optimise get last 50 checks query (#161742) (#161771)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Optimise get last 50 checks query
(#161742)](https://github.com/elastic/kibana/pull/161742)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-12T14:32:57Z","message":"[Synthetics]
Optimise get last 50 checks query
(#161742)","sha":"d166193ac04a8a3db48f252bc90ca36928427507","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161742,"url":"https://github.com/elastic/kibana/pull/161742","mergeCommit":{"message":"[Synthetics]
Optimise get last 50 checks query
(#161742)","sha":"d166193ac04a8a3db48f252bc90ca36928427507"}},"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/161742","number":161742,"mergeCommit":{"message":"[Synthetics]
Optimise get last 50 checks query
(#161742)","sha":"d166193ac04a8a3db48f252bc90ca36928427507"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-12 08:42:56 -07:00
Kibana Machine
8c14f314e4
[8.9] [Infra UI] Hosts flyout test fix (#161244) (#161767)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Infra UI] Hosts flyout test fix
(#161244)](https://github.com/elastic/kibana/pull/161244)

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

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

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2023-07-06T07:50:40Z","message":"[Infra
UI] Hosts flyout test fix (#161244)\n\nCloses #159368 \r\n\r\n##
Summary\r\n\r\nI saw that the test was failing because of a missing
environment set. I\r\nguess that happened because the test runner
doesn't include it like it\r\nis included locally so I removed that
check so the test shouldn't
be\r\nflaky.","sha":"9d57196a54ebe7816d2739ee5b85dcc76a71b253","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra
Monitoring
UI","release_note:skip","backport:prev-minor","v8.10.0"],"number":161244,"url":"https://github.com/elastic/kibana/pull/161244","mergeCommit":{"message":"[Infra
UI] Hosts flyout test fix (#161244)\n\nCloses #159368 \r\n\r\n##
Summary\r\n\r\nI saw that the test was failing because of a missing
environment set. I\r\nguess that happened because the test runner
doesn't include it like it\r\nis included locally so I removed that
check so the test shouldn't
be\r\nflaky.","sha":"9d57196a54ebe7816d2739ee5b85dcc76a71b253"}},"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/161244","number":161244,"mergeCommit":{"message":"[Infra
UI] Hosts flyout test fix (#161244)\n\nCloses #159368 \r\n\r\n##
Summary\r\n\r\nI saw that the test was failing because of a missing
environment set. I\r\nguess that happened because the test runner
doesn't include it like it\r\nis included locally so I removed that
check so the test shouldn't
be\r\nflaky.","sha":"9d57196a54ebe7816d2739ee5b85dcc76a71b253"}}]}]
BACKPORT-->

Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
2023-07-12 08:16:36 -07:00
Kibana Machine
482b747a29
[8.9] [Synthetics] Fix type warning (#161745) (#161766)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Fix type warning
(#161745)](https://github.com/elastic/kibana/pull/161745)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-12T13:44:01Z","message":"[Synthetics]
Fix type warning
(#161745)","sha":"91e065ebc4e06314460afcc19c2a53df06add294","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161745,"url":"https://github.com/elastic/kibana/pull/161745","mergeCommit":{"message":"[Synthetics]
Fix type warning
(#161745)","sha":"91e065ebc4e06314460afcc19c2a53df06add294"}},"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/161745","number":161745,"mergeCommit":{"message":"[Synthetics]
Fix type warning
(#161745)","sha":"91e065ebc4e06314460afcc19c2a53df06add294"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-12 07:52:52 -07:00
Kibana Machine
dbdd4402d4
[8.9] [Migrations - v2] Allow for 1 byte size variation in es_response_too_large (#161626) (#161749)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Migrations - v2] Allow for 1 byte size variation in
es_response_too_large
(#161626)](https://github.com/elastic/kibana/pull/161626)

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

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

<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2023-07-12T11:38:37Z","message":"[Migrations
- v2] Allow for 1 byte size variation in es_response_too_large
(#161626)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/160994\r\n\r\nThere must be
some randomness factor that causes the response payload\r\nsize to have
a 1 byte size variation, as observed in the\r\n`es_response_too_large`
error.\r\n\r\nThis PR relaxes the constraint and accepts a
`es_response_too_large`\r\nerror with either 3184 or 3185
bytes.","sha":"5d5c10a320a7cc6b9f67bd59068e25c7cdca14c2","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","test-failure-flaky","Feature:Migrations","backport:prev-minor","v8.9.0","v8.10.0"],"number":161626,"url":"https://github.com/elastic/kibana/pull/161626","mergeCommit":{"message":"[Migrations
- v2] Allow for 1 byte size variation in es_response_too_large
(#161626)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/160994\r\n\r\nThere must be
some randomness factor that causes the response payload\r\nsize to have
a 1 byte size variation, as observed in the\r\n`es_response_too_large`
error.\r\n\r\nThis PR relaxes the constraint and accepts a
`es_response_too_large`\r\nerror with either 3184 or 3185
bytes.","sha":"5d5c10a320a7cc6b9f67bd59068e25c7cdca14c2"}},"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/161626","number":161626,"mergeCommit":{"message":"[Migrations
- v2] Allow for 1 byte size variation in es_response_too_large
(#161626)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/160994\r\n\r\nThere must be
some randomness factor that causes the response payload\r\nsize to have
a 1 byte size variation, as observed in the\r\n`es_response_too_large`
error.\r\n\r\nThis PR relaxes the constraint and accepts a
`es_response_too_large`\r\nerror with either 3184 or 3185
bytes.","sha":"5d5c10a320a7cc6b9f67bd59068e25c7cdca14c2"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
2023-07-12 07:23:14 -07:00
Garrett Spong
140572b2bc
[8.9] [Security Solution] [Elastic AI Assistant] Consolidates settings into a single modal (#160468) (#161757)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] [Elastic AI Assistant] Consolidates settings into
a single modal (#160468)](https://github.com/elastic/kibana/pull/160468)

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

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

<!--BACKPORT [{"author":{"name":"Garrett
Spong","email":"spong@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-12T07:50:10Z","message":"[Security
Solution] [Elastic AI Assistant] Consolidates settings into a single
modal (#160468)\n\n## Summary\r\n\r\nThis PR fixes the disjointed
settings across the assistant by combining\r\nthem all into a single
settings modal. It also resolves the Connector\r\n`Model` configuration
not being available when using the `OpenAI`\r\nvariant of the GenAI
Connector.\r\n\r\nAdditional issues resolved:\r\n- [x] Clearing
conversation doesn't restore default system prompt\r\n- [X] Double
repeated welcome prompt\r\n- [X] Clicking skip button
broken\r\n\r\nResolves:
https://github.com/elastic/security-team/issues/7110\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161039#pullrequestreview-1517129764\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161027#pullrequestreview-1523018176\r\n\r\n####
Conversations\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"80e271e8-d12a-4d00-b6eb-d63cda2d8017\"\r\n/>\r\n</p>
\r\n\r\n#### Quick Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"417c49c0-2029-49f1-a2f3-b9d0ae3690d3\"\r\n/>\r\n</p>
\r\n\r\n#### System Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"cc2bac93-bfba-49c1-b5b8-6a6efa1c0a92\"\r\n/>\r\n</p>
\r\n\r\n#### Anonymization\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"9a65683a-06cc-4cc7-9397-9db2633b20a3\"\r\n/>\r\n</p>
\r\n\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-
[
]\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","sha":"b323923e65af29416fc820fa4e7c8282d16f8ecc","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","needs_docs","Team:
SecuritySolution","v8.9.0","Feature:Elastic
Assistant","v8.10.0"],"number":160468,"url":"https://github.com/elastic/kibana/pull/160468","mergeCommit":{"message":"[Security
Solution] [Elastic AI Assistant] Consolidates settings into a single
modal (#160468)\n\n## Summary\r\n\r\nThis PR fixes the disjointed
settings across the assistant by combining\r\nthem all into a single
settings modal. It also resolves the Connector\r\n`Model` configuration
not being available when using the `OpenAI`\r\nvariant of the GenAI
Connector.\r\n\r\nAdditional issues resolved:\r\n- [x] Clearing
conversation doesn't restore default system prompt\r\n- [X] Double
repeated welcome prompt\r\n- [X] Clicking skip button
broken\r\n\r\nResolves:
https://github.com/elastic/security-team/issues/7110\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161039#pullrequestreview-1517129764\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161027#pullrequestreview-1523018176\r\n\r\n####
Conversations\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"80e271e8-d12a-4d00-b6eb-d63cda2d8017\"\r\n/>\r\n</p>
\r\n\r\n#### Quick Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"417c49c0-2029-49f1-a2f3-b9d0ae3690d3\"\r\n/>\r\n</p>
\r\n\r\n#### System Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"cc2bac93-bfba-49c1-b5b8-6a6efa1c0a92\"\r\n/>\r\n</p>
\r\n\r\n#### Anonymization\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"9a65683a-06cc-4cc7-9397-9db2633b20a3\"\r\n/>\r\n</p>
\r\n\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-
[
]\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","sha":"b323923e65af29416fc820fa4e7c8282d16f8ecc"}},"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/160468","number":160468,"mergeCommit":{"message":"[Security
Solution] [Elastic AI Assistant] Consolidates settings into a single
modal (#160468)\n\n## Summary\r\n\r\nThis PR fixes the disjointed
settings across the assistant by combining\r\nthem all into a single
settings modal. It also resolves the Connector\r\n`Model` configuration
not being available when using the `OpenAI`\r\nvariant of the GenAI
Connector.\r\n\r\nAdditional issues resolved:\r\n- [x] Clearing
conversation doesn't restore default system prompt\r\n- [X] Double
repeated welcome prompt\r\n- [X] Clicking skip button
broken\r\n\r\nResolves:
https://github.com/elastic/security-team/issues/7110\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161039#pullrequestreview-1517129764\r\nResolves:\r\nhttps://github.com/elastic/kibana/pull/161027#pullrequestreview-1523018176\r\n\r\n####
Conversations\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"80e271e8-d12a-4d00-b6eb-d63cda2d8017\"\r\n/>\r\n</p>
\r\n\r\n#### Quick Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"417c49c0-2029-49f1-a2f3-b9d0ae3690d3\"\r\n/>\r\n</p>
\r\n\r\n#### System Prompts\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"cc2bac93-bfba-49c1-b5b8-6a6efa1c0a92\"\r\n/>\r\n</p>
\r\n\r\n#### Anonymization\r\n\r\n<p align=\"center\">\r\n<img
width=\"500\"\r\nsrc=\"9a65683a-06cc-4cc7-9397-9db2633b20a3\"\r\n/>\r\n</p>
\r\n\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-
[
]\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","sha":"b323923e65af29416fc820fa4e7c8282d16f8ecc"}}]}]
BACKPORT-->
2023-07-12 06:59:46 -07:00
Kibana Machine
39a17a21c9
[8.9] [Synthetics] Fixes dom warnings for p > div (#161744) (#161752)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Fixes dom warnings for p > div
(#161744)](https://github.com/elastic/kibana/pull/161744)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-12T11:53:41Z","message":"[Synthetics]
Fixes dom warnings for p > div
(#161744)","sha":"a78c7b02b3b825826f39289e91e545ee6f4a67d9","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161744,"url":"https://github.com/elastic/kibana/pull/161744","mergeCommit":{"message":"[Synthetics]
Fixes dom warnings for p > div
(#161744)","sha":"a78c7b02b3b825826f39289e91e545ee6f4a67d9"}},"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/161744","number":161744,"mergeCommit":{"message":"[Synthetics]
Fixes dom warnings for p > div
(#161744)","sha":"a78c7b02b3b825826f39289e91e545ee6f4a67d9"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-12 06:39:58 -07:00
Garrett Spong
f3015c7f98
[8.9] [Security Solution] Store last conversation in localstorage #6993 (#161373) (#161743)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Store last conversation in localstorage #6993
(#161373)](https://github.com/elastic/kibana/pull/161373)

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

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

<!--BACKPORT
[{"author":{"name":"Luke","email":"11671118+lgestc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-12T01:02:11Z","message":"[Security
Solution] Store last conversation in localstorage #6993
(#161373)","sha":"ca3146f0ca5dc1d003214878bbf60d0aa1f00a1d","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","Feature:Elastic
Assistant","v8.10.0"],"number":161373,"url":"https://github.com/elastic/kibana/pull/161373","mergeCommit":{"message":"[Security
Solution] Store last conversation in localstorage #6993
(#161373)","sha":"ca3146f0ca5dc1d003214878bbf60d0aa1f00a1d"}},"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/161373","number":161373,"mergeCommit":{"message":"[Security
Solution] Store last conversation in localstorage #6993
(#161373)","sha":"ca3146f0ca5dc1d003214878bbf60d0aa1f00a1d"}}]}]
BACKPORT-->

Co-authored-by: Luke <11671118+lgestc@users.noreply.github.com>
2023-07-12 06:14:55 -06:00
Kibana Machine
86025a1647
[8.9] [Synthetics] Fix parsing of response check json expression (#161634) (#161741)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Fix parsing of response check json expression
(#161634)](https://github.com/elastic/kibana/pull/161634)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-12T10:27:34Z","message":"[Synthetics]
Fix parsing of response check json expression
(#161634)","sha":"707a637f426dbef9cb3201b356cab5af118c8850","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:uptime","v8.9.0","v8.10.0"],"number":161634,"url":"https://github.com/elastic/kibana/pull/161634","mergeCommit":{"message":"[Synthetics]
Fix parsing of response check json expression
(#161634)","sha":"707a637f426dbef9cb3201b356cab5af118c8850"}},"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/161634","number":161634,"mergeCommit":{"message":"[Synthetics]
Fix parsing of response check json expression
(#161634)","sha":"707a637f426dbef9cb3201b356cab5af118c8850"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-12 04:37:47 -07:00
Garrett Spong
89293ae28c
[8.9] [Security solution] Elastic Assistant adds beta label (#161682) (#161727)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security solution] Elastic Assistant adds beta label
(#161682)](https://github.com/elastic/kibana/pull/161682)

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

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

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T20:52:45Z","message":"[Security
solution] Elastic Assistant adds beta label
(#161682)","sha":"6673ffbf18f372ddf8569b8106532f05a45f2d88","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","v8.9.0","Feature:Elastic
Assistant","v8.10.0"],"number":161682,"url":"https://github.com/elastic/kibana/pull/161682","mergeCommit":{"message":"[Security
solution] Elastic Assistant adds beta label
(#161682)","sha":"6673ffbf18f372ddf8569b8106532f05a45f2d88"}},"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/161682","number":161682,"mergeCommit":{"message":"[Security
solution] Elastic Assistant adds beta label
(#161682)","sha":"6673ffbf18f372ddf8569b8106532f05a45f2d88"}}]}]
BACKPORT-->

Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co>
2023-07-12 03:26:48 -07:00
Kibana Machine
0554d9180c
[8.9] [Synthetics] Refactor e2e tests for silent failures (#161638) (#161735)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Refactor e2e tests for silent failures
(#161638)](https://github.com/elastic/kibana/pull/161638)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-12T09:10:03Z","message":"[Synthetics]
Refactor e2e tests for silent failures
(#161638)","sha":"5fca22a79db0ad72d539d7ee297211653e607026","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161638,"url":"https://github.com/elastic/kibana/pull/161638","mergeCommit":{"message":"[Synthetics]
Refactor e2e tests for silent failures
(#161638)","sha":"5fca22a79db0ad72d539d7ee297211653e607026"}},"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/161638","number":161638,"mergeCommit":{"message":"[Synthetics]
Refactor e2e tests for silent failures
(#161638)","sha":"5fca22a79db0ad72d539d7ee297211653e607026"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-12 03:24:40 -07:00
Kibana Machine
0f5b063f97
[8.9] [Cloud Security] Adding vuln filter to the scores index (#161648) (#161734)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Cloud Security] Adding vuln filter to the scores index
(#161648)](https://github.com/elastic/kibana/pull/161648)

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

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

<!--BACKPORT
[{"author":{"name":"Jordan","email":"51442161+JordanSh@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-12T09:09:41Z","message":"[Cloud
Security] Adding vuln filter to the scores index
(#161648)","sha":"47d099e22f537df820858a31e00f05343c026e25","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud
Security","v8.9.0","v8.10.0"],"number":161648,"url":"https://github.com/elastic/kibana/pull/161648","mergeCommit":{"message":"[Cloud
Security] Adding vuln filter to the scores index
(#161648)","sha":"47d099e22f537df820858a31e00f05343c026e25"}},"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/161648","number":161648,"mergeCommit":{"message":"[Cloud
Security] Adding vuln filter to the scores index
(#161648)","sha":"47d099e22f537df820858a31e00f05343c026e25"}}]}]
BACKPORT-->

Co-authored-by: Jordan <51442161+JordanSh@users.noreply.github.com>
2023-07-12 03:23:27 -07:00
Kibana Machine
79d6593e23
[8.9] [ftr] migrate time picker GUI selection to uiSettings API call (#161642) (#161725)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[ftr] migrate time picker GUI selection to uiSettings API call
(#161642)](https://github.com/elastic/kibana/pull/161642)

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

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

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-07-12T07:06:53Z","message":"[ftr]
migrate time picker GUI selection to uiSettings API call
(#161642)\n\ncloses #113998\r\n\r\nIn order to make FTR functional tests
faster and less flaky, we started\r\nmigrating time picker selection
from UI action to Kibana API call:\r\n\r\n```\r\n await
this.kibanaServer.uiSettings.update({\r\n 'timepicker:timeDefaults': `{
\"from\": <startTime>, \"to\": <endTime>}`,\r\n });\r\n```\r\n\r\nIn
this PR I updated most of the tests listed in the meta issue, so
we\r\ncan close it.\r\n\r\nFlaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2606","sha":"85a99c954f386bfa6291b266fe94a1456e312b25","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.10.0","v8.8.3","v8.9.1"],"number":161642,"url":"https://github.com/elastic/kibana/pull/161642","mergeCommit":{"message":"[ftr]
migrate time picker GUI selection to uiSettings API call
(#161642)\n\ncloses #113998\r\n\r\nIn order to make FTR functional tests
faster and less flaky, we started\r\nmigrating time picker selection
from UI action to Kibana API call:\r\n\r\n```\r\n await
this.kibanaServer.uiSettings.update({\r\n 'timepicker:timeDefaults': `{
\"from\": <startTime>, \"to\": <endTime>}`,\r\n });\r\n```\r\n\r\nIn
this PR I updated most of the tests listed in the meta issue, so
we\r\ncan close it.\r\n\r\nFlaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2606","sha":"85a99c954f386bfa6291b266fe94a1456e312b25"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9"],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161642","number":161642,"mergeCommit":{"message":"[ftr]
migrate time picker GUI selection to uiSettings API call
(#161642)\n\ncloses #113998\r\n\r\nIn order to make FTR functional tests
faster and less flaky, we started\r\nmigrating time picker selection
from UI action to Kibana API call:\r\n\r\n```\r\n await
this.kibanaServer.uiSettings.update({\r\n 'timepicker:timeDefaults': `{
\"from\": <startTime>, \"to\": <endTime>}`,\r\n });\r\n```\r\n\r\nIn
this PR I updated most of the tests listed in the meta issue, so
we\r\ncan close it.\r\n\r\nFlaky test
runner\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2606","sha":"85a99c954f386bfa6291b266fe94a1456e312b25"}},{"branch":"8.8","label":"v8.8.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
2023-07-12 01:19:08 -07:00
Steph Milovic
5a5d179d3f
[8.9] [Security solution] Create AI assistant availability model (#161027) (#161692)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security solution] Create AI assistant availability model
(#161027)](https://github.com/elastic/kibana/pull/161027)

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

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

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2023-07-10T23:37:29Z","message":"[Security
solution] Create AI assistant availability model
(#161027)","sha":"ac0630015f8fc0936b99d372924ea2e54e742c74","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting","Team:
SecuritySolution","v8.9.0","v8.10.0"],"number":161027,"url":"https://github.com/elastic/kibana/pull/161027","mergeCommit":{"message":"[Security
solution] Create AI assistant availability model
(#161027)","sha":"ac0630015f8fc0936b99d372924ea2e54e742c74"}},"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/161027","number":161027,"mergeCommit":{"message":"[Security
solution] Create AI assistant availability model
(#161027)","sha":"ac0630015f8fc0936b99d372924ea2e54e742c74"}}]}]
BACKPORT-->
2023-07-12 02:17:38 -06:00
Kibana Machine
c0dda41f80
[8.9] [Enterprise Search] Add ServiceNow connector (#161651) (#161720)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Enterprise Search] Add ServiceNow connector
(#161651)](https://github.com/elastic/kibana/pull/161651)

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

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

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-12T03:22:18Z","message":"[Enterprise
Search] Add ServiceNow connector (#161651)\n\n## Summary\r\n\r\nAdd
ServiceNow in the right
spot.","sha":"8ece07a0e9da0094f3389315373592934b394c19","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.9.0","v8.10.0"],"number":161651,"url":"https://github.com/elastic/kibana/pull/161651","mergeCommit":{"message":"[Enterprise
Search] Add ServiceNow connector (#161651)\n\n## Summary\r\n\r\nAdd
ServiceNow in the right
spot.","sha":"8ece07a0e9da0094f3389315373592934b394c19"}},"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/161651","number":161651,"mergeCommit":{"message":"[Enterprise
Search] Add ServiceNow connector (#161651)\n\n## Summary\r\n\r\nAdd
ServiceNow in the right
spot.","sha":"8ece07a0e9da0094f3389315373592934b394c19"}}]}] BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
2023-07-11 21:30:35 -07:00
Davis Plumlee
5ab9cef56b
[8.9] [Security Solution][Detection Alerts] Alert tagging follow-up (#160305) (#161715)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Detection Alerts] Alert tagging follow-up
(#160305)](https://github.com/elastic/kibana/pull/160305)

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

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

<!--BACKPORT [{"author":{"name":"Davis
Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T21:11:23Z","message":"[Security
Solution][Detection Alerts] Alert tagging follow-up
(#160305)","sha":"88fc4a66271a16808eb6386610ad41c4e43c271c","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:
SecuritySolution","backport:prev-minor","v8.9.0","v8.10.0"],"number":160305,"url":"https://github.com/elastic/kibana/pull/160305","mergeCommit":{"message":"[Security
Solution][Detection Alerts] Alert tagging follow-up
(#160305)","sha":"88fc4a66271a16808eb6386610ad41c4e43c271c"}},"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/160305","number":160305,"mergeCommit":{"message":"[Security
Solution][Detection Alerts] Alert tagging follow-up
(#160305)","sha":"88fc4a66271a16808eb6386610ad41c4e43c271c"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-07-11 17:47:36 -07:00
Kibana Machine
3596e9540e
[8.9] [Synthetics] Configure rules auto for status/tls (#161578) (#161713)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Configure rules auto for status/tls
(#161578)](https://github.com/elastic/kibana/pull/161578)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-11T20:47:43Z","message":"[Synthetics]
Configure rules auto for status/tls (#161578)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/161197\n\n<img width=\"1906\"
alt=\"image\"\nsrc=\"37942f97-c44e-473a-9753-e6dcd4694d3c\">","sha":"7f8310982d1d32ff9f225f661d2f375abb922a0d","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161578,"url":"https://github.com/elastic/kibana/pull/161578","mergeCommit":{"message":"[Synthetics]
Configure rules auto for status/tls (#161578)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/161197\n\n<img width=\"1906\"
alt=\"image\"\nsrc=\"37942f97-c44e-473a-9753-e6dcd4694d3c\">","sha":"7f8310982d1d32ff9f225f661d2f375abb922a0d"}},"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/161578","number":161578,"mergeCommit":{"message":"[Synthetics]
Configure rules auto for status/tls (#161578)\n\n## Summary\n\nFixes
https://github.com/elastic/kibana/issues/161197\n\n<img width=\"1906\"
alt=\"image\"\nsrc=\"37942f97-c44e-473a-9753-e6dcd4694d3c\">","sha":"7f8310982d1d32ff9f225f661d2f375abb922a0d"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-11 14:58:17 -07:00
Kibana Machine
6faee304fe
[8.9] Changing where CodeEditor fields get useDarkMode value (#159638) (#161707)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Changing where CodeEditor fields get useDarkMode value
(#159638)](https://github.com/elastic/kibana/pull/159638)

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

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

<!--BACKPORT
[{"author":{"name":"Kurt","email":"kc13greiner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T18:02:42Z","message":"Changing
where CodeEditor fields get useDarkMode value (#159638)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/157203\r\nCloses
https://github.com/elastic/kibana/issues/158051\r\nCloses
https://github.com/elastic/kibana/issues/158049\r\n\r\nWith the addition
of Per User Dark Mode, components can no longer rely\r\non `uiSettings`
as the source of truth for theme.\r\n\r\nCodeEditor fields used to call
`uiSettings` to determine if Dark Mode\r\nwas enabled, which had been
provided in each callers Kibana React\r\nContext.\r\n\r\nThe new source
of truth for theme is the `CoreStart
>\r\nThemeServiceStart`.\r\n\r\nCurrently, not all callers of CodeEditor
provide the `theme` service in\r\ntheir Kibana Context in a similar way
and some callers don't provide it\r\nat all.\r\n\r\nThis PR updates
CodeEditor to get theme values from the Kibana Context\r\nusing a new
`useKibanaTheme` react hook.\r\n\r\nIt also attempts audit the callers
of CodeEditor to see if their Kibana\r\nContext contains the theme
service at the top level (Where I could add\r\ntheme to a caller's
Context without major changes, I did. Some cases\r\nwill require
CodeOwner guidance).\r\n\r\nThe new `useKibanaTheme` react hook will
throw a TypeError if theme\r\nisn't found in the top level of the Kibana
Context, this will help with\r\ntesting as the component will not
render. I will remove this after\r\ntesting so as not to introduce
breaking changes.\r\n\r\n## Testing\r\n\r\nPlease review files for which
you are CODEOWNER.\r\n\r\nI've attempted to tag all usages of
`CodeEditor`/`CodeEditorFIeld` with\r\na TODO comment with one of the
following scenarios:\r\n\r\n1) a note where theme was provided
already/where I made changes to\r\nprovide it in the appropriate
context\r\n2) I've asked for CODEOWNER guidance\r\n\r\nFor scenario 1,
please pull and test that CodeEditor locally:\r\n\r\n1. Enable Dark Mode
from Edit User Profiles by clicking on the Profile\r\nIcon on the top
right, and updating your profile.\r\n2. Navigate to the CodeEditors in
the plugins you own. If they render\r\nand display in Dark Mode - add a
green check to the table below - and\r\nyou're done!\r\n3. If it is not
rendering, please help me figure out where the theme\r\nservice should
be provided in the context.\r\n\r\nFor scenario 2, we will need to
figure out where to make changes so your\r\ncontext is providing theme.
Some of the more complex usages may need to\r\naddressed in separate
issues.\r\n\r\n\r\n## Tracking\r\n| Team | Plugin | Theme in Context ? |
Verified Working |\r\n| - | - | - | - |\r\n| apm-ui | apm | APM
Storybook broken | ? |\r\n| kibana-presentation | presentation_util |
Yes. | Yes |\r\n| response-ops | trigger_actions_ui | Yes | Yes |\r\n|
response-ops | stack_alerts | Yes | Yes |\r\n| kibana-security |
security | Yes | Yes |\r\n| security-defend-workflows | osquery | Yes |
Yes |\r\n| kibana-app-services | examples/expression_explorer | Yes |
Yes |\r\n| ml-ui | transform | Yes | Yes |\r\n| ml-ui | ml | Yes | Yes
|\r\n| uptime | synthetics | Yes | Yes |\r\n| kibana-gis | maps | Yes |
Yes |\r\n| kibana-gis | file_upload | Yes | Yes |\r\n|
platform-deployment-management | watcher | Yes | [AG] Yes |\r\n|
platform-deployment-management | snapshot_restore | Yes | [AG] Yes
|\r\n| platform-deployment-management | runtime_fields | Yes | [AG] Yes
|\r\n| platform-deployment-management | painless_lab | Yes | [AG] Yes
|\r\n| platform-deployment-management | ingest_pipelines | Yes | [AG]
Yes |\r\n| platform-deployment-management | index_management | Yes |
[AG] Yes |\r\n| platform-deployment-management | grokdebugger | Yes |
[AG] Yes |\r\n| platform-deployment-management | es_ui_shared | Yes |
[AG] Yes |\r\n| fleet | fleet | Yes | Yes |\r\n|
enterprise-search-frontend | enterprise_search | Yes | [AG] Yes |\r\n|
kibana-cloud-security-posture | cloud-security-posture | Yes | yes
|\r\n| sec-cloudnative-integrations | cloud_defend | Yes | Yes |\r\n|
kibana-visualizations/kibana-data-discovery | data | Yes | Yes |\r\n|
kibana-visualizations | examples/testing_embedded_lens | Yes | Yes
|\r\n| kibana-visualizations | vis_types | Yes | Yes |\r\n|
kibana-visualizations | vis_default_editor | Yes | Yes |\r\n|
kibana-visualizations | unified_search | Yes | Yes |\r\n|
kibana-visualizations | packages/kbn-text-based-editor | Yes | Yes
|\r\n| kibana-visualizatons | lens | Yes | Yes|\r\n| kibana-core |
saved_objects_management | Yes | Yes |\r\n| kibana-presentation |
inspector | Yes | Yes |\r\n| kibana-presentation | canvas | Yes | Yes
|\r\n| kibana-data-discovery | discover | Yes | Yes |\r\n|
kibana-data-discovery | data_view_management | Yes | Yes |\r\n|
kibana-data-discovery | data_view_field_editor | Yes | Yes |\r\n|
appex-sharedux | advanced_settings | Yes | Yes |\r\n|
enterprise-search-frontend | serverless_search | Yes | [AG] Yes |\r\n| -
| - | - | - |\r\n\r\n## Unit tests\r\n\r\nCurrently, many tests are
failing since they are probably not providing\r\n`theme` in the context.
Once CODEOWNERs have weighed in on CodeEditors\r\nusages that require
discussion, I will update the accompanying tests.\r\n\r\n## Release
note\r\n- Fixes theming of
CodeEditors\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alison Goryachev <alisonmllr20@gmail.com>\r\nCo-authored-by: Dima
Arnautov <dmitrii.arnautov@elastic.co>\r\nCo-authored-by: Dima Arnautov
<arnautov.dima@gmail.com>","sha":"323b0477e35cb3e49cc01b56b23969fb72c7111e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:APM","Team:Security","Team:uptime","Feature:Drilldowns","Team:Fleet","Feature:Security/User
Profile","backport:prev-minor","v8.10.0"],"number":159638,"url":"https://github.com/elastic/kibana/pull/159638","mergeCommit":{"message":"Changing
where CodeEditor fields get useDarkMode value (#159638)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/157203\r\nCloses
https://github.com/elastic/kibana/issues/158051\r\nCloses
https://github.com/elastic/kibana/issues/158049\r\n\r\nWith the addition
of Per User Dark Mode, components can no longer rely\r\non `uiSettings`
as the source of truth for theme.\r\n\r\nCodeEditor fields used to call
`uiSettings` to determine if Dark Mode\r\nwas enabled, which had been
provided in each callers Kibana React\r\nContext.\r\n\r\nThe new source
of truth for theme is the `CoreStart
>\r\nThemeServiceStart`.\r\n\r\nCurrently, not all callers of CodeEditor
provide the `theme` service in\r\ntheir Kibana Context in a similar way
and some callers don't provide it\r\nat all.\r\n\r\nThis PR updates
CodeEditor to get theme values from the Kibana Context\r\nusing a new
`useKibanaTheme` react hook.\r\n\r\nIt also attempts audit the callers
of CodeEditor to see if their Kibana\r\nContext contains the theme
service at the top level (Where I could add\r\ntheme to a caller's
Context without major changes, I did. Some cases\r\nwill require
CodeOwner guidance).\r\n\r\nThe new `useKibanaTheme` react hook will
throw a TypeError if theme\r\nisn't found in the top level of the Kibana
Context, this will help with\r\ntesting as the component will not
render. I will remove this after\r\ntesting so as not to introduce
breaking changes.\r\n\r\n## Testing\r\n\r\nPlease review files for which
you are CODEOWNER.\r\n\r\nI've attempted to tag all usages of
`CodeEditor`/`CodeEditorFIeld` with\r\na TODO comment with one of the
following scenarios:\r\n\r\n1) a note where theme was provided
already/where I made changes to\r\nprovide it in the appropriate
context\r\n2) I've asked for CODEOWNER guidance\r\n\r\nFor scenario 1,
please pull and test that CodeEditor locally:\r\n\r\n1. Enable Dark Mode
from Edit User Profiles by clicking on the Profile\r\nIcon on the top
right, and updating your profile.\r\n2. Navigate to the CodeEditors in
the plugins you own. If they render\r\nand display in Dark Mode - add a
green check to the table below - and\r\nyou're done!\r\n3. If it is not
rendering, please help me figure out where the theme\r\nservice should
be provided in the context.\r\n\r\nFor scenario 2, we will need to
figure out where to make changes so your\r\ncontext is providing theme.
Some of the more complex usages may need to\r\naddressed in separate
issues.\r\n\r\n\r\n## Tracking\r\n| Team | Plugin | Theme in Context ? |
Verified Working |\r\n| - | - | - | - |\r\n| apm-ui | apm | APM
Storybook broken | ? |\r\n| kibana-presentation | presentation_util |
Yes. | Yes |\r\n| response-ops | trigger_actions_ui | Yes | Yes |\r\n|
response-ops | stack_alerts | Yes | Yes |\r\n| kibana-security |
security | Yes | Yes |\r\n| security-defend-workflows | osquery | Yes |
Yes |\r\n| kibana-app-services | examples/expression_explorer | Yes |
Yes |\r\n| ml-ui | transform | Yes | Yes |\r\n| ml-ui | ml | Yes | Yes
|\r\n| uptime | synthetics | Yes | Yes |\r\n| kibana-gis | maps | Yes |
Yes |\r\n| kibana-gis | file_upload | Yes | Yes |\r\n|
platform-deployment-management | watcher | Yes | [AG] Yes |\r\n|
platform-deployment-management | snapshot_restore | Yes | [AG] Yes
|\r\n| platform-deployment-management | runtime_fields | Yes | [AG] Yes
|\r\n| platform-deployment-management | painless_lab | Yes | [AG] Yes
|\r\n| platform-deployment-management | ingest_pipelines | Yes | [AG]
Yes |\r\n| platform-deployment-management | index_management | Yes |
[AG] Yes |\r\n| platform-deployment-management | grokdebugger | Yes |
[AG] Yes |\r\n| platform-deployment-management | es_ui_shared | Yes |
[AG] Yes |\r\n| fleet | fleet | Yes | Yes |\r\n|
enterprise-search-frontend | enterprise_search | Yes | [AG] Yes |\r\n|
kibana-cloud-security-posture | cloud-security-posture | Yes | yes
|\r\n| sec-cloudnative-integrations | cloud_defend | Yes | Yes |\r\n|
kibana-visualizations/kibana-data-discovery | data | Yes | Yes |\r\n|
kibana-visualizations | examples/testing_embedded_lens | Yes | Yes
|\r\n| kibana-visualizations | vis_types | Yes | Yes |\r\n|
kibana-visualizations | vis_default_editor | Yes | Yes |\r\n|
kibana-visualizations | unified_search | Yes | Yes |\r\n|
kibana-visualizations | packages/kbn-text-based-editor | Yes | Yes
|\r\n| kibana-visualizatons | lens | Yes | Yes|\r\n| kibana-core |
saved_objects_management | Yes | Yes |\r\n| kibana-presentation |
inspector | Yes | Yes |\r\n| kibana-presentation | canvas | Yes | Yes
|\r\n| kibana-data-discovery | discover | Yes | Yes |\r\n|
kibana-data-discovery | data_view_management | Yes | Yes |\r\n|
kibana-data-discovery | data_view_field_editor | Yes | Yes |\r\n|
appex-sharedux | advanced_settings | Yes | Yes |\r\n|
enterprise-search-frontend | serverless_search | Yes | [AG] Yes |\r\n| -
| - | - | - |\r\n\r\n## Unit tests\r\n\r\nCurrently, many tests are
failing since they are probably not providing\r\n`theme` in the context.
Once CODEOWNERs have weighed in on CodeEditors\r\nusages that require
discussion, I will update the accompanying tests.\r\n\r\n## Release
note\r\n- Fixes theming of
CodeEditors\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alison Goryachev <alisonmllr20@gmail.com>\r\nCo-authored-by: Dima
Arnautov <dmitrii.arnautov@elastic.co>\r\nCo-authored-by: Dima Arnautov
<arnautov.dima@gmail.com>","sha":"323b0477e35cb3e49cc01b56b23969fb72c7111e"}},"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/159638","number":159638,"mergeCommit":{"message":"Changing
where CodeEditor fields get useDarkMode value (#159638)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/157203\r\nCloses
https://github.com/elastic/kibana/issues/158051\r\nCloses
https://github.com/elastic/kibana/issues/158049\r\n\r\nWith the addition
of Per User Dark Mode, components can no longer rely\r\non `uiSettings`
as the source of truth for theme.\r\n\r\nCodeEditor fields used to call
`uiSettings` to determine if Dark Mode\r\nwas enabled, which had been
provided in each callers Kibana React\r\nContext.\r\n\r\nThe new source
of truth for theme is the `CoreStart
>\r\nThemeServiceStart`.\r\n\r\nCurrently, not all callers of CodeEditor
provide the `theme` service in\r\ntheir Kibana Context in a similar way
and some callers don't provide it\r\nat all.\r\n\r\nThis PR updates
CodeEditor to get theme values from the Kibana Context\r\nusing a new
`useKibanaTheme` react hook.\r\n\r\nIt also attempts audit the callers
of CodeEditor to see if their Kibana\r\nContext contains the theme
service at the top level (Where I could add\r\ntheme to a caller's
Context without major changes, I did. Some cases\r\nwill require
CodeOwner guidance).\r\n\r\nThe new `useKibanaTheme` react hook will
throw a TypeError if theme\r\nisn't found in the top level of the Kibana
Context, this will help with\r\ntesting as the component will not
render. I will remove this after\r\ntesting so as not to introduce
breaking changes.\r\n\r\n## Testing\r\n\r\nPlease review files for which
you are CODEOWNER.\r\n\r\nI've attempted to tag all usages of
`CodeEditor`/`CodeEditorFIeld` with\r\na TODO comment with one of the
following scenarios:\r\n\r\n1) a note where theme was provided
already/where I made changes to\r\nprovide it in the appropriate
context\r\n2) I've asked for CODEOWNER guidance\r\n\r\nFor scenario 1,
please pull and test that CodeEditor locally:\r\n\r\n1. Enable Dark Mode
from Edit User Profiles by clicking on the Profile\r\nIcon on the top
right, and updating your profile.\r\n2. Navigate to the CodeEditors in
the plugins you own. If they render\r\nand display in Dark Mode - add a
green check to the table below - and\r\nyou're done!\r\n3. If it is not
rendering, please help me figure out where the theme\r\nservice should
be provided in the context.\r\n\r\nFor scenario 2, we will need to
figure out where to make changes so your\r\ncontext is providing theme.
Some of the more complex usages may need to\r\naddressed in separate
issues.\r\n\r\n\r\n## Tracking\r\n| Team | Plugin | Theme in Context ? |
Verified Working |\r\n| - | - | - | - |\r\n| apm-ui | apm | APM
Storybook broken | ? |\r\n| kibana-presentation | presentation_util |
Yes. | Yes |\r\n| response-ops | trigger_actions_ui | Yes | Yes |\r\n|
response-ops | stack_alerts | Yes | Yes |\r\n| kibana-security |
security | Yes | Yes |\r\n| security-defend-workflows | osquery | Yes |
Yes |\r\n| kibana-app-services | examples/expression_explorer | Yes |
Yes |\r\n| ml-ui | transform | Yes | Yes |\r\n| ml-ui | ml | Yes | Yes
|\r\n| uptime | synthetics | Yes | Yes |\r\n| kibana-gis | maps | Yes |
Yes |\r\n| kibana-gis | file_upload | Yes | Yes |\r\n|
platform-deployment-management | watcher | Yes | [AG] Yes |\r\n|
platform-deployment-management | snapshot_restore | Yes | [AG] Yes
|\r\n| platform-deployment-management | runtime_fields | Yes | [AG] Yes
|\r\n| platform-deployment-management | painless_lab | Yes | [AG] Yes
|\r\n| platform-deployment-management | ingest_pipelines | Yes | [AG]
Yes |\r\n| platform-deployment-management | index_management | Yes |
[AG] Yes |\r\n| platform-deployment-management | grokdebugger | Yes |
[AG] Yes |\r\n| platform-deployment-management | es_ui_shared | Yes |
[AG] Yes |\r\n| fleet | fleet | Yes | Yes |\r\n|
enterprise-search-frontend | enterprise_search | Yes | [AG] Yes |\r\n|
kibana-cloud-security-posture | cloud-security-posture | Yes | yes
|\r\n| sec-cloudnative-integrations | cloud_defend | Yes | Yes |\r\n|
kibana-visualizations/kibana-data-discovery | data | Yes | Yes |\r\n|
kibana-visualizations | examples/testing_embedded_lens | Yes | Yes
|\r\n| kibana-visualizations | vis_types | Yes | Yes |\r\n|
kibana-visualizations | vis_default_editor | Yes | Yes |\r\n|
kibana-visualizations | unified_search | Yes | Yes |\r\n|
kibana-visualizations | packages/kbn-text-based-editor | Yes | Yes
|\r\n| kibana-visualizatons | lens | Yes | Yes|\r\n| kibana-core |
saved_objects_management | Yes | Yes |\r\n| kibana-presentation |
inspector | Yes | Yes |\r\n| kibana-presentation | canvas | Yes | Yes
|\r\n| kibana-data-discovery | discover | Yes | Yes |\r\n|
kibana-data-discovery | data_view_management | Yes | Yes |\r\n|
kibana-data-discovery | data_view_field_editor | Yes | Yes |\r\n|
appex-sharedux | advanced_settings | Yes | Yes |\r\n|
enterprise-search-frontend | serverless_search | Yes | [AG] Yes |\r\n| -
| - | - | - |\r\n\r\n## Unit tests\r\n\r\nCurrently, many tests are
failing since they are probably not providing\r\n`theme` in the context.
Once CODEOWNERs have weighed in on CodeEditors\r\nusages that require
discussion, I will update the accompanying tests.\r\n\r\n## Release
note\r\n- Fixes theming of
CodeEditors\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Alison Goryachev <alisonmllr20@gmail.com>\r\nCo-authored-by: Dima
Arnautov <dmitrii.arnautov@elastic.co>\r\nCo-authored-by: Dima Arnautov
<arnautov.dima@gmail.com>","sha":"323b0477e35cb3e49cc01b56b23969fb72c7111e"}}]}]
BACKPORT-->

Co-authored-by: Kurt <kc13greiner@users.noreply.github.com>
2023-07-11 14:14:37 -07:00
Kibana Machine
c1d0010b77
[8.9] [Security Solution] Close the assistant dialog on add to case #6973 (#161686) (#161705)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Close the assistant dialog on add to case #6973
(#161686)](https://github.com/elastic/kibana/pull/161686)

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

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

<!--BACKPORT
[{"author":{"name":"Luke","email":"11671118+lgestc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T18:57:43Z","message":"[Security
Solution] Close the assistant dialog on add to case #6973
(#161686)","sha":"26334b5111ca2347176ac221872d3341f83205be","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","Feature:Elastic
Assistant","v8.10.0"],"number":161686,"url":"https://github.com/elastic/kibana/pull/161686","mergeCommit":{"message":"[Security
Solution] Close the assistant dialog on add to case #6973
(#161686)","sha":"26334b5111ca2347176ac221872d3341f83205be"}},"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/161686","number":161686,"mergeCommit":{"message":"[Security
Solution] Close the assistant dialog on add to case #6973
(#161686)","sha":"26334b5111ca2347176ac221872d3341f83205be"}}]}]
BACKPORT-->

Co-authored-by: Luke <11671118+lgestc@users.noreply.github.com>
2023-07-11 13:20:30 -07:00
Kibana Machine
ba98a47614
[8.9] [Detection Engine] - Unskip flakey test after running through test runner (#161566) (#161704)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Detection Engine] - Unskip flakey test after running through test
runner (#161566)](https://github.com/elastic/kibana/pull/161566)

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

### 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-07-11T18:48:19Z","message":"[Detection
Engine] - Unskip flakey test after running through test runner
(#161566)\n\n## Summary\r\n\r\nResolving 155122 . Unskipping\r\nafter
running through flakey test runner 100
times.","sha":"fc53c18fa4adcbca5d195991c9581187512a5e78","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","v8.9.0","Team:Detection
Engine","v8.10.0"],"number":161566,"url":"https://github.com/elastic/kibana/pull/161566","mergeCommit":{"message":"[Detection
Engine] - Unskip flakey test after running through test runner
(#161566)\n\n## Summary\r\n\r\nResolving 155122 . Unskipping\r\nafter
running through flakey test runner 100
times.","sha":"fc53c18fa4adcbca5d195991c9581187512a5e78"}},"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/161566","number":161566,"mergeCommit":{"message":"[Detection
Engine] - Unskip flakey test after running through test runner
(#161566)\n\n## Summary\r\n\r\nResolving 155122 . Unskipping\r\nafter
running through flakey test runner 100
times.","sha":"fc53c18fa4adcbca5d195991c9581187512a5e78"}}]}]
BACKPORT-->

Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
2023-07-11 12:46:18 -07:00
Kibana Machine
421a072903
[8.9] [Security Solution][Security Assistant] Investigate in timeline control should be visible only on eligible queries. (#161240) (#161701)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution][Security Assistant] Investigate in timeline
control should be visible only on eligible queries.
(#161240)](https://github.com/elastic/kibana/pull/161240)

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

### 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-07-11T18:09:33Z","message":"[Security
Solution][Security Assistant] Investigate in timeline control should be
visible only on eligible queries. (#161240)\n\n## Summary\r\n\r\nHandles
elastic/security-team#6971\r\n\r\nThis PR mainly resolved below 3
issues:\r\n\r\n### Rename to `Add To Timeline` control in conversation
code blocks to\r\n`Investigate in Timeline`\r\n \r\n- `Add to Timeline`
according to existing Security Solution actions\r\nmeans, adding a
condition to the timeline with an `OR` clause without\r\naffecting the
existing Timeline.\r\n\r\n- But the `Add to Timeline` control in the
Security Assistant, creates a\r\nnew timeline on each action by the
user, which contradicts the above\r\nworkflow. Hence, it might confuse
user.\r\n\r\n- `Investigate in Timeline` already means that a new
timeline will be\r\ncreated.\r\n\r\n### `Add To Timeline` control was
visible on types of codeblock. For\r\nexample, it does not make sense
for a `Query DSL` to have an `Add to\r\nTimeline` control.\r\n\r\n- This
PR adds the list of eligible types of queries/code blocks on\r\nwhich
`Add To Timeline` action can be added.\r\n\r\n- Currently, that list
only contains `kql`, `dsl` and `eql`. Below is\r\nthe complete list of
types of query that can occur in code blocks.\r\n\r\n- Please feel free
to suggest a change.\r\n ```\r\n 'eql' | 'kql' | 'dsl' | 'json' |
'no-type';\r\n ```\r\n\r\n### Lazy calculation of CodeBlockPortals and
CodeBlock Action container\r\n\r\n- To add controls to the conversation
code blocks, we need to follow\r\nbelow 2 steps.\r\n 1. get the
codeBlock containers on which the controls can be added.\r\n2. create
portals in the HTML container with our `Add to Timeline`\r\ncontrol.\r\n
\r\n- Below are issues these steps sometime created.\r\n1. We get
codeBlock container in the `useLayoutEffect` but at the time,\r\nall
conversations might not have loaded because of which containers
are\r\nreturns as the undefined.\r\n2. Then, we try to create portal in
the `undefined` container, which\r\nfails and hence, `Add to Timeline`
controls are not visible.\r\n \r\n- Solution:\r\n1. Instead of getting
the codeblock container in useLayoutEffect, we get\r\nthe function which
will eventually return that container, whenever we\r\nare creating the
portal.\r\n2. Converted codeBlock Portal to a callback such that
callback can be\r\ncalled during the rendering which makes sure that all
needed\r\nconversations are available and using above step we can easily
get the\r\nportal containers.\r\nFeel free to let me know if there are
any issues with above strategy. \r\n\r\n### Better Pattern
matching.\r\n\r\n- Currently, when we are trying to identify the type of
codeblock it\r\nmight result in unexpected output because of below
reason.\r\n1. Let say, we are trying to identify KQL Query and for that
we use\r\nbelow phrases to match in the `OpenAI` response.\r\n `'Kibana
Query Language', 'KQL Query'`\r\n2. Because of this, if the `OpenAI`
response contains the phrase `KQL\r\nquery` or `kql query`, that fails
because of case senstivity when\r\nsearching the above phrases.\r\n 3.
This PR makes that part of pattern matching case
insensitive\r\n\r\n\r\n###
Before\r\n\r\n\r\n\r\nb472178a-0145-42d8-8fb9-ab107915086a\r\n\r\n\r\n\r\n###
After\r\n\r\n\r\nb499f099-a7a1-435f-99b2-ab27ee1f5680\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- [x] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard
accessibility](https://webaim.org/techniques/keyboard/))","sha":"091b5c133b4d5e969d39f92d0c7338aa449d64c0","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting:Investigations","v8.9.0","v8.10.0"],"number":161240,"url":"https://github.com/elastic/kibana/pull/161240","mergeCommit":{"message":"[Security
Solution][Security Assistant] Investigate in timeline control should be
visible only on eligible queries. (#161240)\n\n## Summary\r\n\r\nHandles
elastic/security-team#6971\r\n\r\nThis PR mainly resolved below 3
issues:\r\n\r\n### Rename to `Add To Timeline` control in conversation
code blocks to\r\n`Investigate in Timeline`\r\n \r\n- `Add to Timeline`
according to existing Security Solution actions\r\nmeans, adding a
condition to the timeline with an `OR` clause without\r\naffecting the
existing Timeline.\r\n\r\n- But the `Add to Timeline` control in the
Security Assistant, creates a\r\nnew timeline on each action by the
user, which contradicts the above\r\nworkflow. Hence, it might confuse
user.\r\n\r\n- `Investigate in Timeline` already means that a new
timeline will be\r\ncreated.\r\n\r\n### `Add To Timeline` control was
visible on types of codeblock. For\r\nexample, it does not make sense
for a `Query DSL` to have an `Add to\r\nTimeline` control.\r\n\r\n- This
PR adds the list of eligible types of queries/code blocks on\r\nwhich
`Add To Timeline` action can be added.\r\n\r\n- Currently, that list
only contains `kql`, `dsl` and `eql`. Below is\r\nthe complete list of
types of query that can occur in code blocks.\r\n\r\n- Please feel free
to suggest a change.\r\n ```\r\n 'eql' | 'kql' | 'dsl' | 'json' |
'no-type';\r\n ```\r\n\r\n### Lazy calculation of CodeBlockPortals and
CodeBlock Action container\r\n\r\n- To add controls to the conversation
code blocks, we need to follow\r\nbelow 2 steps.\r\n 1. get the
codeBlock containers on which the controls can be added.\r\n2. create
portals in the HTML container with our `Add to Timeline`\r\ncontrol.\r\n
\r\n- Below are issues these steps sometime created.\r\n1. We get
codeBlock container in the `useLayoutEffect` but at the time,\r\nall
conversations might not have loaded because of which containers
are\r\nreturns as the undefined.\r\n2. Then, we try to create portal in
the `undefined` container, which\r\nfails and hence, `Add to Timeline`
controls are not visible.\r\n \r\n- Solution:\r\n1. Instead of getting
the codeblock container in useLayoutEffect, we get\r\nthe function which
will eventually return that container, whenever we\r\nare creating the
portal.\r\n2. Converted codeBlock Portal to a callback such that
callback can be\r\ncalled during the rendering which makes sure that all
needed\r\nconversations are available and using above step we can easily
get the\r\nportal containers.\r\nFeel free to let me know if there are
any issues with above strategy. \r\n\r\n### Better Pattern
matching.\r\n\r\n- Currently, when we are trying to identify the type of
codeblock it\r\nmight result in unexpected output because of below
reason.\r\n1. Let say, we are trying to identify KQL Query and for that
we use\r\nbelow phrases to match in the `OpenAI` response.\r\n `'Kibana
Query Language', 'KQL Query'`\r\n2. Because of this, if the `OpenAI`
response contains the phrase `KQL\r\nquery` or `kql query`, that fails
because of case senstivity when\r\nsearching the above phrases.\r\n 3.
This PR makes that part of pattern matching case
insensitive\r\n\r\n\r\n###
Before\r\n\r\n\r\n\r\nb472178a-0145-42d8-8fb9-ab107915086a\r\n\r\n\r\n\r\n###
After\r\n\r\n\r\nb499f099-a7a1-435f-99b2-ab27ee1f5680\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- [x] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard
accessibility](https://webaim.org/techniques/keyboard/))","sha":"091b5c133b4d5e969d39f92d0c7338aa449d64c0"}},"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/161240","number":161240,"mergeCommit":{"message":"[Security
Solution][Security Assistant] Investigate in timeline control should be
visible only on eligible queries. (#161240)\n\n## Summary\r\n\r\nHandles
elastic/security-team#6971\r\n\r\nThis PR mainly resolved below 3
issues:\r\n\r\n### Rename to `Add To Timeline` control in conversation
code blocks to\r\n`Investigate in Timeline`\r\n \r\n- `Add to Timeline`
according to existing Security Solution actions\r\nmeans, adding a
condition to the timeline with an `OR` clause without\r\naffecting the
existing Timeline.\r\n\r\n- But the `Add to Timeline` control in the
Security Assistant, creates a\r\nnew timeline on each action by the
user, which contradicts the above\r\nworkflow. Hence, it might confuse
user.\r\n\r\n- `Investigate in Timeline` already means that a new
timeline will be\r\ncreated.\r\n\r\n### `Add To Timeline` control was
visible on types of codeblock. For\r\nexample, it does not make sense
for a `Query DSL` to have an `Add to\r\nTimeline` control.\r\n\r\n- This
PR adds the list of eligible types of queries/code blocks on\r\nwhich
`Add To Timeline` action can be added.\r\n\r\n- Currently, that list
only contains `kql`, `dsl` and `eql`. Below is\r\nthe complete list of
types of query that can occur in code blocks.\r\n\r\n- Please feel free
to suggest a change.\r\n ```\r\n 'eql' | 'kql' | 'dsl' | 'json' |
'no-type';\r\n ```\r\n\r\n### Lazy calculation of CodeBlockPortals and
CodeBlock Action container\r\n\r\n- To add controls to the conversation
code blocks, we need to follow\r\nbelow 2 steps.\r\n 1. get the
codeBlock containers on which the controls can be added.\r\n2. create
portals in the HTML container with our `Add to Timeline`\r\ncontrol.\r\n
\r\n- Below are issues these steps sometime created.\r\n1. We get
codeBlock container in the `useLayoutEffect` but at the time,\r\nall
conversations might not have loaded because of which containers
are\r\nreturns as the undefined.\r\n2. Then, we try to create portal in
the `undefined` container, which\r\nfails and hence, `Add to Timeline`
controls are not visible.\r\n \r\n- Solution:\r\n1. Instead of getting
the codeblock container in useLayoutEffect, we get\r\nthe function which
will eventually return that container, whenever we\r\nare creating the
portal.\r\n2. Converted codeBlock Portal to a callback such that
callback can be\r\ncalled during the rendering which makes sure that all
needed\r\nconversations are available and using above step we can easily
get the\r\nportal containers.\r\nFeel free to let me know if there are
any issues with above strategy. \r\n\r\n### Better Pattern
matching.\r\n\r\n- Currently, when we are trying to identify the type of
codeblock it\r\nmight result in unexpected output because of below
reason.\r\n1. Let say, we are trying to identify KQL Query and for that
we use\r\nbelow phrases to match in the `OpenAI` response.\r\n `'Kibana
Query Language', 'KQL Query'`\r\n2. Because of this, if the `OpenAI`
response contains the phrase `KQL\r\nquery` or `kql query`, that fails
because of case senstivity when\r\nsearching the above phrases.\r\n 3.
This PR makes that part of pattern matching case
insensitive\r\n\r\n\r\n###
Before\r\n\r\n\r\n\r\nb472178a-0145-42d8-8fb9-ab107915086a\r\n\r\n\r\n\r\n###
After\r\n\r\n\r\nb499f099-a7a1-435f-99b2-ab27ee1f5680\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- [x] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard
accessibility](https://webaim.org/techniques/keyboard/))","sha":"091b5c133b4d5e969d39f92d0c7338aa449d64c0"}}]}]
BACKPORT-->

Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>
2023-07-11 12:18:35 -07:00
Kibana Machine
03539c0852
[8.9] [RAM] Remove allow slack channels (#161674) (#161691)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[RAM] Remove allow slack channels
(#161674)](https://github.com/elastic/kibana/pull/161674)

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

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

<!--BACKPORT [{"author":{"name":"Xavier
Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T17:25:20Z","message":"[RAM]
Remove allow slack channels (#161674)\n\n## Summary\r\n\r\nRemove allow
slack channels feature for 8.9 until we have a better way\r\nto deal
with channels\r\n\r\n\r\n### Checklist\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"dd292b70b7fc121dcef4fad84b979d730b6c6f6e","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:critical","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.9.0","v8.10.0"],"number":161674,"url":"https://github.com/elastic/kibana/pull/161674","mergeCommit":{"message":"[RAM]
Remove allow slack channels (#161674)\n\n## Summary\r\n\r\nRemove allow
slack channels feature for 8.9 until we have a better way\r\nto deal
with channels\r\n\r\n\r\n### Checklist\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"dd292b70b7fc121dcef4fad84b979d730b6c6f6e"}},"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/161674","number":161674,"mergeCommit":{"message":"[RAM]
Remove allow slack channels (#161674)\n\n## Summary\r\n\r\nRemove allow
slack channels feature for 8.9 until we have a better way\r\nto deal
with channels\r\n\r\n\r\n### Checklist\r\n\r\n- [X] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"dd292b70b7fc121dcef4fad84b979d730b6c6f6e"}}]}]
BACKPORT-->

Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
2023-07-11 11:35:22 -07:00
Kibana Machine
047253e4b0
[8.9] [DOCS] Edits FormatNumber examples for rule action variables (#161678) (#161695)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Edits FormatNumber examples for rule action variables
(#161678)](https://github.com/elastic/kibana/pull/161678)

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

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T17:39:30Z","message":"[DOCS]
Edits FormatNumber examples for rule action variables
(#161678)","sha":"4ce8b3f4ebb602030ad1a7dbbc999e5128ad3daa","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Actions","Team:ResponseOps","docs","backport:prev-minor","v8.9.0","v8.10.0"],"number":161678,"url":"https://github.com/elastic/kibana/pull/161678","mergeCommit":{"message":"[DOCS]
Edits FormatNumber examples for rule action variables
(#161678)","sha":"4ce8b3f4ebb602030ad1a7dbbc999e5128ad3daa"}},"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/161678","number":161678,"mergeCommit":{"message":"[DOCS]
Edits FormatNumber examples for rule action variables
(#161678)","sha":"4ce8b3f4ebb602030ad1a7dbbc999e5128ad3daa"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-07-11 14:04:23 -04:00
Kibana Machine
e34e8bcd74
[8.9] [Security Solution] Add validations for insight form in timeline and rules (#161034) (#161679)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Add validations for insight form in timeline and
rules (#161034)](https://github.com/elastic/kibana/pull/161034)

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

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

<!--BACKPORT
[{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T16:13:02Z","message":"[Security
Solution] Add validations for insight form in timeline and rules
(#161034)\n\n## Summary\r\n\r\nCurrently user can add a note in timeline
with invalid markdown syntax\r\nin insight forms. Same goes to the
investigation guide in rule creation\r\n-> About.\r\n\r\n###
Before\r\n**In timeline ->
Notes**\r\n\r\n![image](33b05592-f97a-41d8-a394-fc111f4cc039)\r\n\r\n\r\n**On
rules ->
about**\r\n\r\n![image](ca09ac1a-7798-4b13-820b-85e5cf0f61c7)\r\n\r\n\r\n###
After\r\n**Timeline -> Notes**\r\nAdd note button should be disabled if
markdown is
invalid\r\n\r\n![image](d34b0ab1-c39b-443a-a309-00aba251731e)\r\n\r\n**On
rules -> about**\r\nField is red if markdown is
invalid\r\n\r\n![image](850f9f4a-71a7-44f8-a9e1-bbfbdb07b0dd)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"08a57b9e3a570329c4f8051dcf195fe80e691eb3","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Investigations","v8.9.0","v8.10.0"],"number":161034,"url":"https://github.com/elastic/kibana/pull/161034","mergeCommit":{"message":"[Security
Solution] Add validations for insight form in timeline and rules
(#161034)\n\n## Summary\r\n\r\nCurrently user can add a note in timeline
with invalid markdown syntax\r\nin insight forms. Same goes to the
investigation guide in rule creation\r\n-> About.\r\n\r\n###
Before\r\n**In timeline ->
Notes**\r\n\r\n![image](33b05592-f97a-41d8-a394-fc111f4cc039)\r\n\r\n\r\n**On
rules ->
about**\r\n\r\n![image](ca09ac1a-7798-4b13-820b-85e5cf0f61c7)\r\n\r\n\r\n###
After\r\n**Timeline -> Notes**\r\nAdd note button should be disabled if
markdown is
invalid\r\n\r\n![image](d34b0ab1-c39b-443a-a309-00aba251731e)\r\n\r\n**On
rules -> about**\r\nField is red if markdown is
invalid\r\n\r\n![image](850f9f4a-71a7-44f8-a9e1-bbfbdb07b0dd)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"08a57b9e3a570329c4f8051dcf195fe80e691eb3"}},"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/161034","number":161034,"mergeCommit":{"message":"[Security
Solution] Add validations for insight form in timeline and rules
(#161034)\n\n## Summary\r\n\r\nCurrently user can add a note in timeline
with invalid markdown syntax\r\nin insight forms. Same goes to the
investigation guide in rule creation\r\n-> About.\r\n\r\n###
Before\r\n**In timeline ->
Notes**\r\n\r\n![image](33b05592-f97a-41d8-a394-fc111f4cc039)\r\n\r\n\r\n**On
rules ->
about**\r\n\r\n![image](ca09ac1a-7798-4b13-820b-85e5cf0f61c7)\r\n\r\n\r\n###
After\r\n**Timeline -> Notes**\r\nAdd note button should be disabled if
markdown is
invalid\r\n\r\n![image](d34b0ab1-c39b-443a-a309-00aba251731e)\r\n\r\n**On
rules -> about**\r\nField is red if markdown is
invalid\r\n\r\n![image](850f9f4a-71a7-44f8-a9e1-bbfbdb07b0dd)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"08a57b9e3a570329c4f8051dcf195fe80e691eb3"}}]}]
BACKPORT-->

Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com>
2023-07-11 10:27:32 -07:00
Kibana Machine
8708317f2d
[8.9] [Synthetics] De-dupe overview status request on load (#161627) (#161675)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] De-dupe overview status request on load
(#161627)](https://github.com/elastic/kibana/pull/161627)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-11T15:55:49Z","message":"[Synthetics]
De-dupe overview status request on load
(#161627)","sha":"70ed2004343561fcc162d287d231b01d8803eab0","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161627,"url":"https://github.com/elastic/kibana/pull/161627","mergeCommit":{"message":"[Synthetics]
De-dupe overview status request on load
(#161627)","sha":"70ed2004343561fcc162d287d231b01d8803eab0"}},"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/161627","number":161627,"mergeCommit":{"message":"[Synthetics]
De-dupe overview status request on load
(#161627)","sha":"70ed2004343561fcc162d287d231b01d8803eab0"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
2023-07-11 10:05:19 -07:00
Kibana Machine
9651fc7331
[8.9] [Defend Workflows] Fix response actions copy (#161615) (#161639)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Defend Workflows] Fix response actions copy
(#161615)](https://github.com/elastic/kibana/pull/161615)

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

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

<!--BACKPORT [{"author":{"name":"Tomasz
Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T10:49:58Z","message":"[Defend
Workflows] Fix response actions copy
(#161615)","sha":"203c9b04b66c4ef67de0b85f572305f43c358bd4","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","Team:Defend
Workflows","v8.9.0","v8.10.0"],"number":161615,"url":"https://github.com/elastic/kibana/pull/161615","mergeCommit":{"message":"[Defend
Workflows] Fix response actions copy
(#161615)","sha":"203c9b04b66c4ef67de0b85f572305f43c358bd4"}},"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/161615","number":161615,"mergeCommit":{"message":"[Defend
Workflows] Fix response actions copy
(#161615)","sha":"203c9b04b66c4ef67de0b85f572305f43c358bd4"}}]}]
BACKPORT-->

Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>
2023-07-11 09:49:35 -07:00
Kibana Machine
f56c7f895d
[8.9] [Security Solution] Rule is created when the conditional logic "If alert matches a query" is left blank (#159690) (#161665)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Rule is created when the conditional logic "If
alert matches a query" is left blank
(#159690)](https://github.com/elastic/kibana/pull/159690)

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

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

<!--BACKPORT [{"author":{"name":"Ievgen
Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T14:27:24Z","message":"[Security
Solution] Rule is created when the conditional logic \"If alert matches
a query\" is left blank (#159690)\n\n## Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156706\r\n\r\nThese changes
prevent user from creating/updating the rule when alert\r\nfilter is
selected and query left blank on the rule's action page. We\r\ngonna
show an error saying \"A custom query is required.\" in this
case.\r\n\r\n<img width=\"1739\" alt=\"Screenshot 2023-06-14 at 14 36
35\"\r\nsrc=\"0456f211-603c-44d9-9271-9cfdf59f12b6\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"9b6ad7280de61c0ed1471eda54b98a64d485b637","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","ci:cloud-deploy","Team:Detection
Engine","v8.10.0","v8.9.1"],"number":159690,"url":"https://github.com/elastic/kibana/pull/159690","mergeCommit":{"message":"[Security
Solution] Rule is created when the conditional logic \"If alert matches
a query\" is left blank (#159690)\n\n## Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156706\r\n\r\nThese changes
prevent user from creating/updating the rule when alert\r\nfilter is
selected and query left blank on the rule's action page. We\r\ngonna
show an error saying \"A custom query is required.\" in this
case.\r\n\r\n<img width=\"1739\" alt=\"Screenshot 2023-06-14 at 14 36
35\"\r\nsrc=\"0456f211-603c-44d9-9271-9cfdf59f12b6\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"9b6ad7280de61c0ed1471eda54b98a64d485b637"}},"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/159690","number":159690,"mergeCommit":{"message":"[Security
Solution] Rule is created when the conditional logic \"If alert matches
a query\" is left blank (#159690)\n\n## Summary\r\n\r\nOriginal ticket:
https://github.com/elastic/kibana/issues/156706\r\n\r\nThese changes
prevent user from creating/updating the rule when alert\r\nfilter is
selected and query left blank on the rule's action page. We\r\ngonna
show an error saying \"A custom query is required.\" in this
case.\r\n\r\n<img width=\"1739\" alt=\"Screenshot 2023-06-14 at 14 36
35\"\r\nsrc=\"0456f211-603c-44d9-9271-9cfdf59f12b6\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"9b6ad7280de61c0ed1471eda54b98a64d485b637"}},{"branch":"8.9","label":"v8.9.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
2023-07-11 09:12:03 -07:00
Lisa Cawley
f345059463
[DOCS] Add case highlights for 8.9 (#161591) 2023-07-11 07:49:14 -07:00
Kibana Machine
e007bd02b7
[8.9] [Docs] Try to make it clear drilldows only available in dashboard (#161469) (#161662)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Docs] Try to make it clear drilldows only available in dashboard
(#161469)](https://github.com/elastic/kibana/pull/161469)

<!--- 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-07-11T14:08:31Z","message":"[Docs]
Try to make it clear drilldows only available in dashboard
(#161469)\n\n## Summary\r\n\r\nIssue [raised
on\r\nSlack](https://elastic.slack.com/archives/C0D8P2XK5/p1688661541837369)\r\nthat
it was a bit unclear on our
[docs\r\npage](https://www.elastic.co/guide/en/kibana/8.8/maps-create-filter-from-map.html#maps-spatial-filters)\r\nthat
to use drilldowns you had to embed your map in Dashboard, and
can't\r\nbe used from the Maps application.\r\n\r\nOriginal:\r\n<img
width=\"808\" alt=\"Screenshot 2023-07-07 at 15 32
27\"\r\nsrc=\"176e7f22-1bb3-4dd0-95d5-4a601487aa6b\">\r\n\r\nUpdated:\r\n<img
width=\"843\" alt=\"Screenshot 2023-07-07 at 11 47
45\"\r\nsrc=\"4d33a39f-2cee-4097-b730-3b24d613c498\">\r\n\r\n---------\r\n\r\nCo-authored-by:
David Kilfoyle
<41695641+kilfoyle@users.noreply.github.com>","sha":"811fb7c4fdc2de23ebf3c5c24117fd69d263875d","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","v8.0.0","release_note:skip","docs","v7.14.0","v7.15.0","v7.16.0","v8.1.0","v7.17.0","v8.2.0","v8.3.0","v8.4.0","v8.5.0","v8.6.0","v8.7.0","v8.8.0","v8.9.0","v8.10.0"],"number":161469,"url":"https://github.com/elastic/kibana/pull/161469","mergeCommit":{"message":"[Docs]
Try to make it clear drilldows only available in dashboard
(#161469)\n\n## Summary\r\n\r\nIssue [raised
on\r\nSlack](https://elastic.slack.com/archives/C0D8P2XK5/p1688661541837369)\r\nthat
it was a bit unclear on our
[docs\r\npage](https://www.elastic.co/guide/en/kibana/8.8/maps-create-filter-from-map.html#maps-spatial-filters)\r\nthat
to use drilldowns you had to embed your map in Dashboard, and
can't\r\nbe used from the Maps application.\r\n\r\nOriginal:\r\n<img
width=\"808\" alt=\"Screenshot 2023-07-07 at 15 32
27\"\r\nsrc=\"176e7f22-1bb3-4dd0-95d5-4a601487aa6b\">\r\n\r\nUpdated:\r\n<img
width=\"843\" alt=\"Screenshot 2023-07-07 at 11 47
45\"\r\nsrc=\"4d33a39f-2cee-4097-b730-3b24d613c498\">\r\n\r\n---------\r\n\r\nCo-authored-by:
David Kilfoyle
<41695641+kilfoyle@users.noreply.github.com>","sha":"811fb7c4fdc2de23ebf3c5c24117fd69d263875d"}},"sourceBranch":"main","suggestedTargetBranches":["8.0","7.14","7.15","7.16","8.1","7.17","8.2","8.3","8.4","8.5","8.6","8.7","8.8","8.9"],"targetPullRequestStates":[{"branch":"8.0","label":"v8.0.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.14","label":"v7.14.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.15","label":"v7.15.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.16","label":"v7.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.1","label":"v8.1.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.2","label":"v8.2.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.3","label":"v8.3.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.4","label":"v8.4.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.5","label":"v8.5.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"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/161469","number":161469,"mergeCommit":{"message":"[Docs]
Try to make it clear drilldows only available in dashboard
(#161469)\n\n## Summary\r\n\r\nIssue [raised
on\r\nSlack](https://elastic.slack.com/archives/C0D8P2XK5/p1688661541837369)\r\nthat
it was a bit unclear on our
[docs\r\npage](https://www.elastic.co/guide/en/kibana/8.8/maps-create-filter-from-map.html#maps-spatial-filters)\r\nthat
to use drilldowns you had to embed your map in Dashboard, and
can't\r\nbe used from the Maps application.\r\n\r\nOriginal:\r\n<img
width=\"808\" alt=\"Screenshot 2023-07-07 at 15 32
27\"\r\nsrc=\"176e7f22-1bb3-4dd0-95d5-4a601487aa6b\">\r\n\r\nUpdated:\r\n<img
width=\"843\" alt=\"Screenshot 2023-07-07 at 11 47
45\"\r\nsrc=\"4d33a39f-2cee-4097-b730-3b24d613c498\">\r\n\r\n---------\r\n\r\nCo-authored-by:
David Kilfoyle
<41695641+kilfoyle@users.noreply.github.com>","sha":"811fb7c4fdc2de23ebf3c5c24117fd69d263875d"}}]}]
BACKPORT-->

Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
2023-07-11 10:34:31 -04:00
Kibana Machine
29376ed5ae
[8.9] [Security Solution] Fix endpoint permissions for rule installation and update (#161641) (#161649)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Fix endpoint permissions for rule installation
and update (#161641)](https://github.com/elastic/kibana/pull/161641)

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

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

<!--BACKPORT [{"author":{"name":"Dmitrii
Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T13:07:35Z","message":"[Security
Solution] Fix endpoint permissions for rule installation and update
(#161641)\n\n**Related to:
https://github.com/elastic/kibana/issues/161443,\r\nhttps://github.com/elastic/kibana/pull/161454**\r\n\r\n##
Summary\r\n\r\nThe `access:securitySolution-all` access level prevents a
properly\r\nconfigured role from installing or updating detection rules.
This PR\r\naligns the access level for the `installation/_perform`
and\r\n`upgrade/_perform` endpoints with the rest of the detection
engine APIs.\r\n\r\n### Test instructions\r\n\r\nConfigure a role with
the following permissions:\r\n\r\n```json\r\n{\r\n \"test\": {\r\n
\"cluster\": [],\r\n \"indices\": [\r\n {\r\n \"names\": [\r\n
\".alerts-security.alerts-default\",\r\n \".lists-default\",\r\n
\".items-default\"\r\n ],\r\n \"privileges\": [\r\n \"read\",\r\n
\"write\",\r\n \"view_index_metadata\",\r\n \"maintenance\"\r\n ],\r\n
\"field_security\": {\r\n \"grant\": [\r\n \"*\"\r\n ]\r\n },\r\n
\"allow_restricted_indices\": false\r\n }\r\n ],\r\n \"applications\":
[\r\n {\r\n \"application\": \"kibana-.kibana\",\r\n \"privileges\":
[\r\n \"feature_siem.all\"\r\n ],\r\n \"resources\": [\r\n \"*\"\r\n
]\r\n }\r\n ],\r\n \"run_as\": [],\r\n \"metadata\": {},\r\n
\"transient_metadata\": {\r\n \"enabled\": true\r\n }\r\n
}\r\n}\r\n```\r\n\r\nCall the upgrade/install APIs on behalf of that
role to see that no 403\r\nis returned:\r\n\r\n```sh\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/installation/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/upgrade/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n```","sha":"a5627bec5781575c02dec671f2635eaab8bc4f40","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","blocker","release_note:skip","impact:critical","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","v8.9.0","v8.10.0"],"number":161641,"url":"https://github.com/elastic/kibana/pull/161641","mergeCommit":{"message":"[Security
Solution] Fix endpoint permissions for rule installation and update
(#161641)\n\n**Related to:
https://github.com/elastic/kibana/issues/161443,\r\nhttps://github.com/elastic/kibana/pull/161454**\r\n\r\n##
Summary\r\n\r\nThe `access:securitySolution-all` access level prevents a
properly\r\nconfigured role from installing or updating detection rules.
This PR\r\naligns the access level for the `installation/_perform`
and\r\n`upgrade/_perform` endpoints with the rest of the detection
engine APIs.\r\n\r\n### Test instructions\r\n\r\nConfigure a role with
the following permissions:\r\n\r\n```json\r\n{\r\n \"test\": {\r\n
\"cluster\": [],\r\n \"indices\": [\r\n {\r\n \"names\": [\r\n
\".alerts-security.alerts-default\",\r\n \".lists-default\",\r\n
\".items-default\"\r\n ],\r\n \"privileges\": [\r\n \"read\",\r\n
\"write\",\r\n \"view_index_metadata\",\r\n \"maintenance\"\r\n ],\r\n
\"field_security\": {\r\n \"grant\": [\r\n \"*\"\r\n ]\r\n },\r\n
\"allow_restricted_indices\": false\r\n }\r\n ],\r\n \"applications\":
[\r\n {\r\n \"application\": \"kibana-.kibana\",\r\n \"privileges\":
[\r\n \"feature_siem.all\"\r\n ],\r\n \"resources\": [\r\n \"*\"\r\n
]\r\n }\r\n ],\r\n \"run_as\": [],\r\n \"metadata\": {},\r\n
\"transient_metadata\": {\r\n \"enabled\": true\r\n }\r\n
}\r\n}\r\n```\r\n\r\nCall the upgrade/install APIs on behalf of that
role to see that no 403\r\nis returned:\r\n\r\n```sh\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/installation/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/upgrade/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n```","sha":"a5627bec5781575c02dec671f2635eaab8bc4f40"}},"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/161641","number":161641,"mergeCommit":{"message":"[Security
Solution] Fix endpoint permissions for rule installation and update
(#161641)\n\n**Related to:
https://github.com/elastic/kibana/issues/161443,\r\nhttps://github.com/elastic/kibana/pull/161454**\r\n\r\n##
Summary\r\n\r\nThe `access:securitySolution-all` access level prevents a
properly\r\nconfigured role from installing or updating detection rules.
This PR\r\naligns the access level for the `installation/_perform`
and\r\n`upgrade/_perform` endpoints with the rest of the detection
engine APIs.\r\n\r\n### Test instructions\r\n\r\nConfigure a role with
the following permissions:\r\n\r\n```json\r\n{\r\n \"test\": {\r\n
\"cluster\": [],\r\n \"indices\": [\r\n {\r\n \"names\": [\r\n
\".alerts-security.alerts-default\",\r\n \".lists-default\",\r\n
\".items-default\"\r\n ],\r\n \"privileges\": [\r\n \"read\",\r\n
\"write\",\r\n \"view_index_metadata\",\r\n \"maintenance\"\r\n ],\r\n
\"field_security\": {\r\n \"grant\": [\r\n \"*\"\r\n ]\r\n },\r\n
\"allow_restricted_indices\": false\r\n }\r\n ],\r\n \"applications\":
[\r\n {\r\n \"application\": \"kibana-.kibana\",\r\n \"privileges\":
[\r\n \"feature_siem.all\"\r\n ],\r\n \"resources\": [\r\n \"*\"\r\n
]\r\n }\r\n ],\r\n \"run_as\": [],\r\n \"metadata\": {},\r\n
\"transient_metadata\": {\r\n \"enabled\": true\r\n }\r\n
}\r\n}\r\n```\r\n\r\nCall the upgrade/install APIs on behalf of that
role to see that no 403\r\nis returned:\r\n\r\n```sh\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/installation/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n\r\ncurl --location
'http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/upgrade/_perform'
\\\r\n--header 'Content-Type: application/json' \\\r\n--header 'Accept:
application/json' \\\r\n--data '{\r\n \"mode\":
\"ALL_RULES\"\r\n}'\r\n```","sha":"a5627bec5781575c02dec671f2635eaab8bc4f40"}}]}]
BACKPORT-->

Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co>
2023-07-11 07:23:49 -07:00
Kibana Machine
c233d5fdcd
[8.9] [Defend Workflows] Unskip policy response test (#161588) (#161644)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Defend Workflows] Unskip policy response test
(#161588)](https://github.com/elastic/kibana/pull/161588)

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

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

<!--BACKPORT
[{"author":{"name":"Ashokaditya","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T11:58:42Z","message":"[Defend
Workflows] Unskip policy response test (#161588)\n\n##
Summary\r\n\r\nUnskip test that was timing out at indexing test hosts.
\r\nThe timeout has since been increased in
elastic/kibana/pull/159518\r\n\r\nWas added in
elastic/kibana/pull/154505 and skipped
in\r\nelastic/kibana/pull/156104","sha":"5d066944fcef558eacc858bb807acb2fb783eaee","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","OLM
Sprint","v8.9.0","v8.10.0"],"number":161588,"url":"https://github.com/elastic/kibana/pull/161588","mergeCommit":{"message":"[Defend
Workflows] Unskip policy response test (#161588)\n\n##
Summary\r\n\r\nUnskip test that was timing out at indexing test hosts.
\r\nThe timeout has since been increased in
elastic/kibana/pull/159518\r\n\r\nWas added in
elastic/kibana/pull/154505 and skipped
in\r\nelastic/kibana/pull/156104","sha":"5d066944fcef558eacc858bb807acb2fb783eaee"}},"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/161588","number":161588,"mergeCommit":{"message":"[Defend
Workflows] Unskip policy response test (#161588)\n\n##
Summary\r\n\r\nUnskip test that was timing out at indexing test hosts.
\r\nThe timeout has since been increased in
elastic/kibana/pull/159518\r\n\r\nWas added in
elastic/kibana/pull/154505 and skipped
in\r\nelastic/kibana/pull/156104","sha":"5d066944fcef558eacc858bb807acb2fb783eaee"}}]}]
BACKPORT-->

Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
2023-07-11 06:08:42 -07:00
Kibana Machine
d844b83c7d
[8.9] [Security Solution] Tests: Filter by rule execution status (#160502) (#161618)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Tests: Filter by rule execution status
(#160502)](https://github.com/elastic/kibana/pull/160502)

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

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

<!--BACKPORT [{"author":{"name":"Nikita
Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T08:12:37Z","message":"[Security
Solution] Tests: Filter by rule execution status
(#160502)\n\n**Resolves:
https://github.com/elastic/kibana/issues/138903**\r\n\r\n##
Summary\r\n\r\nAdds an E2E Cypress test to check filtering by execution
status in the\r\nrules table.\r\n<img width=\"953\" alt=\"Screenshot
2023-06-26 at 14 10
10\"\r\nsrc=\"e1eb67ed-779c-42ad-8194-04a26598cfbc\">","sha":"c30a7d47eb4a467734b08bfea1d8d3c3c301b5cb","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","test_ui_functional","release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection Rule
Management","v8.9.0","v8.10.0"],"number":160502,"url":"https://github.com/elastic/kibana/pull/160502","mergeCommit":{"message":"[Security
Solution] Tests: Filter by rule execution status
(#160502)\n\n**Resolves:
https://github.com/elastic/kibana/issues/138903**\r\n\r\n##
Summary\r\n\r\nAdds an E2E Cypress test to check filtering by execution
status in the\r\nrules table.\r\n<img width=\"953\" alt=\"Screenshot
2023-06-26 at 14 10
10\"\r\nsrc=\"e1eb67ed-779c-42ad-8194-04a26598cfbc\">","sha":"c30a7d47eb4a467734b08bfea1d8d3c3c301b5cb"}},"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/160502","number":160502,"mergeCommit":{"message":"[Security
Solution] Tests: Filter by rule execution status
(#160502)\n\n**Resolves:
https://github.com/elastic/kibana/issues/138903**\r\n\r\n##
Summary\r\n\r\nAdds an E2E Cypress test to check filtering by execution
status in the\r\nrules table.\r\n<img width=\"953\" alt=\"Screenshot
2023-06-26 at 14 10
10\"\r\nsrc=\"e1eb67ed-779c-42ad-8194-04a26598cfbc\">","sha":"c30a7d47eb4a467734b08bfea1d8d3c3c301b5cb"}}]}]
BACKPORT-->

Co-authored-by: Nikita Indik <nikita.indik@elastic.co>
2023-07-11 02:55:33 -07:00
Kibana Machine
4115904db5
[8.9] Move some IT to a separate group (#161535) (#161623)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Move some IT to a separate group
(#161535)](https://github.com/elastic/kibana/pull/161535)

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

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

<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2023-07-11T08:35:45Z","message":"Move
some IT to a separate group (#161535)\n\nThe goal is to prevent the
following warning and reduce overall CI\ntimes:\n\n```\nThe following
\"Jest Integration Tests\" config has a duration that exceeds the
maximum amount of time desired for a single CI job. This is not an
error, and if you don't own this config then you can ignore this
warning. If you own this config please split it up ASAP and ask
Operations if you have questions about how to do
that.\n\nsrc/core/server/integration_tests/saved_objects/migrations/group3/jest.integration.config.js:
40.7 minutes\n```\n\nSource
https://buildkite.com/elastic/kibana-pull-request/builds/140963","sha":"5396f1be916ca8e41e7a2116b949971812d6cddf","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","test-jest-integration","release_note:skip","backport:prev-minor","v8.9.0","v8.10.0"],"number":161535,"url":"https://github.com/elastic/kibana/pull/161535","mergeCommit":{"message":"Move
some IT to a separate group (#161535)\n\nThe goal is to prevent the
following warning and reduce overall CI\ntimes:\n\n```\nThe following
\"Jest Integration Tests\" config has a duration that exceeds the
maximum amount of time desired for a single CI job. This is not an
error, and if you don't own this config then you can ignore this
warning. If you own this config please split it up ASAP and ask
Operations if you have questions about how to do
that.\n\nsrc/core/server/integration_tests/saved_objects/migrations/group3/jest.integration.config.js:
40.7 minutes\n```\n\nSource
https://buildkite.com/elastic/kibana-pull-request/builds/140963","sha":"5396f1be916ca8e41e7a2116b949971812d6cddf"}},"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/161535","number":161535,"mergeCommit":{"message":"Move
some IT to a separate group (#161535)\n\nThe goal is to prevent the
following warning and reduce overall CI\ntimes:\n\n```\nThe following
\"Jest Integration Tests\" config has a duration that exceeds the
maximum amount of time desired for a single CI job. This is not an
error, and if you don't own this config then you can ignore this
warning. If you own this config please split it up ASAP and ask
Operations if you have questions about how to do
that.\n\nsrc/core/server/integration_tests/saved_objects/migrations/group3/jest.integration.config.js:
40.7 minutes\n```\n\nSource
https://buildkite.com/elastic/kibana-pull-request/builds/140963","sha":"5396f1be916ca8e41e7a2116b949971812d6cddf"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
2023-07-11 02:44:54 -07:00
Kibana Machine
7507d73bcc
[8.9] [Profiling] reporting linux bug (#161551) (#161610)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Profiling] reporting linux bug
(#161551)](https://github.com/elastic/kibana/pull/161551)

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

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

<!--BACKPORT [{"author":{"name":"Cauê
Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-11T01:17:56Z","message":"[Profiling]
reporting linux bug (#161551)\n\n<img width=\"1354\" alt=\"Screenshot
2023-07-10 at 11 21 12
AM\"\r\nsrc=\"f9da535c-8fb4-4fb4-b662-ed5e5886d949\">","sha":"e3c3fa605ace5f320855e7bbaf16f1be67c35238","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.10.0"],"number":161551,"url":"https://github.com/elastic/kibana/pull/161551","mergeCommit":{"message":"[Profiling]
reporting linux bug (#161551)\n\n<img width=\"1354\" alt=\"Screenshot
2023-07-10 at 11 21 12
AM\"\r\nsrc=\"f9da535c-8fb4-4fb4-b662-ed5e5886d949\">","sha":"e3c3fa605ace5f320855e7bbaf16f1be67c35238"}},"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/161551","number":161551,"mergeCommit":{"message":"[Profiling]
reporting linux bug (#161551)\n\n<img width=\"1354\" alt=\"Screenshot
2023-07-10 at 11 21 12
AM\"\r\nsrc=\"f9da535c-8fb4-4fb4-b662-ed5e5886d949\">","sha":"e3c3fa605ace5f320855e7bbaf16f1be67c35238"}}]}]
BACKPORT-->

Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>
2023-07-10 19:23:28 -07:00
Kibana Machine
6c8a8dedd3
[8.9] Add RCF to pick user fetching strategy (#161546) (#161604)
# Backport

This will backport the following commits from `main` to `8.9`:
- [Add RCF to pick user fetching strategy
(#161546)](https://github.com/elastic/kibana/pull/161546)

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

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

<!--BACKPORT [{"author":{"name":"Sean
Story","email":"sean.j.story@gmail.com"},"sourceCommit":{"committedDate":"2023-07-10T22:06:09Z","message":"Add
RCF to pick user fetching strategy (#161546)\n\n## Summary\r\n\r\nPart
of https://github.com/elastic/connectors-python/issues/1204\r\n\r\nThis
adds a configuration for the sharepoint online native connector
to\r\nallow it to choose between approaches when fetching users for
DLS.\r\n\r\n\r\n### Checklist\r\n\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###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"fd2ecdfb27985044aa6e0c85662f23d5b000c255","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.9.0","v8.10.0"],"number":161546,"url":"https://github.com/elastic/kibana/pull/161546","mergeCommit":{"message":"Add
RCF to pick user fetching strategy (#161546)\n\n## Summary\r\n\r\nPart
of https://github.com/elastic/connectors-python/issues/1204\r\n\r\nThis
adds a configuration for the sharepoint online native connector
to\r\nallow it to choose between approaches when fetching users for
DLS.\r\n\r\n\r\n### Checklist\r\n\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###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"fd2ecdfb27985044aa6e0c85662f23d5b000c255"}},"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/161546","number":161546,"mergeCommit":{"message":"Add
RCF to pick user fetching strategy (#161546)\n\n## Summary\r\n\r\nPart
of https://github.com/elastic/connectors-python/issues/1204\r\n\r\nThis
adds a configuration for the sharepoint online native connector
to\r\nallow it to choose between approaches when fetching users for
DLS.\r\n\r\n\r\n### Checklist\r\n\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###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"fd2ecdfb27985044aa6e0c85662f23d5b000c255"}}]}]
BACKPORT-->

Co-authored-by: Sean Story <sean.j.story@gmail.com>
2023-07-10 16:13:00 -07:00
Kibana Machine
6b2d4bdef8
[8.9] [Defend workflows] Add tooltip on automated endpoint action form (#161525) (#161580)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Defend workflows] Add tooltip on automated endpoint action form
(#161525)](https://github.com/elastic/kibana/pull/161525)

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

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

<!--BACKPORT [{"author":{"name":"Tomasz
Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2023-07-10T17:40:05Z","message":"[Defend
workflows] Add tooltip on automated endpoint action form
(#161525)","sha":"9e5844f715ed0c999bfc9aeab413bda450e64d54","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Defend
Workflows","v8.9.0","v8.10.0"],"number":161525,"url":"https://github.com/elastic/kibana/pull/161525","mergeCommit":{"message":"[Defend
workflows] Add tooltip on automated endpoint action form
(#161525)","sha":"9e5844f715ed0c999bfc9aeab413bda450e64d54"}},"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/161525","number":161525,"mergeCommit":{"message":"[Defend
workflows] Add tooltip on automated endpoint action form
(#161525)","sha":"9e5844f715ed0c999bfc9aeab413bda450e64d54"}}]}]
BACKPORT-->

Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>
2023-07-10 11:55:39 -07:00
Carlos Crespo
4d0fef7bec
[Infra UI] Fix Normalized Load tooltip (#161530)
closes [#161527](https://github.com/elastic/kibana/issues/161527)

## Summary

This PR fixes the tooltip for the Normalized Load metric

<img width="1445" alt="image"
src="cac013c0-fc30-43a6-9754-9fb77ecefe25">



###  How to test
- Start a local Kibana instance
- Navigate to `Infrastructure` > `Hosts`
- Hover the mouse over the Normalized Load KPI
2023-07-10 20:51:52 +02:00
Kibana Machine
ab0f158b4b
[8.9] [Infra UI] Stop click propagation on tooltip (#161565) (#161579)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Infra UI] Stop click propagation on tooltip
(#161565)](https://github.com/elastic/kibana/pull/161565)

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-10T17:32:11Z","message":"[Infra
UI] Stop click propagation on tooltip (#161565)\n\nfixes
[#161553](https://github.com/elastic/kibana/issues/161553)\r\n\r\n##
Summary\r\n\r\nFixes click event on the tooltip
content\r\n\r\n\r\n\r\n13c8fde1-7dfe-4fb0-92f2-b3e45bd36972\r\n\r\n\r\n###
How to test\r\n\r\n- Start a local Kibana instance\r\n- Navigate to
`Infrastructure` > `Hosts`\r\n- Click on the `?` icon in the table
column headers and then click on\r\nthe content. It must not sort the
table","sha":"6c2170d3856360f25371d30d14b0b0efaf48252f","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics
UI","Team:Infra Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0","v8.10.0"],"number":161565,"url":"https://github.com/elastic/kibana/pull/161565","mergeCommit":{"message":"[Infra
UI] Stop click propagation on tooltip (#161565)\n\nfixes
[#161553](https://github.com/elastic/kibana/issues/161553)\r\n\r\n##
Summary\r\n\r\nFixes click event on the tooltip
content\r\n\r\n\r\n\r\n13c8fde1-7dfe-4fb0-92f2-b3e45bd36972\r\n\r\n\r\n###
How to test\r\n\r\n- Start a local Kibana instance\r\n- Navigate to
`Infrastructure` > `Hosts`\r\n- Click on the `?` icon in the table
column headers and then click on\r\nthe content. It must not sort the
table","sha":"6c2170d3856360f25371d30d14b0b0efaf48252f"}},"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/161565","number":161565,"mergeCommit":{"message":"[Infra
UI] Stop click propagation on tooltip (#161565)\n\nfixes
[#161553](https://github.com/elastic/kibana/issues/161553)\r\n\r\n##
Summary\r\n\r\nFixes click event on the tooltip
content\r\n\r\n\r\n\r\n13c8fde1-7dfe-4fb0-92f2-b3e45bd36972\r\n\r\n\r\n###
How to test\r\n\r\n- Start a local Kibana instance\r\n- Navigate to
`Infrastructure` > `Hosts`\r\n- Click on the `?` icon in the table
column headers and then click on\r\nthe content. It must not sort the
table","sha":"6c2170d3856360f25371d30d14b0b0efaf48252f"}}]}] BACKPORT-->

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
2023-07-10 11:43:24 -07:00
Kibana Machine
bbfcf27d67
[8.9] [Security Solution] Allow only users with 'all' privileges to install and upgrade prebuilt rules (#161454) (#161555)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Security Solution] Allow only users with 'all' privileges to install
and upgrade prebuilt rules
(#161454)](https://github.com/elastic/kibana/pull/161454)

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

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

<!--BACKPORT [{"author":{"name":"Juan Pablo
Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2023-07-10T14:35:17Z","message":"[Security
Solution] Allow only users with 'all' privileges to install and upgrade
prebuilt rules (#161454)\n\nFixes:
https://github.com/elastic/kibana/issues/161443\r\n\r\n##
Summary\r\n\r\n### When user doesn't have write permission:\r\n-
Disables \"Add Elastic rules\" button and removes Rule Updates
tab\r\n\r\n![image](a173f18f-9b6b-4c9a-bf5f-207af13e24cb)\r\n\r\n-
Disables buttons to individually install rules, install selected
rules\r\nand install all
rules\r\n\r\n![image](4d24d440-17f4-4d1d-96fc-4eb07914cff0)\r\n\r\n-
Disables buttons to individually upgrade rules, upgrade selected
rules\r\nand upgrade all
rules\r\n\r\n![image](036236c1-dac0-42b8-87e5-0244d9ead281)\r\n\r\n###
`_perform` endpoints\r\n- Returns 403 when installing all rules or
specific
rules\r\n\r\n![image](d1faf778-d857-458e-afeb-7c573e7bf4d3)\r\n\r\n-
Returns 403 when upgrading all rules or specific
rules\r\n\r\n![image](b8dfecc6-4cfe-462c-9e9c-6344f59aa2d5)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any UI touched in this PR is usable by keyboard only
(learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Dmitrii
<dmitrii.shevchenko@elastic.co>","sha":"31b28a06606d4f5b1fe10173859c44fb9fce3b10","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","blocker","release_note:skip","impact:critical","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection Rules","8.9
candidate","v8.9.0","v8.10.0"],"number":161454,"url":"https://github.com/elastic/kibana/pull/161454","mergeCommit":{"message":"[Security
Solution] Allow only users with 'all' privileges to install and upgrade
prebuilt rules (#161454)\n\nFixes:
https://github.com/elastic/kibana/issues/161443\r\n\r\n##
Summary\r\n\r\n### When user doesn't have write permission:\r\n-
Disables \"Add Elastic rules\" button and removes Rule Updates
tab\r\n\r\n![image](a173f18f-9b6b-4c9a-bf5f-207af13e24cb)\r\n\r\n-
Disables buttons to individually install rules, install selected
rules\r\nand install all
rules\r\n\r\n![image](4d24d440-17f4-4d1d-96fc-4eb07914cff0)\r\n\r\n-
Disables buttons to individually upgrade rules, upgrade selected
rules\r\nand upgrade all
rules\r\n\r\n![image](036236c1-dac0-42b8-87e5-0244d9ead281)\r\n\r\n###
`_perform` endpoints\r\n- Returns 403 when installing all rules or
specific
rules\r\n\r\n![image](d1faf778-d857-458e-afeb-7c573e7bf4d3)\r\n\r\n-
Returns 403 when upgrading all rules or specific
rules\r\n\r\n![image](b8dfecc6-4cfe-462c-9e9c-6344f59aa2d5)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any UI touched in this PR is usable by keyboard only
(learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Dmitrii
<dmitrii.shevchenko@elastic.co>","sha":"31b28a06606d4f5b1fe10173859c44fb9fce3b10"}},"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/161454","number":161454,"mergeCommit":{"message":"[Security
Solution] Allow only users with 'all' privileges to install and upgrade
prebuilt rules (#161454)\n\nFixes:
https://github.com/elastic/kibana/issues/161443\r\n\r\n##
Summary\r\n\r\n### When user doesn't have write permission:\r\n-
Disables \"Add Elastic rules\" button and removes Rule Updates
tab\r\n\r\n![image](a173f18f-9b6b-4c9a-bf5f-207af13e24cb)\r\n\r\n-
Disables buttons to individually install rules, install selected
rules\r\nand install all
rules\r\n\r\n![image](4d24d440-17f4-4d1d-96fc-4eb07914cff0)\r\n\r\n-
Disables buttons to individually upgrade rules, upgrade selected
rules\r\nand upgrade all
rules\r\n\r\n![image](036236c1-dac0-42b8-87e5-0244d9ead281)\r\n\r\n###
`_perform` endpoints\r\n- Returns 403 when installing all rules or
specific
rules\r\n\r\n![image](d1faf778-d857-458e-afeb-7c573e7bf4d3)\r\n\r\n-
Returns 403 when upgrading all rules or specific
rules\r\n\r\n![image](b8dfecc6-4cfe-462c-9e9c-6344f59aa2d5)\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any UI touched in this PR is usable by keyboard only
(learn more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI
touched in this PR does not create any new axe failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Dmitrii
<dmitrii.shevchenko@elastic.co>","sha":"31b28a06606d4f5b1fe10173859c44fb9fce3b10"}}]}]
BACKPORT-->

Co-authored-by: Juan Pablo Djeredjian <jpdjeredjian@gmail.com>
2023-07-10 08:50:41 -07:00
Kibana Machine
a96dd1f0a4
[8.9] [DOCS] Add more automated screenshots for security cases (#161485) (#161558)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[DOCS] Add more automated screenshots for security cases
(#161485)](https://github.com/elastic/kibana/pull/161485)

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

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-07-10T14:50:38Z","message":"[DOCS]
Add more automated screenshots for security cases
(#161485)","sha":"ff6099eb3fbb52671d892b766c81eb184b3c3a21","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","backport:prev-minor","v8.9.0","v8.10.0"],"number":161485,"url":"https://github.com/elastic/kibana/pull/161485","mergeCommit":{"message":"[DOCS]
Add more automated screenshots for security cases
(#161485)","sha":"ff6099eb3fbb52671d892b766c81eb184b3c3a21"}},"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/161485","number":161485,"mergeCommit":{"message":"[DOCS]
Add more automated screenshots for security cases
(#161485)","sha":"ff6099eb3fbb52671d892b766c81eb184b3c3a21"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-07-10 08:46:55 -07:00
Shahzad
40bab9bc0c
[8.9] [Synthetics] Fix TLS alert recovery (#161254) (#161484)
# Backport

This will backport the following commits from `main` to `8.9`:
- [[Synthetics] Fix TLS alert recovery
(#161254)](https://github.com/elastic/kibana/pull/161254)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-07-07T16:01:29Z","message":"[Synthetics]
Fix TLS alert recovery (#161254)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Abdul Wahab Zahid
<awahab07@yahoo.com>","sha":"0fe62fba0bb651d034021cbeab34dd2eb4cd2278","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.9.0","v8.10.0"],"number":161254,"url":"https://github.com/elastic/kibana/pull/161254","mergeCommit":{"message":"[Synthetics]
Fix TLS alert recovery (#161254)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Abdul Wahab Zahid
<awahab07@yahoo.com>","sha":"0fe62fba0bb651d034021cbeab34dd2eb4cd2278"}},"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/161254","number":161254,"mergeCommit":{"message":"[Synthetics]
Fix TLS alert recovery (#161254)\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Abdul Wahab Zahid
<awahab07@yahoo.com>","sha":"0fe62fba0bb651d034021cbeab34dd2eb4cd2278"}}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-07-10 15:26:31 +02:00