github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-22 00:45:43 -04:00
Code Issues Projects Releases Packages Wiki Activity
58852 commits 434 branches 496 tags 22 GiB
Commit graph

27354 commits

Author SHA1 Message Date
Gloria Hornero
5378a1e7e5
[8.6] [Security Solution] [Platform] Updates description default message (#146165) (#146256) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] [Platform] Updates description default message
(#146165)](https://github.com/elastic/kibana/pull/146165)

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

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

<!--BACKPORT [{"author":{"name":"Gloria
Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T09:14:54Z","message":"[Security
Solution] [Platform] Updates description default message
(#146165)","sha":"c76ed9ea1c6d6e49399980be3a2666e7c16c9b6f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Security Solution
Platform","v8.6.0","v8.7.0"],"number":146165,"url":"https://github.com/elastic/kibana/pull/146165","mergeCommit":{"message":"[Security
Solution] [Platform] Updates description default message
(#146165)","sha":"c76ed9ea1c6d6e49399980be3a2666e7c16c9b6f"}},"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/146165","number":146165,"mergeCommit":{"message":"[Security
Solution] [Platform] Updates description default message
(#146165)","sha":"c76ed9ea1c6d6e49399980be3a2666e7c16c9b6f"}}]}]
BACKPORT-->
 2022-11-24 03:42:46 -07:00
Kibana Machine
66f900f93b
[8.6] [RAM] fix logger bug (#146139) (#146253) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[RAM] fix logger bug
(#146139)](https://github.com/elastic/kibana/pull/146139)

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

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

<!--BACKPORT
[{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2022-11-24T08:24:19Z","message":"[RAM]
fix logger bug (#146139)\n\nResolves:
https://github.com/elastic/kibana/issues/146097\r\n\r\n##
Summary\r\n\r\nIn this PR I'm fixing a bug for bulkDelete
endpoint.\r\nIt loggers this error
message:\r\n`[2022-11-22T15:19:31.182+01:00][ERROR][plugins.alerting]
Failure to\r\ndelete schedules for underlying tasks:` even if we do not
have any\r\nfailed to delete tasks.\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":"ad8373c46ff92537f655c095fe58bb634d946a7b","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","backport:prev-minor","v8.6.0"],"number":146139,"url":"https://github.com/elastic/kibana/pull/146139","mergeCommit":{"message":"[RAM]
fix logger bug (#146139)\n\nResolves:
https://github.com/elastic/kibana/issues/146097\r\n\r\n##
Summary\r\n\r\nIn this PR I'm fixing a bug for bulkDelete
endpoint.\r\nIt loggers this error
message:\r\n`[2022-11-22T15:19:31.182+01:00][ERROR][plugins.alerting]
Failure to\r\ndelete schedules for underlying tasks:` even if we do not
have any\r\nfailed to delete tasks.\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":"ad8373c46ff92537f655c095fe58bb634d946a7b"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Julia <iuliia.guskova@elastic.co>
 2022-11-24 03:03:53 -07:00
Kibana Machine
fbf1981c00
[8.6] [ML] Fix Anomaly explorer console error because mismatching data view shape (#146152) (#146244) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Fix Anomaly explorer console error because mismatching data view
shape (#146152)](https://github.com/elastic/kibana/pull/146152)

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

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

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T22:32:57Z","message":"[ML]
Fix Anomaly explorer console error because mismatching data view shape
(#146152)\n\nfixes
https://github.com/elastic/kibana/issues/144341","sha":"42dbbdaeabab36094e8fea1d874827eb2af2fe9e","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","v8.6.0","v8.7.0"],"number":146152,"url":"https://github.com/elastic/kibana/pull/146152","mergeCommit":{"message":"[ML]
Fix Anomaly explorer console error because mismatching data view shape
(#146152)\n\nfixes
https://github.com/elastic/kibana/issues/144341","sha":"42dbbdaeabab36094e8fea1d874827eb2af2fe9e"}},"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/146152","number":146152,"mergeCommit":{"message":"[ML]
Fix Anomaly explorer console error because mismatching data view shape
(#146152)\n\nfixes
https://github.com/elastic/kibana/issues/144341","sha":"42dbbdaeabab36094e8fea1d874827eb2af2fe9e"}}]}]
BACKPORT-->

Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
 2022-11-23 16:38:27 -07:00
Kibana Machine
beeae697a7
[8.6] [Synthetics] Improve image loading on step change (#145967) (#146218) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Synthetics] Improve image loading on step change
(#145967)](https://github.com/elastic/kibana/pull/145967)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T19:40:54Z","message":"[Synthetics]
Improve image loading on step change (#145967)\n\nCo-authored-by: Abdul
Zahid <awahab07@yahoo.com>\r\nFixes
https://github.com/elastic/kibana/issues/145911","sha":"3a3bd141e802f0f8b7fbfd457efaef2c7389a460","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145967,"url":"https://github.com/elastic/kibana/pull/145967","mergeCommit":{"message":"[Synthetics]
Improve image loading on step change (#145967)\n\nCo-authored-by: Abdul
Zahid <awahab07@yahoo.com>\r\nFixes
https://github.com/elastic/kibana/issues/145911","sha":"3a3bd141e802f0f8b7fbfd457efaef2c7389a460"}},"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/145967","number":145967,"mergeCommit":{"message":"[Synthetics]
Improve image loading on step change (#145967)\n\nCo-authored-by: Abdul
Zahid <awahab07@yahoo.com>\r\nFixes
https://github.com/elastic/kibana/issues/145911","sha":"3a3bd141e802f0f8b7fbfd457efaef2c7389a460"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad.muhammad@elastic.co>
 2022-11-23 15:47:15 -07:00
Catherine Liu
46052ad87d
[8.6] [Canvas] Fixes broken data view sort (#146209) (#146232) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Canvas] Fixes broken data view sort
(#146209)](https://github.com/elastic/kibana/pull/146209)

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

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

<!--BACKPORT [{"author":{"name":"Catherine
Liu","email":"catherine.liu@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T20:54:10Z","message":"[Canvas]
Fixes broken data view sort (#146209)\n\n## Summary\r\n\r\nCloses
#146171.\r\n\r\nThis sorting function for the data view options was
assuming that `name`\r\nwas always defined, but with some legacy data
views/index patterns,\r\n`name` is not defined and only `title` is. This
changes the sort\r\nfunction to use `name` or `title` when sorting, so
it doesn't error out\r\nwhen `name` or `title` is missing. I also
noticed that we were still\r\nusing the data plugin here instead of the
data views plugin directly, so\r\nI fixed that too.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
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":"87e88694f2ef3c32e0ace5a35704f992fcef2f0a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","Team:Presentation","loe:hours","release_note:skip","impact:critical","Feature:Canvas","v8.6.0","v8.7.0"],"number":146209,"url":"https://github.com/elastic/kibana/pull/146209","mergeCommit":{"message":"[Canvas]
Fixes broken data view sort (#146209)\n\n## Summary\r\n\r\nCloses
#146171.\r\n\r\nThis sorting function for the data view options was
assuming that `name`\r\nwas always defined, but with some legacy data
views/index patterns,\r\n`name` is not defined and only `title` is. This
changes the sort\r\nfunction to use `name` or `title` when sorting, so
it doesn't error out\r\nwhen `name` or `title` is missing. I also
noticed that we were still\r\nusing the data plugin here instead of the
data views plugin directly, so\r\nI fixed that too.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
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":"87e88694f2ef3c32e0ace5a35704f992fcef2f0a"}},"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/146209","number":146209,"mergeCommit":{"message":"[Canvas]
Fixes broken data view sort (#146209)\n\n## Summary\r\n\r\nCloses
#146171.\r\n\r\nThis sorting function for the data view options was
assuming that `name`\r\nwas always defined, but with some legacy data
views/index patterns,\r\n`name` is not defined and only `title` is. This
changes the sort\r\nfunction to use `name` or `title` when sorting, so
it doesn't error out\r\nwhen `name` or `title` is missing. I also
noticed that we were still\r\nusing the data plugin here instead of the
data views plugin directly, so\r\nI fixed that too.\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n###
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":"87e88694f2ef3c32e0ace5a35704f992fcef2f0a"}}]}]
BACKPORT-->
 2022-11-23 14:54:47 -07:00
Kibana Machine
c929f357fa
[8.6] [ML] Anomaly Detection: Adds functional tests for filtering by influencers in the Anomaly Explorer (#146085) (#146215) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Anomaly Detection: Adds functional tests for filtering by
influencers in the Anomaly Explorer
(#146085)](https://github.com/elastic/kibana/pull/146085)

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

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

<!--BACKPORT [{"author":{"name":"Melissa
Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T19:00:34Z","message":"[ML]
Anomaly Detection: Adds functional tests for filtering by influencers in
the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests
for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky
test
build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","v8.6.0","v8.7.0"],"number":146085,"url":"https://github.com/elastic/kibana/pull/146085","mergeCommit":{"message":"[ML]
Anomaly Detection: Adds functional tests for filtering by influencers in
the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests
for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky
test
build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389"}},"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/146085","number":146085,"mergeCommit":{"message":"[ML]
Anomaly Detection: Adds functional tests for filtering by influencers in
the Anomaly Explorer (#146085)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142456\r\nAdds functional tests
for filtering by influencers in the Anomaly\r\nExplorer\r\n\r\nFlaky
test
build\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1592\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"395fe5a0919d190cd8333af96c787efc36e4a389"}}]}]
BACKPORT-->

Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co>
 2022-11-23 13:06:26 -07:00
Kibana Machine
22e9eacbc8
[8.6] [ML] Fix Data Visualizer time picker showing even if data view has been configured not to use a time filter (#146080) (#146210) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Fix Data Visualizer time picker showing even if data view has
been configured not to use a time filter
(#146080)](https://github.com/elastic/kibana/pull/146080)

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

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

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T18:55:42Z","message":"[ML]
Fix Data Visualizer time picker showing even if data view has been
configured not to use a time filter (#146080)\n\nfixes
https://github.com/elastic/kibana/issues/139480","sha":"14437dffcc110a8665444e6dd0e32ac6bc8fefe5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:File
Data
Viz","v8.6.0","v8.7.0"],"number":146080,"url":"https://github.com/elastic/kibana/pull/146080","mergeCommit":{"message":"[ML]
Fix Data Visualizer time picker showing even if data view has been
configured not to use a time filter (#146080)\n\nfixes
https://github.com/elastic/kibana/issues/139480","sha":"14437dffcc110a8665444e6dd0e32ac6bc8fefe5"}},"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/146080","number":146080,"mergeCommit":{"message":"[ML]
Fix Data Visualizer time picker showing even if data view has been
configured not to use a time filter (#146080)\n\nfixes
https://github.com/elastic/kibana/issues/139480","sha":"14437dffcc110a8665444e6dd0e32ac6bc8fefe5"}}]}]
BACKPORT-->

Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
 2022-11-23 13:01:10 -07:00
Christos Nasikas
60108b3bb2
[8.6] [Cases] Fix create case form flaky tests (#145829) (#146213) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Cases] Fix create case form flaky tests
(#145829)](https://github.com/elastic/kibana/pull/145829)

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

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

<!--BACKPORT [{"author":{"name":"Christos
Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T16:37:57Z","message":"[Cases]
Fix create case form flaky tests (#145829)\n\n## Summary\r\n\r\nThe
connectors in the create case form use `select` elements to
display\r\nvarious fields. The values of the `select` are being fetched
from the\r\nexternal service. To prevent flakiness we are waiting for
the values to\r\nbe presented first before trying to select the
value.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/142284,\r\nhttps://github.com/elastic/kibana/issues/142282,\r\nhttps://github.com/elastic/kibana/issues/143407\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cf0cde26a05623a9ba956ba7bb17e2389138a9bd","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","backport:prev-minor","v8.7.0"],"number":145829,"url":"https://github.com/elastic/kibana/pull/145829","mergeCommit":{"message":"[Cases]
Fix create case form flaky tests (#145829)\n\n## Summary\r\n\r\nThe
connectors in the create case form use `select` elements to
display\r\nvarious fields. The values of the `select` are being fetched
from the\r\nexternal service. To prevent flakiness we are waiting for
the values to\r\nbe presented first before trying to select the
value.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/142284,\r\nhttps://github.com/elastic/kibana/issues/142282,\r\nhttps://github.com/elastic/kibana/issues/143407\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cf0cde26a05623a9ba956ba7bb17e2389138a9bd"}},"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/145829","number":145829,"mergeCommit":{"message":"[Cases]
Fix create case form flaky tests (#145829)\n\n## Summary\r\n\r\nThe
connectors in the create case form use `select` elements to
display\r\nvarious fields. The values of the `select` are being fetched
from the\r\nexternal service. To prevent flakiness we are waiting for
the values to\r\nbe presented first before trying to select the
value.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/142284,\r\nhttps://github.com/elastic/kibana/issues/142282,\r\nhttps://github.com/elastic/kibana/issues/143407\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"cf0cde26a05623a9ba956ba7bb17e2389138a9bd"}}]}]
BACKPORT-->
 2022-11-23 12:50:42 -07:00
Kibana Machine
b3b18f0bd1
[8.6] change name guided_onboarding_sample_rule (#146062) (#146201) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [change name guided_onboarding_sample_rule
(#146062)](https://github.com/elastic/kibana/pull/146062)

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

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

<!--BACKPORT
[{"author":{"name":"Isai","email":"59296946+imays11@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T17:59:22Z","message":"change
name guided_onboarding_sample_rule (#146062)\n\n##
Summary\r\n\r\nChanges guided onboarding detection rule name to \"My
First Rule\"\r\n\r\nCC
@approksiu","sha":"78a67648b53f144d5e47a0f1e290b1f2e7b0e9f7","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0"],"number":146062,"url":"https://github.com/elastic/kibana/pull/146062","mergeCommit":{"message":"change
name guided_onboarding_sample_rule (#146062)\n\n##
Summary\r\n\r\nChanges guided onboarding detection rule name to \"My
First Rule\"\r\n\r\nCC
@approksiu","sha":"78a67648b53f144d5e47a0f1e290b1f2e7b0e9f7"}},"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/146062","number":146062,"mergeCommit":{"message":"change
name guided_onboarding_sample_rule (#146062)\n\n##
Summary\r\n\r\nChanges guided onboarding detection rule name to \"My
First Rule\"\r\n\r\nCC
@approksiu","sha":"78a67648b53f144d5e47a0f1e290b1f2e7b0e9f7"}}]}]
BACKPORT-->

Co-authored-by: Isai <59296946+imays11@users.noreply.github.com>
 2022-11-23 12:31:53 -07:00
Kibana Machine
605bab90fa skip failing test suite (#146067) 2022-11-23 14:27:41 -05:00
Kibana Machine
4d0df98519 skip failing test suite (#146068) 2022-11-23 14:27:23 -05:00
Kibana Machine
7bc3f2e114
[8.6] Fix close alerts from flyout (#145939) (#146196) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Fix close alerts from flyout
(#145939)](https://github.com/elastic/kibana/pull/145939)

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

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

<!--BACKPORT [{"author":{"name":"Khristinin
Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T17:21:04Z","message":"Fix
close alerts from flyout (#145939)\n\n## Closing alerts from flyout
effect only alerts related to this rule\r\n\r\nFix:
https://github.com/elastic/kibana/issues/145675\r\n\r\nFor the
exceptions component, we need to have `rule.rule_id` which\r\nwasn't
initially in the timeline response.\r\nWe can't safely use `rule.id`, it
is
[described\r\nhere](https://github.com/elastic/kibana/pull/120053).\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6102f0e39b1b4053886e1dc6ccd8696fe1bf6967","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security
Solution
Platform","backport:prev-minor","v8.7.0"],"number":145939,"url":"https://github.com/elastic/kibana/pull/145939","mergeCommit":{"message":"Fix
close alerts from flyout (#145939)\n\n## Closing alerts from flyout
effect only alerts related to this rule\r\n\r\nFix:
https://github.com/elastic/kibana/issues/145675\r\n\r\nFor the
exceptions component, we need to have `rule.rule_id` which\r\nwasn't
initially in the timeline response.\r\nWe can't safely use `rule.id`, it
is
[described\r\nhere](https://github.com/elastic/kibana/pull/120053).\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6102f0e39b1b4053886e1dc6ccd8696fe1bf6967"}},"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/145939","number":145939,"mergeCommit":{"message":"Fix
close alerts from flyout (#145939)\n\n## Closing alerts from flyout
effect only alerts related to this rule\r\n\r\nFix:
https://github.com/elastic/kibana/issues/145675\r\n\r\nFor the
exceptions component, we need to have `rule.rule_id` which\r\nwasn't
initially in the timeline response.\r\nWe can't safely use `rule.id`, it
is
[described\r\nhere](https://github.com/elastic/kibana/pull/120053).\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6102f0e39b1b4053886e1dc6ccd8696fe1bf6967"}}]}]
BACKPORT-->

Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>
 2022-11-23 11:57:12 -07:00
Kibana Machine
d378339e07
[8.6] [Lens] Assign initial focus on annotation query popover open (#145972) (#146179) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Lens] Assign initial focus on annotation query popover open
(#145972)](https://github.com/elastic/kibana/pull/145972)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T16:07:27Z","message":"[Lens]
Assign initial focus on annotation query popover open (#145972)\n\n##
Summary\r\n\r\nFixes #144717 \r\n\r\nAssign focus to query input on
popover open for the query annotation\r\npanel.\r\nI think it should be
extended also to the Filters popover case, but\r\nperhaps it's worth
consider it as separate
case.\r\n\r\n\r\n![query_annotation_focus](https://user-images.githubusercontent.com/924948/203303631-5170b1ec-9009-4d9b-84f7-297273328278.gif)\r\n\r\n##
Notes\r\n\r\n#### Why using a CSS selector with the `data-test-subj`
rather than\r\nusing a ref or an Id?\r\nBoth ref and id are controlled
internally by the `QueryStringInputUI`\r\ncomponent and perhaps it would
require some more work to either accept a\r\nref/id from the wrapper
component, or having a callback system to get\r\nthese internal refs
upstream.\r\nI thought using an unique identifier like the
`data-test-subj` would\r\nsuffice in this specific context, but open to
discuss alternatives.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d01dd6d8dccd60c36296401e2d22a70f6285b131","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","v8.6.0","v8.7.0"],"number":145972,"url":"https://github.com/elastic/kibana/pull/145972","mergeCommit":{"message":"[Lens]
Assign initial focus on annotation query popover open (#145972)\n\n##
Summary\r\n\r\nFixes #144717 \r\n\r\nAssign focus to query input on
popover open for the query annotation\r\npanel.\r\nI think it should be
extended also to the Filters popover case, but\r\nperhaps it's worth
consider it as separate
case.\r\n\r\n\r\n![query_annotation_focus](https://user-images.githubusercontent.com/924948/203303631-5170b1ec-9009-4d9b-84f7-297273328278.gif)\r\n\r\n##
Notes\r\n\r\n#### Why using a CSS selector with the `data-test-subj`
rather than\r\nusing a ref or an Id?\r\nBoth ref and id are controlled
internally by the `QueryStringInputUI`\r\ncomponent and perhaps it would
require some more work to either accept a\r\nref/id from the wrapper
component, or having a callback system to get\r\nthese internal refs
upstream.\r\nI thought using an unique identifier like the
`data-test-subj` would\r\nsuffice in this specific context, but open to
discuss alternatives.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d01dd6d8dccd60c36296401e2d22a70f6285b131"}},"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/145972","number":145972,"mergeCommit":{"message":"[Lens]
Assign initial focus on annotation query popover open (#145972)\n\n##
Summary\r\n\r\nFixes #144717 \r\n\r\nAssign focus to query input on
popover open for the query annotation\r\npanel.\r\nI think it should be
extended also to the Filters popover case, but\r\nperhaps it's worth
consider it as separate
case.\r\n\r\n\r\n![query_annotation_focus](https://user-images.githubusercontent.com/924948/203303631-5170b1ec-9009-4d9b-84f7-297273328278.gif)\r\n\r\n##
Notes\r\n\r\n#### Why using a CSS selector with the `data-test-subj`
rather than\r\nusing a ref or an Id?\r\nBoth ref and id are controlled
internally by the `QueryStringInputUI`\r\ncomponent and perhaps it would
require some more work to either accept a\r\nref/id from the wrapper
component, or having a callback system to get\r\nthese internal refs
upstream.\r\nI thought using an unique identifier like the
`data-test-subj` would\r\nsuffice in this specific context, but open to
discuss alternatives.\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d01dd6d8dccd60c36296401e2d22a70f6285b131"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2022-11-23 11:46:00 -07:00
Kibana Machine
27c8d08005
[8.6] [ML] Add accessibility test for population and advanced job wizards (#146052) (#146191) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Add accessibility test for population and advanced job wizards
(#146052)](https://github.com/elastic/kibana/pull/146052)

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

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

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T16:48:38Z","message":"[ML]
Add accessibility test for population and advanced job wizards
(#146052)","sha":"83bf248540e0f61a66973b8b5dcc538f2dc0554d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v8.6.0","v8.7.0"],"number":146052,"url":"https://github.com/elastic/kibana/pull/146052","mergeCommit":{"message":"[ML]
Add accessibility test for population and advanced job wizards
(#146052)","sha":"83bf248540e0f61a66973b8b5dcc538f2dc0554d"}},"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/146052","number":146052,"mergeCommit":{"message":"[ML]
Add accessibility test for population and advanced job wizards
(#146052)","sha":"83bf248540e0f61a66973b8b5dcc538f2dc0554d"}}]}]
BACKPORT-->

Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
 2022-11-23 10:52:21 -07:00
Kibana Machine
30c042f34d
[8.6] [File data visualizer] fix mappings parsing when missing properties (#146109) (#146178) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[File data visualizer] fix mappings parsing when missing properties
(#146109)](https://github.com/elastic/kibana/pull/146109)

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

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

<!--BACKPORT [{"author":{"name":"James
Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T15:58:42Z","message":"[File
data visualizer] fix mappings parsing when missing properties
(#146109)\n\nWhen attempting to read the time field from the mappings,
we are\r\nassuming the `properties` key exists. If it doesn't the import
fails.\r\n\r\nFixes
https://github.com/elastic/kibana/issues/146027","sha":"e32f508c90e6a36ddfac3f0d6c0058121e06b841","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:File
Data
Viz","v8.6.0","v8.7.0"],"number":146109,"url":"https://github.com/elastic/kibana/pull/146109","mergeCommit":{"message":"[File
data visualizer] fix mappings parsing when missing properties
(#146109)\n\nWhen attempting to read the time field from the mappings,
we are\r\nassuming the `properties` key exists. If it doesn't the import
fails.\r\n\r\nFixes
https://github.com/elastic/kibana/issues/146027","sha":"e32f508c90e6a36ddfac3f0d6c0058121e06b841"}},"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/146109","number":146109,"mergeCommit":{"message":"[File
data visualizer] fix mappings parsing when missing properties
(#146109)\n\nWhen attempting to read the time field from the mappings,
we are\r\nassuming the `properties` key exists. If it doesn't the import
fails.\r\n\r\nFixes
https://github.com/elastic/kibana/issues/146027","sha":"e32f508c90e6a36ddfac3f0d6c0058121e06b841"}}]}]
BACKPORT-->

Co-authored-by: James Gowdy <jgowdy@elastic.co>
 2022-11-23 10:09:03 -07:00
Kibana Machine
3a2197c8bb
[8.6] [Enterprise Search] Clarify crawler interval scheduling copy (#146138) (#146172) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Clarify crawler interval scheduling copy
(#146138)](https://github.com/elastic/kibana/pull/146138)

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

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

<!--BACKPORT [{"author":{"name":"Liam
Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T15:46:39Z","message":"[Enterprise
Search] Clarify crawler interval scheduling copy (#146138)\n\nTiny
copyedit to update explanatory copy for crawler interval
scheduling.","sha":"5203973a4d3ea8b6fc70d4fccfa96739703230d6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146138,"url":"https://github.com/elastic/kibana/pull/146138","mergeCommit":{"message":"[Enterprise
Search] Clarify crawler interval scheduling copy (#146138)\n\nTiny
copyedit to update explanatory copy for crawler interval
scheduling.","sha":"5203973a4d3ea8b6fc70d4fccfa96739703230d6"}},"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/146138","number":146138,"mergeCommit":{"message":"[Enterprise
Search] Clarify crawler interval scheduling copy (#146138)\n\nTiny
copyedit to update explanatory copy for crawler interval
scheduling.","sha":"5203973a4d3ea8b6fc70d4fccfa96739703230d6"}}]}]
BACKPORT-->

Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
 2022-11-23 10:05:06 -07:00
Kibana Machine
9ba222a45a skip failing test suite (#146067) 2022-11-23 11:57:38 -05:00
Kibana Machine
2a690f27e3 skip failing test suite (#146068) 2022-11-23 11:57:17 -05:00
Kibana Machine
8c6d2c93b8
[8.6] [Security Solution] [Explore] Update tour step font size (#145284) (#146076) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] [Explore] Update tour step font size
(#145284)](https://github.com/elastic/kibana/pull/145284)

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

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

<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T21:45:19Z","message":"[Security
Solution] [Explore] Update tour step font size (#145284)\n\nUpdates
`alertsCases` tour step body font size to 14px in alignment
with\r\nhttps://github.com/elastic/kibana/issues/144810","sha":"ecd862184a706b98679a73293101e82e6724b157","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Explore","v8.6.0","v8.7.0"],"number":145284,"url":"https://github.com/elastic/kibana/pull/145284","mergeCommit":{"message":"[Security
Solution] [Explore] Update tour step font size (#145284)\n\nUpdates
`alertsCases` tour step body font size to 14px in alignment
with\r\nhttps://github.com/elastic/kibana/issues/144810","sha":"ecd862184a706b98679a73293101e82e6724b157"}},"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/145284","number":145284,"mergeCommit":{"message":"[Security
Solution] [Explore] Update tour step font size (#145284)\n\nUpdates
`alertsCases` tour step body font size to 14px in alignment
with\r\nhttps://github.com/elastic/kibana/issues/144810","sha":"ecd862184a706b98679a73293101e82e6724b157"}}]}]
BACKPORT-->

Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co>
 2022-11-23 08:56:12 -07:00
Tiago Costa
03acd77918
skip flaky suite (#131535) 2022-11-23 15:52:01 +00:00
Kibana Machine
7361470460
[8.6] [Security Solution] [Rules] Fixes bug where editing a rule with a data view throws an unhandled exception (#145658) (#146153) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] [Rules] Fixes bug where editing a rule with a
data view throws an unhandled exception
(#145658)](https://github.com/elastic/kibana/pull/145658)

<!--- 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-11-23T14:11:05Z","message":"[Security
Solution] [Rules] Fixes bug where editing a rule with a data view throws
an unhandled exception (#145658)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/145078","sha":"584752f36693d2e9af56605f2e914285a1d4d62d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","Team:Security
Solution Platform","Feature:Rule
Details","backport:prev-minor","v8.6.0","v8.7.0"],"number":145658,"url":"https://github.com/elastic/kibana/pull/145658","mergeCommit":{"message":"[Security
Solution] [Rules] Fixes bug where editing a rule with a data view throws
an unhandled exception (#145658)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/145078","sha":"584752f36693d2e9af56605f2e914285a1d4d62d"}},"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/145658","number":145658,"mergeCommit":{"message":"[Security
Solution] [Rules] Fixes bug where editing a rule with a data view throws
an unhandled exception (#145658)\n\n## Summary\r\n\r\nRef:
https://github.com/elastic/kibana/issues/145078","sha":"584752f36693d2e9af56605f2e914285a1d4d62d"}}]}]
BACKPORT-->

Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co>
 2022-11-23 08:44:50 -07:00
Kibana Machine
d458b8f214
[8.6] [Synthetics] Hide URL field when value is falsey (#145938) (#146156) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Synthetics] Hide URL field when value is falsey
(#145938)](https://github.com/elastic/kibana/pull/145938)

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

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

<!--BACKPORT [{"author":{"name":"Justin
Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T14:32:30Z","message":"[Synthetics]
Hide URL field when value is falsey (#145938)\n\n##
Summary\r\n\r\nResolves #144855.\r\n\r\nResolves #144854.\r\n\r\nHides
the URL field when it has no value, like in the case of
multistep\r\nmonitors.\r\n\r\n## Testing this PR\r\n\r\nCreate a
multistep monitor that will not have a URL field, and view the\r\nflyout
for your monitor. See that there is no URL field
displayed.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"78f22099436519dc8c069d12d21f9a90b3a6eb92","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145938,"url":"https://github.com/elastic/kibana/pull/145938","mergeCommit":{"message":"[Synthetics]
Hide URL field when value is falsey (#145938)\n\n##
Summary\r\n\r\nResolves #144855.\r\n\r\nResolves #144854.\r\n\r\nHides
the URL field when it has no value, like in the case of
multistep\r\nmonitors.\r\n\r\n## Testing this PR\r\n\r\nCreate a
multistep monitor that will not have a URL field, and view the\r\nflyout
for your monitor. See that there is no URL field
displayed.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"78f22099436519dc8c069d12d21f9a90b3a6eb92"}},"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/145938","number":145938,"mergeCommit":{"message":"[Synthetics]
Hide URL field when value is falsey (#145938)\n\n##
Summary\r\n\r\nResolves #144855.\r\n\r\nResolves #144854.\r\n\r\nHides
the URL field when it has no value, like in the case of
multistep\r\nmonitors.\r\n\r\n## Testing this PR\r\n\r\nCreate a
multistep monitor that will not have a URL field, and view the\r\nflyout
for your monitor. See that there is no URL field
displayed.\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"78f22099436519dc8c069d12d21f9a90b3a6eb92"}}]}]
BACKPORT-->

Co-authored-by: Justin Kambic <jk@elastic.co>
 2022-11-23 08:38:55 -07:00
Kibana Machine
e0f1586207
[8.6] Fix placeholder for search bar (#146110) (#146147) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Fix placeholder for search bar
(#146110)](https://github.com/elastic/kibana/pull/146110)

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

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

<!--BACKPORT [{"author":{"name":"Khristinin
Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T13:28:24Z","message":"Fix
placeholder for search bar (#146110)\n\n## Fix placeholder for search
bar, which shows how to search for list_id\r\n\r\nFIX:
https://github.com/elastic/kibana/issues/145674","sha":"a7df8d10334fdb1523ed2530fe8f34095fda5c58","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security
Solution
Platform","backport:prev-minor","v8.7.0"],"number":146110,"url":"https://github.com/elastic/kibana/pull/146110","mergeCommit":{"message":"Fix
placeholder for search bar (#146110)\n\n## Fix placeholder for search
bar, which shows how to search for list_id\r\n\r\nFIX:
https://github.com/elastic/kibana/issues/145674","sha":"a7df8d10334fdb1523ed2530fe8f34095fda5c58"}},"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/146110","number":146110,"mergeCommit":{"message":"Fix
placeholder for search bar (#146110)\n\n## Fix placeholder for search
bar, which shows how to search for list_id\r\n\r\nFIX:
https://github.com/elastic/kibana/issues/145674","sha":"a7df8d10334fdb1523ed2530fe8f34095fda5c58"}}]}]
BACKPORT-->

Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>
 2022-11-23 07:56:11 -07:00
Kibana Machine
c99712f98c
[8.6] [Cases] Enhance labels in the bulk edit tags flyout (#145811) (#146142) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Cases] Enhance labels in the bulk edit tags flyout
(#145811)](https://github.com/elastic/kibana/pull/145811)

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

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

<!--BACKPORT [{"author":{"name":"Christos
Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T12:56:44Z","message":"[Cases]
Enhance labels in the bulk edit tags flyout (#145811)\n\n##
Summary\r\n\r\nThis PR a) fixes the label when there are no tags, b)
adds a label when\r\nthere are no matches, c) removes a `useEffect`
which is not necessary\r\nanymore, and d) shortens the help text for the
tags field.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/145214\r\n\r\n##
Screenshots\r\n\r\n<img width=\"640\" alt=\"Screenshot 2022-11-19 at 12
57 50
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005858-e7270771-4aaf-40a6-9174-306bacfb55fd.png\">\r\n\r\n<img
width=\"639\" alt=\"Screenshot 2022-11-19 at 12 45 55
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005874-6a42eff5-2c28-4962-8b53-58b2eb21b97e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6d9811ec7dcd732bc6a5984c35cf628e8ca588f8","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Cases","ui-copy","backport:prev-minor","v8.7.0"],"number":145811,"url":"https://github.com/elastic/kibana/pull/145811","mergeCommit":{"message":"[Cases]
Enhance labels in the bulk edit tags flyout (#145811)\n\n##
Summary\r\n\r\nThis PR a) fixes the label when there are no tags, b)
adds a label when\r\nthere are no matches, c) removes a `useEffect`
which is not necessary\r\nanymore, and d) shortens the help text for the
tags field.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/145214\r\n\r\n##
Screenshots\r\n\r\n<img width=\"640\" alt=\"Screenshot 2022-11-19 at 12
57 50
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005858-e7270771-4aaf-40a6-9174-306bacfb55fd.png\">\r\n\r\n<img
width=\"639\" alt=\"Screenshot 2022-11-19 at 12 45 55
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005874-6a42eff5-2c28-4962-8b53-58b2eb21b97e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6d9811ec7dcd732bc6a5984c35cf628e8ca588f8"}},"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/145811","number":145811,"mergeCommit":{"message":"[Cases]
Enhance labels in the bulk edit tags flyout (#145811)\n\n##
Summary\r\n\r\nThis PR a) fixes the label when there are no tags, b)
adds a label when\r\nthere are no matches, c) removes a `useEffect`
which is not necessary\r\nanymore, and d) shortens the help text for the
tags field.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/145214\r\n\r\n##
Screenshots\r\n\r\n<img width=\"640\" alt=\"Screenshot 2022-11-19 at 12
57 50
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005858-e7270771-4aaf-40a6-9174-306bacfb55fd.png\">\r\n\r\n<img
width=\"639\" alt=\"Screenshot 2022-11-19 at 12 45 55
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/7871006/203005874-6a42eff5-2c28-4962-8b53-58b2eb21b97e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"6d9811ec7dcd732bc6a5984c35cf628e8ca588f8"}}]}]
BACKPORT-->

Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
 2022-11-23 07:04:35 -07:00
Kibana Machine
72710f039e
[8.6] [SecuritySolution] Inspect modal styling issue (#146015) (#146137) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[SecuritySolution] Inspect modal styling issue
(#146015)](https://github.com/elastic/kibana/pull/146015)

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

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

<!--BACKPORT [{"author":{"name":"Angela
Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T12:31:47Z","message":"[SecuritySolution]
Inspect modal styling issue (#146015)\n\n## Summary\r\n\r\nOriginal
issue: https://github.com/elastic/kibana/issues/145800\r\nThe size of
inspect modal was not aligned between request and
response.\r\n\r\nBefore:\r\n\r\n\r\n203363965-b80f89fe-5456-4e89-bd99-567637b80735.mov","sha":"99340486af49ba542e1df3891a4ee20d7a7977d2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Explore","v8.6.0","v8.7.0"],"number":146015,"url":"https://github.com/elastic/kibana/pull/146015","mergeCommit":{"message":"[SecuritySolution]
Inspect modal styling issue (#146015)\n\n## Summary\r\n\r\nOriginal
issue: https://github.com/elastic/kibana/issues/145800\r\nThe size of
inspect modal was not aligned between request and
response.\r\n\r\nBefore:\r\n\r\n\r\n203363965-b80f89fe-5456-4e89-bd99-567637b80735.mov","sha":"99340486af49ba542e1df3891a4ee20d7a7977d2"}},"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/146015","number":146015,"mergeCommit":{"message":"[SecuritySolution]
Inspect modal styling issue (#146015)\n\n## Summary\r\n\r\nOriginal
issue: https://github.com/elastic/kibana/issues/145800\r\nThe size of
inspect modal was not aligned between request and
response.\r\n\r\nBefore:\r\n\r\n\r\n203363965-b80f89fe-5456-4e89-bd99-567637b80735.mov","sha":"99340486af49ba542e1df3891a4ee20d7a7977d2"}}]}]
BACKPORT-->

Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>
 2022-11-23 07:00:47 -07:00
Sander Philipse
a0966fce64
[8.6] [Enterprise Search] Split documents count into added and deleted docs (#145366) (#146141) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Split documents count into added and deleted docs
(#145366)](https://github.com/elastic/kibana/pull/145366)

<!--- 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-11-16T16:48:32Z","message":"[Enterprise
Search] Split documents count into added and deleted docs
(#145366)","sha":"858b46922dfa709b6cb6a1d438750c5b890eb4ab","branchLabelMapping":{"^v8.6.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport
missing","auto-backport","Team:EnterpriseSearch","v8.6.0"],"number":145366,"url":"https://github.com/elastic/kibana/pull/145366","mergeCommit":{"message":"[Enterprise
Search] Split documents count into added and deleted docs
(#145366)","sha":"858b46922dfa709b6cb6a1d438750c5b890eb4ab"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.6.0","labelRegex":"^v8.6.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/145366","number":145366,"mergeCommit":{"message":"[Enterprise
Search] Split documents count into added and deleted docs
(#145366)","sha":"858b46922dfa709b6cb6a1d438750c5b890eb4ab"}}]}]
BACKPORT-->
 2022-11-23 06:53:22 -07:00
Kibana Machine
d2bd1a4992
[8.6] Fixing delete action and empty message bugs (#145463) (#146134) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Fixing delete action and empty message bugs
(#145463)](https://github.com/elastic/kibana/pull/145463)

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

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

<!--BACKPORT [{"author":{"name":"Jonathan
Buttner","email":"56361221+jonathan-buttner@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T11:40:12Z","message":"Fixing
delete action and empty message bugs (#145463)\n\nThis PR addresses two
issues:\r\n\r\n1. This bug:
https://github.com/elastic/kibana/issues/144128 when a user\r\ndeletes
an action at say index 0 within the rule form , if the action
at\r\nindex 1 was a different type (`createAlert` vs `closeAlert`) the
user\r\nwould lose the information in the action.\r\n - Now the
information from the action at index 1 should persistent\r\n2. A user
could save the rule when the `message` field was a string of\r\nall
spaces\r\n - Now the user should not be able to save the
rule\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/144128\r\n\r\n### Deleting the
action\r\n\r\n\r\n202298074-34878a4c-5fa0-4d8d-8192-ae5f43439cd0.mov\r\n\r\n\r\n\r\n###
Whitespace message
field\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56361221/202298085-95f1fe3f-2652-4b92-86c7-b49b0b23d913.mov","sha":"ba16f55c5e3357737ae7f4ffc5381988a1c31b8d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Feature:Actions","Team:ResponseOps","v8.6.0","v8.7.0"],"number":145463,"url":"https://github.com/elastic/kibana/pull/145463","mergeCommit":{"message":"Fixing
delete action and empty message bugs (#145463)\n\nThis PR addresses two
issues:\r\n\r\n1. This bug:
https://github.com/elastic/kibana/issues/144128 when a user\r\ndeletes
an action at say index 0 within the rule form , if the action
at\r\nindex 1 was a different type (`createAlert` vs `closeAlert`) the
user\r\nwould lose the information in the action.\r\n - Now the
information from the action at index 1 should persistent\r\n2. A user
could save the rule when the `message` field was a string of\r\nall
spaces\r\n - Now the user should not be able to save the
rule\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/144128\r\n\r\n### Deleting the
action\r\n\r\n\r\n202298074-34878a4c-5fa0-4d8d-8192-ae5f43439cd0.mov\r\n\r\n\r\n\r\n###
Whitespace message
field\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56361221/202298085-95f1fe3f-2652-4b92-86c7-b49b0b23d913.mov","sha":"ba16f55c5e3357737ae7f4ffc5381988a1c31b8d"}},"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/145463","number":145463,"mergeCommit":{"message":"Fixing
delete action and empty message bugs (#145463)\n\nThis PR addresses two
issues:\r\n\r\n1. This bug:
https://github.com/elastic/kibana/issues/144128 when a user\r\ndeletes
an action at say index 0 within the rule form , if the action
at\r\nindex 1 was a different type (`createAlert` vs `closeAlert`) the
user\r\nwould lose the information in the action.\r\n - Now the
information from the action at index 1 should persistent\r\n2. A user
could save the rule when the `message` field was a string of\r\nall
spaces\r\n - Now the user should not be able to save the
rule\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/144128\r\n\r\n### Deleting the
action\r\n\r\n\r\n202298074-34878a4c-5fa0-4d8d-8192-ae5f43439cd0.mov\r\n\r\n\r\n\r\n###
Whitespace message
field\r\n\r\n\r\n\r\nhttps://user-images.githubusercontent.com/56361221/202298085-95f1fe3f-2652-4b92-86c7-b49b0b23d913.mov","sha":"ba16f55c5e3357737ae7f4ffc5381988a1c31b8d"}}]}]
BACKPORT-->

Co-authored-by: Jonathan Buttner <56361221+jonathan-buttner@users.noreply.github.com>
 2022-11-23 06:37:19 -07:00
Kibana Machine
411da5f0db
[8.6] [Enterprise Search] Update on_demand enum value (#146127) (#146135) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Update on_demand enum value
(#146127)](https://github.com/elastic/kibana/pull/146127)

<!--- 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-11-23T11:45:55Z","message":"[Enterprise
Search] Update on_demand enum value (#146127)\n\nThis updates the
TriggerMethod enum to match the connectors
protocol.","sha":"a2549b7c92c024389bd6690b84073b75608a6a34","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146127,"url":"https://github.com/elastic/kibana/pull/146127","mergeCommit":{"message":"[Enterprise
Search] Update on_demand enum value (#146127)\n\nThis updates the
TriggerMethod enum to match the connectors
protocol.","sha":"a2549b7c92c024389bd6690b84073b75608a6a34"}},"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/146127","number":146127,"mergeCommit":{"message":"[Enterprise
Search] Update on_demand enum value (#146127)\n\nThis updates the
TriggerMethod enum to match the connectors
protocol.","sha":"a2549b7c92c024389bd6690b84073b75608a6a34"}}]}]
BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2022-11-23 06:02:35 -07:00
Kibana Machine
2720f45855
[8.6] Fix exceptions_success_count relate only to exceptions items (#145700) (#146012) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Fix exceptions_success_count relate only to exceptions items
(#145700)](https://github.com/elastic/kibana/pull/145700)

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

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

<!--BACKPORT [{"author":{"name":"Khristinin
Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T15:51:54Z","message":"Fix
exceptions_success_count relate only to exceptions items (#145700)\n\n##
Fix import rules success message\r\n\r\nfix
https://github.com/elastic/kibana/issues/136760\r\n\r\nexceptions_success_count
now don't count exceptions list, only\r\nexceptions list
items\r\n\r\nAfter discussion with the team, that is ok to return only
exceptions\r\nlist items as success_count for the rule import, because
it reflects our\r\nUI. It does not really reflect the backend, because
we also have the\r\nexceptions list
container.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/202669384-5ddda1a7-e832-41a9-b899-5473a8188681.mov\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"93e0cf5a34bd5aef5a2be6cb8d43c8f9597e3b02","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security
Solution
Platform","backport:prev-minor","v8.7.0"],"number":145700,"url":"https://github.com/elastic/kibana/pull/145700","mergeCommit":{"message":"Fix
exceptions_success_count relate only to exceptions items (#145700)\n\n##
Fix import rules success message\r\n\r\nfix
https://github.com/elastic/kibana/issues/136760\r\n\r\nexceptions_success_count
now don't count exceptions list, only\r\nexceptions list
items\r\n\r\nAfter discussion with the team, that is ok to return only
exceptions\r\nlist items as success_count for the rule import, because
it reflects our\r\nUI. It does not really reflect the backend, because
we also have the\r\nexceptions list
container.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/202669384-5ddda1a7-e832-41a9-b899-5473a8188681.mov\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"93e0cf5a34bd5aef5a2be6cb8d43c8f9597e3b02"}},"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/145700","number":145700,"mergeCommit":{"message":"Fix
exceptions_success_count relate only to exceptions items (#145700)\n\n##
Fix import rules success message\r\n\r\nfix
https://github.com/elastic/kibana/issues/136760\r\n\r\nexceptions_success_count
now don't count exceptions list, only\r\nexceptions list
items\r\n\r\nAfter discussion with the team, that is ok to return only
exceptions\r\nlist items as success_count for the rule import, because
it reflects our\r\nUI. It does not really reflect the backend, because
we also have the\r\nexceptions list
container.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7609147/202669384-5ddda1a7-e832-41a9-b899-5473a8188681.mov\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"93e0cf5a34bd5aef5a2be6cb8d43c8f9597e3b02"}}]}]
BACKPORT-->

Co-authored-by: Khristinin Nikita <nikita.khristinin@elastic.co>
 2022-11-23 05:05:30 -07:00
Kibana Machine
7b6d34c7d0
[8.6] [Security Solution][List details page]: Sort Manage rules table based on selection (#146003) (#146123) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution][List details page]: Sort Manage rules table based
on selection (#146003)](https://github.com/elastic/kibana/pull/146003)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T10:28:36Z","message":"[Security
Solution][List details page]: Sort Manage rules table based on selection
(#146003)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n\r\n- Sort table
based on the `initiallySelectedRules` so it renders the\r\nselected on
the first
page","sha":"8ded29a18abc958d36ab3ab5e2488628fb20f353","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security
Solution
Platform","backport:prev-minor","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":146003,"url":"https://github.com/elastic/kibana/pull/146003","mergeCommit":{"message":"[Security
Solution][List details page]: Sort Manage rules table based on selection
(#146003)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n\r\n- Sort table
based on the `initiallySelectedRules` so it renders the\r\nselected on
the first
page","sha":"8ded29a18abc958d36ab3ab5e2488628fb20f353"}},"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/146003","number":146003,"mergeCommit":{"message":"[Security
Solution][List details page]: Sort Manage rules table based on selection
(#146003)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n\r\n- Sort table
based on the `initiallySelectedRules` so it renders the\r\nselected on
the first page","sha":"8ded29a18abc958d36ab3ab5e2488628fb20f353"}}]}]
BACKPORT-->

Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co>
 2022-11-23 05:02:20 -07:00
Kibana Machine
e4baf889b7
[8.6] Change style of rule tags in alert details page (#145946) (#146118) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Change style of rule tags in alert details page
(#145946)](https://github.com/elastic/kibana/pull/145946)

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

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

<!--BACKPORT [{"author":{"name":"Bena
Kansara","email":"69037875+benakansara@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T10:01:29Z","message":"Change
style of rule tags in alert details page (#145946)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/141674\r\n\r\nStyling of rule
tags changed and some other minor style changes in Alert\r\nsummary
component of Alert details page.\r\n\r\n<img width=\"1723\"
alt=\"Screenshot 2022-11-22 at 18 59
14\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387567-f4b7e89e-f075-4c2a-84fc-ac477cf5ba63.png\">\r\n\r\n\r\n<img
width=\"1724\" alt=\"Screenshot 2022-11-22 at 18 57
24\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387362-2cd7c549-09e2-4772-8de9-33aebfd6d428.png\">\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
shahzad31
<shahzad.muhammad@elastic.co>","sha":"3e7d3ec2598821d034f18e13a343ec3dc994a5bc","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
Actionable
Observability","backport:prev-minor","v8.6.0","v8.7.0"],"number":145946,"url":"https://github.com/elastic/kibana/pull/145946","mergeCommit":{"message":"Change
style of rule tags in alert details page (#145946)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/141674\r\n\r\nStyling of rule
tags changed and some other minor style changes in Alert\r\nsummary
component of Alert details page.\r\n\r\n<img width=\"1723\"
alt=\"Screenshot 2022-11-22 at 18 59
14\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387567-f4b7e89e-f075-4c2a-84fc-ac477cf5ba63.png\">\r\n\r\n\r\n<img
width=\"1724\" alt=\"Screenshot 2022-11-22 at 18 57
24\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387362-2cd7c549-09e2-4772-8de9-33aebfd6d428.png\">\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
shahzad31
<shahzad.muhammad@elastic.co>","sha":"3e7d3ec2598821d034f18e13a343ec3dc994a5bc"}},"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/145946","number":145946,"mergeCommit":{"message":"Change
style of rule tags in alert details page (#145946)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/141674\r\n\r\nStyling of rule
tags changed and some other minor style changes in Alert\r\nsummary
component of Alert details page.\r\n\r\n<img width=\"1723\"
alt=\"Screenshot 2022-11-22 at 18 59
14\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387567-f4b7e89e-f075-4c2a-84fc-ac477cf5ba63.png\">\r\n\r\n\r\n<img
width=\"1724\" alt=\"Screenshot 2022-11-22 at 18 57
24\"\r\nsrc=\"https://user-images.githubusercontent.com/69037875/203387362-2cd7c549-09e2-4772-8de9-33aebfd6d428.png\">\r\n\r\n###
Checklist\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
shahzad31
<shahzad.muhammad@elastic.co>","sha":"3e7d3ec2598821d034f18e13a343ec3dc994a5bc"}}]}]
BACKPORT-->

Co-authored-by: Bena Kansara <69037875+benakansara@users.noreply.github.com>
 2022-11-23 04:44:42 -07:00
Kibana Machine
91741d4ed8
[8.6] [Uptime] Use absolute time instead of relative for TLS rule query (#145293) (#146117) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Uptime] Use absolute time instead of relative for TLS rule query
(#145293)](https://github.com/elastic/kibana/pull/145293)

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

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

<!--BACKPORT [{"author":{"name":"Justin
Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T10:00:13Z","message":"[Uptime]
Use absolute time instead of relative for TLS rule query
(#145293)\n\nCo-authored-by: shahzad31
<shahzad.muhammad@elastic.co>\r\nResolves
https://github.com/elastic/kibana/issues/144131","sha":"723485e9e5d01ac252ec55b0f0deff32cef49fc2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:uptime","v8.6.0","v8.7.0"],"number":145293,"url":"https://github.com/elastic/kibana/pull/145293","mergeCommit":{"message":"[Uptime]
Use absolute time instead of relative for TLS rule query
(#145293)\n\nCo-authored-by: shahzad31
<shahzad.muhammad@elastic.co>\r\nResolves
https://github.com/elastic/kibana/issues/144131","sha":"723485e9e5d01ac252ec55b0f0deff32cef49fc2"}},"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/145293","number":145293,"mergeCommit":{"message":"[Uptime]
Use absolute time instead of relative for TLS rule query
(#145293)\n\nCo-authored-by: shahzad31
<shahzad.muhammad@elastic.co>\r\nResolves
https://github.com/elastic/kibana/issues/144131","sha":"723485e9e5d01ac252ec55b0f0deff32cef49fc2"}}]}]
BACKPORT-->

Co-authored-by: Justin Kambic <jk@elastic.co>
 2022-11-23 04:43:30 -07:00
Kibana Machine
c6e8c3423e
[8.6] [Enterprise Search] Disable setting schedule for disabled schedules (#145557) (#145611) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Disable setting schedule for disabled schedules
(#145557)](https://github.com/elastic/kibana/pull/145557)

<!--- 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-11-17T18:39:45Z","message":"[Enterprise
Search] Disable setting schedule for disabled schedules
(#145557)\n\nThis disables setting a sync schedule for connectors if
synchronization\r\nis
disabled.","sha":"58cb0e43e3f0b08ae22abba0532435c9e10bfb50","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":145557,"url":"https://github.com/elastic/kibana/pull/145557","mergeCommit":{"message":"[Enterprise
Search] Disable setting schedule for disabled schedules
(#145557)\n\nThis disables setting a sync schedule for connectors if
synchronization\r\nis
disabled.","sha":"58cb0e43e3f0b08ae22abba0532435c9e10bfb50"}},"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/145557","number":145557,"mergeCommit":{"message":"[Enterprise
Search] Disable setting schedule for disabled schedules
(#145557)\n\nThis disables setting a sync schedule for connectors if
synchronization\r\nis
disabled.","sha":"58cb0e43e3f0b08ae22abba0532435c9e10bfb50"}}]}]
BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2022-11-23 03:58:28 -07:00
Kibana Machine
f776764cfb
[8.6] [Security Solution] Visualisation actions button is overlap on to the bar chart (#145973) (#146106) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] Visualisation actions button is overlap on to the
bar chart (#145973)](https://github.com/elastic/kibana/pull/145973)

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

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

<!--BACKPORT [{"author":{"name":"Angela
Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-23T09:27:58Z","message":"[Security
Solution] Visualisation actions button is overlap on to the bar chart
(#145973)\n\n## Summary\r\n\r\nOriginal issue: Visualisation actions
button is overlap on to the
bar\r\nchart.\r\nhttps://github.com/elastic/kibana/issues/128344\r\n\r\nBefore:\r\n<img
width=\"575\" alt=\"Screenshot 2022-11-22 at 11 31
19\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304147-ff0ec823-182c-40bf-8da5-fa45180eae0a.png\">\r\n\r\nAfter:\r\n<img
width=\"765\" alt=\"Screenshot 2022-11-22 at 11 30
39\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304150-5dae9a4a-341d-4717-abb1-f56aa20ba6bd.png\">","sha":"a0658669f29ed508c87b79d678f21695591fca89","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat
Hunting","Team:Threat
Hunting:Explore","v8.6.0","v8.7.0"],"number":145973,"url":"https://github.com/elastic/kibana/pull/145973","mergeCommit":{"message":"[Security
Solution] Visualisation actions button is overlap on to the bar chart
(#145973)\n\n## Summary\r\n\r\nOriginal issue: Visualisation actions
button is overlap on to the
bar\r\nchart.\r\nhttps://github.com/elastic/kibana/issues/128344\r\n\r\nBefore:\r\n<img
width=\"575\" alt=\"Screenshot 2022-11-22 at 11 31
19\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304147-ff0ec823-182c-40bf-8da5-fa45180eae0a.png\">\r\n\r\nAfter:\r\n<img
width=\"765\" alt=\"Screenshot 2022-11-22 at 11 30
39\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304150-5dae9a4a-341d-4717-abb1-f56aa20ba6bd.png\">","sha":"a0658669f29ed508c87b79d678f21695591fca89"}},"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/145973","number":145973,"mergeCommit":{"message":"[Security
Solution] Visualisation actions button is overlap on to the bar chart
(#145973)\n\n## Summary\r\n\r\nOriginal issue: Visualisation actions
button is overlap on to the
bar\r\nchart.\r\nhttps://github.com/elastic/kibana/issues/128344\r\n\r\nBefore:\r\n<img
width=\"575\" alt=\"Screenshot 2022-11-22 at 11 31
19\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304147-ff0ec823-182c-40bf-8da5-fa45180eae0a.png\">\r\n\r\nAfter:\r\n<img
width=\"765\" alt=\"Screenshot 2022-11-22 at 11 30
39\"\r\nsrc=\"https://user-images.githubusercontent.com/6295984/203304150-5dae9a4a-341d-4717-abb1-f56aa20ba6bd.png\">","sha":"a0658669f29ed508c87b79d678f21695591fca89"}}]}]
BACKPORT-->

Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>
 2022-11-23 03:54:45 -07:00
Kibana Machine
1e89fbe536
[8.6] [Uptime] Don't show no data state while loading for ping histogram (#145244) (#146064) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Uptime] Don't show no data state while loading for ping histogram
(#145244)](https://github.com/elastic/kibana/pull/145244)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T19:51:42Z","message":"[Uptime]
Don't show no data state while loading for ping histogram
(#145244)\n\nFixes
https://github.com/elastic/kibana/issues/145243","sha":"c3b96a379a341ad842fb01bd0eab533baa7fcf8f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145244,"url":"https://github.com/elastic/kibana/pull/145244","mergeCommit":{"message":"[Uptime]
Don't show no data state while loading for ping histogram
(#145244)\n\nFixes
https://github.com/elastic/kibana/issues/145243","sha":"c3b96a379a341ad842fb01bd0eab533baa7fcf8f"}},"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/145244","number":145244,"mergeCommit":{"message":"[Uptime]
Don't show no data state while loading for ping histogram
(#145244)\n\nFixes
https://github.com/elastic/kibana/issues/145243","sha":"c3b96a379a341ad842fb01bd0eab533baa7fcf8f"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad.muhammad@elastic.co>
 2022-11-23 03:42:44 -07:00
Kibana Machine
7b99f4c6cd
[8.6] Fleet Usage telemetry extension (#145353) (#146105) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Fleet Usage telemetry extension
(#145353)](https://github.com/elastic/kibana/pull/145353)

<!--- 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-11-23T09:22:20Z","message":"Fleet
Usage telemetry extension (#145353)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/ingest-dev/issues/1261\r\n\r\nAdded a snippet
to the telemetry that I added for each requirement.\r\nPlease review and
let me know if any changes are needed.\r\nAlso asked a few questions
below. @jlind23 @kpollich \r\n\r\n6. is blocked by
[elasticsearch\r\nchange](https://github.com/elastic/elasticsearch/pull/91701)
to give\r\nkibana_system the missing privilege to read
logs-elastic_agent* indices.\r\n\r\nTook inspiration for task versioning
from\r\nhttps://github.com/elastic/kibana/pull/144494/files#diff-0c7c49bf5c55c45c19e9c42d5428e99e52c3a39dd6703633f427724d36108186\r\n\r\n-
[x] 1. Elastic Agent versions\r\nVersions of all the Elastic Agent
running: `agent.version` field on\r\n`.fleet-agents`
documents\r\n\r\n```\r\n\"agent_versions\": [\r\n \"8.6.0\"\r\n
],\r\n```\r\n\r\n- [x] 2. Fleet server configuration\r\nThink we can
query for `.fleet-policies` where some `input` has
`type:\r\n'fleet-server'` for this, as well as use the `Fleet Server
Hosts`\r\nsettings that we define via saved objects in
Fleet\r\n\r\n\r\n```\r\n \"fleet_server_config\": {\r\n \"policies\":
[\r\n {\r\n \"input_config\": {\r\n \"server\": {\r\n
\"limits.max_agents\": 10000\r\n },\r\n \"server.runtime\":
\"gc_percent:20\"\r\n }\r\n }\r\n ]\r\n }\r\n```\r\n\r\n- [x] 3. Number
of policies\r\nCount of `.fleet-policies` index \r\n\r\nTo confirm, did
we mean agent policies here?\r\n\r\n```\r\n \"agent_policies\": {\r\n
\"count\": 7,\r\n```\r\n\r\n- [x] 4. Output type contained in those
policies\r\nCollecting this from ts logic, querying from
`.fleet-policies` index.\r\nThe alternative would be to write a painless
script (because the\r\n`outputs` are an object with dynamic keys, we
can't do an aggregation\r\ndirectly).\r\n\r\n```\r\n\"agent_policies\":
{\r\n \"output_types\": [\r\n \"elasticsearch\"\r\n ]\r\n
}\r\n```\r\n\r\nDid we mean to just collect the types here, or any other
info? e.g.\r\noutput urls\r\n\r\n- [x] 5. Average number of checkin
failures\r\nWe only have the most recent checkin status and timestamp
on\r\n`.fleet-agents`.\r\n\r\nDo we mean here to publish the total last
checkin failure count? E.g. 3\r\nif 3 agents are in failure checkin
status currently.\r\nOr do we mean to publish specific info for all
agents\r\n(`last_checkin_status`, `last_checkin` time,
`last_checkin_message`)?\r\nAre the only statuses `error` and `degraded`
that we want to send?\r\n\r\n```\r\n \"agent_last_checkin_status\":
{\r\n \"error\": 0,\r\n \"degraded\": 0\r\n },\r\n```\r\n\r\n- [ ] 6.
Top 3 most common errors in the Elastic Agent logs\r\n\r\nDo we mean
here elastic-agent logs only, or fleet-server logs as well\r\n(maybe
separately)?\r\n\r\nI found an alternative way to query the message
field using sampler and\r\ncategorize text aggregation:\r\n```\r\nGET
logs-elastic_agent*/_search\r\n{\r\n \"size\": 0,\r\n \"query\": {\r\n
\"bool\": {\r\n \"must\": [\r\n {\r\n \"term\": {\r\n \"log.level\":
\"error\"\r\n }\r\n },\r\n {\r\n \"range\": {\r\n \"@timestamp\": {\r\n
\"gte\": \"now-1h\"\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n },\r\n
\"aggregations\": {\r\n \"message_sample\": {\r\n \"sampler\": {\r\n
\"shard_size\": 200\r\n },\r\n \"aggs\": {\r\n \"categories\": {\r\n
\"categorize_text\": {\r\n \"field\": \"message\",\r\n \"size\": 10\r\n
}\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\nExample
response:\r\n```\r\n\"aggregations\": {\r\n \"message_sample\": {\r\n
\"doc_count\": 112,\r\n \"categories\": {\r\n \"buckets\": [\r\n {\r\n
\"doc_count\": 73,\r\n \"key\": \"failed to unenroll offline
agents\",\r\n \"regex\":
\".*?failed.+?to.+?unenroll.+?offline.+?agents.*?\",\r\n
\"max_matching_length\": 36\r\n },\r\n {\r\n \"doc_count\": 7,\r\n
\"key\": \"\"\"stderr panic close of closed channel n ngoroutine running
Stop ngithub.com/elastic/beats/v7/libbeat/cmd/instance Beat launch.func5
\\n\\t/go/src/github.com/elastic/beats/libbeat/cmd/instance/beat.go
n\r\n```\r\n\r\n\r\n- [x] 7. Number of checkin failure over the past
period of time\r\n\r\nI think this is almost the same as #5. The
difference would be to report\r\nnew failures happened only in the last
hour, or report all agents in\r\nfailure state. (which would be an
increasing number if the agent stays\r\nin failed state).\r\nDo we want
these 2 separate telemetry fields?\r\n\r\nEDIT: removed the last1hr
query, instead added a new field to report\r\nagents enrolled per policy
(top 10). See comments below.\r\n\r\n```\r\n \"agent_checkin_status\":
{\r\n \"error\": 3,\r\n \"degraded\": 0\r\n },\r\n
\"agents_per_policy\": [2, 1000],\r\n```\r\n\r\n- [x] 8. Number of
Elastic Agent and number of fleet server\r\n\r\nThis is already there in
the existing telemetry:\r\n```\r\n \"agents\": {\r\n \"total_enrolled\":
0,\r\n \"healthy\": 0,\r\n \"unhealthy\": 0,\r\n \"offline\": 0,\r\n
\"total_all_statuses\": 1,\r\n \"updating\": 0\r\n },\r\n
\"fleet_server\": {\r\n \"total_enrolled\": 0,\r\n \"healthy\": 0,\r\n
\"unhealthy\": 0,\r\n \"offline\": 0,\r\n \"updating\": 0,\r\n
\"total_all_statuses\": 0,\r\n \"num_host_urls\": 1\r\n
},\r\n```\r\n\r\n\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\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e00e26e86854bdbde7c14f88453b717505fed4d9","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":145353,"url":"https://github.com/elastic/kibana/pull/145353","mergeCommit":{"message":"Fleet
Usage telemetry extension (#145353)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/ingest-dev/issues/1261\r\n\r\nAdded a snippet
to the telemetry that I added for each requirement.\r\nPlease review and
let me know if any changes are needed.\r\nAlso asked a few questions
below. @jlind23 @kpollich \r\n\r\n6. is blocked by
[elasticsearch\r\nchange](https://github.com/elastic/elasticsearch/pull/91701)
to give\r\nkibana_system the missing privilege to read
logs-elastic_agent* indices.\r\n\r\nTook inspiration for task versioning
from\r\nhttps://github.com/elastic/kibana/pull/144494/files#diff-0c7c49bf5c55c45c19e9c42d5428e99e52c3a39dd6703633f427724d36108186\r\n\r\n-
[x] 1. Elastic Agent versions\r\nVersions of all the Elastic Agent
running: `agent.version` field on\r\n`.fleet-agents`
documents\r\n\r\n```\r\n\"agent_versions\": [\r\n \"8.6.0\"\r\n
],\r\n```\r\n\r\n- [x] 2. Fleet server configuration\r\nThink we can
query for `.fleet-policies` where some `input` has
`type:\r\n'fleet-server'` for this, as well as use the `Fleet Server
Hosts`\r\nsettings that we define via saved objects in
Fleet\r\n\r\n\r\n```\r\n \"fleet_server_config\": {\r\n \"policies\":
[\r\n {\r\n \"input_config\": {\r\n \"server\": {\r\n
\"limits.max_agents\": 10000\r\n },\r\n \"server.runtime\":
\"gc_percent:20\"\r\n }\r\n }\r\n ]\r\n }\r\n```\r\n\r\n- [x] 3. Number
of policies\r\nCount of `.fleet-policies` index \r\n\r\nTo confirm, did
we mean agent policies here?\r\n\r\n```\r\n \"agent_policies\": {\r\n
\"count\": 7,\r\n```\r\n\r\n- [x] 4. Output type contained in those
policies\r\nCollecting this from ts logic, querying from
`.fleet-policies` index.\r\nThe alternative would be to write a painless
script (because the\r\n`outputs` are an object with dynamic keys, we
can't do an aggregation\r\ndirectly).\r\n\r\n```\r\n\"agent_policies\":
{\r\n \"output_types\": [\r\n \"elasticsearch\"\r\n ]\r\n
}\r\n```\r\n\r\nDid we mean to just collect the types here, or any other
info? e.g.\r\noutput urls\r\n\r\n- [x] 5. Average number of checkin
failures\r\nWe only have the most recent checkin status and timestamp
on\r\n`.fleet-agents`.\r\n\r\nDo we mean here to publish the total last
checkin failure count? E.g. 3\r\nif 3 agents are in failure checkin
status currently.\r\nOr do we mean to publish specific info for all
agents\r\n(`last_checkin_status`, `last_checkin` time,
`last_checkin_message`)?\r\nAre the only statuses `error` and `degraded`
that we want to send?\r\n\r\n```\r\n \"agent_last_checkin_status\":
{\r\n \"error\": 0,\r\n \"degraded\": 0\r\n },\r\n```\r\n\r\n- [ ] 6.
Top 3 most common errors in the Elastic Agent logs\r\n\r\nDo we mean
here elastic-agent logs only, or fleet-server logs as well\r\n(maybe
separately)?\r\n\r\nI found an alternative way to query the message
field using sampler and\r\ncategorize text aggregation:\r\n```\r\nGET
logs-elastic_agent*/_search\r\n{\r\n \"size\": 0,\r\n \"query\": {\r\n
\"bool\": {\r\n \"must\": [\r\n {\r\n \"term\": {\r\n \"log.level\":
\"error\"\r\n }\r\n },\r\n {\r\n \"range\": {\r\n \"@timestamp\": {\r\n
\"gte\": \"now-1h\"\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n },\r\n
\"aggregations\": {\r\n \"message_sample\": {\r\n \"sampler\": {\r\n
\"shard_size\": 200\r\n },\r\n \"aggs\": {\r\n \"categories\": {\r\n
\"categorize_text\": {\r\n \"field\": \"message\",\r\n \"size\": 10\r\n
}\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\nExample
response:\r\n```\r\n\"aggregations\": {\r\n \"message_sample\": {\r\n
\"doc_count\": 112,\r\n \"categories\": {\r\n \"buckets\": [\r\n {\r\n
\"doc_count\": 73,\r\n \"key\": \"failed to unenroll offline
agents\",\r\n \"regex\":
\".*?failed.+?to.+?unenroll.+?offline.+?agents.*?\",\r\n
\"max_matching_length\": 36\r\n },\r\n {\r\n \"doc_count\": 7,\r\n
\"key\": \"\"\"stderr panic close of closed channel n ngoroutine running
Stop ngithub.com/elastic/beats/v7/libbeat/cmd/instance Beat launch.func5
\\n\\t/go/src/github.com/elastic/beats/libbeat/cmd/instance/beat.go
n\r\n```\r\n\r\n\r\n- [x] 7. Number of checkin failure over the past
period of time\r\n\r\nI think this is almost the same as #5. The
difference would be to report\r\nnew failures happened only in the last
hour, or report all agents in\r\nfailure state. (which would be an
increasing number if the agent stays\r\nin failed state).\r\nDo we want
these 2 separate telemetry fields?\r\n\r\nEDIT: removed the last1hr
query, instead added a new field to report\r\nagents enrolled per policy
(top 10). See comments below.\r\n\r\n```\r\n \"agent_checkin_status\":
{\r\n \"error\": 3,\r\n \"degraded\": 0\r\n },\r\n
\"agents_per_policy\": [2, 1000],\r\n```\r\n\r\n- [x] 8. Number of
Elastic Agent and number of fleet server\r\n\r\nThis is already there in
the existing telemetry:\r\n```\r\n \"agents\": {\r\n \"total_enrolled\":
0,\r\n \"healthy\": 0,\r\n \"unhealthy\": 0,\r\n \"offline\": 0,\r\n
\"total_all_statuses\": 1,\r\n \"updating\": 0\r\n },\r\n
\"fleet_server\": {\r\n \"total_enrolled\": 0,\r\n \"healthy\": 0,\r\n
\"unhealthy\": 0,\r\n \"offline\": 0,\r\n \"updating\": 0,\r\n
\"total_all_statuses\": 0,\r\n \"num_host_urls\": 1\r\n
},\r\n```\r\n\r\n\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\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e00e26e86854bdbde7c14f88453b717505fed4d9"}},"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/145353","number":145353,"mergeCommit":{"message":"Fleet
Usage telemetry extension (#145353)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/ingest-dev/issues/1261\r\n\r\nAdded a snippet
to the telemetry that I added for each requirement.\r\nPlease review and
let me know if any changes are needed.\r\nAlso asked a few questions
below. @jlind23 @kpollich \r\n\r\n6. is blocked by
[elasticsearch\r\nchange](https://github.com/elastic/elasticsearch/pull/91701)
to give\r\nkibana_system the missing privilege to read
logs-elastic_agent* indices.\r\n\r\nTook inspiration for task versioning
from\r\nhttps://github.com/elastic/kibana/pull/144494/files#diff-0c7c49bf5c55c45c19e9c42d5428e99e52c3a39dd6703633f427724d36108186\r\n\r\n-
[x] 1. Elastic Agent versions\r\nVersions of all the Elastic Agent
running: `agent.version` field on\r\n`.fleet-agents`
documents\r\n\r\n```\r\n\"agent_versions\": [\r\n \"8.6.0\"\r\n
],\r\n```\r\n\r\n- [x] 2. Fleet server configuration\r\nThink we can
query for `.fleet-policies` where some `input` has
`type:\r\n'fleet-server'` for this, as well as use the `Fleet Server
Hosts`\r\nsettings that we define via saved objects in
Fleet\r\n\r\n\r\n```\r\n \"fleet_server_config\": {\r\n \"policies\":
[\r\n {\r\n \"input_config\": {\r\n \"server\": {\r\n
\"limits.max_agents\": 10000\r\n },\r\n \"server.runtime\":
\"gc_percent:20\"\r\n }\r\n }\r\n ]\r\n }\r\n```\r\n\r\n- [x] 3. Number
of policies\r\nCount of `.fleet-policies` index \r\n\r\nTo confirm, did
we mean agent policies here?\r\n\r\n```\r\n \"agent_policies\": {\r\n
\"count\": 7,\r\n```\r\n\r\n- [x] 4. Output type contained in those
policies\r\nCollecting this from ts logic, querying from
`.fleet-policies` index.\r\nThe alternative would be to write a painless
script (because the\r\n`outputs` are an object with dynamic keys, we
can't do an aggregation\r\ndirectly).\r\n\r\n```\r\n\"agent_policies\":
{\r\n \"output_types\": [\r\n \"elasticsearch\"\r\n ]\r\n
}\r\n```\r\n\r\nDid we mean to just collect the types here, or any other
info? e.g.\r\noutput urls\r\n\r\n- [x] 5. Average number of checkin
failures\r\nWe only have the most recent checkin status and timestamp
on\r\n`.fleet-agents`.\r\n\r\nDo we mean here to publish the total last
checkin failure count? E.g. 3\r\nif 3 agents are in failure checkin
status currently.\r\nOr do we mean to publish specific info for all
agents\r\n(`last_checkin_status`, `last_checkin` time,
`last_checkin_message`)?\r\nAre the only statuses `error` and `degraded`
that we want to send?\r\n\r\n```\r\n \"agent_last_checkin_status\":
{\r\n \"error\": 0,\r\n \"degraded\": 0\r\n },\r\n```\r\n\r\n- [ ] 6.
Top 3 most common errors in the Elastic Agent logs\r\n\r\nDo we mean
here elastic-agent logs only, or fleet-server logs as well\r\n(maybe
separately)?\r\n\r\nI found an alternative way to query the message
field using sampler and\r\ncategorize text aggregation:\r\n```\r\nGET
logs-elastic_agent*/_search\r\n{\r\n \"size\": 0,\r\n \"query\": {\r\n
\"bool\": {\r\n \"must\": [\r\n {\r\n \"term\": {\r\n \"log.level\":
\"error\"\r\n }\r\n },\r\n {\r\n \"range\": {\r\n \"@timestamp\": {\r\n
\"gte\": \"now-1h\"\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n },\r\n
\"aggregations\": {\r\n \"message_sample\": {\r\n \"sampler\": {\r\n
\"shard_size\": 200\r\n },\r\n \"aggs\": {\r\n \"categories\": {\r\n
\"categorize_text\": {\r\n \"field\": \"message\",\r\n \"size\": 10\r\n
}\r\n }\r\n }\r\n }\r\n }\r\n}\r\n```\r\nExample
response:\r\n```\r\n\"aggregations\": {\r\n \"message_sample\": {\r\n
\"doc_count\": 112,\r\n \"categories\": {\r\n \"buckets\": [\r\n {\r\n
\"doc_count\": 73,\r\n \"key\": \"failed to unenroll offline
agents\",\r\n \"regex\":
\".*?failed.+?to.+?unenroll.+?offline.+?agents.*?\",\r\n
\"max_matching_length\": 36\r\n },\r\n {\r\n \"doc_count\": 7,\r\n
\"key\": \"\"\"stderr panic close of closed channel n ngoroutine running
Stop ngithub.com/elastic/beats/v7/libbeat/cmd/instance Beat launch.func5
\\n\\t/go/src/github.com/elastic/beats/libbeat/cmd/instance/beat.go
n\r\n```\r\n\r\n\r\n- [x] 7. Number of checkin failure over the past
period of time\r\n\r\nI think this is almost the same as #5. The
difference would be to report\r\nnew failures happened only in the last
hour, or report all agents in\r\nfailure state. (which would be an
increasing number if the agent stays\r\nin failed state).\r\nDo we want
these 2 separate telemetry fields?\r\n\r\nEDIT: removed the last1hr
query, instead added a new field to report\r\nagents enrolled per policy
(top 10). See comments below.\r\n\r\n```\r\n \"agent_checkin_status\":
{\r\n \"error\": 3,\r\n \"degraded\": 0\r\n },\r\n
\"agents_per_policy\": [2, 1000],\r\n```\r\n\r\n- [x] 8. Number of
Elastic Agent and number of fleet server\r\n\r\nThis is already there in
the existing telemetry:\r\n```\r\n \"agents\": {\r\n \"total_enrolled\":
0,\r\n \"healthy\": 0,\r\n \"unhealthy\": 0,\r\n \"offline\": 0,\r\n
\"total_all_statuses\": 1,\r\n \"updating\": 0\r\n },\r\n
\"fleet_server\": {\r\n \"total_enrolled\": 0,\r\n \"healthy\": 0,\r\n
\"unhealthy\": 0,\r\n \"offline\": 0,\r\n \"updating\": 0,\r\n
\"total_all_statuses\": 0,\r\n \"num_host_urls\": 1\r\n
},\r\n```\r\n\r\n\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\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e00e26e86854bdbde7c14f88453b717505fed4d9"}}]}]
BACKPORT-->

Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
 2022-11-23 03:31:26 -07:00
Kibana Machine
b6907b84b0
[8.6] [Cases] Update email content and footer (#146036) (#146104) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Cases] Update email content and footer
(#146036)](https://github.com/elastic/kibana/pull/146036)

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

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

<!--BACKPORT [{"author":{"name":"Christos
Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2022-11-23T09:04:26Z","message":"[Cases]
Update email content and footer (#146036)\n\n## Summary\r\n\r\nThis PR
replace `Kibana` with `Elastic` in the email content and
footer.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ca2a0cadc3e031ed91a3886e131f796aaa1d11f1","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","Feature:Actions/ConnectorTypes","v8.6.0","v8.7.0"],"number":146036,"url":"https://github.com/elastic/kibana/pull/146036","mergeCommit":{"message":"[Cases]
Update email content and footer (#146036)\n\n## Summary\r\n\r\nThis PR
replace `Kibana` with `Elastic` in the email content and
footer.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ca2a0cadc3e031ed91a3886e131f796aaa1d11f1"}},"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/146036","number":146036,"mergeCommit":{"message":"[Cases]
Update email content and footer (#146036)\n\n## Summary\r\n\r\nThis PR
replace `Kibana` with `Elastic` in the email content and
footer.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"ca2a0cadc3e031ed91a3886e131f796aaa1d11f1"}}]}]
BACKPORT-->

Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
 2022-11-23 03:16:28 -07:00
Kibana Machine
88bc66714e
[8.6] [Security Solution] Fix advanced policy migration where bad advanced policy key event_filters was added (#146050) (#146079) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution] Fix advanced policy migration where bad advanced
policy key `event_filters` was added
(#146050)](https://github.com/elastic/kibana/pull/146050)

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

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

<!--BACKPORT [{"author":{"name":"Kevin
Logan","email":"56395104+kevinlog@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-22T21:55:26Z","message":"[Security
Solution] Fix advanced policy migration where bad advanced policy key
`event_filters` was added
(#146050)","sha":"05703509016fa7b44c461e6490768c696c30d2c2","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","Team:Onboarding
and Lifecycle
Mgt","auto-backport","v8.6.0","v8.7.0"],"number":146050,"url":"https://github.com/elastic/kibana/pull/146050","mergeCommit":{"message":"[Security
Solution] Fix advanced policy migration where bad advanced policy key
`event_filters` was added
(#146050)","sha":"05703509016fa7b44c461e6490768c696c30d2c2"}},"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/146050","number":146050,"mergeCommit":{"message":"[Security
Solution] Fix advanced policy migration where bad advanced policy key
`event_filters` was added
(#146050)","sha":"05703509016fa7b44c461e6490768c696c30d2c2"}}]}]
BACKPORT-->

Co-authored-by: Kevin Logan <56395104+kevinlog@users.noreply.github.com>
 2022-11-22 16:01:33 -07:00
Kibana Machine
a453cfcc25
[8.6] [APM] Mobile - Filters are not responsive (#145996) (#146071) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[APM] Mobile - Filters are not responsive
(#145996)](https://github.com/elastic/kibana/pull/145996)

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

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

<!--BACKPORT [{"author":{"name":"Cauê
Marcondes","email":"55978943+cauemarcondes@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-22T21:09:10Z","message":"[APM]
Mobile - Filters are not responsive (#145996)\n\ncloses
203395543-186369c2-460b-4fb3-82be-8ef87f5182e2.mov","sha":"ef391c2f93ae4a06c57d9eff0ab64fa5e49d260a","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":145996,"url":"https://github.com/elastic/kibana/pull/145996","mergeCommit":{"message":"[APM]
Mobile - Filters are not responsive (#145996)\n\ncloses
203395543-186369c2-460b-4fb3-82be-8ef87f5182e2.mov","sha":"ef391c2f93ae4a06c57d9eff0ab64fa5e49d260a"}},"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/145996","number":145996,"mergeCommit":{"message":"[APM]
Mobile - Filters are not responsive (#145996)\n\ncloses
203395543-186369c2-460b-4fb3-82be-8ef87f5182e2.mov","sha":"ef391c2f93ae4a06c57d9eff0ab64fa5e49d260a"}}]}]
BACKPORT-->

Co-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>
 2022-11-22 15:34:50 -07:00
Kibana Machine
010bb24b87
[8.6] [ML] Explain Log Rate Spikes: Additional functional tests with artificial logs dataset (#145763) (#146038) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: Additional functional tests with
artificial logs dataset
(#145763)](https://github.com/elastic/kibana/pull/145763)

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

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

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T17:28:54Z","message":"[ML]
Explain Log Rate Spikes: Additional functional tests with artificial
logs dataset (#145763)\n\nAdditional functional tests with artificial
logs dataset.\r\n\r\nThis generates an artificial logs dataset with the
purpose of asserting\r\nthe case where grouping needs to identify 2
non-overlapping groups. The\r\nprimary use case of the test is to track
possible regressions related to\r\nwhen trying to improve
`frequent_items` aggregation settings and the\r\ncustom grouping
code.","sha":"c45f55660584381d385e11817d4285e3e24eb546","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":145763,"url":"https://github.com/elastic/kibana/pull/145763","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Additional functional tests with artificial
logs dataset (#145763)\n\nAdditional functional tests with artificial
logs dataset.\r\n\r\nThis generates an artificial logs dataset with the
purpose of asserting\r\nthe case where grouping needs to identify 2
non-overlapping groups. The\r\nprimary use case of the test is to track
possible regressions related to\r\nwhen trying to improve
`frequent_items` aggregation settings and the\r\ncustom grouping
code.","sha":"c45f55660584381d385e11817d4285e3e24eb546"}},"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/145763","number":145763,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: Additional functional tests with artificial
logs dataset (#145763)\n\nAdditional functional tests with artificial
logs dataset.\r\n\r\nThis generates an artificial logs dataset with the
purpose of asserting\r\nthe case where grouping needs to identify 2
non-overlapping groups. The\r\nprimary use case of the test is to track
possible regressions related to\r\nwhen trying to improve
`frequent_items` aggregation settings and the\r\ncustom grouping
code.","sha":"c45f55660584381d385e11817d4285e3e24eb546"}}]}] BACKPORT-->

Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>
 2022-11-22 12:01:26 -07:00
Kibana Machine
cc1a155cd6
[8.6] Adjust CCS Remote Clusters Test To Find Index Based On Index Name (#145786) (#146043) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Adjust CCS Remote Clusters Test To Find Index Based On Index Name
(#145786)](https://github.com/elastic/kibana/pull/145786)

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

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

<!--BACKPORT [{"author":{"name":"John
Dorlus","email":"jsdorlus@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T16:55:14Z","message":"Adjust
CCS Remote Clusters Test To Find Index Based On Index Name
(#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","test_ui_functional","test_xpack_functional","release_note:skip","Feature:Functional
Testing","backport:prev-minor","v8.7.0"],"number":145786,"url":"https://github.com/elastic/kibana/pull/145786","mergeCommit":{"message":"Adjust
CCS Remote Clusters Test To Find Index Based On Index Name
(#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a"}},"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/145786","number":145786,"mergeCommit":{"message":"Adjust
CCS Remote Clusters Test To Find Index Based On Index Name
(#145786)","sha":"8e1618ac905d33de2963c23a2296204f8e60d44a"}}]}]
BACKPORT-->

Co-authored-by: John Dorlus <jsdorlus@elastic.co>
 2022-11-22 11:46:42 -07:00
Kibana Machine
367192b3d7
[8.6] [Enterprise Search] Rename filtering to sync rules (#146013) (#146040) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Enterprise Search] Rename filtering to sync rules
(#146013)](https://github.com/elastic/kibana/pull/146013)

<!--- 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-11-22T17:38:49Z","message":"[Enterprise
Search] Rename filtering to sync rules (#146013)\n\nThis renames
'Filter(ing) Rules' to Sync rules across the Enterprise\r\nSearch
Content application. Also adds docs links for these
rules.","sha":"9c6272c1f24f9b9ac128ac655233ad098ed7ce3d","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.6.0","v8.7.0"],"number":146013,"url":"https://github.com/elastic/kibana/pull/146013","mergeCommit":{"message":"[Enterprise
Search] Rename filtering to sync rules (#146013)\n\nThis renames
'Filter(ing) Rules' to Sync rules across the Enterprise\r\nSearch
Content application. Also adds docs links for these
rules.","sha":"9c6272c1f24f9b9ac128ac655233ad098ed7ce3d"}},"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/146013","number":146013,"mergeCommit":{"message":"[Enterprise
Search] Rename filtering to sync rules (#146013)\n\nThis renames
'Filter(ing) Rules' to Sync rules across the Enterprise\r\nSearch
Content application. Also adds docs links for these
rules.","sha":"9c6272c1f24f9b9ac128ac655233ad098ed7ce3d"}}]}]
BACKPORT-->

Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com>
 2022-11-22 11:44:55 -07:00
Kibana Machine
70b026910a
[8.6] [Lens] [Annotation] Update ignoreGlobalFilters icon for annotation layers (#145975) (#146023) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Lens] [Annotation] Update ignoreGlobalFilters icon for annotation
layers (#145975)](https://github.com/elastic/kibana/pull/145975)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-22T16:39:29Z","message":"[Lens]
[Annotation] Update ignoreGlobalFilters icon for annotation layers
(#145975)\n\n## Summary\r\n\r\nFixes #142382 \r\n\r\nUpdated icon after
latest EUI upgrade.\r\n\r\n<img width=\"332\" alt=\"Screenshot
2022-11-22 at 12 55
03\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308138-b9de86a6-8c30-49a2-98c7-ae417227bbda.png\">\r\n<img
width=\"332\" alt=\"Screenshot 2022-11-22 at 12 55
16\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308147-9af11383-e65f-4f57-b49c-a588b74cc22f.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2fce9d6514546290ca64b41c6b60703617f3e060","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","v8.6.0","v8.7.0"],"number":145975,"url":"https://github.com/elastic/kibana/pull/145975","mergeCommit":{"message":"[Lens]
[Annotation] Update ignoreGlobalFilters icon for annotation layers
(#145975)\n\n## Summary\r\n\r\nFixes #142382 \r\n\r\nUpdated icon after
latest EUI upgrade.\r\n\r\n<img width=\"332\" alt=\"Screenshot
2022-11-22 at 12 55
03\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308138-b9de86a6-8c30-49a2-98c7-ae417227bbda.png\">\r\n<img
width=\"332\" alt=\"Screenshot 2022-11-22 at 12 55
16\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308147-9af11383-e65f-4f57-b49c-a588b74cc22f.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2fce9d6514546290ca64b41c6b60703617f3e060"}},"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/145975","number":145975,"mergeCommit":{"message":"[Lens]
[Annotation] Update ignoreGlobalFilters icon for annotation layers
(#145975)\n\n## Summary\r\n\r\nFixes #142382 \r\n\r\nUpdated icon after
latest EUI upgrade.\r\n\r\n<img width=\"332\" alt=\"Screenshot
2022-11-22 at 12 55
03\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308138-b9de86a6-8c30-49a2-98c7-ae417227bbda.png\">\r\n<img
width=\"332\" alt=\"Screenshot 2022-11-22 at 12 55
16\"\r\nsrc=\"https://user-images.githubusercontent.com/924948/203308147-9af11383-e65f-4f57-b49c-a588b74cc22f.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2fce9d6514546290ca64b41c6b60703617f3e060"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2022-11-22 11:20:05 -07:00
Kibana Machine
482b8d2416 skip failing test suite (#146014) 2022-11-22 13:13:53 -05:00
Kibana Machine
1da8e9dc45
[8.6] [SecuritySolution] Update area chart settings for user authentications (#145896) (#146007) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[SecuritySolution] Update area chart settings for user
authentications
(#145896)](https://github.com/elastic/kibana/pull/145896)

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

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

<!--BACKPORT [{"author":{"name":"Angela
Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-22T15:02:16Z","message":"[SecuritySolution]
Update area chart settings for user authentications (#145896)\n\n##
Summary\r\n\r\nOriginal issue: Title of x-axis on user authentications
area chart\r\nshould be
hidden.\r\n203034916-ced5dec7-5bca-44e6-a21f-21a8d5e5ccda.jpg\"\r\n/>\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","sha":"09b821daf97cf5db51062f7722b27693ff6fcd9c","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Threat
Hunting","Team: SecuritySolution","Team:Threat
Hunting:Explore","v8.6.0","v8.7.0","v8.5.2"],"number":145896,"url":"https://github.com/elastic/kibana/pull/145896","mergeCommit":{"message":"[SecuritySolution]
Update area chart settings for user authentications (#145896)\n\n##
Summary\r\n\r\nOriginal issue: Title of x-axis on user authentications
area chart\r\nshould be
hidden.\r\n203034916-ced5dec7-5bca-44e6-a21f-21a8d5e5ccda.jpg\"\r\n/>\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","sha":"09b821daf97cf5db51062f7722b27693ff6fcd9c"}},"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/145896","number":145896,"mergeCommit":{"message":"[SecuritySolution]
Update area chart settings for user authentications (#145896)\n\n##
Summary\r\n\r\nOriginal issue: Title of x-axis on user authentications
area chart\r\nshould be
hidden.\r\n203034916-ced5dec7-5bca-44e6-a21f-21a8d5e5ccda.jpg\"\r\n/>\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","sha":"09b821daf97cf5db51062f7722b27693ff6fcd9c"}},{"branch":"8.5","label":"v8.5.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Angela Chuang <6295984+angorayc@users.noreply.github.com>
 2022-11-22 09:39:02 -07:00
Kibana Machine
7fdd6925ce
[8.6] [ML] Explain Log Rate Spikes: improve the display of large groups (#145609) (#145934) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[ML] Explain Log Rate Spikes: improve the display of large groups
(#145609)](https://github.com/elastic/kibana/pull/145609)

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

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

<!--BACKPORT [{"author":{"name":"Melissa
Alvarez","email":"melissa.alvarez@elastic.co"},"sourceCommit":{"committedDate":"2022-11-21T20:21:14Z","message":"[ML]
Explain Log Rate Spikes: improve the display of large groups
(#145609)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142626\r\n\r\nImproves the
display of large groups by limiting the badges displayed to\r\n10 and
updates the +more badge.\r\n\r\n<img width=\"1066\" alt=\"image
(2)\"\r\nsrc=\"https://user-images.githubusercontent.com/6446462/202530438-210c7005-feb6-4e76-9bbd-48eb6b26293e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn
more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] 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\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"95dd36893232d9b6802799dc27ca911c59dee629","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","cosmetic","release_note:skip","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":145609,"url":"https://github.com/elastic/kibana/pull/145609","mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: improve the display of large groups
(#145609)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142626\r\n\r\nImproves the
display of large groups by limiting the badges displayed to\r\n10 and
updates the +more badge.\r\n\r\n<img width=\"1066\" alt=\"image
(2)\"\r\nsrc=\"https://user-images.githubusercontent.com/6446462/202530438-210c7005-feb6-4e76-9bbd-48eb6b26293e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn
more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] 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\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"95dd36893232d9b6802799dc27ca911c59dee629"}},"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/145609","number":145609,"mergeCommit":{"message":"[ML]
Explain Log Rate Spikes: improve the display of large groups
(#145609)\n\n## Summary\r\n\r\nRelated meta issue:
https://github.com/elastic/kibana/issues/142626\r\n\r\nImproves the
display of large groups by limiting the badges displayed to\r\n10 and
updates the +more badge.\r\n\r\n<img width=\"1066\" alt=\"image
(2)\"\r\nsrc=\"https://user-images.githubusercontent.com/6446462/202530438-210c7005-feb6-4e76-9bbd-48eb6b26293e.png\">\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn
more\r\nabout [keyboard
accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] 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\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"95dd36893232d9b6802799dc27ca911c59dee629"}}]}]
BACKPORT-->

Co-authored-by: Melissa Alvarez <melissa.alvarez@elastic.co>
 2022-11-22 09:25:52 -07:00
Kibana Machine
c26fc8684f
[8.6] [Synthetics] Getting started comment out the link (#145957) (#146010) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Synthetics] Getting started comment out the link
(#145957)](https://github.com/elastic/kibana/pull/145957)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad.muhammad@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T15:22:33Z","message":"[Synthetics]
Getting started comment out the link (#145957)\n\nFixes
https://github.com/elastic/kibana/issues/144863","sha":"ed56731a90f64683de2505919a8475b0f3d1b4de","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145957,"url":"https://github.com/elastic/kibana/pull/145957","mergeCommit":{"message":"[Synthetics]
Getting started comment out the link (#145957)\n\nFixes
https://github.com/elastic/kibana/issues/144863","sha":"ed56731a90f64683de2505919a8475b0f3d1b4de"}},"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/145957","number":145957,"mergeCommit":{"message":"[Synthetics]
Getting started comment out the link (#145957)\n\nFixes
https://github.com/elastic/kibana/issues/144863","sha":"ed56731a90f64683de2505919a8475b0f3d1b4de"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad.muhammad@elastic.co>
 2022-11-22 09:25:10 -07:00
Kibana Machine
2a20152880
[8.6] [Cases] Escape special characters in Parent issue field of Jira connector (#145610) (#146009) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Cases] Escape special characters in Parent issue field of Jira
connector (#145610)](https://github.com/elastic/kibana/pull/145610)

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

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

<!--BACKPORT [{"author":{"name":"Janki
Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2022-11-22T15:06:29Z","message":"[Cases]
Escape special characters in Parent issue field of Jira connector
(#145610)\n\n## Summary\r\n\r\nFixes #131281\r\n \r\nEscapes special
characters `+ - & | ! ( ) { } [ ] ^ ~ * ? \\ :` from\r\nparent issue
field.\r\n\r\n**Before**\r\n\r\n![image](202526111-4324ce5b-ea13-4bb6-8d96-388178b1b60d.png)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a42314d27046c34c7eebc4570f548870636ffe93","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Cases","v8.6.0","v8.7.0"],"number":145610,"url":"https://github.com/elastic/kibana/pull/145610","mergeCommit":{"message":"[Cases]
Escape special characters in Parent issue field of Jira connector
(#145610)\n\n## Summary\r\n\r\nFixes #131281\r\n \r\nEscapes special
characters `+ - & | ! ( ) { } [ ] ^ ~ * ? \\ :` from\r\nparent issue
field.\r\n\r\n**Before**\r\n\r\n![image](202526111-4324ce5b-ea13-4bb6-8d96-388178b1b60d.png)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a42314d27046c34c7eebc4570f548870636ffe93"}},"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/145610","number":145610,"mergeCommit":{"message":"[Cases]
Escape special characters in Parent issue field of Jira connector
(#145610)\n\n## Summary\r\n\r\nFixes #131281\r\n \r\nEscapes special
characters `+ - & | ! ( ) { } [ ] ^ ~ * ? \\ :` from\r\nparent issue
field.\r\n\r\n**Before**\r\n\r\n![image](202526111-4324ce5b-ea13-4bb6-8d96-388178b1b60d.png)\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a42314d27046c34c7eebc4570f548870636ffe93"}}]}]
BACKPORT-->

Co-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com>
 2022-11-22 09:11:07 -07:00
Kibana Machine
07884bf0a1
[8.6] [Security Solution][List details page]: Fix number of linked rules count (#145976) (#146002) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Security Solution][List details page]: Fix number of linked rules
count (#145976)](https://github.com/elastic/kibana/pull/145976)

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

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

<!--BACKPORT [{"author":{"name":"Wafaa
Nasr","email":"wafaa.nasr@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T14:33:44Z","message":"[Security
Solution][List details page]: Fix number of linked rules count
(#145976)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n- Getting all Rules
by passing all the pagination object as in the Rule\r\nExceptions
page","sha":"cd8dc111fa252d15a7971f38935301cdf60b2a68","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","Team:Security Solution
Platform","ci:cloud-deploy","v8.6.0","v8.7.0"],"number":145976,"url":"https://github.com/elastic/kibana/pull/145976","mergeCommit":{"message":"[Security
Solution][List details page]: Fix number of linked rules count
(#145976)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n- Getting all Rules
by passing all the pagination object as in the Rule\r\nExceptions
page","sha":"cd8dc111fa252d15a7971f38935301cdf60b2a68"}},"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/145976","number":145976,"mergeCommit":{"message":"[Security
Solution][List details page]: Fix number of linked rules count
(#145976)\n\n## Summary\r\n\r\n- Addresses
https://github.com/elastic/kibana/issues/145807\r\n- Getting all Rules
by passing all the pagination object as in the Rule\r\nExceptions
page","sha":"cd8dc111fa252d15a7971f38935301cdf60b2a68"}}]}] BACKPORT-->

Co-authored-by: Wafaa Nasr <wafaa.nasr@elastic.co>
 2022-11-22 09:05:35 -07:00
Kibana Machine
b58576010d
[8.6] [Synthetics] Overview - standardize queries for monitor duration metric item (#145916) (#146005) 
# Backport

This will backport the following commits from `main` to `8.6`:
- [[Synthetics] Overview - standardize queries for monitor duration
metric item (#145916)](https://github.com/elastic/kibana/pull/145916)

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

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

<!--BACKPORT [{"author":{"name":"Dominique
Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2022-11-22T14:49:07Z","message":"[Synthetics]
Overview - standardize queries for monitor duration metric item
(#145916)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/145922\r\nResolves
https://github.com/elastic/kibana/issues/145270\r\n\r\nFixes a
regression from
https://github.com/elastic/kibana/issues/143309\r\n\r\nStandardizes the
way the monitor duration metric is queried, ensuring\r\nthat both
monitor types, UI and Project, are queries in the same way.\r\n\r\nThe
changes were also carried into changes to the Monitor
Flyout\r\n\r\nBefore (duration for UI monitor shows, but not the
duration for
project\r\nmonitors)\r\n\r\n![image](https://user-images.githubusercontent.com/11356435/203143905-4564b14e-a2af-402c-a2c1-5b95d22ad1e3.png)\r\n\r\nAfter
(duration shows for both monitor types)\r\n<img width=\"1366\"
alt=\"Screen Shot 2022-11-21 at 2 39 09
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203144056-d74617e5-6745-4c17-9a68-e5164f4be689.png\">\r\n\r\n###
Testing\r\n1. Create at least one project monitor and one UI
monitor\r\n2. Ensure that both monitor types display the duration metric
on the\r\nOverview page after running\r\n3. In the actions popover,
click edit monitor. Ensure the page redirects\r\nto the monitor edit
page appropriately\r\n4. In the actions popover, click go to monitor.
Ensure that the page\r\nredirects to the monitor details page
appropriately\r\n5. In the actions popover, disable the monitor. Ensure
it is successful.\r\n6. In the actions popover, click inspect. Ensure
the monitor flyout\r\nappears, then close the flyout.\r\n7. Click on
both monitor types, ensure the monitor flyout appears\r\n8. Ensure the
monitor duration metric appears in the monitor flyout\r\n9. Ensure the
last test run appears in the monitor flyout\r\n10. Ensure both enable
toggles work in the monitor flyout (in the body\r\nof the flyout and
actions popover next to the flyout title)\r\n11. Ensure the go to
monitor link works in the monitor flyout actions\r\npopover next to the
monitor title\r\n12. Ensure the edit monitor link works in the monitor
flyout actions\r\npopover next to the monitor
title\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e8d77b3f0f46ac62e9220ffe28eb455880854906","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.6.0","v8.7.0"],"number":145916,"url":"https://github.com/elastic/kibana/pull/145916","mergeCommit":{"message":"[Synthetics]
Overview - standardize queries for monitor duration metric item
(#145916)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/145922\r\nResolves
https://github.com/elastic/kibana/issues/145270\r\n\r\nFixes a
regression from
https://github.com/elastic/kibana/issues/143309\r\n\r\nStandardizes the
way the monitor duration metric is queried, ensuring\r\nthat both
monitor types, UI and Project, are queries in the same way.\r\n\r\nThe
changes were also carried into changes to the Monitor
Flyout\r\n\r\nBefore (duration for UI monitor shows, but not the
duration for
project\r\nmonitors)\r\n\r\n![image](https://user-images.githubusercontent.com/11356435/203143905-4564b14e-a2af-402c-a2c1-5b95d22ad1e3.png)\r\n\r\nAfter
(duration shows for both monitor types)\r\n<img width=\"1366\"
alt=\"Screen Shot 2022-11-21 at 2 39 09
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203144056-d74617e5-6745-4c17-9a68-e5164f4be689.png\">\r\n\r\n###
Testing\r\n1. Create at least one project monitor and one UI
monitor\r\n2. Ensure that both monitor types display the duration metric
on the\r\nOverview page after running\r\n3. In the actions popover,
click edit monitor. Ensure the page redirects\r\nto the monitor edit
page appropriately\r\n4. In the actions popover, click go to monitor.
Ensure that the page\r\nredirects to the monitor details page
appropriately\r\n5. In the actions popover, disable the monitor. Ensure
it is successful.\r\n6. In the actions popover, click inspect. Ensure
the monitor flyout\r\nappears, then close the flyout.\r\n7. Click on
both monitor types, ensure the monitor flyout appears\r\n8. Ensure the
monitor duration metric appears in the monitor flyout\r\n9. Ensure the
last test run appears in the monitor flyout\r\n10. Ensure both enable
toggles work in the monitor flyout (in the body\r\nof the flyout and
actions popover next to the flyout title)\r\n11. Ensure the go to
monitor link works in the monitor flyout actions\r\npopover next to the
monitor title\r\n12. Ensure the edit monitor link works in the monitor
flyout actions\r\npopover next to the monitor
title\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e8d77b3f0f46ac62e9220ffe28eb455880854906"}},"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/145916","number":145916,"mergeCommit":{"message":"[Synthetics]
Overview - standardize queries for monitor duration metric item
(#145916)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/145922\r\nResolves
https://github.com/elastic/kibana/issues/145270\r\n\r\nFixes a
regression from
https://github.com/elastic/kibana/issues/143309\r\n\r\nStandardizes the
way the monitor duration metric is queried, ensuring\r\nthat both
monitor types, UI and Project, are queries in the same way.\r\n\r\nThe
changes were also carried into changes to the Monitor
Flyout\r\n\r\nBefore (duration for UI monitor shows, but not the
duration for
project\r\nmonitors)\r\n\r\n![image](https://user-images.githubusercontent.com/11356435/203143905-4564b14e-a2af-402c-a2c1-5b95d22ad1e3.png)\r\n\r\nAfter
(duration shows for both monitor types)\r\n<img width=\"1366\"
alt=\"Screen Shot 2022-11-21 at 2 39 09
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/203144056-d74617e5-6745-4c17-9a68-e5164f4be689.png\">\r\n\r\n###
Testing\r\n1. Create at least one project monitor and one UI
monitor\r\n2. Ensure that both monitor types display the duration metric
on the\r\nOverview page after running\r\n3. In the actions popover,
click edit monitor. Ensure the page redirects\r\nto the monitor edit
page appropriately\r\n4. In the actions popover, click go to monitor.
Ensure that the page\r\nredirects to the monitor details page
appropriately\r\n5. In the actions popover, disable the monitor. Ensure
it is successful.\r\n6. In the actions popover, click inspect. Ensure
the monitor flyout\r\nappears, then close the flyout.\r\n7. Click on
both monitor types, ensure the monitor flyout appears\r\n8. Ensure the
monitor duration metric appears in the monitor flyout\r\n9. Ensure the
last test run appears in the monitor flyout\r\n10. Ensure both enable
toggles work in the monitor flyout (in the body\r\nof the flyout and
actions popover next to the flyout title)\r\n11. Ensure the go to
monitor link works in the monitor flyout actions\r\npopover next to the
monitor title\r\n12. Ensure the edit monitor link works in the monitor
flyout actions\r\npopover next to the monitor
title\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"e8d77b3f0f46ac62e9220ffe28eb455880854906"}}]}]
BACKPORT-->

Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
 2022-11-22 08:54:32 -07:00