github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 17:59:23 -04:00
Code Issues Projects Releases Packages Wiki Activity
58824 commits 429 branches 496 tags 23 GiB
Commit graph

58824 commits

This branch
This branch
All branches
Author SHA1 Message Date
Kibana Machine
67a0f935d1
[8.6] [@kbn/handlebars] Improve types (#147800) (#148026) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[@kbn/handlebars] Improve types
(#147800)](https://github.com/elastic/kibana/pull/147800)

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

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

<!--BACKPORT [{"author":{"name":"Thomas
Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T17:27:56Z","message":"[@kbn/handlebars]
Improve types
(#147800)","sha":"41fd68b7193d9ea160692124345a64ac7aba410a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.7.0"],"number":147800,"url":"https://github.com/elastic/kibana/pull/147800","mergeCommit":{"message":"[@kbn/handlebars]
Improve types
(#147800)","sha":"41fd68b7193d9ea160692124345a64ac7aba410a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147800","number":147800,"mergeCommit":{"message":"[@kbn/handlebars]
Improve types
(#147800)","sha":"41fd68b7193d9ea160692124345a64ac7aba410a"}}]}]
BACKPORT-->

Co-authored-by: Thomas Watson <watson@elastic.co>
 2022-12-22 11:32:44 -07:00
Kibana Machine
008b9efae5
[8.6] [Security Solution] [Exceptions] UX updates (#147955) (#148019) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] [Exceptions] UX updates
(#147955)](https://github.com/elastic/kibana/pull/147955)

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

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

<!--BACKPORT [{"author":{"name":"Devin W.
Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T16:56:30Z","message":"[Security
Solution] [Exceptions] UX updates (#147955)\n\n##
Summary\r\n\r\n<details><summary>Display link on rule details page ->
add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds
manage rules functionality to list view
overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot
2022-12-21 at 4 59 11
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames
page to Shared exception lists and updates\r\npage description with
hyperlink to manage rules page</summary>\r\n<img width=\"635\"
alt=\"Screen Shot 2022-12-21 at 4 58 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates
sidebar title + navigation title</summary>\r\n<img width=\"590\"
alt=\"Screen Shot 2022-12-21 at 4 58 36
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null
FYI displaying all shared exception lists on the rule\r\ndetails -> add
exception flyout is not possible for 8.6. The ability to\r\nadd any
exception to any list was not part of the original design of
the\r\ncomponent and would require more time to update the component and
the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks
like the above is possible if we pass in `null` for the
rules\r\nproperty of the `AddExceptionFlyout` but we might want to
finalize a\r\ndesign to better help users trying to add the exception to
a shared list\r\nwhile **inside** of the rule details
page.\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###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by:
Khristinin Nikita
<nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Rule
Exceptions","Team:Security Solution
Platform","backport:prev-minor","v8.6.0","v8.7.0"],"number":147955,"url":"https://github.com/elastic/kibana/pull/147955","mergeCommit":{"message":"[Security
Solution] [Exceptions] UX updates (#147955)\n\n##
Summary\r\n\r\n<details><summary>Display link on rule details page ->
add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds
manage rules functionality to list view
overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot
2022-12-21 at 4 59 11
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames
page to Shared exception lists and updates\r\npage description with
hyperlink to manage rules page</summary>\r\n<img width=\"635\"
alt=\"Screen Shot 2022-12-21 at 4 58 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates
sidebar title + navigation title</summary>\r\n<img width=\"590\"
alt=\"Screen Shot 2022-12-21 at 4 58 36
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null
FYI displaying all shared exception lists on the rule\r\ndetails -> add
exception flyout is not possible for 8.6. The ability to\r\nadd any
exception to any list was not part of the original design of
the\r\ncomponent and would require more time to update the component and
the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks
like the above is possible if we pass in `null` for the
rules\r\nproperty of the `AddExceptionFlyout` but we might want to
finalize a\r\ndesign to better help users trying to add the exception to
a shared list\r\nwhile **inside** of the rule details
page.\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###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by:
Khristinin Nikita
<nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147955","number":147955,"mergeCommit":{"message":"[Security
Solution] [Exceptions] UX updates (#147955)\n\n##
Summary\r\n\r\n<details><summary>Display link on rule details page ->
add exception\r\nflyout</summary>\r\n\r\n<img width=\"1108\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/616158/209036807-973a83b9-2903-4d45-a15d-7fd6751f30a1.png\">\r\n\r\n</details>\r\n<details><summary>Adds
manage rules functionality to list view
overflow\r\nmenu</summary>\r\n\r\n<img width=\"802\" alt=\"Screen Shot
2022-12-21 at 4 59 11
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010900-4b609f9c-6fb1-46ca-a1f9-6aa3e67f5366.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Renames
page to Shared exception lists and updates\r\npage description with
hyperlink to manage rules page</summary>\r\n<img width=\"635\"
alt=\"Screen Shot 2022-12-21 at 4 58 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209010964-2c7ba8bd-7b1c-4bf9-a0a6-12a456386aed.png\">\r\n\r\n</details>\r\n\r\n<details><summary>Updates
sidebar title + navigation title</summary>\r\n<img width=\"590\"
alt=\"Screen Shot 2022-12-21 at 4 58 36
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/915763/209011050-45df0005-37eb-42b7-840f-eb916472d987.png\">\r\n\r\n</details>\r\n\r\n\r\n~~@jethr0null
FYI displaying all shared exception lists on the rule\r\ndetails -> add
exception flyout is not possible for 8.6. The ability to\r\nadd any
exception to any list was not part of the original design of
the\r\ncomponent and would require more time to update the component and
the\r\ndata model to allow for this sort of flexibility.~~\r\n\r\nLooks
like the above is possible if we pass in `null` for the
rules\r\nproperty of the `AddExceptionFlyout` but we might want to
finalize a\r\ndesign to better help users trying to add the exception to
a shared list\r\nwhile **inside** of the rule details
page.\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###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
Pedro Jaramillo <pedro.jaramillo@elastic.co>\r\nCo-authored-by:
Khristinin Nikita
<nikita.khristinin@elastic.co>","sha":"9eddb4c9cdbf9de2fefdd28c301c06f5e2b3cba4"}}]}]
BACKPORT-->

Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co>
 2022-12-22 11:22:33 -07:00
Kibana Machine
ab79db4362
[8.6] Bump pdfmake v0.2.5 to v0.2.7 (#147999) (#148010) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Bump pdfmake v0.2.5 to v0.2.7
(#147999)](https://github.com/elastic/kibana/pull/147999)

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

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

<!--BACKPORT [{"author":{"name":"Thomas
Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-22T15:08:23Z","message":"Bump
pdfmake v0.2.5 to v0.2.7
(#147999)","sha":"f3f4a2efb1a5fd88d103958a3c05529bc0e2666b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.7.0"],"number":147999,"url":"https://github.com/elastic/kibana/pull/147999","mergeCommit":{"message":"Bump
pdfmake v0.2.5 to v0.2.7
(#147999)","sha":"f3f4a2efb1a5fd88d103958a3c05529bc0e2666b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147999","number":147999,"mergeCommit":{"message":"Bump
pdfmake v0.2.5 to v0.2.7
(#147999)","sha":"f3f4a2efb1a5fd88d103958a3c05529bc0e2666b"}}]}]
BACKPORT-->

Co-authored-by: Thomas Watson <watson@elastic.co>
 2022-12-22 09:14:21 -07:00
Kibana Machine
5f4de824fd
[8.6] [Security Solution] Fix rule status refresh/loading indicator on the Rule Details page (#147806) (#147817) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] Fix rule status refresh/loading indicator on the
Rule Details page
(#147806)](https://github.com/elastic/kibana/pull/147806)

<!--- 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":"2022-12-19T21:49:00Z","message":"[Security
Solution] Fix rule status refresh/loading indicator on the Rule Details
page (#147806)\n\n**Fixes:**
https://github.com/elastic/kibana/issues/146362\r\n\r\n##
Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\"
network
throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:low","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rules","Feature:Rule
Details","v8.6.0","v8.7.0"],"number":147806,"url":"https://github.com/elastic/kibana/pull/147806","mergeCommit":{"message":"[Security
Solution] Fix rule status refresh/loading indicator on the Rule Details
page (#147806)\n\n**Fixes:**
https://github.com/elastic/kibana/issues/146362\r\n\r\n##
Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\"
network
throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147806","number":147806,"mergeCommit":{"message":"[Security
Solution] Fix rule status refresh/loading indicator on the Rule Details
page (#147806)\n\n**Fixes:**
https://github.com/elastic/kibana/issues/146362\r\n\r\n##
Summary\r\n\r\nWith normal network settings and then with \"Slow 3G\"
network
throttling:\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7359339/208510625-f9cbcff2-bc52-4e00-87aa-146e94abf7f3.mov\r\n\r\n\r\n###
Checklist\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"e4f4133ab7e1b2cd9f0d39a506555e5015ea585c"}}]}]
BACKPORT-->

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
 2022-12-22 04:39:23 -07:00
Kibana Machine
ed2fdb41d6
[8.6] [Documentation] Fix links to repository files on Best Practices page (#96152) (#147953) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Documentation] Fix links to repository files on Best Practices page
(#96152)](https://github.com/elastic/kibana/pull/96152)

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

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

<!--BACKPORT
[{"author":{"name":"hardikpnsp","email":"hardikpnsp@gmail.com"},"sourceCommit":{"committedDate":"2022-12-21T21:16:11Z","message":"[Documentation]
Fix links to repository files on Best Practices page
(#96152)","sha":"af2a7d63f4769bb0e002db0407ae41dd16ab15b6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v8.0.0","Team:AppServicesSv","release_note:skip","💝community","docs","auto-backport","v8.1.0","v7.17.0","v8.2.0","v8.3.0","v8.4.0","v8.5.0","v8.6.0"],"number":96152,"url":"https://github.com/elastic/kibana/pull/96152","mergeCommit":{"message":"[Documentation]
Fix links to repository files on Best Practices page
(#96152)","sha":"af2a7d63f4769bb0e002db0407ae41dd16ab15b6"}},"sourceBranch":"main","suggestedTargetBranches":["8.0","8.1","7.17","8.2","8.3","8.4","8.5","8.6"],"targetPullRequestStates":[{"branch":"8.0","label":"v8.0.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"}]}]
BACKPORT-->

Co-authored-by: hardikpnsp <hardikpnsp@gmail.com>
 2022-12-21 16:35:30 -05:00
Terrance DeJesus
8a6f1ec8c1
[8.6] Remove Guided Onboarding Rule from 8.6 (#147936) 
## Summary
The guided onboarding feature is not ready for 8.6 and was pushed back
to 8.7. As a result we need to remove the detection rule from the 8.6
branch. The rule is fine to remain in main as we intend it to be ready
for the 8.7 release.

As a side note, this rule should not make it into the 8.6 release
either.
 2022-12-21 11:55:49 -07:00
Kibana Machine
1c30c54075
[8.6] [APM] Add parallel builds for cypress tests (#142598) (#147930) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[APM] Add parallel builds for cypress tests
(#142598)](https://github.com/elastic/kibana/pull/142598)

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

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

<!--BACKPORT [{"author":{"name":"Giorgos
Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2022-12-21T15:36:08Z","message":"[APM]
Add parallel builds for cypress tests (#142598)\n\n- Tests runs
initiated by the flaky test runner are not recorded
or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:APM","release_note:skip","v8.6.0","v8.7.0"],"number":142598,"url":"https://github.com/elastic/kibana/pull/142598","mergeCommit":{"message":"[APM]
Add parallel builds for cypress tests (#142598)\n\n- Tests runs
initiated by the flaky test runner are not recorded
or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/142598","number":142598,"mergeCommit":{"message":"[APM]
Add parallel builds for cypress tests (#142598)\n\n- Tests runs
initiated by the flaky test runner are not recorded
or\r\nparallelized","sha":"042403e606e59468024b9a822ab7a9c199a487f5"}}]}]
BACKPORT-->

Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>
 2022-12-21 09:41:21 -07:00
Kibana Machine
867319cfae
[8.6] [Security Solution] [Exceptions] fixes error where validation of isAlertsLoading was missing reference to memoized data view id (#147641) (#147794) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] [Exceptions] fixes error where validation of
isAlertsLoading was missing reference to memoized data view id
(#147641)](https://github.com/elastic/kibana/pull/147641)

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

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

<!--BACKPORT [{"author":{"name":"Devin W.
Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:52:19Z","message":"[Security
Solution] [Exceptions] fixes error where validation of isAlertsLoading
was missing reference to memoized data view id (#147641)\n\n##
Summary\r\n\r\nref:
https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks
@nkhristinin for pairing up on this today!\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Gloria Hornero
<gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","impact:critical","Feature:Rule
Exceptions","Team:Security Solution
Platform","v8.6.0","v8.7.0"],"number":147641,"url":"https://github.com/elastic/kibana/pull/147641","mergeCommit":{"message":"[Security
Solution] [Exceptions] fixes error where validation of isAlertsLoading
was missing reference to memoized data view id (#147641)\n\n##
Summary\r\n\r\nref:
https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks
@nkhristinin for pairing up on this today!\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Gloria Hornero
<gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147641","number":147641,"mergeCommit":{"message":"[Security
Solution] [Exceptions] fixes error where validation of isAlertsLoading
was missing reference to memoized data view id (#147641)\n\n##
Summary\r\n\r\nref:
https://github.com/elastic/kibana/issues/147591\r\n\r\nThanks
@nkhristinin for pairing up on this today!\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Gloria Hornero
<gloria.hornero@elastic.co>","sha":"42006836a105febf482089860113c26d39c9945d"}}]}]
BACKPORT-->

Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co>
 2022-12-21 09:40:16 -07:00
Kibana Machine
d660fc6f08
[8.6] [Synthetics] unskip flaky test (#147859) (#147927) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Synthetics] unskip flaky test
(#147859)](https://github.com/elastic/kibana/pull/147859)

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

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

<!--BACKPORT [{"author":{"name":"Dominique
Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-12-21T15:28:00Z","message":"[Synthetics]
unskip flaky test (#147859)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/146014\r\n\r\nUnskip flaky
test.\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1664","sha":"b3d7ecb68df66e2a49ed9ad04003ae645b26fb6c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":147859,"url":"https://github.com/elastic/kibana/pull/147859","mergeCommit":{"message":"[Synthetics]
unskip flaky test (#147859)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/146014\r\n\r\nUnskip flaky
test.\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1664","sha":"b3d7ecb68df66e2a49ed9ad04003ae645b26fb6c"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147859","number":147859,"mergeCommit":{"message":"[Synthetics]
unskip flaky test (#147859)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/146014\r\n\r\nUnskip flaky
test.\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1664","sha":"b3d7ecb68df66e2a49ed9ad04003ae645b26fb6c"}}]}]
BACKPORT-->

Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
 2022-12-21 09:22:26 -07:00
Kibana Machine
70f8974db5
[8.6] Update dependency selenium-webdriver to ^4.7.1 (main) (#147905) (#147923) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Update dependency selenium-webdriver to ^4.7.1 (main)
(#147905)](https://github.com/elastic/kibana/pull/147905)

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

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

<!--BACKPORT
[{"author":{"name":"renovate[bot]","email":"29139614+renovate[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-21T14:51:20Z","message":"Update
dependency selenium-webdriver to ^4.7.1 (main)
(#147905)\n\n[![Mend\r\nRenovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)\r\n\r\nThis
PR contains the following updates:\r\n\r\n| Package | Change | Age |
Adoption | Passing | Confidence
|\r\n|---|---|---|---|---|---|\r\n|\r\n[selenium-webdriver](https://togithub.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver#readme)\r\n([source](https://togithub.com/SeleniumHQ/selenium))
| [`^4.7.0`
->\r\n`^4.7.1`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.7.0/4.7.1)\r\n|\r\n[![age](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/age-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![adoption](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![passing](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/compatibility-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![confidence](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/confidence-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n\r\n---\r\n\r\n###
Release
Notes\r\n\r\n<details>\r\n<summary>SeleniumHQ/selenium</summary>\r\n\r\n###\r\n[`v4.7.1`](0a5b49d16f...a379331ad6)\r\n\r\n</details>\r\n\r\n---\r\n\r\n###
Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\r\nAutomerge - At any time (no schedule
defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR
becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕
**Ignore**: Close this PR and you won't be reminded about this
update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you
want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis
PR has been generated by
[Mend\r\nRenovate](https://www.mend.io/free-developer-tools/renovate/).
View\r\nrepository job
log\r\n[here](https://app.renovatebot.com/dashboard#github/elastic/kibana).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC42Ni4xIiwidXBkYXRlZEluVmVyIjoiMzQuNjYuMSJ9-->\r\n\r\nCo-authored-by:
renovate[bot]
<29139614+renovate[bot]@users.noreply.github.com>","sha":"690595ce484eaf348b8b4ab10ce5a8da47afabe3","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.7.0"],"number":147905,"url":"https://github.com/elastic/kibana/pull/147905","mergeCommit":{"message":"Update
dependency selenium-webdriver to ^4.7.1 (main)
(#147905)\n\n[![Mend\r\nRenovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)\r\n\r\nThis
PR contains the following updates:\r\n\r\n| Package | Change | Age |
Adoption | Passing | Confidence
|\r\n|---|---|---|---|---|---|\r\n|\r\n[selenium-webdriver](https://togithub.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver#readme)\r\n([source](https://togithub.com/SeleniumHQ/selenium))
| [`^4.7.0`
->\r\n`^4.7.1`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.7.0/4.7.1)\r\n|\r\n[![age](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/age-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![adoption](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![passing](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/compatibility-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![confidence](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/confidence-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n\r\n---\r\n\r\n###
Release
Notes\r\n\r\n<details>\r\n<summary>SeleniumHQ/selenium</summary>\r\n\r\n###\r\n[`v4.7.1`](0a5b49d16f...a379331ad6)\r\n\r\n</details>\r\n\r\n---\r\n\r\n###
Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\r\nAutomerge - At any time (no schedule
defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR
becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕
**Ignore**: Close this PR and you won't be reminded about this
update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you
want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis
PR has been generated by
[Mend\r\nRenovate](https://www.mend.io/free-developer-tools/renovate/).
View\r\nrepository job
log\r\n[here](https://app.renovatebot.com/dashboard#github/elastic/kibana).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC42Ni4xIiwidXBkYXRlZEluVmVyIjoiMzQuNjYuMSJ9-->\r\n\r\nCo-authored-by:
renovate[bot]
<29139614+renovate[bot]@users.noreply.github.com>","sha":"690595ce484eaf348b8b4ab10ce5a8da47afabe3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147905","number":147905,"mergeCommit":{"message":"Update
dependency selenium-webdriver to ^4.7.1 (main)
(#147905)\n\n[![Mend\r\nRenovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)\r\n\r\nThis
PR contains the following updates:\r\n\r\n| Package | Change | Age |
Adoption | Passing | Confidence
|\r\n|---|---|---|---|---|---|\r\n|\r\n[selenium-webdriver](https://togithub.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver#readme)\r\n([source](https://togithub.com/SeleniumHQ/selenium))
| [`^4.7.0`
->\r\n`^4.7.1`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.7.0/4.7.1)\r\n|\r\n[![age](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/age-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![adoption](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![passing](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/compatibility-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n[![confidence](https://badges.renovateapi.com/packages/npm/selenium-webdriver/4.7.1/confidence-slim/4.7.0)](https://docs.renovatebot.com/merge-confidence/)\r\n|\r\n\r\n---\r\n\r\n###
Release
Notes\r\n\r\n<details>\r\n<summary>SeleniumHQ/selenium</summary>\r\n\r\n###\r\n[`v4.7.1`](0a5b49d16f...a379331ad6)\r\n\r\n</details>\r\n\r\n---\r\n\r\n###
Configuration\r\n\r\n📅 **Schedule**: Branch creation - At any time (no
schedule defined),\r\nAutomerge - At any time (no schedule
defined).\r\n\r\n🚦 **Automerge**: Disabled by config. Please merge this
manually once you\r\nare satisfied.\r\n\r\n♻ **Rebasing**: Whenever PR
becomes conflicted, or you tick the\r\nrebase/retry checkbox.\r\n\r\n🔕
**Ignore**: Close this PR and you won't be reminded about this
update\r\nagain.\r\n\r\n---\r\n\r\n- [ ] <!-- rebase-check -->If you
want to rebase/retry this PR, check\r\nthis box\r\n\r\n---\r\n\r\nThis
PR has been generated by
[Mend\r\nRenovate](https://www.mend.io/free-developer-tools/renovate/).
View\r\nrepository job
log\r\n[here](https://app.renovatebot.com/dashboard#github/elastic/kibana).\r\n\r\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC42Ni4xIiwidXBkYXRlZEluVmVyIjoiMzQuNjYuMSJ9-->\r\n\r\nCo-authored-by:
renovate[bot]
<29139614+renovate[bot]@users.noreply.github.com>","sha":"690595ce484eaf348b8b4ab10ce5a8da47afabe3"}}]}]
BACKPORT-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
 2022-12-21 08:54:58 -07:00
Kibana Machine
6c82749a8c
[8.6] [Security Solution] Reduce load on Kibana generated by Cypress tests (#147349) (#147875) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] Reduce load on Kibana generated by Cypress tests
(#147349)](https://github.com/elastic/kibana/pull/147349)

<!--- 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":"2022-12-12T17:56:32Z","message":"[Security
Solution] Reduce load on Kibana generated by Cypress tests
(#147349)\n\n## Summary\r\n\r\nThis PR makes the following adjustments
in the Cypress tests:\r\n\r\n- Increases the default rule interval from
1 second to 100 minutes.\r\n- Increases the long-polling interval for
the\r\n`api/detection_engine/rules/prepackaged/_status` endpoint from
0.1 to 2\r\nseconds.\r\n\r\nThis should hopefully reduce the load that
Cypress tests generate on CI\r\non Kibana which makes the tests
themselves slower.\r\n\r\nIn the next episodes:\r\n\r\n-
https://github.com/elastic/kibana/issues/147377\r\n\r\n##
Background\r\n\r\nWith the recent issues related to installing the
prebuilt rules package,\r\n\r\n> @dhurley14 did some initial research
and found that there are some\r\nbulk_edit cypress tests that are going
into an infinitely loop. Looks\r\nlike the infinite loops can be
reproduced locally and are happening
here\r\n[3e56eba64d/x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules.cy.ts (L166))\r\n\r\n@xcrzx
@maximpn and I reproduced the issue locally and found that:\r\n\r\n-
There's no infinite loop in the `bulk_edit_rules.cy.ts` tests, but
it\r\ntook more than 1 hour to run 3 attempts of a single test: `Only
prebuilt\r\nrules selected`.\r\n- 6 rules that this test created were
enabled and were executing every 1\r\nsecond each.\r\n- The
`api/detection_engine/rules/prepackaged/_status` endpoint was\r\nbeing
called 600 times per minute until the timeout. It looks like it\r\ntook
_way_ more than a few minutes to run each attempt.\r\n\r\nWe were able
to reproduce this locally with the exception that the\r\nattempts didn't
take much time to fail.\r\n\r\nThe hypothesis is that on CI where we
have less computing power our\r\nCypress tests overload the Kibana
server by creating enabled rules that\r\nexecute way too frequently. We
shouldn't need rules to be enabled in\r\nmany of the tests; we should be
able to set a very long rule interval\r\nwhere rules have to be enabled.
Finally, we shouldn't be spamming the\r\nAPI with highly frequent
requests where we implement long-polling and\r\nwait for something to
happen on the BE
side.","sha":"7a8ed4cf866db32fb2f957a6000ddc2474f7cd77","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","performance","technical
debt","release_note:skip","Team:Detections and Resp","Team:
SecuritySolution","auto-backport","Team:Detection
Rules","v8.6.0","v8.7.0"],"number":147349,"url":"https://github.com/elastic/kibana/pull/147349","mergeCommit":{"message":"[Security
Solution] Reduce load on Kibana generated by Cypress tests
(#147349)\n\n## Summary\r\n\r\nThis PR makes the following adjustments
in the Cypress tests:\r\n\r\n- Increases the default rule interval from
1 second to 100 minutes.\r\n- Increases the long-polling interval for
the\r\n`api/detection_engine/rules/prepackaged/_status` endpoint from
0.1 to 2\r\nseconds.\r\n\r\nThis should hopefully reduce the load that
Cypress tests generate on CI\r\non Kibana which makes the tests
themselves slower.\r\n\r\nIn the next episodes:\r\n\r\n-
https://github.com/elastic/kibana/issues/147377\r\n\r\n##
Background\r\n\r\nWith the recent issues related to installing the
prebuilt rules package,\r\n\r\n> @dhurley14 did some initial research
and found that there are some\r\nbulk_edit cypress tests that are going
into an infinitely loop. Looks\r\nlike the infinite loops can be
reproduced locally and are happening
here\r\n[3e56eba64d/x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules.cy.ts (L166))\r\n\r\n@xcrzx
@maximpn and I reproduced the issue locally and found that:\r\n\r\n-
There's no infinite loop in the `bulk_edit_rules.cy.ts` tests, but
it\r\ntook more than 1 hour to run 3 attempts of a single test: `Only
prebuilt\r\nrules selected`.\r\n- 6 rules that this test created were
enabled and were executing every 1\r\nsecond each.\r\n- The
`api/detection_engine/rules/prepackaged/_status` endpoint was\r\nbeing
called 600 times per minute until the timeout. It looks like it\r\ntook
_way_ more than a few minutes to run each attempt.\r\n\r\nWe were able
to reproduce this locally with the exception that the\r\nattempts didn't
take much time to fail.\r\n\r\nThe hypothesis is that on CI where we
have less computing power our\r\nCypress tests overload the Kibana
server by creating enabled rules that\r\nexecute way too frequently. We
shouldn't need rules to be enabled in\r\nmany of the tests; we should be
able to set a very long rule interval\r\nwhere rules have to be enabled.
Finally, we shouldn't be spamming the\r\nAPI with highly frequent
requests where we implement long-polling and\r\nwait for something to
happen on the BE
side.","sha":"7a8ed4cf866db32fb2f957a6000ddc2474f7cd77"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147349","number":147349,"mergeCommit":{"message":"[Security
Solution] Reduce load on Kibana generated by Cypress tests
(#147349)\n\n## Summary\r\n\r\nThis PR makes the following adjustments
in the Cypress tests:\r\n\r\n- Increases the default rule interval from
1 second to 100 minutes.\r\n- Increases the long-polling interval for
the\r\n`api/detection_engine/rules/prepackaged/_status` endpoint from
0.1 to 2\r\nseconds.\r\n\r\nThis should hopefully reduce the load that
Cypress tests generate on CI\r\non Kibana which makes the tests
themselves slower.\r\n\r\nIn the next episodes:\r\n\r\n-
https://github.com/elastic/kibana/issues/147377\r\n\r\n##
Background\r\n\r\nWith the recent issues related to installing the
prebuilt rules package,\r\n\r\n> @dhurley14 did some initial research
and found that there are some\r\nbulk_edit cypress tests that are going
into an infinitely loop. Looks\r\nlike the infinite loops can be
reproduced locally and are happening
here\r\n[3e56eba64d/x-pack/plugins/security_solution/cypress/e2e/detection_rules/bulk_edit_rules.cy.ts (L166))\r\n\r\n@xcrzx
@maximpn and I reproduced the issue locally and found that:\r\n\r\n-
There's no infinite loop in the `bulk_edit_rules.cy.ts` tests, but
it\r\ntook more than 1 hour to run 3 attempts of a single test: `Only
prebuilt\r\nrules selected`.\r\n- 6 rules that this test created were
enabled and were executing every 1\r\nsecond each.\r\n- The
`api/detection_engine/rules/prepackaged/_status` endpoint was\r\nbeing
called 600 times per minute until the timeout. It looks like it\r\ntook
_way_ more than a few minutes to run each attempt.\r\n\r\nWe were able
to reproduce this locally with the exception that the\r\nattempts didn't
take much time to fail.\r\n\r\nThe hypothesis is that on CI where we
have less computing power our\r\nCypress tests overload the Kibana
server by creating enabled rules that\r\nexecute way too frequently. We
shouldn't need rules to be enabled in\r\nmany of the tests; we should be
able to set a very long rule interval\r\nwhere rules have to be enabled.
Finally, we shouldn't be spamming the\r\nAPI with highly frequent
requests where we implement long-polling and\r\nwait for something to
happen on the BE
side.","sha":"7a8ed4cf866db32fb2f957a6000ddc2474f7cd77"}}]}] BACKPORT-->

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co>
Co-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>
Co-authored-by: Dmitrii <dmitrii.shevchenko@elastic.co>
 2022-12-21 06:40:09 -07:00
Kibana Machine
e8c73a3189
[8.6] [Reporting] Fixes a sharpness issue in some charts in PDF reports (#147854) (#147911) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Reporting] Fixes a sharpness issue in some charts in PDF reports
(#147854)](https://github.com/elastic/kibana/pull/147854)

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

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

<!--BACKPORT [{"author":{"name":"Anton
Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2022-12-21T11:30:15Z","message":"[Reporting]
Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n##
Summary\r\n\r\nFixes the bug that pdf reports can be generated with
blurry text, for\r\nexample:\r\n\r\n![Screenshot 2022-12-21 at 11
22\r\n52](https://user-images.githubusercontent.com/7784120/208882394-2dff0abb-923e-4430-a322-4e03f8c38792.png)\r\n\r\n\r\nFixed
version example: \r\n\r\n![Screenshot 2022-12-21 at 11
23\r\n06](https://user-images.githubusercontent.com/7784120/208882431-080d6fb6-39f1-49a8-a791-286fb3e8e6f0.png)\r\n\r\n\r\nThe
bug happened because the device pixel ration was
changing\r\nmid-capture. The the page was opened with scaleFactor=1.
Before the\r\nscreenshot is captured, the viewport is resized to
scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts
as most of them don't\r\nredraw on devicePixelRatio changes (this has to
be fixed separately).\r\nThis fix attempts to open the page with the
final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n###
Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF
reports\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Reporting","Team:Global
Experience","backport:prev-minor","v8.7.0"],"number":147854,"url":"https://github.com/elastic/kibana/pull/147854","mergeCommit":{"message":"[Reporting]
Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n##
Summary\r\n\r\nFixes the bug that pdf reports can be generated with
blurry text, for\r\nexample:\r\n\r\n![Screenshot 2022-12-21 at 11
22\r\n52](https://user-images.githubusercontent.com/7784120/208882394-2dff0abb-923e-4430-a322-4e03f8c38792.png)\r\n\r\n\r\nFixed
version example: \r\n\r\n![Screenshot 2022-12-21 at 11
23\r\n06](https://user-images.githubusercontent.com/7784120/208882431-080d6fb6-39f1-49a8-a791-286fb3e8e6f0.png)\r\n\r\n\r\nThe
bug happened because the device pixel ration was
changing\r\nmid-capture. The the page was opened with scaleFactor=1.
Before the\r\nscreenshot is captured, the viewport is resized to
scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts
as most of them don't\r\nredraw on devicePixelRatio changes (this has to
be fixed separately).\r\nThis fix attempts to open the page with the
final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n###
Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF
reports\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147854","number":147854,"mergeCommit":{"message":"[Reporting]
Fixes a sharpness issue in some charts in PDF reports (#147854)\n\n##
Summary\r\n\r\nFixes the bug that pdf reports can be generated with
blurry text, for\r\nexample:\r\n\r\n![Screenshot 2022-12-21 at 11
22\r\n52](https://user-images.githubusercontent.com/7784120/208882394-2dff0abb-923e-4430-a322-4e03f8c38792.png)\r\n\r\n\r\nFixed
version example: \r\n\r\n![Screenshot 2022-12-21 at 11
23\r\n06](https://user-images.githubusercontent.com/7784120/208882431-080d6fb6-39f1-49a8-a791-286fb3e8e6f0.png)\r\n\r\n\r\nThe
bug happened because the device pixel ration was
changing\r\nmid-capture. The the page was opened with scaleFactor=1.
Before the\r\nscreenshot is captured, the viewport is resized to
scaleFactor=2. This\r\ncould cause issues with `<canvas>` based charts
as most of them don't\r\nredraw on devicePixelRatio changes (this has to
be fixed separately).\r\nThis fix attempts to open the page with the
final scaleFactor (which in\r\nthe most cases is 2)\r\n\r\n\r\n###
Release Notes\r\n\r\nFixes a sharpness issue in some charts in PDF
reports\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"56519fa4af98fa4d560b9286d9dd834647b6ebfb"}}]}]
BACKPORT-->

Co-authored-by: Anton Dosov <anton.dosov@elastic.co>
 2022-12-21 05:36:34 -07:00
Muhammad Ibragimov
4ade190ac4
[8.6] [Console] Fix issue with bulk requests (#147596) (#147902) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Console] Fix issue with bulk requests
(#147596)](https://github.com/elastic/kibana/pull/147596)

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

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

<!--BACKPORT [{"author":{"name":"Muhammad
Ibragimov","email":"53621505+mibragimov@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-16T10:01:50Z","message":"[Console]
Fix issue with bulk requests (#147596)\n\nFixes
https://github.com/elastic/kibana/issues/146366\r\n\r\n\r\n###
Summary\r\n\r\nThe issue was that the parser was not able to detect the
end of a bulk\r\nrequest correctly when multiple requests were sent.
This PR fixes that\r\nissue.\r\n\r\n### How to test\r\n\r\n1. Go to
Console\r\n2. Send a bulk request with multiple requests. For example
the following\r\nrequests:\r\n\r\n```\r\nPUT
/metrics-hello-world/_bulk?refresh\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:49:00Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:45:50Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:44:50Z\",\"namespace\":\"namespace26\"}\r\n\r\n\r\nGET
_alias\r\n\r\nPUT <foo>/_bar/_baz%{test}\r\n```\r\n\r\n3. Send the
request by pressing `CMD ⌘ + A` and `ENTER`\r\n4. The response should be
displayed correctly\r\n\r\nCo-authored-by: Muhammad Ibragimov
<muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fa9094366c63aa371b7010a19e5ba5eb99b74236","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Deployment
Management","release_note:skip","backport:skip","v8.7.0"],"number":147596,"url":"https://github.com/elastic/kibana/pull/147596","mergeCommit":{"message":"[Console]
Fix issue with bulk requests (#147596)\n\nFixes
https://github.com/elastic/kibana/issues/146366\r\n\r\n\r\n###
Summary\r\n\r\nThe issue was that the parser was not able to detect the
end of a bulk\r\nrequest correctly when multiple requests were sent.
This PR fixes that\r\nissue.\r\n\r\n### How to test\r\n\r\n1. Go to
Console\r\n2. Send a bulk request with multiple requests. For example
the following\r\nrequests:\r\n\r\n```\r\nPUT
/metrics-hello-world/_bulk?refresh\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:49:00Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:45:50Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:44:50Z\",\"namespace\":\"namespace26\"}\r\n\r\n\r\nGET
_alias\r\n\r\nPUT <foo>/_bar/_baz%{test}\r\n```\r\n\r\n3. Send the
request by pressing `CMD ⌘ + A` and `ENTER`\r\n4. The response should be
displayed correctly\r\n\r\nCo-authored-by: Muhammad Ibragimov
<muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fa9094366c63aa371b7010a19e5ba5eb99b74236"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147596","number":147596,"mergeCommit":{"message":"[Console]
Fix issue with bulk requests (#147596)\n\nFixes
https://github.com/elastic/kibana/issues/146366\r\n\r\n\r\n###
Summary\r\n\r\nThe issue was that the parser was not able to detect the
end of a bulk\r\nrequest correctly when multiple requests were sent.
This PR fixes that\r\nissue.\r\n\r\n### How to test\r\n\r\n1. Go to
Console\r\n2. Send a bulk request with multiple requests. For example
the following\r\nrequests:\r\n\r\n```\r\nPUT
/metrics-hello-world/_bulk?refresh\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:49:00Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:45:50Z\",\"namespace\":\"namespace26\"}\r\n{\"create\":{}}\r\n{\"@timestamp\":\"2022-06-21T15:44:50Z\",\"namespace\":\"namespace26\"}\r\n\r\n\r\nGET
_alias\r\n\r\nPUT <foo>/_bar/_baz%{test}\r\n```\r\n\r\n3. Send the
request by pressing `CMD ⌘ + A` and `ENTER`\r\n4. The response should be
displayed correctly\r\n\r\nCo-authored-by: Muhammad Ibragimov
<muhammad.ibragimov@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"fa9094366c63aa371b7010a19e5ba5eb99b74236"}}]}]
BACKPORT-->
 2022-12-21 11:56:23 +05:00
Walter Rafelsberger
0586a4bc15
[8.6] [ML] Transforms/Data Visualizer: Fix handling of aggregate_metric_double field types. (#147711) (#147889) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Transforms/Data Visualizer: Fix handling of
aggregate_metric_double field types.
(#147711)](https://github.com/elastic/kibana/pull/147711)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-20T19:29:47Z","message":"[ML]
Transforms/Data Visualizer: Fix handling of aggregate_metric_double
field types. (#147711)\n\nFix to avoid aggregating on
`aggregate_metric_double` field
types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:Transforms","v8.6.0","v8.7.0"],"number":147711,"url":"https://github.com/elastic/kibana/pull/147711","mergeCommit":{"message":"[ML]
Transforms/Data Visualizer: Fix handling of aggregate_metric_double
field types. (#147711)\n\nFix to avoid aggregating on
`aggregate_metric_double` field
types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147711","number":147711,"mergeCommit":{"message":"[ML]
Transforms/Data Visualizer: Fix handling of aggregate_metric_double
field types. (#147711)\n\nFix to avoid aggregating on
`aggregate_metric_double` field
types.","sha":"087fec38f93362a52cbacb3fa73a4e05607ae4ac"}}]}]
BACKPORT-->
 2022-12-20 13:38:18 -07:00
Kibana Machine
bed40632ae
[8.6] [Enterprise Search] Gate native connectors for low-memory deployments (#147845) (#147883) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Gate native connectors for low-memory deployments
(#147845)](https://github.com/elastic/kibana/pull/147845)

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

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

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-20T17:31:04Z","message":"[Enterprise
Search] Gate native connectors for low-memory deployments
(#147845)\n\nThis blocks native connectors from being deployed on
deployments with\r\ntoo little
memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":147845,"url":"https://github.com/elastic/kibana/pull/147845","mergeCommit":{"message":"[Enterprise
Search] Gate native connectors for low-memory deployments
(#147845)\n\nThis blocks native connectors from being deployed on
deployments with\r\ntoo little
memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147845","number":147845,"mergeCommit":{"message":"[Enterprise
Search] Gate native connectors for low-memory deployments
(#147845)\n\nThis blocks native connectors from being deployed on
deployments with\r\ntoo little
memory.","sha":"3b38da4e57b4786607880db1efa3e7e7e4832ed4"}}]}]
BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2022-12-20 12:16:03 -07:00
Kibana Machine
35ca3798b9
[8.6] [ML] Explain Log Rate Spikes: Fix mini histograms for groups with multiples values per field. (#147597) (#147865) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: Fix mini histograms for groups with
multiples values per field.
(#147597)](https://github.com/elastic/kibana/pull/147597)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-20T15:31:12Z","message":"[ML]
Explain Log Rate Spikes: Fix mini histograms for groups with multiples
values per field. (#147597)\n\nFor groups that have multiple values for
the same field, the group\r\nhistogram query wasn't able to fetch data
because it filters with a bool\r\n`must` and individual `term`
aggregations. This PR fixes it by using a\r\n`terms` aggregation if
there are multiple values for a field so just\r\nthese get treated as
`OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147597,"url":"https://github.com/elastic/kibana/pull/147597","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix mini histograms for groups with multiples
values per field. (#147597)\n\nFor groups that have multiple values for
the same field, the group\r\nhistogram query wasn't able to fetch data
because it filters with a bool\r\n`must` and individual `term`
aggregations. This PR fixes it by using a\r\n`terms` aggregation if
there are multiple values for a field so just\r\nthese get treated as
`OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147597","number":147597,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix mini histograms for groups with multiples
values per field. (#147597)\n\nFor groups that have multiple values for
the same field, the group\r\nhistogram query wasn't able to fetch data
because it filters with a bool\r\n`must` and individual `term`
aggregations. This PR fixes it by using a\r\n`terms` aggregation if
there are multiple values for a field so just\r\nthese get treated as
`OR`.","sha":"3a48b7a84e587f0d5b9bffef0abecbce9c62e2e6"}}]}] BACKPORT-->

Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>
 2022-12-20 09:41:16 -07:00
Kibana Machine
a6a51f9216
[8.6] [data view editor] Revalidate index pattern when 'allow hidden' changes (#147807) (#147857) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[data view editor] Revalidate index pattern when 'allow hidden'
changes (#147807)](https://github.com/elastic/kibana/pull/147807)

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

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

<!--BACKPORT [{"author":{"name":"Matthew
Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2022-12-20T13:24:45Z","message":"[data
view editor] Revalidate index pattern when 'allow hidden' changes
(#147807)\n\n## Summary\r\n\r\nSteps to reproduce problem -\r\n\r\n1)
Open create data view flyout\r\n2) Enter `.kibana` as index pattern\r\n
- no indices will match, the field will display an error\r\n3) Click on
'Advanced Options'\r\n4) Click 'Allow Hidden'\r\n - the index pattern
will still show an error\r\n\r\nThis PR fixes the index pattern error
state after step four. It will\r\nrevalidate the index pattern field and
load the timestamp field
list\r\nagain.","sha":"6b29787e6fb361358117c0accf7a0ef22c278fa4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Data
Views","Feature:Kibana
Management","release_note:skip","Team:DataDiscovery","backport:all-open","v8.7.0"],"number":147807,"url":"https://github.com/elastic/kibana/pull/147807","mergeCommit":{"message":"[data
view editor] Revalidate index pattern when 'allow hidden' changes
(#147807)\n\n## Summary\r\n\r\nSteps to reproduce problem -\r\n\r\n1)
Open create data view flyout\r\n2) Enter `.kibana` as index pattern\r\n
- no indices will match, the field will display an error\r\n3) Click on
'Advanced Options'\r\n4) Click 'Allow Hidden'\r\n - the index pattern
will still show an error\r\n\r\nThis PR fixes the index pattern error
state after step four. It will\r\nrevalidate the index pattern field and
load the timestamp field
list\r\nagain.","sha":"6b29787e6fb361358117c0accf7a0ef22c278fa4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147807","number":147807,"mergeCommit":{"message":"[data
view editor] Revalidate index pattern when 'allow hidden' changes
(#147807)\n\n## Summary\r\n\r\nSteps to reproduce problem -\r\n\r\n1)
Open create data view flyout\r\n2) Enter `.kibana` as index pattern\r\n
- no indices will match, the field will display an error\r\n3) Click on
'Advanced Options'\r\n4) Click 'Allow Hidden'\r\n - the index pattern
will still show an error\r\n\r\nThis PR fixes the index pattern error
state after step four. It will\r\nrevalidate the index pattern field and
load the timestamp field
list\r\nagain.","sha":"6b29787e6fb361358117c0accf7a0ef22c278fa4"}}]}]
BACKPORT-->

Co-authored-by: Matthew Kime <matt@mattki.me>
 2022-12-20 08:03:04 -07:00
Kibana Machine
335b86a633
[8.6] [Fleet] refactored bulk update tags retry (#147594) (#147839) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Fleet] refactored bulk update tags retry
(#147594)](https://github.com/elastic/kibana/pull/147594)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-20T09:36:36Z","message":"[Fleet]
refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/144161\r\n\r\nAs
discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe
existing implementation of update tags doesn't work well with
real\r\nagents, as there are many conflicts with checkin, even when
trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries
more efficient:\r\n- Instead of aborting the whole bulk action on
conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if
an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but
only the 1k conflicts,\r\nthis makes it less likely to conflict on
retry.\r\n- Because of this, on retry we have to know which agents don't
yet have\r\nthe tag added/removed. For this, added an additional filter
to the\r\n`updateByQuery` request. Only adding the filter if there is
exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use
case from the\r\nUI, and handling other cases would complicate the logic
more (each\r\nadditional tag to add/remove would result in another OR
query, which\r\nwould match more agents, making conflicts more
likely).\r\n- Added this additional query on the initial request as well
(not only\r\nretries) to save on unnecessary work e.g. if the user tries
to add a tag\r\non 50k agents, but 48k already have it, it is enough to
update the\r\nremaining 2k agents.\r\n- This improvement has the effect
that 'Agent activity' shows the real\r\nupdated agent count, not the
total selected. I think this is not really\r\na problem for update
tags.\r\n- Cleaned up some of the UI logic, because the conflicts are
fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce
the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try
to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll
50k agents (I used 50k with create_agents script, and 1k with\r\nhorde).
Enroll 50k with horde if possible.\r\n- Select all on UI and try to
add/remove one or more tags\r\n- Expect the changes to propagate quickly
(up to 1m). It might take a\r\nfew refreshes to see the result on agent
list and tags list, because the\r\nUI polls the agents every 30s. It is
expected that the tags list\r\ntemporarily shows incorrect data because
the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag
quickly:\r\n<img width=\"1776\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img
width=\"422\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe
logs show the details of how many `version_conflicts` were there,\r\nand
it decreased with
retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet]
{\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet]
{\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 10857
agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 26245
agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet]
{\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet]
Retry #1 of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de
failed: version conflict of 1000
agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO
][plugins.fleet] processed 26245 agents, took
5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet]
{\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO
][plugins.fleet] processed 1000 agents, took
379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.7.0","v8.6.1"],"number":147594,"url":"https://github.com/elastic/kibana/pull/147594","mergeCommit":{"message":"[Fleet]
refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/144161\r\n\r\nAs
discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe
existing implementation of update tags doesn't work well with
real\r\nagents, as there are many conflicts with checkin, even when
trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries
more efficient:\r\n- Instead of aborting the whole bulk action on
conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if
an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but
only the 1k conflicts,\r\nthis makes it less likely to conflict on
retry.\r\n- Because of this, on retry we have to know which agents don't
yet have\r\nthe tag added/removed. For this, added an additional filter
to the\r\n`updateByQuery` request. Only adding the filter if there is
exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use
case from the\r\nUI, and handling other cases would complicate the logic
more (each\r\nadditional tag to add/remove would result in another OR
query, which\r\nwould match more agents, making conflicts more
likely).\r\n- Added this additional query on the initial request as well
(not only\r\nretries) to save on unnecessary work e.g. if the user tries
to add a tag\r\non 50k agents, but 48k already have it, it is enough to
update the\r\nremaining 2k agents.\r\n- This improvement has the effect
that 'Agent activity' shows the real\r\nupdated agent count, not the
total selected. I think this is not really\r\na problem for update
tags.\r\n- Cleaned up some of the UI logic, because the conflicts are
fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce
the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try
to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll
50k agents (I used 50k with create_agents script, and 1k with\r\nhorde).
Enroll 50k with horde if possible.\r\n- Select all on UI and try to
add/remove one or more tags\r\n- Expect the changes to propagate quickly
(up to 1m). It might take a\r\nfew refreshes to see the result on agent
list and tags list, because the\r\nUI polls the agents every 30s. It is
expected that the tags list\r\ntemporarily shows incorrect data because
the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag
quickly:\r\n<img width=\"1776\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img
width=\"422\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe
logs show the details of how many `version_conflicts` were there,\r\nand
it decreased with
retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet]
{\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet]
{\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 10857
agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 26245
agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet]
{\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet]
Retry #1 of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de
failed: version conflict of 1000
agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO
][plugins.fleet] processed 26245 agents, took
5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet]
{\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO
][plugins.fleet] processed 1000 agents, took
379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147594","number":147594,"mergeCommit":{"message":"[Fleet]
refactored bulk update tags retry (#147594)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/144161\r\n\r\nAs
discussed\r\n[here](https://github.com/elastic/kibana/issues/144161#issuecomment-1348668610),\r\nthe
existing implementation of update tags doesn't work well with
real\r\nagents, as there are many conflicts with checkin, even when
trying to\r\nadd/remove one tag.\r\nRefactored the logic to make retries
more efficient:\r\n- Instead of aborting the whole bulk action on
conflicts, changed the\r\nconflict strategy to 'proceed'. This means, if
an action of 50k agents\r\nhas 1k conflicts, not all 50k is retried, but
only the 1k conflicts,\r\nthis makes it less likely to conflict on
retry.\r\n- Because of this, on retry we have to know which agents don't
yet have\r\nthe tag added/removed. For this, added an additional filter
to the\r\n`updateByQuery` request. Only adding the filter if there is
exactly one\r\n`tagsToAdd` or one `tagsToRemove`. This is the main use
case from the\r\nUI, and handling other cases would complicate the logic
more (each\r\nadditional tag to add/remove would result in another OR
query, which\r\nwould match more agents, making conflicts more
likely).\r\n- Added this additional query on the initial request as well
(not only\r\nretries) to save on unnecessary work e.g. if the user tries
to add a tag\r\non 50k agents, but 48k already have it, it is enough to
update the\r\nremaining 2k agents.\r\n- This improvement has the effect
that 'Agent activity' shows the real\r\nupdated agent count, not the
total selected. I think this is not really\r\na problem for update
tags.\r\n- Cleaned up some of the UI logic, because the conflicts are
fully\r\nhandled now on the backend.\r\n- Locally I couldn't reproduce
the conflict with agent checkins, even\r\nwith 1k horde agents. I'll try
to test in cloud with more real agents.\r\n\r\nTo verify:\r\n- Enroll
50k agents (I used 50k with create_agents script, and 1k with\r\nhorde).
Enroll 50k with horde if possible.\r\n- Select all on UI and try to
add/remove one or more tags\r\n- Expect the changes to propagate quickly
(up to 1m). It might take a\r\nfew refreshes to see the result on agent
list and tags list, because the\r\nUI polls the agents every 30s. It is
expected that the tags list\r\ntemporarily shows incorrect data because
the action is async.\r\n\r\nE.g. removed `test3` tag and added `add` tag
quickly:\r\n<img width=\"1776\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824481-411f0f70-d7e8-42a6-b73f-ed80e77b7700.png\">\r\n<img
width=\"422\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207824550-582d43fc-87db-45e1-ba58-15915447fefd.png\">\r\n\r\nThe
logs show the details of how many `version_conflicts` were there,\r\nand
it decreased with
retries.\r\n\r\n```\r\n[2022-12-15T10:32:12.937+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:12.981+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:16.477+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:16.537+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:22.893+01:00][DEBUG][plugins.fleet]
{\"took\":9886,\"timed_out\":false,\"total\":52000,\"updated\":41143,\"deleted\":0,\"batches\":52,\"version_conflicts\":10857,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:26.066+01:00][DEBUG][plugins.fleet]
{\"took\":9518,\"timed_out\":false,\"total\":52000,\"updated\":25755,\"deleted\":0,\"batches\":52,\"version_conflicts\":26245,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:27.401+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 10857
agents\r\n[2022-12-15T10:32:27.461+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:27.462+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:29.274+01:00][ERROR][plugins.fleet]
Action failed: version conflict of 26245
agents\r\n[2022-12-15T10:32:29.353+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:29.353+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:31.480+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:31.481+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:31.481+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:31.481+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:31.485+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:33.841+01:00][DEBUG][plugins.fleet]
{\"took\":2347,\"timed_out\":false,\"total\":10857,\"updated\":9857,\"deleted\":0,\"batches\":11,\"version_conflicts\":1000,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:34.556+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:34.557+01:00][DEBUG][plugins.fleet] Retry #1
of task
fleet:update_agent_tags:retry:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:34.557+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
29e9da70-7194-4e52-8004-2c1b19f6dfd5, total agents:
52000\r\n[2022-12-15T10:32:34.557+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:34.560+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:35.388+01:00][ERROR][plugins.fleet]
Retry #1 of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de
failed: version conflict of 1000
agents\r\n[2022-12-15T10:32:35.468+01:00][INFO ][plugins.fleet]
Scheduling task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:35.468+01:00][INFO
][plugins.fleet] Retrying in task:
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n{\"took\":5509,\"timed_out\":false,\"total\":26245,\"updated\":26245,\"deleted\":0,\"batches\":27,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:42.722+01:00][INFO
][plugins.fleet] processed 26245 agents, took
5509ms\r\n[2022-12-15T10:32:42.723+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:29e9da70-7194-4e52-8004-2c1b19f6dfd5\r\n[2022-12-15T10:32:46.705+01:00][INFO
][plugins.fleet] Running bulk action retry
task\r\n[2022-12-15T10:32:46.706+01:00][DEBUG][plugins.fleet] Retry #2
of task
fleet:update_agent_tags:retry:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:46.707+01:00][INFO
][plugins.fleet] Running action asynchronously, actionId:
90acd541-19ac-4738-b3d3-db32789233de, total agents:
52000\r\n[2022-12-15T10:32:46.707+01:00][INFO ][plugins.fleet] Completed
bulk action retry task\r\n[2022-12-15T10:32:46.711+01:00][INFO
][plugins.fleet] Scheduling task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n[2022-12-15T10:32:47.099+01:00][DEBUG][plugins.fleet]
{\"took\":379,\"timed_out\":false,\"total\":1000,\"updated\":1000,\"deleted\":0,\"batches\":1,\"version_conflicts\":0,\"noops\":0,\"retries\":{\"bulk\":0,\"search\":0},\"throttled_millis\":0,\"requests_per_second\":-1,\"throttled_until_millis\":0,\"failures\":[]}\r\n[2022-12-15T10:32:47.623+01:00][INFO
][plugins.fleet] processed 1000 agents, took
379ms\r\n[2022-12-15T10:32:47.623+01:00][INFO ][plugins.fleet] Removing
task
fleet:update_agent_tags:retry:check:90acd541-19ac-4738-b3d3-db32789233de\r\n```\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"687987aa9ce56ce359f722485330179a4807d79a"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2022-12-20 03:41:33 -07:00
Walter Rafelsberger
32265b766d
[8.6] [ML] Explain Log Rate Spikes: Fix client side code to transform groups into table rows. (#147592) (#147832) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: Fix client side code to transform
groups into table rows.
(#147592)](https://github.com/elastic/kibana/pull/147592)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-20T08:19:11Z","message":"[ML]
Explain Log Rate Spikes: Fix client side code to transform groups into
table rows. (#147592)\n\nFixes client side code to transform groups into
table rows. Because the\r\ntransformation used a dictionary like
structure with field names as\r\nkeys, we missed if there were multiple
values for a field. This changes\r\nthe structure to an array of
field/value pairs so we can support\r\nmultiple values per
field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147592,"url":"https://github.com/elastic/kibana/pull/147592","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix client side code to transform groups into
table rows. (#147592)\n\nFixes client side code to transform groups into
table rows. Because the\r\ntransformation used a dictionary like
structure with field names as\r\nkeys, we missed if there were multiple
values for a field. This changes\r\nthe structure to an array of
field/value pairs so we can support\r\nmultiple values per
field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147592","number":147592,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix client side code to transform groups into
table rows. (#147592)\n\nFixes client side code to transform groups into
table rows. Because the\r\ntransformation used a dictionary like
structure with field names as\r\nkeys, we missed if there were multiple
values for a field. This changes\r\nthe structure to an array of
field/value pairs so we can support\r\nmultiple values per
field.","sha":"92ffe2764f01a67658db854506bbd5003f0adcb8"}}]}]
BACKPORT-->
 2022-12-20 02:39:02 -07:00
Hannah Mudge
d868e360a5
[8.6] [Dashboard] [Controls] Allow control changes to be discarded (#147482) (#147819) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Dashboard] [Controls] Allow control changes to be discarded
(#147482)](https://github.com/elastic/kibana/pull/147482)

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

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

<!--BACKPORT [{"author":{"name":"Hannah
Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-19T21:55:31Z","message":"[Dashboard]
[Controls] Allow control changes to be discarded (#147482)\n\nCloses
https://github.com/elastic/kibana/issues/147293\r\n\r\n##
Summary\r\n\r\nBefore this change, the Redux state `explicitInput` was
getting out of\r\nsync with the embeddable `explicitInput` in scenarios
where the new\r\n`explicitInput` was missing a key that the old
`explicitInput` had -\r\ntherefore, because they were out of sync, the
changes that **should**\r\nhave been discarded kept getting injected
back into the embeddable\r\n`explicitInput`, which made it impossible to
actually discard anything\r\nunless the key existed in both the before
and after state.\r\n\r\nThis PR fixes this by replacing the entire Redux
state `explicitInput`\r\nwith the embeddable `explicitInput` rather than
spreading the new value.\r\nIt also fixes a bug with the time slider
control where changes to the\r\nembeddable's input were not reflected
properly in the control's state,\r\nso nothing could be discarded even
after the initial bug was fixed.\r\n\r\n#### Further Explanation
\r\n\r\nWhen a control is first created, all the optional properties of
the\r\nexplicit input do not yet exist - for example, when creating an
options\r\nlist control, the `selections` key does not exist in the
`explicitInput`\r\nuntil a selection is made. Therefore, imagine the
following scenario:\r\n\r\n1. You create an options list control (where
the `selections` key does\r\nnot exist) and save the dashboard\r\n2. You
make some selections, which causes `unsaved changes` because
the\r\n`selections` key now exists and is equal to an array\r\n3. You
switch to view mode and choose to discard your changes,
thus\r\n(supposedly) removing the `selections` key from the
`explicitInput`\r\nobject once again\r\n\r\nUnfortunately, the Redux
embeddable state for each control was **not**\r\naccurately removing the
`selections` key as expected - this was because,\r\nwhen trying to
update the `explicitInput` via the old\r\n`updateEmbeddableReduxInput`,
the new value was **spread** on top of the\r\nolder value rather than
replacing it. In a simplified scenario, this\r\nresulted in something
like this:\r\n\r\n```typescript\r\nconst oldExplicitInput = { id:
'test_id', selections: ['test selection'] };\r\nconst newExplicitInput =
{ id: 'test_id' }\r\nconst result = { ...oldExplicitInput,
...newExplicitInput };\r\n```\r\n\r\nIn this code, because
`newExplicitInput` does not have the `selections`\r\nkey, `result` will
equal `{ id: 'test_id', selections: ['test\r\nselection'] }` - this is
not the behaviour we want! Instead, we wanted\r\nto replace the entire
old `explicitInput` with the new `explicitInput`.\r\nEffectively, that
is what this PR does.\r\n\r\nThanks to @ThomThomson for helping out with
finding the root cause of\r\nthis after I got lost :)\r\n\r\n### How to
Test\r\nFor both options list and range slider controls, \r\n1. Create a
control of the desired type\r\n2. Save the dashboard \r\n3. Make some
sort of change that causes unsaved changes - for example,\r\nmake a
selection or, if an options list control, set `exclude` to `true`\r\n4.
Switch to view mode, discarding the changes\r\n5. Ensure that the
changes made in step 3 are no longer applied ✅ \r\n6. Switch back to
edit mode\r\n7. Ensure that there are no `unsaved changes` ✅
\r\n\r\n#### Flaky Test
Runner\r\n\r\n<a\r\nhref=\"207701101-69cdfada-77c6-4510-b254-1fd1fa13af5c.png\"/></a>\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7a6eac8d1bfe492b8dce83c7a0f47dc26706e388","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Dashboard","release_note:fix","Feature:Input
Control","Team:Presentation","loe:days","impact:high","Project:Controls","backport:prev-minor","v8.7.0"],"number":147482,"url":"https://github.com/elastic/kibana/pull/147482","mergeCommit":{"message":"[Dashboard]
[Controls] Allow control changes to be discarded (#147482)\n\nCloses
https://github.com/elastic/kibana/issues/147293\r\n\r\n##
Summary\r\n\r\nBefore this change, the Redux state `explicitInput` was
getting out of\r\nsync with the embeddable `explicitInput` in scenarios
where the new\r\n`explicitInput` was missing a key that the old
`explicitInput` had -\r\ntherefore, because they were out of sync, the
changes that **should**\r\nhave been discarded kept getting injected
back into the embeddable\r\n`explicitInput`, which made it impossible to
actually discard anything\r\nunless the key existed in both the before
and after state.\r\n\r\nThis PR fixes this by replacing the entire Redux
state `explicitInput`\r\nwith the embeddable `explicitInput` rather than
spreading the new value.\r\nIt also fixes a bug with the time slider
control where changes to the\r\nembeddable's input were not reflected
properly in the control's state,\r\nso nothing could be discarded even
after the initial bug was fixed.\r\n\r\n#### Further Explanation
\r\n\r\nWhen a control is first created, all the optional properties of
the\r\nexplicit input do not yet exist - for example, when creating an
options\r\nlist control, the `selections` key does not exist in the
`explicitInput`\r\nuntil a selection is made. Therefore, imagine the
following scenario:\r\n\r\n1. You create an options list control (where
the `selections` key does\r\nnot exist) and save the dashboard\r\n2. You
make some selections, which causes `unsaved changes` because
the\r\n`selections` key now exists and is equal to an array\r\n3. You
switch to view mode and choose to discard your changes,
thus\r\n(supposedly) removing the `selections` key from the
`explicitInput`\r\nobject once again\r\n\r\nUnfortunately, the Redux
embeddable state for each control was **not**\r\naccurately removing the
`selections` key as expected - this was because,\r\nwhen trying to
update the `explicitInput` via the old\r\n`updateEmbeddableReduxInput`,
the new value was **spread** on top of the\r\nolder value rather than
replacing it. In a simplified scenario, this\r\nresulted in something
like this:\r\n\r\n```typescript\r\nconst oldExplicitInput = { id:
'test_id', selections: ['test selection'] };\r\nconst newExplicitInput =
{ id: 'test_id' }\r\nconst result = { ...oldExplicitInput,
...newExplicitInput };\r\n```\r\n\r\nIn this code, because
`newExplicitInput` does not have the `selections`\r\nkey, `result` will
equal `{ id: 'test_id', selections: ['test\r\nselection'] }` - this is
not the behaviour we want! Instead, we wanted\r\nto replace the entire
old `explicitInput` with the new `explicitInput`.\r\nEffectively, that
is what this PR does.\r\n\r\nThanks to @ThomThomson for helping out with
finding the root cause of\r\nthis after I got lost :)\r\n\r\n### How to
Test\r\nFor both options list and range slider controls, \r\n1. Create a
control of the desired type\r\n2. Save the dashboard \r\n3. Make some
sort of change that causes unsaved changes - for example,\r\nmake a
selection or, if an options list control, set `exclude` to `true`\r\n4.
Switch to view mode, discarding the changes\r\n5. Ensure that the
changes made in step 3 are no longer applied ✅ \r\n6. Switch back to
edit mode\r\n7. Ensure that there are no `unsaved changes` ✅
\r\n\r\n#### Flaky Test
Runner\r\n\r\n<a\r\nhref=\"207701101-69cdfada-77c6-4510-b254-1fd1fa13af5c.png\"/></a>\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7a6eac8d1bfe492b8dce83c7a0f47dc26706e388"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147482","number":147482,"mergeCommit":{"message":"[Dashboard]
[Controls] Allow control changes to be discarded (#147482)\n\nCloses
https://github.com/elastic/kibana/issues/147293\r\n\r\n##
Summary\r\n\r\nBefore this change, the Redux state `explicitInput` was
getting out of\r\nsync with the embeddable `explicitInput` in scenarios
where the new\r\n`explicitInput` was missing a key that the old
`explicitInput` had -\r\ntherefore, because they were out of sync, the
changes that **should**\r\nhave been discarded kept getting injected
back into the embeddable\r\n`explicitInput`, which made it impossible to
actually discard anything\r\nunless the key existed in both the before
and after state.\r\n\r\nThis PR fixes this by replacing the entire Redux
state `explicitInput`\r\nwith the embeddable `explicitInput` rather than
spreading the new value.\r\nIt also fixes a bug with the time slider
control where changes to the\r\nembeddable's input were not reflected
properly in the control's state,\r\nso nothing could be discarded even
after the initial bug was fixed.\r\n\r\n#### Further Explanation
\r\n\r\nWhen a control is first created, all the optional properties of
the\r\nexplicit input do not yet exist - for example, when creating an
options\r\nlist control, the `selections` key does not exist in the
`explicitInput`\r\nuntil a selection is made. Therefore, imagine the
following scenario:\r\n\r\n1. You create an options list control (where
the `selections` key does\r\nnot exist) and save the dashboard\r\n2. You
make some selections, which causes `unsaved changes` because
the\r\n`selections` key now exists and is equal to an array\r\n3. You
switch to view mode and choose to discard your changes,
thus\r\n(supposedly) removing the `selections` key from the
`explicitInput`\r\nobject once again\r\n\r\nUnfortunately, the Redux
embeddable state for each control was **not**\r\naccurately removing the
`selections` key as expected - this was because,\r\nwhen trying to
update the `explicitInput` via the old\r\n`updateEmbeddableReduxInput`,
the new value was **spread** on top of the\r\nolder value rather than
replacing it. In a simplified scenario, this\r\nresulted in something
like this:\r\n\r\n```typescript\r\nconst oldExplicitInput = { id:
'test_id', selections: ['test selection'] };\r\nconst newExplicitInput =
{ id: 'test_id' }\r\nconst result = { ...oldExplicitInput,
...newExplicitInput };\r\n```\r\n\r\nIn this code, because
`newExplicitInput` does not have the `selections`\r\nkey, `result` will
equal `{ id: 'test_id', selections: ['test\r\nselection'] }` - this is
not the behaviour we want! Instead, we wanted\r\nto replace the entire
old `explicitInput` with the new `explicitInput`.\r\nEffectively, that
is what this PR does.\r\n\r\nThanks to @ThomThomson for helping out with
finding the root cause of\r\nthis after I got lost :)\r\n\r\n### How to
Test\r\nFor both options list and range slider controls, \r\n1. Create a
control of the desired type\r\n2. Save the dashboard \r\n3. Make some
sort of change that causes unsaved changes - for example,\r\nmake a
selection or, if an options list control, set `exclude` to `true`\r\n4.
Switch to view mode, discarding the changes\r\n5. Ensure that the
changes made in step 3 are no longer applied ✅ \r\n6. Switch back to
edit mode\r\n7. Ensure that there are no `unsaved changes` ✅
\r\n\r\n#### Flaky Test
Runner\r\n\r\n<a\r\nhref=\"207701101-69cdfada-77c6-4510-b254-1fd1fa13af5c.png\"/></a>\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"7a6eac8d1bfe492b8dce83c7a0f47dc26706e388"}}]}]
BACKPORT-->
 2022-12-19 16:30:33 -07:00
Kibana Machine
1a94e763a7
[8.6] [@kbn/handlebars] Ensure only decorators have an options.args property (#147791) (#147799) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[@kbn/handlebars] Ensure only decorators have an `options.args`
property (#147791)](https://github.com/elastic/kibana/pull/147791)

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

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

<!--BACKPORT [{"author":{"name":"Thomas
Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T19:40:18Z","message":"[@kbn/handlebars]
Ensure only decorators have an `options.args` property
(#147791)\n\nAfter adding support for decorators an `args` property has
added to\r\n`HelperOptions` (which is shared with decorators). To not
leak this into\r\nregular helpers and to align with the upstream
handlebars, this PR\r\nremoves the `args` property from regular helpers
so that it's only\r\nvisible to
decorators.","sha":"800f45180cb1706a67f264ba5cee95c1a2031b8a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.7.0"],"number":147791,"url":"https://github.com/elastic/kibana/pull/147791","mergeCommit":{"message":"[@kbn/handlebars]
Ensure only decorators have an `options.args` property
(#147791)\n\nAfter adding support for decorators an `args` property has
added to\r\n`HelperOptions` (which is shared with decorators). To not
leak this into\r\nregular helpers and to align with the upstream
handlebars, this PR\r\nremoves the `args` property from regular helpers
so that it's only\r\nvisible to
decorators.","sha":"800f45180cb1706a67f264ba5cee95c1a2031b8a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147791","number":147791,"mergeCommit":{"message":"[@kbn/handlebars]
Ensure only decorators have an `options.args` property
(#147791)\n\nAfter adding support for decorators an `args` property has
added to\r\n`HelperOptions` (which is shared with decorators). To not
leak this into\r\nregular helpers and to align with the upstream
handlebars, this PR\r\nremoves the `args` property from regular helpers
so that it's only\r\nvisible to
decorators.","sha":"800f45180cb1706a67f264ba5cee95c1a2031b8a"}}]}]
BACKPORT-->

Co-authored-by: Thomas Watson <watson@elastic.co>
 2022-12-19 13:45:03 -07:00
Kibana Machine
47066b37dc
[8.6] [ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614) (#147792) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: Fix field candidate selection.
(#147614)](https://github.com/elastic/kibana/pull/147614)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:35:31Z","message":"[ML]
Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe
field candidate selection for Explain Log Rate Spikes was missing
a\r\ncheck if the supported field type is also aggregatable. For
example, a\r\n`keyword` type field could still be non-aggregatable if it
was both not\r\nindexed and `doc_values` set to `false`. Additionally,
if no groups were\r\ndetected, we showed a \"Try to continue analysis\"
button in the UI even\r\nif the analysis was able to finish. In this PR
the artificial logs dataset for functional tests was extended\r\nto
include a field like
that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147614,"url":"https://github.com/elastic/kibana/pull/147614","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe
field candidate selection for Explain Log Rate Spikes was missing
a\r\ncheck if the supported field type is also aggregatable. For
example, a\r\n`keyword` type field could still be non-aggregatable if it
was both not\r\nindexed and `doc_values` set to `false`. Additionally,
if no groups were\r\ndetected, we showed a \"Try to continue analysis\"
button in the UI even\r\nif the analysis was able to finish. In this PR
the artificial logs dataset for functional tests was extended\r\nto
include a field like
that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147614","number":147614,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix field candidate selection. (#147614)\n\nThe
field candidate selection for Explain Log Rate Spikes was missing
a\r\ncheck if the supported field type is also aggregatable. For
example, a\r\n`keyword` type field could still be non-aggregatable if it
was both not\r\nindexed and `doc_values` set to `false`. Additionally,
if no groups were\r\ndetected, we showed a \"Try to continue analysis\"
button in the UI even\r\nif the analysis was able to finish. In this PR
the artificial logs dataset for functional tests was extended\r\nto
include a field like
that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}}]}] BACKPORT-->

Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>
 2022-12-19 12:06:34 -07:00
Kibana Machine
18e8c0c45c
[8.6] [@kbn/handlebars] Code cleanup (#147425) (#147789) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[@kbn/handlebars] Code cleanup
(#147425)](https://github.com/elastic/kibana/pull/147425)

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

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

<!--BACKPORT [{"author":{"name":"Thomas
Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:24:26Z","message":"[@kbn/handlebars]
Code cleanup
(#147425)","sha":"b00a2643cd7a2980902ee693d67cc6b801daacab","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.7.0"],"number":147425,"url":"https://github.com/elastic/kibana/pull/147425","mergeCommit":{"message":"[@kbn/handlebars]
Code cleanup
(#147425)","sha":"b00a2643cd7a2980902ee693d67cc6b801daacab"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147425","number":147425,"mergeCommit":{"message":"[@kbn/handlebars]
Code cleanup
(#147425)","sha":"b00a2643cd7a2980902ee693d67cc6b801daacab"}}]}]
BACKPORT-->

Co-authored-by: Thomas Watson <watson@elastic.co>
 2022-12-19 11:31:30 -07:00
Kibana Machine
cf147cb76d
[8.6] Updates upgrade assistant doclinks to point to current rather than hard-coded 7.17 (#147585) (#147780) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Updates upgrade assistant doclinks to point to current rather than
hard-coded 7.17
(#147585)](https://github.com/elastic/kibana/pull/147585)

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

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

<!--BACKPORT [{"author":{"name":"Christiane (Tina)
Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T16:19:26Z","message":"Updates
upgrade assistant doclinks to point to current rather than hard-coded
7.17 (#147585)\n\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nFix
https://github.com/elastic/kibana/issues/145092","sha":"049d8021eb3cce6614a86a2904bc8d285f5ce028","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Feature:Upgrade
Assistant","docs","backport:prev-minor","v8.7.0"],"number":147585,"url":"https://github.com/elastic/kibana/pull/147585","mergeCommit":{"message":"Updates
upgrade assistant doclinks to point to current rather than hard-coded
7.17 (#147585)\n\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nFix
https://github.com/elastic/kibana/issues/145092","sha":"049d8021eb3cce6614a86a2904bc8d285f5ce028"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147585","number":147585,"mergeCommit":{"message":"Updates
upgrade assistant doclinks to point to current rather than hard-coded
7.17 (#147585)\n\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nFix
https://github.com/elastic/kibana/issues/145092","sha":"049d8021eb3cce6614a86a2904bc8d285f5ce028"}}]}]
BACKPORT-->

Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
 2022-12-19 11:42:16 -05:00
Kibana Machine
3d1a52e139
[8.6] [Enterprise Search] Add copy button for pipelines (#147712) (#147771) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Add copy button for pipelines
(#147712)](https://github.com/elastic/kibana/pull/147712)

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

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

<!--BACKPORT [{"author":{"name":"Sander
Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-19T14:24:26Z","message":"[Enterprise
Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy
button shows up for curl requests on the\r\nconnectors pipeline
page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":147712,"url":"https://github.com/elastic/kibana/pull/147712","mergeCommit":{"message":"[Enterprise
Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy
button shows up for curl requests on the\r\nconnectors pipeline
page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147712","number":147712,"mergeCommit":{"message":"[Enterprise
Search] Add copy button for pipelines (#147712)\n\nThis ensures the copy
button shows up for curl requests on the\r\nconnectors pipeline
page.","sha":"32de227cd1350dceffeae8b1093f4a81ad7103e9"}}]}] BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2022-12-19 09:36:29 -07:00
Lisa Cawley
6686c00b45
[8.6] [DOCS] Add server.publicBaseUrl to case setup (#147652) (#147726) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[DOCS] Add server.publicBaseUrl to case setup
(#147652)](https://github.com/elastic/kibana/pull/147652)

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

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

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2022-12-16T18:37:56Z","message":"[DOCS]
Add server.publicBaseUrl to case setup
(#147652)","sha":"a0671ed13e0faeabba3f50bb4873ac038d6719f5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:ResponseOps","docs","Feature:Cases","v8.7.0","8.6.1"],"number":147652,"url":"https://github.com/elastic/kibana/pull/147652","mergeCommit":{"message":"[DOCS]
Add server.publicBaseUrl to case setup
(#147652)","sha":"a0671ed13e0faeabba3f50bb4873ac038d6719f5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147652","number":147652,"mergeCommit":{"message":"[DOCS]
Add server.publicBaseUrl to case setup
(#147652)","sha":"a0671ed13e0faeabba3f50bb4873ac038d6719f5"}}]}]
BACKPORT-->
 2022-12-17 01:29:13 -05:00
Kibana Machine
656e3f7141
[8.6] [DOCS] Option to schedule Osquery packs for individual policies or globally (#146482) (#147719) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[DOCS] Option to schedule Osquery packs for individual policies or
globally (#146482)](https://github.com/elastic/kibana/pull/146482)

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

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

<!--BACKPORT
[{"author":{"name":"nastasha-solomon","email":"79124755+nastasha-solomon@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-16T20:39:58Z","message":"[DOCS]
Option to schedule Osquery packs for individual policies or globally
(#146482)\n\nAddresses
https://github.com/elastic/kibana/issues/146468.\r\n\r\nPreview\r\n[here](https://kibana_146482.docs-preview.app.elstc.co/guide/en/kibana/master/osquery.html#osquery-schedule-query)\r\n(updated
step 4).\r\n\r\nCo-authored-by: Joe Peeples
<joe.peeples@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d92e2f90bf6a93d39da55600b981eba92470b7fc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","Team:Asset
Mgmt","Osquery","v8.6.0","v8.7.0"],"number":146482,"url":"https://github.com/elastic/kibana/pull/146482","mergeCommit":{"message":"[DOCS]
Option to schedule Osquery packs for individual policies or globally
(#146482)\n\nAddresses
https://github.com/elastic/kibana/issues/146468.\r\n\r\nPreview\r\n[here](https://kibana_146482.docs-preview.app.elstc.co/guide/en/kibana/master/osquery.html#osquery-schedule-query)\r\n(updated
step 4).\r\n\r\nCo-authored-by: Joe Peeples
<joe.peeples@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d92e2f90bf6a93d39da55600b981eba92470b7fc"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146482","number":146482,"mergeCommit":{"message":"[DOCS]
Option to schedule Osquery packs for individual policies or globally
(#146482)\n\nAddresses
https://github.com/elastic/kibana/issues/146468.\r\n\r\nPreview\r\n[here](https://kibana_146482.docs-preview.app.elstc.co/guide/en/kibana/master/osquery.html#osquery-schedule-query)\r\n(updated
step 4).\r\n\r\nCo-authored-by: Joe Peeples
<joe.peeples@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d92e2f90bf6a93d39da55600b981eba92470b7fc"}}]}]
BACKPORT-->

Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com>
 2022-12-16 15:58:06 -05:00
Ersin Erdal
77715566f2
[8.6] [Fix] scheduling multiple recovered alert actions (#147617) (#147715) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Fix] scheduling multiple recovered alert actions
(#147617)](https://github.com/elastic/kibana/pull/147617)

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

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

<!--BACKPORT [{"author":{"name":"Ersin
Erdal","email":"92688503+ersin-erdal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-16T18:04:36Z","message":"[Fix]
scheduling multiple recovered alert actions (#147617)\n\nRemoves the
code that blocks running multiple recovered actions of
an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","ci:cloud-deploy","v8.7.0","v8.6.1"],"number":147617,"url":"https://github.com/elastic/kibana/pull/147617","mergeCommit":{"message":"[Fix]
scheduling multiple recovered alert actions (#147617)\n\nRemoves the
code that blocks running multiple recovered actions of
an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147617","number":147617,"mergeCommit":{"message":"[Fix]
scheduling multiple recovered alert actions (#147617)\n\nRemoves the
code that blocks running multiple recovered actions of
an\r\nalert.","sha":"5145f8d246ec3fa0ea05e0c975bed344457c2e1d"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
 2022-12-16 13:24:01 -07:00
Lisa Cawley
13a8c7c129
[8.6] [DOCS] Refresh alerting troubleshooting (#147633) (#147662) 2022-12-16 12:12:31 -05:00
Alison Goryachev
49a1e9b2e7
[Guided onboarding] Disable guided onboarding (#147649) 2022-12-16 11:30:50 -05:00
Kibana Machine
74baee4a17
[8.6] Consistency fixes for Elasticsearch client custom integrations (#147690) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Consistency fixes for Elasticsearch client custom
integrations](https://github.com/elastic/kibana/pull/147627)

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

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

<!--BACKPORT [{"author":{"name":"Seth Michael
Larson","email":"seth.larson@elastic.co"},"sourceCommit":{"committedDate":"2022-12-16T13:27:36Z","message":"Consistency
fixes for Elasticsearch client custom integrations\n\nThis PR is a
follow-up to a set of consistency fixes identified after\r\nall
integrations were completed. Removes the \"Generate API Key\"
button\r\nand also removes the example Cloud ID in favor of an
obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas
Chaulet
<nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.7.0"],"number":147627,"url":"https://github.com/elastic/kibana/pull/147627","mergeCommit":{"message":"Consistency
fixes for Elasticsearch client custom integrations\n\nThis PR is a
follow-up to a set of consistency fixes identified after\r\nall
integrations were completed. Removes the \"Generate API Key\"
button\r\nand also removes the example Cloud ID in favor of an
obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas
Chaulet
<nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147627","number":147627,"mergeCommit":{"message":"Consistency
fixes for Elasticsearch client custom integrations\n\nThis PR is a
follow-up to a set of consistency fixes identified after\r\nall
integrations were completed. Removes the \"Generate API Key\"
button\r\nand also removes the example Cloud ID in favor of an
obviously\r\nplaceholder Cloud ID value.\r\n\r\nCo-authored-by: Nicolas
Chaulet
<nicolas.chaulet@elastic.co>","sha":"959f8e9c6c2fd69b8c9556ad6147d3d470e4a239"}}]}]
BACKPORT-->

Co-authored-by: Seth Michael Larson <seth.larson@elastic.co>
 2022-12-16 08:08:10 -07:00
Kibana Machine
c6c52e17d5
[8.6] [ML] Explain Log Rate Spikes: Fix item set post processing. (#147499) (#147670) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: Fix item set post processing.
(#147499)](https://github.com/elastic/kibana/pull/147499)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-16T08:21:47Z","message":"[ML]
Explain Log Rate Spikes: Fix item set post processing.
(#147499)\n\nFixes cases where the item set post processing would end up
with duplicate
entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147499,"url":"https://github.com/elastic/kibana/pull/147499","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix item set post processing.
(#147499)\n\nFixes cases where the item set post processing would end up
with duplicate
entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147499","number":147499,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Fix item set post processing.
(#147499)\n\nFixes cases where the item set post processing would end up
with duplicate
entries.","sha":"6a87f7e844f59b551c63dce9eba33b989a6b4cb2"}}]}]
BACKPORT-->

Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>
 2022-12-16 02:27:19 -07:00
Kibana Machine
4b7303aa08
[8.6] [data.search.aggs] Add support for rate aggregation (#143487) (#147661) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[data.search.aggs] Add support for rate aggregation
(#143487)](https://github.com/elastic/kibana/pull/143487)

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

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

<!--BACKPORT [{"author":{"name":"Lukas
Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2022-12-15T23:49:20Z","message":"[data.search.aggs]
Add support for rate aggregation (#143487)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/131386.\r\n\r\nAdds support for
the rate aggregation. Usage may look something like
the\r\nfollowing:\r\n\r\n```ts\r\nconst aggs = [\r\n {\r\n type:
'date_histogram',\r\n params: {\r\n field: '@timestamp',\r\n interval:
'1h',\r\n },\r\n },\r\n {\r\n type: 'rate',\r\n params: {\r\n field:
'bytes', // optional\r\n unit: 'hour',\r\n },\r\n },\r\n];\r\nconst
aggsDsl = data.search.aggs.createAggConfigs(dataView,
aggs).toDsl();\r\n\r\n// Which generates the following DSL:\r\n{\r\n
\"1\": {\r\n \"date_histogram\": {\r\n \"field\": \"@timestamp\",\r\n
\"calendar_interval\": \"1h\",\r\n \"time_zone\":
\"America/Phoenix\",\r\n \"min_doc_count\": 1\r\n },\r\n \"aggs\": {\r\n
\"2\": {\r\n \"rate\": {\r\n \"field\": \"bytes\",\r\n \"unit\":
\"hour\"\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\nCo-authored-by:
Peter Pisljar
<peter.pisljar@elastic.co>","sha":"5a6bf1dacdb0d0a8969459c761dcdcf7347efb51","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Search","Feature:Aggregations","Team:AppServicesSv","release_note:skip","v8.6.0","v8.7.0"],"number":143487,"url":"https://github.com/elastic/kibana/pull/143487","mergeCommit":{"message":"[data.search.aggs]
Add support for rate aggregation (#143487)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/131386.\r\n\r\nAdds support for
the rate aggregation. Usage may look something like
the\r\nfollowing:\r\n\r\n```ts\r\nconst aggs = [\r\n {\r\n type:
'date_histogram',\r\n params: {\r\n field: '@timestamp',\r\n interval:
'1h',\r\n },\r\n },\r\n {\r\n type: 'rate',\r\n params: {\r\n field:
'bytes', // optional\r\n unit: 'hour',\r\n },\r\n },\r\n];\r\nconst
aggsDsl = data.search.aggs.createAggConfigs(dataView,
aggs).toDsl();\r\n\r\n// Which generates the following DSL:\r\n{\r\n
\"1\": {\r\n \"date_histogram\": {\r\n \"field\": \"@timestamp\",\r\n
\"calendar_interval\": \"1h\",\r\n \"time_zone\":
\"America/Phoenix\",\r\n \"min_doc_count\": 1\r\n },\r\n \"aggs\": {\r\n
\"2\": {\r\n \"rate\": {\r\n \"field\": \"bytes\",\r\n \"unit\":
\"hour\"\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\nCo-authored-by:
Peter Pisljar
<peter.pisljar@elastic.co>","sha":"5a6bf1dacdb0d0a8969459c761dcdcf7347efb51"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/143487","number":143487,"mergeCommit":{"message":"[data.search.aggs]
Add support for rate aggregation (#143487)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/131386.\r\n\r\nAdds support for
the rate aggregation. Usage may look something like
the\r\nfollowing:\r\n\r\n```ts\r\nconst aggs = [\r\n {\r\n type:
'date_histogram',\r\n params: {\r\n field: '@timestamp',\r\n interval:
'1h',\r\n },\r\n },\r\n {\r\n type: 'rate',\r\n params: {\r\n field:
'bytes', // optional\r\n unit: 'hour',\r\n },\r\n },\r\n];\r\nconst
aggsDsl = data.search.aggs.createAggConfigs(dataView,
aggs).toDsl();\r\n\r\n// Which generates the following DSL:\r\n{\r\n
\"1\": {\r\n \"date_histogram\": {\r\n \"field\": \"@timestamp\",\r\n
\"calendar_interval\": \"1h\",\r\n \"time_zone\":
\"America/Phoenix\",\r\n \"min_doc_count\": 1\r\n },\r\n \"aggs\": {\r\n
\"2\": {\r\n \"rate\": {\r\n \"field\": \"bytes\",\r\n \"unit\":
\"hour\"\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\n\r\n###
Checklist\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\nCo-authored-by:
Peter Pisljar
<peter.pisljar@elastic.co>","sha":"5a6bf1dacdb0d0a8969459c761dcdcf7347efb51"}}]}]
BACKPORT-->

Co-authored-by: Lukas Olson <lukas@elastic.co>
 2022-12-15 18:35:25 -07:00
Kaarina Tungseth
4290e35d8f
[DOCS] Adds the 8.6.0 release notes (#145768) 
## Summary

Adds the release notes for the 8.6.0 release.

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com>
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
 2022-12-15 14:37:36 -06:00
Jonathan Budzenski
8fc7affcbf skip flaky suite (#147222) 2022-12-15 12:29:55 -06:00
Kibana Machine
65a1706be4
[8.6] [Fleet] publish agents_per_version telemetry as separate docs (#147615) (#147622) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Fleet] publish `agents_per_version` telemetry as separate docs
(#147615)](https://github.com/elastic/kibana/pull/147615)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-15T15:15:10Z","message":"[Fleet]
publish `agents_per_version` telemetry as separate docs (#147615)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147543\r\n\r\nSending
`agents_per_version` telemetry as separate docs with a new
type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index
in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to
kibana, will result in 2\r\ndocuments sent\r\n```\r\n{
\"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{
\"agents_per_version\":
{\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is
visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add
a new indexer to have proper data
types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img
width=\"605\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":147615,"url":"https://github.com/elastic/kibana/pull/147615","mergeCommit":{"message":"[Fleet]
publish `agents_per_version` telemetry as separate docs (#147615)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147543\r\n\r\nSending
`agents_per_version` telemetry as separate docs with a new
type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index
in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to
kibana, will result in 2\r\ndocuments sent\r\n```\r\n{
\"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{
\"agents_per_version\":
{\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is
visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add
a new indexer to have proper data
types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img
width=\"605\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147615","number":147615,"mergeCommit":{"message":"[Fleet]
publish `agents_per_version` telemetry as separate docs (#147615)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147543\r\n\r\nSending
`agents_per_version` telemetry as separate docs with a new
type\r\n`fleet_agents`.\r\nThis docs then can be indexed to a new index
in telemetry.\r\n\r\nE.g. having 2 versions of agents enrolled to
kibana, will result in 2\r\ndocuments sent\r\n```\r\n{
\"agents_per_version\": {\"version\":\"8.2.0\",\"count\":2000}}\r\n{
\"agents_per_version\":
{\"version\":\"8.6.0\",\"count\":1}}\r\n\r\n```\r\n\r\nthe new data is
visible in staging, under `ebt-kibana-server` index\r\npattern, I'll add
a new indexer to have proper data
types:\r\nhttps://telemetry-v2-staging.elastic.dev/s/kibana-core/app/r/s/QbN5e\r\n<img
width=\"605\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/90178898/207886931-6d3e7922-9b18-45f5-8002-ff109b62310b.png\">","sha":"9273d2d373b6c54777dbf141dad4c2459984ac0c"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2022-12-15 10:04:47 -07:00
Kibana Machine
2f08d7ddaa
[8.6] [Security Solution] Reintroduce loading spinner while bulk deleting rules (#147598) (#147609) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] Reintroduce loading spinner while bulk deleting
rules (#147598)](https://github.com/elastic/kibana/pull/147598)

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

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

<!--BACKPORT [{"author":{"name":"Juan Pablo
Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2022-12-15T13:10:32Z","message":"[Security
Solution] Reintroduce loading spinner while bulk deleting rules
(#147598)\n\nRelates to
https://github.com/elastic/kibana/issues/147564\r\n\r\n##
Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the
behaviour of\r\nthe Rules Table, so that the table was fully disabled
(with an overlay\r\nloading spinner) during preflight requests. In the
other requests types,\r\n`enable`ing, `disable`ing and actual `edit`
requests, each rule would be\r\ndisabled individually.\r\n\r\nThis
however did not include **deletion**, so we incorrectly still\r\nallowed
the user to enable and disable rules while they were being
bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while
a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete
any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Management","Team:Detection
Rules","backport:prev-minor","v8.6.0","v8.7.0"],"number":147598,"url":"https://github.com/elastic/kibana/pull/147598","mergeCommit":{"message":"[Security
Solution] Reintroduce loading spinner while bulk deleting rules
(#147598)\n\nRelates to
https://github.com/elastic/kibana/issues/147564\r\n\r\n##
Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the
behaviour of\r\nthe Rules Table, so that the table was fully disabled
(with an overlay\r\nloading spinner) during preflight requests. In the
other requests types,\r\n`enable`ing, `disable`ing and actual `edit`
requests, each rule would be\r\ndisabled individually.\r\n\r\nThis
however did not include **deletion**, so we incorrectly still\r\nallowed
the user to enable and disable rules while they were being
bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while
a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete
any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147598","number":147598,"mergeCommit":{"message":"[Security
Solution] Reintroduce loading spinner while bulk deleting rules
(#147598)\n\nRelates to
https://github.com/elastic/kibana/issues/147564\r\n\r\n##
Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/145905 changed the
behaviour of\r\nthe Rules Table, so that the table was fully disabled
(with an overlay\r\nloading spinner) during preflight requests. In the
other requests types,\r\n`enable`ing, `disable`ing and actual `edit`
requests, each rule would be\r\ndisabled individually.\r\n\r\nThis
however did not include **deletion**, so we incorrectly still\r\nallowed
the user to enable and disable rules while they were being
bulk\r\ndeleted.\r\n\r\nThis PR fixes that by disabling the switch while
a delete action is in\r\nprogress.\r\n\r\n### Checklist\r\n\r\nDelete
any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
For maintainers\r\n\r\n- [ ] This was checked for breaking API changes
and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"9c3b76a19a4e45e764b861df86402b1fc0449c24"}}]}]
BACKPORT-->

Co-authored-by: Juan Pablo Djeredjian <jpdjeredjian@gmail.com>
 2022-12-15 07:41:28 -07:00
Dmitry Tomashevich
66d0f5590d
[8.6] [Discover] Fix Discover navigation from Lens embeddable (#147000) (#147608) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Discover] Fix Discover navigation from Lens embeddable
(#147000)](https://github.com/elastic/kibana/pull/147000)

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

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

<!--BACKPORT [{"author":{"name":"Dmitry
Tomashevich","email":"39378793+dimaanj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-14T13:17:17Z","message":"[Discover]
Fix Discover navigation from Lens embeddable (#147000)\n\n##
Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover
from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Marco Liberati
<dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","auto-backport","Team:DataDiscovery","v8.7.0","v8.6.1"],"number":147000,"url":"https://github.com/elastic/kibana/pull/147000","mergeCommit":{"message":"[Discover]
Fix Discover navigation from Lens embeddable (#147000)\n\n##
Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover
from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Marco Liberati
<dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147000","number":147000,"mergeCommit":{"message":"[Discover]
Fix Discover navigation from Lens embeddable (#147000)\n\n##
Summary\r\n\r\nFixes #146761\r\n\r\nThis PR fixes navigation to Discover
from Lens embeddable.\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Marco Liberati
<dej611@users.noreply.github.com>","sha":"1f04bf89a3df377c79dba225dd47c9a96dc3e395"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
 2022-12-15 06:52:57 -07:00
Kibana Machine
5d961c8ec0
[8.6] [Profiling] Add color for PHP JIT frames (#147495) (#147588) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Profiling] Add color for PHP JIT frames
(#147495)](https://github.com/elastic/kibana/pull/147495)

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

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

<!--BACKPORT [{"author":{"name":"Florian
Lehner","email":"florianl@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-15T06:35:21Z","message":"[Profiling]
Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for
the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.7.0","v8.6.1"],"number":147495,"url":"https://github.com/elastic/kibana/pull/147495","mergeCommit":{"message":"[Profiling]
Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for
the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147495","number":147495,"mergeCommit":{"message":"[Profiling]
Add color for PHP JIT frames (#147495)\n\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>\r\n\r\n## Summary\r\n\r\nAdd a color for
the PHP JIT frame type.\r\n\r\nSigned-off-by: Florian Lehner
<florian.lehner@elastic.cloud>","sha":"e7f858bdbe5539163d7e95ce6f41d973c841756e"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Florian Lehner <florianl@users.noreply.github.com>
 2022-12-15 00:41:35 -07:00
Xavier Mouligneau
6842085e4e
[8.6] [RAM] Reactivate most tests in triggers_actions_ui #147535 (#147582) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[RAM] Reactivate most tests in triggers_actions_ui
#147535](https://github.com/elastic/kibana/pull/147535)

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

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

<!--BACKPORT [{"author":{"name":"Ievgen
Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T21:15:30Z","message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection
Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":147550,"url":"https://github.com/elastic/kibana/pull/147550","mergeCommit":{"message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147550","number":147550,"mergeCommit":{"message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}}]}]
BACKPORT-->

Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
 2022-12-14 16:16:59 -07:00
Kibana Machine
74a68fd452
[8.6] [Security Solution] ML job enchancement: update warning message (#147550) (#147580) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] ML job enchancement: update warning message
(#147550)](https://github.com/elastic/kibana/pull/147550)

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

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

<!--BACKPORT [{"author":{"name":"Ievgen
Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T21:15:30Z","message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection
Alerts","backport:prev-minor","ci:cloud-deploy","v8.7.0"],"number":147550,"url":"https://github.com/elastic/kibana/pull/147550","mergeCommit":{"message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147550","number":147550,"mergeCommit":{"message":"[Security
Solution] ML job enchancement: update warning message (#147550)\n\n##
Summary\r\n\r\nThese changes update the wording around the ML job
selection in ML rule.\r\nAs we gonna try to start selected job/s in case
those are not running,\r\nwe should accordingly mention that in the
callout below the job\r\nselection
combobox.\r\n\r\nSlack\r\n[discussion](https://elastic.slack.com/archives/C03DXS9UZDF/p1670950300234779)\r\n\r\nMain
ticket:\r\n[#1912](https://github.com/elastic/security-team/issues/1912)\r\n\r\n<img
width=\"1860\" alt=\"Screenshot 2022-12-14 at 17 50
48\"\r\nsrc=\"https://user-images.githubusercontent.com/2700761/207658080-deb81240-3643-4634-aa01-0c9dee59c3b2.png\">\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b74e7f9b8227a3229b0a2b8099df776d1761fb86"}}]}]
BACKPORT-->

Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co>
 2022-12-14 15:44:01 -07:00
Kibana Machine
346a7a0c78
[8.6] [Discover] Fixes the transition from Discover to Lens for the Visualize button (#147502) (#147559) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Discover] Fixes the transition from Discover to Lens for the
Visualize button
(#147502)](https://github.com/elastic/kibana/pull/147502)

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

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

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T17:24:11Z","message":"[Discover]
Fixes the transition from Discover to Lens for the Visualize button
(#147502)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a
regression that exists on 8.6.0 when the users are trying
to\r\nVisualize a field and have selected columns in
Discover.\r\n\r\nThe problem is that the text based datasource is also
providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra
checks:\r\n\r\n- if the context has the fieldname it returns empty
suggestions (in the\r\ntext based mode we suggest based on the query and
not the field\r\n- If there is no aggregate query we also return empty
suggestions\r\n\r\n\r\n![discover](https://user-images.githubusercontent.com/17003240/207583040-fb58d5d8-bb26-48bb-b809-fe8091b93619.gif)\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.7.0","v8.6.1"],"number":147502,"url":"https://github.com/elastic/kibana/pull/147502","mergeCommit":{"message":"[Discover]
Fixes the transition from Discover to Lens for the Visualize button
(#147502)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a
regression that exists on 8.6.0 when the users are trying
to\r\nVisualize a field and have selected columns in
Discover.\r\n\r\nThe problem is that the text based datasource is also
providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra
checks:\r\n\r\n- if the context has the fieldname it returns empty
suggestions (in the\r\ntext based mode we suggest based on the query and
not the field\r\n- If there is no aggregate query we also return empty
suggestions\r\n\r\n\r\n![discover](https://user-images.githubusercontent.com/17003240/207583040-fb58d5d8-bb26-48bb-b809-fe8091b93619.gif)\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147502","number":147502,"mergeCommit":{"message":"[Discover]
Fixes the transition from Discover to Lens for the Visualize button
(#147502)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/147479\r\n\r\nThis is a
regression that exists on 8.6.0 when the users are trying
to\r\nVisualize a field and have selected columns in
Discover.\r\n\r\nThe problem is that the text based datasource is also
providing some\r\nsuggestions while it shouldn't. This PR adds 2 extra
checks:\r\n\r\n- if the context has the fieldname it returns empty
suggestions (in the\r\ntext based mode we suggest based on the query and
not the field\r\n- If there is no aggregate query we also return empty
suggestions\r\n\r\n\r\n![discover](https://user-images.githubusercontent.com/17003240/207583040-fb58d5d8-bb26-48bb-b809-fe8091b93619.gif)\r\n\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"1382f48c604f56b15a2a1c587bc7044aef6c51a4"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2022-12-14 11:51:48 -07:00
Kibana Machine
1adab28560
[8.6] [maps] Fix uploading FeatureCollection as feature when file contains single Feature (#147207) (#147556) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[maps] Fix uploading FeatureCollection as feature when file contains
single Feature (#147207)](https://github.com/elastic/kibana/pull/147207)

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

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

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T17:08:00Z","message":"[maps]
Fix uploading FeatureCollection as feature when file contains single
Feature (#147207)\n\nFixes
https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge
case where when uploading a file containing a\r\nFeatureCollection with
a single feature, the results incorrectly state\r\nthat 2 features where
indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","backport:prev-minor","Feature:Maps","v8.7.0"],"number":147207,"url":"https://github.com/elastic/kibana/pull/147207","mergeCommit":{"message":"[maps]
Fix uploading FeatureCollection as feature when file contains single
Feature (#147207)\n\nFixes
https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge
case where when uploading a file containing a\r\nFeatureCollection with
a single feature, the results incorrectly state\r\nthat 2 features where
indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147207","number":147207,"mergeCommit":{"message":"[maps]
Fix uploading FeatureCollection as feature when file contains single
Feature (#147207)\n\nFixes
https://github.com/elastic/kibana/issues/146417\r\n\r\nPR resolves edge
case where when uploading a file containing a\r\nFeatureCollection with
a single feature, the results incorrectly state\r\nthat 2 features where
indexed with one failing.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"58c11ed59cf73683cd4b3c2bfbfc1623df399705"}}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
 2022-12-14 11:11:03 -07:00
Kibana Machine
8079031ff2
[8.6] [Profiling] Remove link to 'Other' bucket (#147523) (#147540) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Profiling] Remove link to 'Other' bucket
(#147523)](https://github.com/elastic/kibana/pull/147523)

<!--- 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":"2022-12-14T15:57:32Z","message":"[Profiling]
Remove link to 'Other' bucket (#147523)\n\nCloses
https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v8.7.0","v8.6.1"],"number":147523,"url":"https://github.com/elastic/kibana/pull/147523","mergeCommit":{"message":"[Profiling]
Remove link to 'Other' bucket (#147523)\n\nCloses
https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147523","number":147523,"mergeCommit":{"message":"[Profiling]
Remove link to 'Other' bucket (#147523)\n\nCloses
https://github.com/elastic/prodfiler/issues/2739","sha":"f2fcb1c5afc19f8439dfff4c4137e1b2253478dc"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co>
 2022-12-14 09:59:18 -07:00
Kibana Machine
690e4a15b3
[8.6] [Fleet] added a logic to use destinationId when tagging imported SOs (#147439) (#147528) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Fleet] added a logic to use `destinationId` when tagging imported
SOs (#147439)](https://github.com/elastic/kibana/pull/147439)

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

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

<!--BACKPORT [{"author":{"name":"Julia
Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-14T14:09:23Z","message":"[Fleet]
added a logic to use `destinationId` when tagging imported SOs
(#147439)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing
an integration, and some assets already exist in Kibana,\r\nthe imported
SOs will recieve a newly generated ID. This caused a\r\nproblem
previously when the tagging logic didn't find the SOs with
their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those
SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to
verify**\r\n1. Add system integration in default space\r\n2. Enroll an
agent and wait for system metrics to be ingested\r\n3. Create an Admin
space\r\n4. Remove the system package policy, and uninstall the system
package\r\nfrom Default space\r\n5. Go to Admin space and add system
integration again\r\n6. Verify that the integration is added
successfully, assets are created\r\nin Admin space and assets are tagged
with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x]
[Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.6.0","v8.7.0","v8.5.4"],"number":147439,"url":"https://github.com/elastic/kibana/pull/147439","mergeCommit":{"message":"[Fleet]
added a logic to use `destinationId` when tagging imported SOs
(#147439)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing
an integration, and some assets already exist in Kibana,\r\nthe imported
SOs will recieve a newly generated ID. This caused a\r\nproblem
previously when the tagging logic didn't find the SOs with
their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those
SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to
verify**\r\n1. Add system integration in default space\r\n2. Enroll an
agent and wait for system metrics to be ingested\r\n3. Create an Admin
space\r\n4. Remove the system package policy, and uninstall the system
package\r\nfrom Default space\r\n5. Go to Admin space and add system
integration again\r\n6. Verify that the integration is added
successfully, assets are created\r\nin Admin space and assets are tagged
with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x]
[Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266"}},"sourceBranch":"main","suggestedTargetBranches":["8.6","8.5"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147439","number":147439,"mergeCommit":{"message":"[Fleet]
added a logic to use `destinationId` when tagging imported SOs
(#147439)\n\n## Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/147364\r\n\r\nWhen installing
an integration, and some assets already exist in Kibana,\r\nthe imported
SOs will recieve a newly generated ID. This caused a\r\nproblem
previously when the tagging logic didn't find the SOs with
their\r\noriginal ID.\r\nThe fix takes the new `destinationId` of those
SOs, so the tagging can\r\ncomplete successfully.\r\n\r\n**Steps to
verify**\r\n1. Add system integration in default space\r\n2. Enroll an
agent and wait for system metrics to be ingested\r\n3. Create an Admin
space\r\n4. Remove the system package policy, and uninstall the system
package\r\nfrom Default space\r\n5. Go to Admin space and add system
integration again\r\n6. Verify that the integration is added
successfully, assets are created\r\nin Admin space and assets are tagged
with Managed and System tags.\r\n\r\n\r\n### Checklist\r\n\r\n- [x]
[Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7cee9fff787f1d647142d711f9f2618dd9dbc266"}},{"branch":"8.5","label":"v8.5.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2022-12-14 08:14:20 -07:00
Kibana Machine
c9ca8486c0
[8.6] Do not skip UPDATE_TARGET_MAPPINGS if upgrading to a newer stack version (#147503) (#147522) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Do not skip UPDATE_TARGET_MAPPINGS if upgrading to a newer stack
version (#147503)](https://github.com/elastic/kibana/pull/147503)

<!--- 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":"2022-12-14T13:39:47Z","message":"Do
not skip UPDATE_TARGET_MAPPINGS if upgrading to a newer stack version
(#147503)\n\nFixes
https://github.com/elastic/kibana/issues/147450","sha":"4f72a2eb5beded9a3086de7766021d9b65a197f3","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:Core","release_note:skip","Feature:Migrations","backport:prev-minor","v8.6.0","v8.7.0","v8.6.1"],"number":147503,"url":"https://github.com/elastic/kibana/pull/147503","mergeCommit":{"message":"Do
not skip UPDATE_TARGET_MAPPINGS if upgrading to a newer stack version
(#147503)\n\nFixes
https://github.com/elastic/kibana/issues/147450","sha":"4f72a2eb5beded9a3086de7766021d9b65a197f3"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147503","number":147503,"mergeCommit":{"message":"Do
not skip UPDATE_TARGET_MAPPINGS if upgrading to a newer stack version
(#147503)\n\nFixes
https://github.com/elastic/kibana/issues/147450","sha":"4f72a2eb5beded9a3086de7766021d9b65a197f3"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
 2022-12-14 07:45:35 -07:00
Yngrid Coello
e4711bb3eb
[8.6] [APM] Switching service groups from grid to flex layout (#147448) (#147513) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[APM] Switching service groups from grid to flex layout
(#147448)](https://github.com/elastic/kibana/pull/147448)

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

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

<!--BACKPORT [{"author":{"name":"Yngrid
Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T11:03:32Z","message":"[APM]
Switching service groups from grid to flex layout (#147448)\n\nCloses
https://github.com/elastic/kibana/issues/147435.\r\n\r\n### Changes\r\n-
`ServiceGroupList` is now using `EuiFlexGroup`. Grid is not
suitable\r\nfor this case since the `ServiceGroupCard` has a fixed
width.\r\n- `ServiceGroupCard` width is changed to `100%` when we are in
mobile\r\nresolutions.\r\n\r\n**Before**\r\n\r\n\r\n207371298-fc970def-332f-4cfe-9603-efdf68f1ce8e.mov","sha":"d53a159405dd90e8f70c18d137ce5997d6403cd8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:APM","release_note:skip","v8.6.0","v8.7.0"],"number":147448,"url":"https://github.com/elastic/kibana/pull/147448","mergeCommit":{"message":"[APM]
Switching service groups from grid to flex layout (#147448)\n\nCloses
https://github.com/elastic/kibana/issues/147435.\r\n\r\n### Changes\r\n-
`ServiceGroupList` is now using `EuiFlexGroup`. Grid is not
suitable\r\nfor this case since the `ServiceGroupCard` has a fixed
width.\r\n- `ServiceGroupCard` width is changed to `100%` when we are in
mobile\r\nresolutions.\r\n\r\n**Before**\r\n\r\n\r\n207371298-fc970def-332f-4cfe-9603-efdf68f1ce8e.mov","sha":"d53a159405dd90e8f70c18d137ce5997d6403cd8"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147448","number":147448,"mergeCommit":{"message":"[APM]
Switching service groups from grid to flex layout (#147448)\n\nCloses
https://github.com/elastic/kibana/issues/147435.\r\n\r\n### Changes\r\n-
`ServiceGroupList` is now using `EuiFlexGroup`. Grid is not
suitable\r\nfor this case since the `ServiceGroupCard` has a fixed
width.\r\n- `ServiceGroupCard` width is changed to `100%` when we are in
mobile\r\nresolutions.\r\n\r\n**Before**\r\n\r\n\r\n207371298-fc970def-332f-4cfe-9603-efdf68f1ce8e.mov","sha":"d53a159405dd90e8f70c18d137ce5997d6403cd8"}}]}]
BACKPORT-->
 2022-12-14 06:52:52 -07:00
Kibana Machine
a8726a0c55
[8.6] [Vega] Fix charts are leaking memory on each refresh (#147309) (#147337) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Vega] Fix charts are leaking memory on each refresh
(#147309)](https://github.com/elastic/kibana/pull/147309)

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

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

<!--BACKPORT [{"author":{"name":"Alexey
Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2022-12-12T10:21:59Z","message":"[Vega]
Fix charts are leaking memory on each refresh (#147309)\n\nCloses:
#146170\r\n\r\n**Summary:** \r\n[Vega] Fix charts are leaking memory on
each refresh\r\n\r\n**Steps for checking:** \r\n1. Create a new
`Dashboard` with one `Vega Visualization `(or two)\r\n2. Open **Dev
tools** -> **Memory** -> **Heap snapshot** -> **Take\r\nsnapshot**
(execute `Collect Garbage` before)\r\n3. Do refresh `Dashboard` \r\n4.
Execute step 2 and compare snapshots\r\n\r\n\r\n**Before:**\r\n\r\n<img
width=\"767\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700742-4f6cb8ad-5a0f-41a5-8a0a-6f058f43d124.png\">\r\n
\r\n**After:**\r\n\r\n<img width=\"765\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700824-9f96e44a-7860-47fa-ba3e-acf9b05b1ae1.png\">\r\n\r\nCo-authored-by:
Yaroslav Kuznietsov
<kuznetsov.yaroslav.yk@gmail.com>","sha":"df65cd907c8e1a91f4675cb8c8c544ab6d88bf06","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Vega","Team:Visualizations","backport:prev-minor","v8.7.0","v8.6.1"],"number":147309,"url":"https://github.com/elastic/kibana/pull/147309","mergeCommit":{"message":"[Vega]
Fix charts are leaking memory on each refresh (#147309)\n\nCloses:
#146170\r\n\r\n**Summary:** \r\n[Vega] Fix charts are leaking memory on
each refresh\r\n\r\n**Steps for checking:** \r\n1. Create a new
`Dashboard` with one `Vega Visualization `(or two)\r\n2. Open **Dev
tools** -> **Memory** -> **Heap snapshot** -> **Take\r\nsnapshot**
(execute `Collect Garbage` before)\r\n3. Do refresh `Dashboard` \r\n4.
Execute step 2 and compare snapshots\r\n\r\n\r\n**Before:**\r\n\r\n<img
width=\"767\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700742-4f6cb8ad-5a0f-41a5-8a0a-6f058f43d124.png\">\r\n
\r\n**After:**\r\n\r\n<img width=\"765\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700824-9f96e44a-7860-47fa-ba3e-acf9b05b1ae1.png\">\r\n\r\nCo-authored-by:
Yaroslav Kuznietsov
<kuznetsov.yaroslav.yk@gmail.com>","sha":"df65cd907c8e1a91f4675cb8c8c544ab6d88bf06"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147309","number":147309,"mergeCommit":{"message":"[Vega]
Fix charts are leaking memory on each refresh (#147309)\n\nCloses:
#146170\r\n\r\n**Summary:** \r\n[Vega] Fix charts are leaking memory on
each refresh\r\n\r\n**Steps for checking:** \r\n1. Create a new
`Dashboard` with one `Vega Visualization `(or two)\r\n2. Open **Dev
tools** -> **Memory** -> **Heap snapshot** -> **Take\r\nsnapshot**
(execute `Collect Garbage` before)\r\n3. Do refresh `Dashboard` \r\n4.
Execute step 2 and compare snapshots\r\n\r\n\r\n**Before:**\r\n\r\n<img
width=\"767\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700742-4f6cb8ad-5a0f-41a5-8a0a-6f058f43d124.png\">\r\n
\r\n**After:**\r\n\r\n<img width=\"765\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/20072247/206700824-9f96e44a-7860-47fa-ba3e-acf9b05b1ae1.png\">\r\n\r\nCo-authored-by:
Yaroslav Kuznietsov
<kuznetsov.yaroslav.yk@gmail.com>","sha":"df65cd907c8e1a91f4675cb8c8c544ab6d88bf06"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2022-12-14 04:40:12 -07:00
Kibana Machine
29576ba168
[8.6] [Discover] Fix saved search with custom label running into "aborted" error on a dashboard (#147310) (#147496) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Discover] Fix saved search with custom label running into "aborted"
error on a dashboard
(#147310)](https://github.com/elastic/kibana/pull/147310)

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

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

<!--BACKPORT [{"author":{"name":"Matthias
Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2022-12-14T09:49:22Z","message":"[Discover]
Fix saved search with custom label running into \"aborted\" error on a
dashboard
(#147310)","sha":"e3364c9c3d8f0f2ae3f1273969823b3c6d275bae","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-minor","v8.7.0"],"number":147310,"url":"https://github.com/elastic/kibana/pull/147310","mergeCommit":{"message":"[Discover]
Fix saved search with custom label running into \"aborted\" error on a
dashboard
(#147310)","sha":"e3364c9c3d8f0f2ae3f1273969823b3c6d275bae"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147310","number":147310,"mergeCommit":{"message":"[Discover]
Fix saved search with custom label running into \"aborted\" error on a
dashboard
(#147310)","sha":"e3364c9c3d8f0f2ae3f1273969823b3c6d275bae"}}]}]
BACKPORT-->

Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>
 2022-12-14 03:52:22 -07:00
Kibana Machine
fb98bca516
[8.6] [RAM] Fix docLink for Connectors (#147395) (#147487) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[RAM] Fix docLink for Connectors
(#147395)](https://github.com/elastic/kibana/pull/147395)

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

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

<!--BACKPORT [{"author":{"name":"Zacqary Adam
Xeper","email":"Zacqary@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-12-13T23:39:42Z","message":"[RAM]
Fix docLink for Connectors (#147395)\n\n## Summary\r\n\r\nFixes #146164
\r\n\r\nDocumentation for Connectors didn't make it into the PR that
added the\r\nnew page. This fixes the broken link.\r\n\r\n\r\n###
Checklist\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"cbcc675811a7089ffc8779e52d740c2065528209","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.7.0","v8.6.1"],"number":147395,"url":"https://github.com/elastic/kibana/pull/147395","mergeCommit":{"message":"[RAM]
Fix docLink for Connectors (#147395)\n\n## Summary\r\n\r\nFixes #146164
\r\n\r\nDocumentation for Connectors didn't make it into the PR that
added the\r\nnew page. This fixes the broken link.\r\n\r\n\r\n###
Checklist\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"cbcc675811a7089ffc8779e52d740c2065528209"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147395","number":147395,"mergeCommit":{"message":"[RAM]
Fix docLink for Connectors (#147395)\n\n## Summary\r\n\r\nFixes #146164
\r\n\r\nDocumentation for Connectors didn't make it into the PR that
added the\r\nnew page. This fixes the broken link.\r\n\r\n\r\n###
Checklist\r\n\r\n-
[x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or
tutorials\r\n\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"cbcc675811a7089ffc8779e52d740c2065528209"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Zacqary Adam Xeper <Zacqary@users.noreply.github.com>
 2022-12-13 17:48:42 -07:00