mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 07:48:52 -04:00
30744 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
c7c074756d
|
[8.8] [ResponseOps][Alerting] Some legacy mustache variables are not rendering for Security Solution rules after upgrading to 8.8.x (#160451) (#160459)
# Backport This will backport the following commits from `main` to `8.8`: - [[ResponseOps][Alerting] Some legacy mustache variables are not rendering for Security Solution rules after upgrading to 8.8.x (#160451)](https://github.com/elastic/kibana/pull/160451) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexi Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-23T20:34:31Z","message":"[ResponseOps][Alerting] Some legacy mustache variables are not rendering for Security Solution rules after upgrading to 8.8.x (#160451)\n\nResolves https://github.com/elastic/kibana/issues/160446\r\n\r\n## Summary\r\n\r\nAdding the following variables to\r\n`x-pack/plugins/alerting/server/task_runner/transform_action_params.ts`:\r\n\r\n- alertId\r\n- alertName\r\n- spaceId\r\n- tags\r\n- params\r\n- alertInstanceId\r\n- alertActionGroup\r\n- alertActionGroupName\r\n- alert.id\r\n- alert.uuid\r\n- alert.actionGroup\r\n- alert.actionGroupName\r\n- alert.flapping\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"857ca82352d5bec70814b52d524fbe4c8757625a","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v8.8.0","v8.9.0","v8.10.0"],"number":160451,"url":"https://github.com/elastic/kibana/pull/160451","mergeCommit":{"message":"[ResponseOps][Alerting] Some legacy mustache variables are not rendering for Security Solution rules after upgrading to 8.8.x (#160451)\n\nResolves https://github.com/elastic/kibana/issues/160446\r\n\r\n## Summary\r\n\r\nAdding the following variables to\r\n`x-pack/plugins/alerting/server/task_runner/transform_action_params.ts`:\r\n\r\n- alertId\r\n- alertName\r\n- spaceId\r\n- tags\r\n- params\r\n- alertInstanceId\r\n- alertActionGroup\r\n- alertActionGroupName\r\n- alert.id\r\n- alert.uuid\r\n- alert.actionGroup\r\n- alert.actionGroupName\r\n- alert.flapping\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"857ca82352d5bec70814b52d524fbe4c8757625a"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.9"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/160451","number":160451,"mergeCommit":{"message":"[ResponseOps][Alerting] Some legacy mustache variables are not rendering for Security Solution rules after upgrading to 8.8.x (#160451)\n\nResolves https://github.com/elastic/kibana/issues/160446\r\n\r\n## Summary\r\n\r\nAdding the following variables to\r\n`x-pack/plugins/alerting/server/task_runner/transform_action_params.ts`:\r\n\r\n- alertId\r\n- alertName\r\n- spaceId\r\n- tags\r\n- params\r\n- alertInstanceId\r\n- alertActionGroup\r\n- alertActionGroupName\r\n- alert.id\r\n- alert.uuid\r\n- alert.actionGroup\r\n- alert.actionGroupName\r\n- alert.flapping\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"857ca82352d5bec70814b52d524fbe4c8757625a"}}]}] BACKPORT--> Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com> |
||
|
Kibana Machine
|
97610fbc3e
|
[8.8] FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957) (#160435)
# Backport This will backport the following commits from `main` to `8.8`: - [FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957)](https://github.com/elastic/kibana/pull/159957) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-06-23T16:04:11Z","message":"FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better understand the PR, we need to have a look at `esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n- It processes the file and if it finds saved object index (e.g.\r\n`.kibana`), it will delete all SO indexes (.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created on Kibana\r\nstart. Then esArchiver will re-create all indexes according to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to the latest code changes, it is\r\ngood to avoid re-creating SO indexes and use \"official\" ones whenever it\r\nis possible. This PR removes/cleans `mappings.json` files where it seems\r\nreasonable. I also deleted few not used archives:\r\n- es_archiver/saved_objects/ui_counters\r\n- es_archiver/saved_objects/usage_counters\r\n- security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.2","v8.10.0"],"number":159957,"url":"https://github.com/elastic/kibana/pull/159957","mergeCommit":{"message":"FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better understand the PR, we need to have a look at `esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n- It processes the file and if it finds saved object index (e.g.\r\n`.kibana`), it will delete all SO indexes (.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created on Kibana\r\nstart. Then esArchiver will re-create all indexes according to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to the latest code changes, it is\r\ngood to avoid re-creating SO indexes and use \"official\" ones whenever it\r\nis possible. This PR removes/cleans `mappings.json` files where it seems\r\nreasonable. I also deleted few not used archives:\r\n- es_archiver/saved_objects/ui_counters\r\n- es_archiver/saved_objects/usage_counters\r\n- security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777"}},"sourceBranch":"main","suggestedTargetBranches":["8.9","8.8"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159957","number":159957,"mergeCommit":{"message":"FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957)\n\n## Summary\r\n\r\nRelated to #159582\r\n\r\nTo better understand the PR, we need to have a look at `esArchiver.load`\r\nfunction and how it handles `mappings.json`:\r\n- It processes the file and if it finds saved object index (e.g.\r\n`.kibana`), it will delete all SO indexes (.kibana,\r\n.kibana_task_manager, .kibana_alerting_cases, etc.) created on Kibana\r\nstart. Then esArchiver will re-create all indexes according to defined\r\nmappings.\r\n\r\nIn order to keep our tests relevant to the latest code changes, it is\r\ngood to avoid re-creating SO indexes and use \"official\" ones whenever it\r\nis possible. This PR removes/cleans `mappings.json` files where it seems\r\nreasonable. I also deleted few not used archives:\r\n- es_archiver/saved_objects/ui_counters\r\n- es_archiver/saved_objects/usage_counters\r\n- security_solution_cypress/es_archives/empty_kibana","sha":"88871faf60ec5a62c4aea48911883a6d7f937777"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
James Gowdy
|
913ea518cc
|
[ML] [8.8] fix saved object sync check for jobs in different space (#160402)
Manual backport of https://github.com/elastic/kibana/pull/160266 |
||
|
Kibana Machine
|
3a08f5a8fa
|
[8.8] [ML] Fix not blocking forced downgrades/installation if cannot delete indices (#159814) (#160089)
Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com> fix",":ml","Team:Fleet","v8.9.0","v8.8.2"],"number":159814,"url":"https://github.com/elastic/kibana/pull/159814","mergeCommit":{"message":"[ML] |
||
Jatin Kathuria
|
5df083d62f
|
[8.8] [Security Solution] [Fix] [Performance] Alert Page Controls should query only from Alert Index. (#157286) (#160138)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] [Fix] [Performance] Alert Page Controls should query only from Alert Index. (#157286)](https://github.com/elastic/kibana/pull/157286) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2023-06-21T12:21:16Z","message":"[Security Solution] [Fix] [Performance] Alert Page Controls should query only from Alert Index. (#157286)\n\n## Summary\r\n\r\nHandles : #157217\r\n\r\n\r\n|Before|After|\r\n|---|---|\r\n| <video\r\nsrc=\" |
||
|
Kibana Machine
|
3888dc0309
|
[8.8] [Fleet] Datastreams api do not query warm nodes anymore (#160234) (#160254)
# Backport This will backport the following commits from `main` to `8.8`: - [[Fleet] Datastreams api do not query warm nodes anymore (#160234)](https://github.com/elastic/kibana/pull/160234) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-22T10:38:50Z","message":"[Fleet] Datastreams api do not query warm nodes anymore (#160234)\n\nFixes https://github.com/elastic/kibana/issues/159977\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/159253/files we removed cold\r\nnodes from datastreams apis because of performance issues. Now we are\r\nalso removing warm nodes as they were still causing high load.","sha":"924da11c89955b6c5e7acf6bbb8c6dcd5f2f499e","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.9.0","v8.8.2"],"number":160234,"url":"https://github.com/elastic/kibana/pull/160234","mergeCommit":{"message":"[Fleet] Datastreams api do not query warm nodes anymore (#160234)\n\nFixes https://github.com/elastic/kibana/issues/159977\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/159253/files we removed cold\r\nnodes from datastreams apis because of performance issues. Now we are\r\nalso removing warm nodes as they were still causing high load.","sha":"924da11c89955b6c5e7acf6bbb8c6dcd5f2f499e"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/160234","number":160234,"mergeCommit":{"message":"[Fleet] Datastreams api do not query warm nodes anymore (#160234)\n\nFixes https://github.com/elastic/kibana/issues/159977\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/159253/files we removed cold\r\nnodes from datastreams apis because of performance issues. Now we are\r\nalso removing warm nodes as they were still causing high load.","sha":"924da11c89955b6c5e7acf6bbb8c6dcd5f2f499e"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com> |
||
|
Kibana Machine
|
db8521641e
|
[8.8] [AO] Fix issue with alert summary widget refresh on the Alerts page (#160159) (#160233)
# Backport This will backport the following commits from `main` to `8.8`: - [[AO] Fix issue with alert summary widget refresh on the Alerts page (#160159)](https://github.com/elastic/kibana/pull/160159) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2023-06-22T08:36:41Z","message":"[AO] Fix issue with alert summary widget refresh on the Alerts page (#160159)\n\nFixes #157245\r\n\r\n## Summary\r\n\r\nThis PR updates the absolute time range when the refresh button is\r\nclicked.\r\n\r\n## 🧪 How to test\r\n- On the Alerts page, click on refresh and check the time range of\r\n`_alert_summary` API call, it should be updated with each refresh\r\n\r\n\r\n
Dario Gieselaar
|
f190fd1da9
|
Revert "[8.8] [APM] Circuit breaker and perf improvements for service… (#160132) | ||
|
Kibana Machine
|
d861400833
|
[8.8] [Detection Engine][Exceptions] - Fix exception item update route (#159223) (#159420)
# Backport This will backport the following commits from `main` to `8.8`: - [[Detection Engine][Exceptions] - Fix exception item update route (#159223)](https://github.com/elastic/kibana/pull/159223) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-09T19:31:03Z","message":"[Detection Engine][Exceptions] - Fix exception item update route (#159223)\n\n## Summary\r\n\r\nAddresses issue 159230","sha":"f895c5c2058f3f36c828fe9d8f1dbc0c19a2b381","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team: SecuritySolution","Feature:Rule Exceptions","v8.7.2","v8.9.0","Team:Detection Engine","v8.8.2"],"number":159223,"url":"https://github.com/elastic/kibana/pull/159223","mergeCommit":{"message":"[Detection Engine][Exceptions] - Fix exception item update route (#159223)\n\n## Summary\r\n\r\nAddresses issue 159230","sha":"f895c5c2058f3f36c828fe9d8f1dbc0c19a2b381"}},"sourceBranch":"main","suggestedTargetBranches":["8.7","8.8"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159223","number":159223,"mergeCommit":{"message":"[Detection Engine][Exceptions] - Fix exception item update route (#159223)\n\n## Summary\r\n\r\nAddresses issue 159230","sha":"f895c5c2058f3f36c828fe9d8f1dbc0c19a2b381"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com> |
||
|
Kibana Machine
|
e2c3c9a301
|
[8.8] Fixes per-object audit logging for saved object resolve actions (#160014) (#160101)
# Backport This will backport the following commits from `main` to `8.8`: - [Fixes per-object audit logging for saved object resolve actions (#160014)](https://github.com/elastic/kibana/pull/160014) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-06-21T08:03:31Z","message":"Fixes per-object audit logging for saved object resolve actions (#160014)\n\n## Summary\r\nIt was noticed that audit logs for Saved Object 'resolve' actions were\r\nnot getting generated. On investigation we found that this regression\r\nwas introduced in #148165. During work on migrating saved object\r\nauthorization and auditing logic into the saved object security\r\nextension, several abstracted functions were created for reuse. One of\r\nthese is responsible for performing audit logging (`auditHelper`). In\r\nmigration of the unit tests, inputs to the `auditHelper`, via\r\n`authorize` and `enforceAuthoriztion`, were not correctly validated for\r\n`authorizeAndRedactInternalBulkResolve`.\r\n\r\nThis PR corrects the regression by passing the saved object information\r\nthrough the call chain to `auditHelper`, and addresses the error in the\r\nunit tests by implementing checks to validate the input parameters at\r\neach level of the call chain.\r\n\r\nThis PR also corrects the unit test for auditObjectsForSpaceDeletion.\r\n\r\n### Tests\r\nSee\r\n`x-pack/plugins/security/server/saved_objects/saved_objects_security_extension.test.ts`\r\n'#authorizeAndRedactInternalBulkResolve'\r\n\r\n### Manual testing:\r\n- Enable audit logging, example:\r\n\r\n```yaml\r\nxpack.security.audit.enabled: true\r\nxpack.security.audit.appender:\r\n type: rolling-file\r\n fileName: ./logs/audit.log\r\n policy:\r\n type: time-interval\r\n interval: 24h\r\n strategy:\r\n type: numeric\r\n max: 10\r\n layout:\r\n type: json\r\n```\r\n\r\n- Create several dashboards (or add all sample data sets)\r\n- Open each dashboard in the Kibana UI\r\n- Check the audit logs and verify that there is a \"saved_object_resolve\"\r\nentry to describe each dashboard access event, and that each log\r\ncontains the dashboard type and id, example:\r\n\r\n>\r\n{\"event\":{\"action\":\"saved_object_resolve\",\"category\":[\"database\"],\"type\":[\"access\"],\"outcome\":\"success\"},\"kibana\":{\"space_id\":\"default\",\"session_id\":\"HrDKOgZ6EiEV2bf8Io9bc/enfGsS+fTtbQ5g2ap21CU=\",\"saved_object\":{\"type\":\"dashboard\",\"id\":\"7adfa750-4c81-11e8-b3d7-01146121b73d\"}},\"user\":{\"id\":\"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\"name\":\"elastic\",\"roles\":[\"superuser\"]},\"trace\":{\"id\":\"b11f0414-ca68-4e28-854a-249b19f88c36\"},\"client\":{\"ip\":\"127.0.0.1\"},\"http\":{\"request\":{\"headers\":{\"x-forwarded-for\":\"127.0.0.1\"}}},\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}},\"ecs\":{\"version\":\"8.6.1\"},\"@timestamp\":\"2023-06-20T18:30:20.943+02:00\",\"message\":\"User\r\nhas resolved dashboard\r\n[id=7adfa750-4c81-11e8-b3d7-01146121b73d]\",\"log\":{\"level\":\"INFO\",\"logger\":\"plugins.security.audit.ecs\"},\"process\":{\"pid\":15004},\"transaction\":{\"id\":\"4917a352c3f68cd6\"}}\r\n\r\n## Release Note:\r\nThis PR fixes a regression where the \"saved_object_resolve\" audit action\r\nwas not being logged per object.","sha":"2ec067f7474118d089f46c0e2a9e726dc4c6c852","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["blocker","release_note:fix","Feature:Saved Objects","Feature:Security/Audit","backport:prev-minor","v8.9.0","v8.8.2"],"number":160014,"url":"https://github.com/elastic/kibana/pull/160014","mergeCommit":{"message":"Fixes per-object audit logging for saved object resolve actions (#160014)\n\n## Summary\r\nIt was noticed that audit logs for Saved Object 'resolve' actions were\r\nnot getting generated. On investigation we found that this regression\r\nwas introduced in #148165. During work on migrating saved object\r\nauthorization and auditing logic into the saved object security\r\nextension, several abstracted functions were created for reuse. One of\r\nthese is responsible for performing audit logging (`auditHelper`). In\r\nmigration of the unit tests, inputs to the `auditHelper`, via\r\n`authorize` and `enforceAuthoriztion`, were not correctly validated for\r\n`authorizeAndRedactInternalBulkResolve`.\r\n\r\nThis PR corrects the regression by passing the saved object information\r\nthrough the call chain to `auditHelper`, and addresses the error in the\r\nunit tests by implementing checks to validate the input parameters at\r\neach level of the call chain.\r\n\r\nThis PR also corrects the unit test for auditObjectsForSpaceDeletion.\r\n\r\n### Tests\r\nSee\r\n`x-pack/plugins/security/server/saved_objects/saved_objects_security_extension.test.ts`\r\n'#authorizeAndRedactInternalBulkResolve'\r\n\r\n### Manual testing:\r\n- Enable audit logging, example:\r\n\r\n```yaml\r\nxpack.security.audit.enabled: true\r\nxpack.security.audit.appender:\r\n type: rolling-file\r\n fileName: ./logs/audit.log\r\n policy:\r\n type: time-interval\r\n interval: 24h\r\n strategy:\r\n type: numeric\r\n max: 10\r\n layout:\r\n type: json\r\n```\r\n\r\n- Create several dashboards (or add all sample data sets)\r\n- Open each dashboard in the Kibana UI\r\n- Check the audit logs and verify that there is a \"saved_object_resolve\"\r\nentry to describe each dashboard access event, and that each log\r\ncontains the dashboard type and id, example:\r\n\r\n>\r\n{\"event\":{\"action\":\"saved_object_resolve\",\"category\":[\"database\"],\"type\":[\"access\"],\"outcome\":\"success\"},\"kibana\":{\"space_id\":\"default\",\"session_id\":\"HrDKOgZ6EiEV2bf8Io9bc/enfGsS+fTtbQ5g2ap21CU=\",\"saved_object\":{\"type\":\"dashboard\",\"id\":\"7adfa750-4c81-11e8-b3d7-01146121b73d\"}},\"user\":{\"id\":\"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\"name\":\"elastic\",\"roles\":[\"superuser\"]},\"trace\":{\"id\":\"b11f0414-ca68-4e28-854a-249b19f88c36\"},\"client\":{\"ip\":\"127.0.0.1\"},\"http\":{\"request\":{\"headers\":{\"x-forwarded-for\":\"127.0.0.1\"}}},\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}},\"ecs\":{\"version\":\"8.6.1\"},\"@timestamp\":\"2023-06-20T18:30:20.943+02:00\",\"message\":\"User\r\nhas resolved dashboard\r\n[id=7adfa750-4c81-11e8-b3d7-01146121b73d]\",\"log\":{\"level\":\"INFO\",\"logger\":\"plugins.security.audit.ecs\"},\"process\":{\"pid\":15004},\"transaction\":{\"id\":\"4917a352c3f68cd6\"}}\r\n\r\n## Release Note:\r\nThis PR fixes a regression where the \"saved_object_resolve\" audit action\r\nwas not being logged per object.","sha":"2ec067f7474118d089f46c0e2a9e726dc4c6c852"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/160014","number":160014,"mergeCommit":{"message":"Fixes per-object audit logging for saved object resolve actions (#160014)\n\n## Summary\r\nIt was noticed that audit logs for Saved Object 'resolve' actions were\r\nnot getting generated. On investigation we found that this regression\r\nwas introduced in #148165. During work on migrating saved object\r\nauthorization and auditing logic into the saved object security\r\nextension, several abstracted functions were created for reuse. One of\r\nthese is responsible for performing audit logging (`auditHelper`). In\r\nmigration of the unit tests, inputs to the `auditHelper`, via\r\n`authorize` and `enforceAuthoriztion`, were not correctly validated for\r\n`authorizeAndRedactInternalBulkResolve`.\r\n\r\nThis PR corrects the regression by passing the saved object information\r\nthrough the call chain to `auditHelper`, and addresses the error in the\r\nunit tests by implementing checks to validate the input parameters at\r\neach level of the call chain.\r\n\r\nThis PR also corrects the unit test for auditObjectsForSpaceDeletion.\r\n\r\n### Tests\r\nSee\r\n`x-pack/plugins/security/server/saved_objects/saved_objects_security_extension.test.ts`\r\n'#authorizeAndRedactInternalBulkResolve'\r\n\r\n### Manual testing:\r\n- Enable audit logging, example:\r\n\r\n```yaml\r\nxpack.security.audit.enabled: true\r\nxpack.security.audit.appender:\r\n type: rolling-file\r\n fileName: ./logs/audit.log\r\n policy:\r\n type: time-interval\r\n interval: 24h\r\n strategy:\r\n type: numeric\r\n max: 10\r\n layout:\r\n type: json\r\n```\r\n\r\n- Create several dashboards (or add all sample data sets)\r\n- Open each dashboard in the Kibana UI\r\n- Check the audit logs and verify that there is a \"saved_object_resolve\"\r\nentry to describe each dashboard access event, and that each log\r\ncontains the dashboard type and id, example:\r\n\r\n>\r\n{\"event\":{\"action\":\"saved_object_resolve\",\"category\":[\"database\"],\"type\":[\"access\"],\"outcome\":\"success\"},\"kibana\":{\"space_id\":\"default\",\"session_id\":\"HrDKOgZ6EiEV2bf8Io9bc/enfGsS+fTtbQ5g2ap21CU=\",\"saved_object\":{\"type\":\"dashboard\",\"id\":\"7adfa750-4c81-11e8-b3d7-01146121b73d\"}},\"user\":{\"id\":\"u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0\",\"name\":\"elastic\",\"roles\":[\"superuser\"]},\"trace\":{\"id\":\"b11f0414-ca68-4e28-854a-249b19f88c36\"},\"client\":{\"ip\":\"127.0.0.1\"},\"http\":{\"request\":{\"headers\":{\"x-forwarded-for\":\"127.0.0.1\"}}},\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}},\"ecs\":{\"version\":\"8.6.1\"},\"@timestamp\":\"2023-06-20T18:30:20.943+02:00\",\"message\":\"User\r\nhas resolved dashboard\r\n[id=7adfa750-4c81-11e8-b3d7-01146121b73d]\",\"log\":{\"level\":\"INFO\",\"logger\":\"plugins.security.audit.ecs\"},\"process\":{\"pid\":15004},\"transaction\":{\"id\":\"4917a352c3f68cd6\"}}\r\n\r\n## Release Note:\r\nThis PR fixes a regression where the \"saved_object_resolve\" audit action\r\nwas not being logged per object.","sha":"2ec067f7474118d089f46c0e2a9e726dc4c6c852"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> |
||
Ievgen Sorokopud
|
c3cb2f713a
|
[8.8] [Security Solutions] Error pops up on rules creation for uninstalled ML jobs (#159316) (#160043)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solutions] Error pops up on rules creation for uninstalled ML jobs (#159316)](https://github.com/elastic/kibana/pull/159316) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2023-06-19T11:11:19Z","message":"[Security Solutions] Error pops up on rules creation for uninstalled ML jobs (#159316)\n\n## Summary\r\n\r\nOriginal ticket: https://github.com/elastic/kibana/issues/151168\r\n\r\nThese changes fix the issue with unexpected error toasts being shown on\r\nselecting uninstalled ML jobs while creating an ML rule.\r\n\r\nThe issue was that we used ML API `'/internal/ml/jobs/jobs'` to fetch\r\nthe information about the job which assumed that requested jobs are\r\ninstalled. When jobs are not, it throws an exception.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f0f299f5c1fb649ca71d6aa85d468dd9f5575d50","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","ci:cloud-deploy","8.9 candidate","v8.9.0","Team:Detection Engine","v8.8.2"],"number":159316,"url":"https://github.com/elastic/kibana/pull/159316","mergeCommit":{"message":"[Security Solutions] Error pops up on rules creation for uninstalled ML jobs (#159316)\n\n## Summary\r\n\r\nOriginal ticket: https://github.com/elastic/kibana/issues/151168\r\n\r\nThese changes fix the issue with unexpected error toasts being shown on\r\nselecting uninstalled ML jobs while creating an ML rule.\r\n\r\nThe issue was that we used ML API `'/internal/ml/jobs/jobs'` to fetch\r\nthe information about the job which assumed that requested jobs are\r\ninstalled. When jobs are not, it throws an exception.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f0f299f5c1fb649ca71d6aa85d468dd9f5575d50"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159316","number":159316,"mergeCommit":{"message":"[Security Solutions] Error pops up on rules creation for uninstalled ML jobs (#159316)\n\n## Summary\r\n\r\nOriginal ticket: https://github.com/elastic/kibana/issues/151168\r\n\r\nThese changes fix the issue with unexpected error toasts being shown on\r\nselecting uninstalled ML jobs while creating an ML rule.\r\n\r\nThe issue was that we used ML API `'/internal/ml/jobs/jobs'` to fetch\r\nthe information about the job which assumed that requested jobs are\r\ninstalled. When jobs are not, it throws an exception.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"f0f299f5c1fb649ca71d6aa85d468dd9f5575d50"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
b2688fe4ed
|
[8.8] [APM] Circuit breaker and perf improvements for service map (#159883) (#160060)
# Backport This will backport the following commits from `main` to `8.8`: - [[APM] Circuit breaker and perf improvements for service map (#159883)](https://github.com/elastic/kibana/pull/159883) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2023-06-20T16:38:23Z","message":"[APM] Circuit breaker and perf improvements for service map (#159883)\n\nCloses #101920\r\n\r\nThis PR does three things:\r\n\r\n- add a `terminate_after` parameter to the search request for the\r\nscripted metric agg. This is a configurable setting\r\n(`xpack.apm.serviceMapTerminateAfter`) and defaults to 100k. This is a\r\nshard-level parameter, so there's still the possibility of lots of\r\nshards individually returning 100k documents and the coordinating node\r\nrunning out of memory because it is collecting all these docs from\r\nindividual shards. However, I suspect that there is already some\r\nprotection in the reduce phase that will terminate the request with a\r\nstack_overflow_error without OOMing, I've reached out to the ES team to\r\nconfirm whether this is the case.\r\n- add `xpack.apm.serviceMapMaxTraces`: this tells the max traces to\r\ninspect in total, not just per search request. IE, if\r\n`xpack.apm.serviceMapMaxTracesPerRequest` is 1, we simply chunk the\r\ntraces in n chunks, so it doesn't really help with memory management.\r\n`serviceMapMaxTraces` refers to the total amount of traces to inspect.\r\n- rewrite `getConnections` to use local mutation instead of\r\nimmutability. I saw huge CPU usage (with admittedly a pathological\r\nscenario where there are 100s of services) in the `getConnections`\r\nfunction, because it uses a deduplication mechanism that is O(n²), so I\r\nrewrote it to O(n). Here's a before :\r\n\r\n\r\n (#160023)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] Add support for GET requests to the Detection Engine health API (#159970)](https://github.com/elastic/kibana/pull/159970) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2023-06-20T14:03:27Z","message":"[Security Solution] Add support for GET requests to the Detection Engine health API (#159970)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/125642\r\n\r\n## Summary\r\n\r\nThe PoC of the Detection Engine health API has been implemented in\r\nhttps://github.com/elastic/kibana/pull/157155. Now, we need to integrate\r\nit into the\r\n[support-diagnostics](https://github.com/elastic/support-diagnostics)\r\ntool. It looks like the tool requires the APIs it calls to be callable\r\nwith the `GET` verb.\r\n\r\nThis PR makes it possible to call 2 out of 3 health endpoints with\r\n`GET`:\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_cluster\r\n```\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_space\r\n```\r\n\r\nThe `GET` routes don't accept any parameters and use the default\r\nparameters instead:\r\n\r\n- interval: `last_day`\r\n- granularity: `hour`\r\n- debug: `false`\r\n\r\n\r\n### Checklist\r\n\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [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":"7047f24c1743a2a98e22e332403c5260d6062374","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Monitoring","Team:Detection Rule Management","v8.9.0","v8.8.2"],"number":159970,"url":"https://github.com/elastic/kibana/pull/159970","mergeCommit":{"message":"[Security Solution] Add support for GET requests to the Detection Engine health API (#159970)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/125642\r\n\r\n## Summary\r\n\r\nThe PoC of the Detection Engine health API has been implemented in\r\nhttps://github.com/elastic/kibana/pull/157155. Now, we need to integrate\r\nit into the\r\n[support-diagnostics](https://github.com/elastic/support-diagnostics)\r\ntool. It looks like the tool requires the APIs it calls to be callable\r\nwith the `GET` verb.\r\n\r\nThis PR makes it possible to call 2 out of 3 health endpoints with\r\n`GET`:\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_cluster\r\n```\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_space\r\n```\r\n\r\nThe `GET` routes don't accept any parameters and use the default\r\nparameters instead:\r\n\r\n- interval: `last_day`\r\n- granularity: `hour`\r\n- debug: `false`\r\n\r\n\r\n### Checklist\r\n\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [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":"7047f24c1743a2a98e22e332403c5260d6062374"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159970","number":159970,"mergeCommit":{"message":"[Security Solution] Add support for GET requests to the Detection Engine health API (#159970)\n\n**Partially addresses:** https://github.com/elastic/kibana/issues/125642\r\n\r\n## Summary\r\n\r\nThe PoC of the Detection Engine health API has been implemented in\r\nhttps://github.com/elastic/kibana/pull/157155. Now, we need to integrate\r\nit into the\r\n[support-diagnostics](https://github.com/elastic/support-diagnostics)\r\ntool. It looks like the tool requires the APIs it calls to be callable\r\nwith the `GET` verb.\r\n\r\nThis PR makes it possible to call 2 out of 3 health endpoints with\r\n`GET`:\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_cluster\r\n```\r\n\r\n```txt\r\nGET /internal/detection_engine/health/_space\r\n```\r\n\r\nThe `GET` routes don't accept any parameters and use the default\r\nparameters instead:\r\n\r\n- interval: `last_day`\r\n- granularity: `hour`\r\n- debug: `false`\r\n\r\n\r\n### Checklist\r\n\r\n- [x]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [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":"7047f24c1743a2a98e22e332403c5260d6062374"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> |
||
|
Kibana Machine
|
58d19d3ae7
|
[8.8] [Security Solution][ResponseOps] fixes context.results_link in actions params (#159966) (#160022)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution][ResponseOps] fixes context.results_link in actions params (#159966)](https://github.com/elastic/kibana/pull/159966) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-20T14:02:53Z","message":"[Security Solution][ResponseOps] fixes context.results_link in actions params (#159966)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/159586\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- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard 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\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":"a653a3eca984da1a1c013330f8324dff727d3c48","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Detections and Resp","Team: SecuritySolution","backport:prev-minor","v8.9.0","Team:Detection Engine","v8.8.2"],"number":159966,"url":"https://github.com/elastic/kibana/pull/159966","mergeCommit":{"message":"[Security Solution][ResponseOps] fixes context.results_link in actions params (#159966)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/159586\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- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard 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\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":"a653a3eca984da1a1c013330f8324dff727d3c48"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159966","number":159966,"mergeCommit":{"message":"[Security Solution][ResponseOps] fixes context.results_link in actions params (#159966)\n\n## Summary\r\n\r\n- fixes https://github.com/elastic/kibana/issues/159586\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- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard 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\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":"a653a3eca984da1a1c013330f8324dff727d3c48"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
4fde17f20c
|
[8.8] [Security Solution] Adds several new fields to allowed Exceptions for Endpoint (#159835) (#159924)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] Adds several new fields to allowed Exceptions for Endpoint (#159835)](https://github.com/elastic/kibana/pull/159835) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Logan","email":"56395104+kevinlog@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-19T12:58:08Z","message":"[Security Solution] Adds several new fields to allowed Exceptions for Endpoint (#159835)\n\n## Summary\r\n\r\nAdds the following new fields to allowed Exceptions for Endpoint after\r\ncustomer and internal requests.\r\n\r\nWe can backport this to `8.8.2` in addition to shipping in `8.9.0`\r\n\r\n```\r\n \"process.args\",\r\n \"process.parent.args\",\r\n \"dns.question.type\",\r\n \"file.pe.Ext.dotnet\",\r\n \"file.pe.Ext.streams.hash.md5\",\r\n \"file.pe.Ext.streams.hash.sha256\",\r\n \"file.pe.Ext.sections.hash.sha256\",\r\n \"file.pe.Ext.sections.hash.md5\",\r\n \"file.pe.Ext.streams.name\",\r\n \"Effective_process.entity_id\",\r\n \"Effective_process.executable\",\r\n \"Effective_process.name\",\r\n \"Effective_process.pid\"\r\n```\r\n\r\nSee the Endpoint Exception builder below with the new fields available\r\nfor use.\r\n\r\n\r\n
Julia Bardi
|
546f2cd0a6
|
[8.8] [Fleet] Fix usage of AsyncLocalStorage for audit log (#159983)
Backport https://github.com/elastic/kibana/pull/159807 Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
2faa186224
|
[8.8] [AO] Handle buildEsQuery error (such as leading wildcard) in status change (#159891) (#159938)
# Backport This will backport the following commits from `main` to `8.8`: - [AO] Handle buildEsQuery error (such as leading wildcard) in status change (#159891) ( |
||
|
Kibana Machine
|
1147d386fb
|
[8.8] [ML] Reverting use of isPopulatedObject in error utils (#159913) (#159923)
# Backport This will backport the following commits from `main` to `8.8`: - [[ML] Reverting use of isPopulatedObject in error utils (#159913)](https://github.com/elastic/kibana/pull/159913) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2023-06-19T12:52:11Z","message":"[ML] Reverting use of isPopulatedObject in error utils (#159913)\n\nPR https://github.com/elastic/kibana/pull/155372 moved our error utils\r\nto a package and also made a few small code changes, one of which added\r\n`isPopulatedObject` to the error object type guards.\r\n`isPopulatedObject` uses `Object.keys` under the hood which cannot be\r\nused to access the non-enumerable properties of an object, like Error's\r\n`message`.\r\n\r\n\r\n (#159918)
# Backport This will backport the following commits from `main` to `8.8`: - [[Synthetics] http monitors - account for custom Content-Type headers (#159737)](https://github.com/elastic/kibana/pull/159737) <!--- 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":"2023-06-19T11:49:55Z","message":"[Synthetics] http monitors - account for custom Content-Type headers (#159737)","sha":"fc32999c91760ed399b872d507fd84d308f5829e","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:uptime","v8.9.0","v8.8.2"],"number":159737,"url":"https://github.com/elastic/kibana/pull/159737","mergeCommit":{"message":"[Synthetics] http monitors - account for custom Content-Type headers (#159737)","sha":"fc32999c91760ed399b872d507fd84d308f5829e"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159737","number":159737,"mergeCommit":{"message":"[Synthetics] http monitors - account for custom Content-Type headers (#159737)","sha":"fc32999c91760ed399b872d507fd84d308f5829e"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
Devon Thomson
|
9e48a57755
|
[8.8] [Dashboard] Fast Navigation Between Dashboards (#157437) (#159827)
# Backport This will backport the following commits from `main` to `8.8`: - [[Dashboard] Fast Navigation Between Dashboards (#157437)](https://github.com/elastic/kibana/pull/157437) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devon Thomson","email":"devon.thomson@elastic.co"},"sourceCommit":{"committedDate":"2023-05-25T18:40:48Z","message":"[Dashboard] Fast Navigation Between Dashboards (#157437)\n\n## Summary\r\nMakes all navigation from one Dashboard to another feel snappier.","sha":"5342563a22a54223180a727a542a7b6c99caea7f","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Dashboard","Team:Presentation","loe:days","impact:medium","backport:skip","v8.8.0","v8.9.0"],"number":157437,"url":"https://github.com/elastic/kibana/pull/157437","mergeCommit":{"message":"[Dashboard] Fast Navigation Between Dashboards (#157437)\n\n## Summary\r\nMakes all navigation from one Dashboard to another feel snappier.","sha":"5342563a22a54223180a727a542a7b6c99caea7f"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157437","number":157437,"mergeCommit":{"message":"[Dashboard] Fast Navigation Between Dashboards (#157437)\n\n## Summary\r\nMakes all navigation from one Dashboard to another feel snappier.","sha":"5342563a22a54223180a727a542a7b6c99caea7f"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com> |
||
|
Kibana Machine
|
1bdfebab70
|
[8.8] [SecuritySolution] Update checkIndicesExists logic (#159806) (#159836)
# Backport This will backport the following commits from `main` to `8.8`: - [[SecuritySolution] Update checkIndicesExists logic (#159806)](https://github.com/elastic/kibana/pull/159806) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-15T19:06:30Z","message":"[SecuritySolution] Update checkIndicesExists logic (#159806)\n\n## Summary\r\n\r\nissue: https://github.com/elastic/kibana/issues/159107\r\n\r\n\r\n\r\n**Steps to verify:**\r\n\r\n1. Generate some alerts and enable host or user risk score module.\r\n2. Hard refresh the page, select the alerts data view. \r\n\r\n<img width=\"639\" alt=\"Screenshot 2023-06-15 at 14 54 54\"\r\nsrc=\" |
||
Nathan Reese
|
8899487bbf
|
[8.8][maps] fix layer group loading indicator always on when group has non-visible layer (#159517) (#159830)
Backport of https://github.com/elastic/kibana/pull/159517 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
608652a0a7
|
[8.8] [Security Solution] Improve rules exception flyout opening for the indices with huge amount of fields (#159216) (#159801)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] Improve rules exception flyout opening for the indices with huge amount of fields (#159216)](https://github.com/elastic/kibana/pull/159216) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2023-06-15T12:57:15Z","message":"[Security Solution] Improve rules exception flyout opening for the indices with huge amount of fields (#159216)\n\n## Summary\r\n\r\nOriginal ticket:\r\n[#158751](https://github.com/elastic/kibana/issues/158751)\r\n\r\nThese changes improve the rule's exceptions flyout opening experience.\r\nWe had a few complaints that it is very slow to open it and sometimes it\r\nthrows an exception about the limited response size.\r\n\r\nTo fix this, we decided to load extended field's data (conflicts and\r\nunmapped info) only when user selects some field instead of fetching\r\nthis data for all fields on flyout opening.\r\n\r\n## NOTES:\r\n\r\nAfter these changes we gonna do next steps related to fields loading\r\nwhen user creates/edits rule exceptions:\r\n1. We will call `_fields_for_wildcard` **WITHOUT**\r\n`include_unmapped=true` parameter to fetch all fields specs on exception\r\nflyout loading\r\n2. We will call `_fields_for_wildcard` **WITH** `include_unmapped=true`\r\nfor only one field when user selects it from the dropdown menu\r\n\r\nWith these changes we will improve slow exception flyout opening when\r\nuser has lots of fields which are unmapped in different indices. If for\r\nsome reason user has a lot of (thousands) conflicting fields around\r\nindices then the loading is still might be slow as the\r\n`_fields_for_wildcard` call will return conflicts information even\r\nwithout `include_unmapped=true` parameter.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"31b34771c5e6f710858a7f617bbca04537cf5c1b","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","ci:cloud-deploy","v8.9.0","Team:Detection Engine","v8.8.2"],"number":159216,"url":"https://github.com/elastic/kibana/pull/159216","mergeCommit":{"message":"[Security Solution] Improve rules exception flyout opening for the indices with huge amount of fields (#159216)\n\n## Summary\r\n\r\nOriginal ticket:\r\n[#158751](https://github.com/elastic/kibana/issues/158751)\r\n\r\nThese changes improve the rule's exceptions flyout opening experience.\r\nWe had a few complaints that it is very slow to open it and sometimes it\r\nthrows an exception about the limited response size.\r\n\r\nTo fix this, we decided to load extended field's data (conflicts and\r\nunmapped info) only when user selects some field instead of fetching\r\nthis data for all fields on flyout opening.\r\n\r\n## NOTES:\r\n\r\nAfter these changes we gonna do next steps related to fields loading\r\nwhen user creates/edits rule exceptions:\r\n1. We will call `_fields_for_wildcard` **WITHOUT**\r\n`include_unmapped=true` parameter to fetch all fields specs on exception\r\nflyout loading\r\n2. We will call `_fields_for_wildcard` **WITH** `include_unmapped=true`\r\nfor only one field when user selects it from the dropdown menu\r\n\r\nWith these changes we will improve slow exception flyout opening when\r\nuser has lots of fields which are unmapped in different indices. If for\r\nsome reason user has a lot of (thousands) conflicting fields around\r\nindices then the loading is still might be slow as the\r\n`_fields_for_wildcard` call will return conflicts information even\r\nwithout `include_unmapped=true` parameter.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"31b34771c5e6f710858a7f617bbca04537cf5c1b"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159216","number":159216,"mergeCommit":{"message":"[Security Solution] Improve rules exception flyout opening for the indices with huge amount of fields (#159216)\n\n## Summary\r\n\r\nOriginal ticket:\r\n[#158751](https://github.com/elastic/kibana/issues/158751)\r\n\r\nThese changes improve the rule's exceptions flyout opening experience.\r\nWe had a few complaints that it is very slow to open it and sometimes it\r\nthrows an exception about the limited response size.\r\n\r\nTo fix this, we decided to load extended field's data (conflicts and\r\nunmapped info) only when user selects some field instead of fetching\r\nthis data for all fields on flyout opening.\r\n\r\n## NOTES:\r\n\r\nAfter these changes we gonna do next steps related to fields loading\r\nwhen user creates/edits rule exceptions:\r\n1. We will call `_fields_for_wildcard` **WITHOUT**\r\n`include_unmapped=true` parameter to fetch all fields specs on exception\r\nflyout loading\r\n2. We will call `_fields_for_wildcard` **WITH** `include_unmapped=true`\r\nfor only one field when user selects it from the dropdown menu\r\n\r\nWith these changes we will improve slow exception flyout opening when\r\nuser has lots of fields which are unmapped in different indices. If for\r\nsome reason user has a lot of (thousands) conflicting fields around\r\nindices then the loading is still might be slow as the\r\n`_fields_for_wildcard` call will return conflicts information even\r\nwithout `include_unmapped=true` parameter.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"31b34771c5e6f710858a7f617bbca04537cf5c1b"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
Georgii Gorbachev
|
c65f896563
|
[8.8] [Security Solution] PoC of the Detection Engine health API (#157155) (#159717)
# Backport This will backport the following PR from `main` to `8.8`: - https://github.com/elastic/kibana/pull/157155 ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) |
||
|
Kibana Machine
|
858100d843
|
[8.8] [Security Solution] Fix timeline bug receiving dataProvider value as number (#159723) (#159775)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] Fix timeline bug receiving dataProvider value as number (#159723)](https://github.com/elastic/kibana/pull/159723) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2023-06-15T08:39:45Z","message":"[Security Solution] Fix timeline bug receiving dataProvider value as number (#159723)\n\n## Summary\r\n\r\nissue: https://github.com/elastic/kibana/issues/159720\r\nTimeline save request fails when the dataProvider value stored is a\r\nNumber type.\r\n\r\nAdding the dataProvider through timeline page itself does not cause the\r\nbug. it sets a string value even if the field type is `number`.\r\n\r\nThe bug only happens when using \"add to timeline\" CellAction on a field\r\nwith type `number`\r\n\r\n### Solution\r\n\r\nCast the dataProvider values to a `string` before adding them to the\r\ntimeline.","sha":"b9d6beb070ba60a533857616150c453cc7714237","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting","Team:Threat Hunting:Investigations","Team:Threat Hunting:Explore","v8.9.0","v8.8.2"],"number":159723,"url":"https://github.com/elastic/kibana/pull/159723","mergeCommit":{"message":"[Security Solution] Fix timeline bug receiving dataProvider value as number (#159723)\n\n## Summary\r\n\r\nissue: https://github.com/elastic/kibana/issues/159720\r\nTimeline save request fails when the dataProvider value stored is a\r\nNumber type.\r\n\r\nAdding the dataProvider through timeline page itself does not cause the\r\nbug. it sets a string value even if the field type is `number`.\r\n\r\nThe bug only happens when using \"add to timeline\" CellAction on a field\r\nwith type `number`\r\n\r\n### Solution\r\n\r\nCast the dataProvider values to a `string` before adding them to the\r\ntimeline.","sha":"b9d6beb070ba60a533857616150c453cc7714237"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159723","number":159723,"mergeCommit":{"message":"[Security Solution] Fix timeline bug receiving dataProvider value as number (#159723)\n\n## Summary\r\n\r\nissue: https://github.com/elastic/kibana/issues/159720\r\nTimeline save request fails when the dataProvider value stored is a\r\nNumber type.\r\n\r\nAdding the dataProvider through timeline page itself does not cause the\r\nbug. it sets a string value even if the field type is `number`.\r\n\r\nThe bug only happens when using \"add to timeline\" CellAction on a field\r\nwith type `number`\r\n\r\n### Solution\r\n\r\nCast the dataProvider values to a `string` before adding them to the\r\ntimeline.","sha":"b9d6beb070ba60a533857616150c453cc7714237"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
e3345b1f17
|
[8.8] [Cloud Security] [Bug Fix] Fix for status unprivileged issue (#159538) (#159604)
# Backport This will backport the following commits from `main` to `8.8`: - [[Cloud Security] [Bug Fix] Fix for status unprivileged issue (#159538)](https://github.com/elastic/kibana/pull/159538) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rickyanto Ang","email":"rickyangwyn@gmail.com"},"sourceCommit":{"committedDate":"2023-06-13T16:31:12Z","message":"[Cloud Security] [Bug Fix] Fix for status unprivileged issue (#159538)","sha":"935ae789dac57bab241a7aa13d21132ec1c48435","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Cloud Security","v8.9.0","v8.8.2"],"number":159538,"url":"https://github.com/elastic/kibana/pull/159538","mergeCommit":{"message":"[Cloud Security] [Bug Fix] Fix for status unprivileged issue (#159538)","sha":"935ae789dac57bab241a7aa13d21132ec1c48435"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159538","number":159538,"mergeCommit":{"message":"[Cloud Security] [Bug Fix] Fix for status unprivileged issue (#159538)","sha":"935ae789dac57bab241a7aa13d21132ec1c48435"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com> |
||
Jeramy Soucy
|
ad4ad3a96b
|
[8.8] [Failing Tests] Skips and comments tests failing with no_shard_available_action (#159039) (#159546)
# Backport This will backport the following commits from `main` to `8.8`: - [[Failing Tests] Skips and comments tests failing with no_shard_available_action (#159039)](https://github.com/elastic/kibana/pull/159039) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-06-06T07:11:22Z","message":"[Failing Tests] Skips and comments tests failing with no_shard_available_action (#159039)\n\n## Summary\r\n\r\nSkips several tests failing with the\r\n`no_shard_available_action_exception`. Also adds comments noting the\r\nrelated test failure issues and the [master issue being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee issue #158918 and PR #159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Saved Objects","Feature:Security/Spaces","skipped-test","release_note:skip","backport:prev-minor","v8.9.0"],"number":159039,"url":"https://github.com/elastic/kibana/pull/159039","mergeCommit":{"message":"[Failing Tests] Skips and comments tests failing with no_shard_available_action (#159039)\n\n## Summary\r\n\r\nSkips several tests failing with the\r\n`no_shard_available_action_exception`. Also adds comments noting the\r\nrelated test failure issues and the [master issue being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee issue #158918 and PR #159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159039","number":159039,"mergeCommit":{"message":"[Failing Tests] Skips and comments tests failing with no_shard_available_action (#159039)\n\n## Summary\r\n\r\nSkips several tests failing with the\r\n`no_shard_available_action_exception`. Also adds comments noting the\r\nrelated test failure issues and the [master issue being\r\ntracked](https://github.com/elastic/kibana/issues/158918).\r\n\r\nSee issue #158918 and PR #159002.","sha":"63bd0ba9f9cec244cac38affc2bc572ad5f6a6aa"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
842dad88bb
|
[8.8] [Infrastructure UI] Hosts View: Unified Search bar with auto-refresh enabled (#157011) (#159543)
# Backport This will backport the following commits from `main` to `8.8`: - [[Infrastructure UI] Hosts View: Unified Search bar with auto-refresh enabled (#157011)](https://github.com/elastic/kibana/pull/157011) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2023-06-13T08:07:58Z","message":"[Infrastructure UI] Hosts View: Unified Search bar with auto-refresh enabled (#157011)\n\nCloses #156690 \r\n\r\n## Summary\r\n\r\nThis PR adds a flag (`isAutoRefreshDisabled`) to disable the default\r\nauto-refresh option in the unified search.\r\n\r\n## Background\r\n\r\nThe auto refresh is added by default when using a unified search bar in\r\n[defaultOnRefreshChange](https://github.com/elastic/kibana/blob/main/src/plugins/unified_search/public/search_bar/create_search_bar.tsx/#L59)\r\nand it appeared on the host view page when currently the auto-refresh\r\noption is not supported.\r\n\r\n\r\n| with `isAutoRefreshDisabled` (true) | without `isAutoRefreshDisabled`\r\n(false/undefined) |\r\n| ------------------------------------ |\r\n-------------------------------------------------- |\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862888-63efdb13-6b07-41c2-abe8-88247c9c96e1.png\">\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862409-4f36ec6a-f274-4dae-960b-407ea30f330b.png\">\r\n|\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"77d864e4ff04027f800789259fd6c6194b51c59a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","backport:prev-minor","v8.9.0"],"number":157011,"url":"https://github.com/elastic/kibana/pull/157011","mergeCommit":{"message":"[Infrastructure UI] Hosts View: Unified Search bar with auto-refresh enabled (#157011)\n\nCloses #156690 \r\n\r\n## Summary\r\n\r\nThis PR adds a flag (`isAutoRefreshDisabled`) to disable the default\r\nauto-refresh option in the unified search.\r\n\r\n## Background\r\n\r\nThe auto refresh is added by default when using a unified search bar in\r\n[defaultOnRefreshChange](https://github.com/elastic/kibana/blob/main/src/plugins/unified_search/public/search_bar/create_search_bar.tsx/#L59)\r\nand it appeared on the host view page when currently the auto-refresh\r\noption is not supported.\r\n\r\n\r\n| with `isAutoRefreshDisabled` (true) | without `isAutoRefreshDisabled`\r\n(false/undefined) |\r\n| ------------------------------------ |\r\n-------------------------------------------------- |\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862888-63efdb13-6b07-41c2-abe8-88247c9c96e1.png\">\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862409-4f36ec6a-f274-4dae-960b-407ea30f330b.png\">\r\n|\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"77d864e4ff04027f800789259fd6c6194b51c59a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157011","number":157011,"mergeCommit":{"message":"[Infrastructure UI] Hosts View: Unified Search bar with auto-refresh enabled (#157011)\n\nCloses #156690 \r\n\r\n## Summary\r\n\r\nThis PR adds a flag (`isAutoRefreshDisabled`) to disable the default\r\nauto-refresh option in the unified search.\r\n\r\n## Background\r\n\r\nThe auto refresh is added by default when using a unified search bar in\r\n[defaultOnRefreshChange](https://github.com/elastic/kibana/blob/main/src/plugins/unified_search/public/search_bar/create_search_bar.tsx/#L59)\r\nand it appeared on the host view page when currently the auto-refresh\r\noption is not supported.\r\n\r\n\r\n| with `isAutoRefreshDisabled` (true) | without `isAutoRefreshDisabled`\r\n(false/undefined) |\r\n| ------------------------------------ |\r\n-------------------------------------------------- |\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862888-63efdb13-6b07-41c2-abe8-88247c9c96e1.png\">\r\n| <img width=\"200\" alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/14139027/236862409-4f36ec6a-f274-4dae-960b-407ea30f330b.png\">\r\n|\r\n\r\n---------\r\n\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"77d864e4ff04027f800789259fd6c6194b51c59a"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
|
Nathan Reese
|
3168766884
|
[8.8] [maps] fix geo line source not loaded unless maps application is opened (#159432) (#159532)
Manual backport of https://github.com/elastic/kibana/pull/159432 Needed to remove ES_DISTANCE_SOURCE reference since ES_DISTANCE_SOURCE does not exist on 8.8 branch --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d252e30ffa
|
[8.8] [Synthetics] adjust alert timing (#159511) (#159515)
# Backport This will backport the following commits from `main` to `8.8`: - [[Synthetics] adjust alert timing (#159511)](https://github.com/elastic/kibana/pull/159511) <!--- 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":"2023-06-12T19:08:53Z","message":"[Synthetics] adjust alert timing (#159511)\n\n### Release note\r\n\r\nResolves https://github.com/elastic/kibana/issues/158172\r\n\r\nFixes an issue where alerting on Synthetics monitors could sometimes\r\nbecome delayed.\r\n \r\n## Summary\r\nAdjust alerting timing to account for alerting framework delays.\r\n\r\nAlert executors do not fire perfectly on the specified interval (in our\r\ncase, every 1 minute). They are typically delayed a few seconds, be can\r\nespecially delayed if the customer does not have their alerting settings\r\nconfigured to scale and there is no CPU available to take on the\r\nscheduled task.\r\n\r\nThis PR accounts for small delays in the alerting framework, by\r\nsubtracting an additional 1 minute from the `from` value for our current\r\nstatus query.","sha":"d549500d3433b67cd5ec1f7aa60e866d4fb699c1","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:uptime","v8.9.0","v8.8.2"],"number":159511,"url":"https://github.com/elastic/kibana/pull/159511","mergeCommit":{"message":"[Synthetics] adjust alert timing (#159511)\n\n### Release note\r\n\r\nResolves https://github.com/elastic/kibana/issues/158172\r\n\r\nFixes an issue where alerting on Synthetics monitors could sometimes\r\nbecome delayed.\r\n \r\n## Summary\r\nAdjust alerting timing to account for alerting framework delays.\r\n\r\nAlert executors do not fire perfectly on the specified interval (in our\r\ncase, every 1 minute). They are typically delayed a few seconds, be can\r\nespecially delayed if the customer does not have their alerting settings\r\nconfigured to scale and there is no CPU available to take on the\r\nscheduled task.\r\n\r\nThis PR accounts for small delays in the alerting framework, by\r\nsubtracting an additional 1 minute from the `from` value for our current\r\nstatus query.","sha":"d549500d3433b67cd5ec1f7aa60e866d4fb699c1"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159511","number":159511,"mergeCommit":{"message":"[Synthetics] adjust alert timing (#159511)\n\n### Release note\r\n\r\nResolves https://github.com/elastic/kibana/issues/158172\r\n\r\nFixes an issue where alerting on Synthetics monitors could sometimes\r\nbecome delayed.\r\n \r\n## Summary\r\nAdjust alerting timing to account for alerting framework delays.\r\n\r\nAlert executors do not fire perfectly on the specified interval (in our\r\ncase, every 1 minute). They are typically delayed a few seconds, be can\r\nespecially delayed if the customer does not have their alerting settings\r\nconfigured to scale and there is no CPU available to take on the\r\nscheduled task.\r\n\r\nThis PR accounts for small delays in the alerting framework, by\r\nsubtracting an additional 1 minute from the `from` value for our current\r\nstatus query.","sha":"d549500d3433b67cd5ec1f7aa60e866d4fb699c1"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> |
||
Gergő Ábrahám
|
d185b71109
|
[8.8] [Security Solution][Testing] Improve policy related endpoint regression test coverage (#157412) (#159482)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution][Testing] Improve policy related endpoint regression test coverage (#157412)](https://github.com/elastic/kibana/pull/157412) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2023-05-30T09:21:14Z","message":"[Security Solution][Testing] Improve policy related endpoint regression test coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage for Policy Detail page related manual\r\ntests. See linked issue for test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases will be added in a\r\nseparate PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:Defend Workflows","v8.9.0"],"number":157412,"url":"https://github.com/elastic/kibana/pull/157412","mergeCommit":{"message":"[Security Solution][Testing] Improve policy related endpoint regression test coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage for Policy Detail page related manual\r\ntests. See linked issue for test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases will be added in a\r\nseparate PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157412","number":157412,"mergeCommit":{"message":"[Security Solution][Testing] Improve policy related endpoint regression test coverage (#157412)\n\n## Summary\r\n\r\n- Adds automated test coverage for Policy Detail page related manual\r\ntests. See linked issue for test cases.\r\n- fixes e2e alerts tests\r\n\r\n~Note: 3 more e2e test cases are coming soon.~\r\nUpdate: ready to review, the 3 e2e test cases will be added in a\r\nseparate PR.","sha":"771c8790d7f05bfde308506c4eb4174540057d11"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
639d1a3f6f
|
[8.8] [Infrastructure UI] Filter control re-rendering problem fix (#159320) (#159458)
# Backport This will backport the following commits from `main` to `8.8`: - [[Infrastructure UI] Filter control re-rendering problem fix (#159320)](https://github.com/elastic/kibana/pull/159320) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-12T12:30:23Z","message":"[Infrastructure UI] Filter control re-rendering problem fix (#159320)\n\nfixes https://github.com/elastic/kibana/issues/159317 \r\n\r\n## Summary\r\n\r\nThis PR fixes a problem in the utilization of the `ControlGroupRenderer`\r\ncomponent in the Hosts View. The problem originated from the need to\r\nmanually compare changes in the `filterPanel` object, to prevent the\r\npage from making duplicate requests\r\n\r\n\r\n |
||
|
Kibana Machine
|
72d429011a
|
[8.8] [RO] Incorrect Deletion of Webhook Actions in Kibana Rules (#159204) (#159443)
# Backport This will backport the following commits from `main` to `8.8`: - [[RO] Incorrect Deletion of Webhook Actions in Kibana Rules (#159204)](https://github.com/elastic/kibana/pull/159204) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-12T08:19:20Z","message":"[RO] Incorrect Deletion of Webhook Actions in Kibana Rules (#159204)\n\n## Summary\r\n\r\nFixes #158167\r\n\r\nThe issue occurred because we were using a number called \"index\" as the\r\nReact key prop. When we removed the first element, the second one took\r\nits place, but React still showed the removed element.\r\n\r\nTo fix this problem, we found a solution by using the uuid field that\r\neach action item has. We now generate it for each new action we create\r\nin the action form and use that as key\r\n\r\nI was told to add @pmuellr as you might know if we are missing something\r\n🙇\r\n\r\n### Test: why xpath selector?\r\n\r\nI had to use the xpath selector to fix a problem we had. The problem was\r\nbetween two actions we set up. They look the same, but the body content\r\nis the only different (I've attached a screenshot for more details).\r\n\r\nWe use a third party component for these actions. This component doesn't\r\nhave any \"value\" attribute and doesn't add anything besides the HTML\r\ntext. I tried to find other useful details but couldn't find any.\r\n\r\nThe problem comes up when we try to delete one of the actions. To fix\r\nit, we needed to check if that component was missing. We already have\r\ntools that can look for missing components, but they don't work with the\r\nxpath selector. So, I added a new function that can do this. Now, we can\r\nuse the xpath selector to look for missing components and fix the\r\nproblem\r\n \r\n<details>\r\n<summary>See Screenshot</summary>\r\n<img\r\nsrc=\" |
||
|
Kibana Machine
|
44c76823a3
|
[8.8] [DOCS] Conditional actions in rule open API specifications (#157951) (#159405)
# Backport This will backport the following commits from `main` to `8.8`: - [[DOCS] Conditional actions in rule open API specifications (#157951)](https://github.com/elastic/kibana/pull/157951) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-06-09T15:33:43Z","message":"[DOCS] Conditional actions in rule open API specifications (#157951)","sha":"b6a2611361170b6d80a845a22d080a073ee2e4ad","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.9.0","v8.8.2"],"number":157951,"url":"https://github.com/elastic/kibana/pull/157951","mergeCommit":{"message":"[DOCS] Conditional actions in rule open API specifications (#157951)","sha":"b6a2611361170b6d80a845a22d080a073ee2e4ad"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157951","number":157951,"mergeCommit":{"message":"[DOCS] Conditional actions in rule open API specifications (#157951)","sha":"b6a2611361170b6d80a845a22d080a073ee2e4ad"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
118a1be7f6
|
[8.8] [Enterprise Search] Fix wrong config value in postgresql (#159231) (#159249)
# Backport This will backport the following commits from `main` to `8.8`: - [[Enterprise Search] Fix wrong config value in postgresql (#159231)](https://github.com/elastic/kibana/pull/159231) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-07T17:25:31Z","message":"[Enterprise Search] Fix wrong config value in postgresql (#159231)\n\n## Summary\r\n\r\nThis fixes the PostgreSQL config being broken due to a mislabeled config\r\nkey.","sha":"031c23743972d38eb39cc742f3f046f96c196f39","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:EnterpriseSearch","v8.9.0","v8.8.2"],"number":159231,"url":"https://github.com/elastic/kibana/pull/159231","mergeCommit":{"message":"[Enterprise Search] Fix wrong config value in postgresql (#159231)\n\n## Summary\r\n\r\nThis fixes the PostgreSQL config being broken due to a mislabeled config\r\nkey.","sha":"031c23743972d38eb39cc742f3f046f96c196f39"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159231","number":159231,"mergeCommit":{"message":"[Enterprise Search] Fix wrong config value in postgresql (#159231)\n\n## Summary\r\n\r\nThis fixes the PostgreSQL config being broken due to a mislabeled config\r\nkey.","sha":"031c23743972d38eb39cc742f3f046f96c196f39"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
7bf0394252
|
[8.8] Fix global search crash on missing tag (#159196) (#159379)
# Backport This will backport the following commits from `main` to `8.8`: - [Fix global search crash on missing tag (#159196)](https://github.com/elastic/kibana/pull/159196) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2023-06-09T10:27:41Z","message":"Fix global search crash on missing tag (#159196)\n\n## Summary\r\n\r\nClose https://github.com/elastic/kibana/issues/157682,\r\nhttps://github.com/elastic/kibana/issues/159152\r\n\r\nFixes global search component crashing on the missing tag. Ideally this\r\nshould never happen as data is inconsistent, but we also shouldn't just\r\ncrash the component.\r\n\r\nAdds a console warning in case hitting this edge case.","sha":"aa4a5e5cc4459be3929f02d63ebb679448a531bd","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Navigational Search","Team:SharedUX","backport:prev-minor","v8.9.0"],"number":159196,"url":"https://github.com/elastic/kibana/pull/159196","mergeCommit":{"message":"Fix global search crash on missing tag (#159196)\n\n## Summary\r\n\r\nClose https://github.com/elastic/kibana/issues/157682,\r\nhttps://github.com/elastic/kibana/issues/159152\r\n\r\nFixes global search component crashing on the missing tag. Ideally this\r\nshould never happen as data is inconsistent, but we also shouldn't just\r\ncrash the component.\r\n\r\nAdds a console warning in case hitting this edge case.","sha":"aa4a5e5cc4459be3929f02d63ebb679448a531bd"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159196","number":159196,"mergeCommit":{"message":"Fix global search crash on missing tag (#159196)\n\n## Summary\r\n\r\nClose https://github.com/elastic/kibana/issues/157682,\r\nhttps://github.com/elastic/kibana/issues/159152\r\n\r\nFixes global search component crashing on the missing tag. Ideally this\r\nshould never happen as data is inconsistent, but we also shouldn't just\r\ncrash the component.\r\n\r\nAdds a console warning in case hitting this edge case.","sha":"aa4a5e5cc4459be3929f02d63ebb679448a531bd"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <anton.dosov@elastic.co> |
||
|
Kibana Machine
|
c6b775b4d8
|
[8.8] [Infrastructure UI] Remove sensitive info from telemetry payload (#159314) (#159366)
# Backport This will backport the following commits from `main` to `8.8`: - [[Infrastructure UI] Remove sensitive info from telemetry payload (#159314)](https://github.com/elastic/kibana/pull/159314) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-09T07:58:08Z","message":"[Infrastructure UI] Remove sensitive info from telemetry payload (#159314)\n\n## Summary\r\n\r\nThis PR changes the `Hosts View Query Submitted` telemetry event\r\npayload, stopping Kibana from sending potentially sensitive information\r\nto analytics services.\r\n\r\nAn example of the new payload:\r\n\r\n```ts\r\n{\r\n control_filter_fields: ['host.os.name'],\r\n filter_fields: ['host.name', 'cloud.provider'],\r\n interval: 'interval(now-1h)',\r\n with_query: false,\r\n limit: 100,\r\n}\r\n```\r\n\r\nInstead of sending filter values, we'll pass only the field names.\r\nExcept for the query bar, because it's to complicated to parse and\r\nretrieve that information\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3bc3a362caa38427a849b2555ca0ad711bb870f1","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics UI","Team:Infra Monitoring UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":159314,"url":"https://github.com/elastic/kibana/pull/159314","mergeCommit":{"message":"[Infrastructure UI] Remove sensitive info from telemetry payload (#159314)\n\n## Summary\r\n\r\nThis PR changes the `Hosts View Query Submitted` telemetry event\r\npayload, stopping Kibana from sending potentially sensitive information\r\nto analytics services.\r\n\r\nAn example of the new payload:\r\n\r\n```ts\r\n{\r\n control_filter_fields: ['host.os.name'],\r\n filter_fields: ['host.name', 'cloud.provider'],\r\n interval: 'interval(now-1h)',\r\n with_query: false,\r\n limit: 100,\r\n}\r\n```\r\n\r\nInstead of sending filter values, we'll pass only the field names.\r\nExcept for the query bar, because it's to complicated to parse and\r\nretrieve that information\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3bc3a362caa38427a849b2555ca0ad711bb870f1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159314","number":159314,"mergeCommit":{"message":"[Infrastructure UI] Remove sensitive info from telemetry payload (#159314)\n\n## Summary\r\n\r\nThis PR changes the `Hosts View Query Submitted` telemetry event\r\npayload, stopping Kibana from sending potentially sensitive information\r\nto analytics services.\r\n\r\nAn example of the new payload:\r\n\r\n```ts\r\n{\r\n control_filter_fields: ['host.os.name'],\r\n filter_fields: ['host.name', 'cloud.provider'],\r\n interval: 'interval(now-1h)',\r\n with_query: false,\r\n limit: 100,\r\n}\r\n```\r\n\r\nInstead of sending filter values, we'll pass only the field names.\r\nExcept for the query bar, because it's to complicated to parse and\r\nretrieve that information\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"3bc3a362caa38427a849b2555ca0ad711bb870f1"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
Tiago Costa
|
7fbe1d5daf
|
chore(NA): bump version to 8.8.2 (#159304)
Usually bump from 8.8.1 to 8.8.2 |
||
|
Kibana Machine
|
20bb4c7739
|
[8.8] [Fleet] Do not query cold/frozen indices when querying for agent metrics (#159307) (#159323)
# Backport This will backport the following commits from `main` to `8.8`: - [[Fleet] Do not query cold/frozen indices when querying for agent metrics (#159307)](https://github.com/elastic/kibana/pull/159307) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2023-06-08T15:03:30Z","message":"[Fleet] Do not query cold/frozen indices when querying for agent metrics (#159307)","sha":"48e783972a1e1f73527d6285a724a89ffadf48e0","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v8.9.0","v8.8.2"],"number":159307,"url":"https://github.com/elastic/kibana/pull/159307","mergeCommit":{"message":"[Fleet] Do not query cold/frozen indices when querying for agent metrics (#159307)","sha":"48e783972a1e1f73527d6285a724a89ffadf48e0"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159307","number":159307,"mergeCommit":{"message":"[Fleet] Do not query cold/frozen indices when querying for agent metrics (#159307)","sha":"48e783972a1e1f73527d6285a724a89ffadf48e0"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
97bb42c9cc
|
[8.8] [Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565) (#159331)
# Backport This will backport the following commits from `main` to `8.8`: - [[Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565)](https://github.com/elastic/kibana/pull/158565) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"GitStart","email":"1501599+gitstart@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-08T15:57:03Z","message":"[Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565)\n\n## What does this PR do?\r\n* It doesn't allows the user to pick the same date and time in the\r\nschedule component.\r\n\r\n## Issue References\r\n* Client: https://github.com/elastic/kibana/issues/157865\r\n\r\n## Video/Screenshot Demo \r\n\r\n###### FIX:\r\nhttps://www.loom.com/share/fc4a43eba71f485384621ecec457ce1a\r\n\r\n---\r\nThis code was written and reviewed by GitStart Community. Growing great\r\nengineers, one PR at a time.\r\n\r\nCo-authored-by: KlingerMatheus <klinger.matheus@gitstart.dev>\r\nCo-authored-by: gitstart_bot <gitstart_bot@users.noreply.github.com>","sha":"d9eff3fd84c7eb9da0f3d3e1106d6054b3a4cad7","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","💝community","v8.9.0","v8.8.2"],"number":158565,"url":"https://github.com/elastic/kibana/pull/158565","mergeCommit":{"message":"[Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565)\n\n## What does this PR do?\r\n* It doesn't allows the user to pick the same date and time in the\r\nschedule component.\r\n\r\n## Issue References\r\n* Client: https://github.com/elastic/kibana/issues/157865\r\n\r\n## Video/Screenshot Demo \r\n\r\n###### FIX:\r\nhttps://www.loom.com/share/fc4a43eba71f485384621ecec457ce1a\r\n\r\n---\r\nThis code was written and reviewed by GitStart Community. Growing great\r\nengineers, one PR at a time.\r\n\r\nCo-authored-by: KlingerMatheus <klinger.matheus@gitstart.dev>\r\nCo-authored-by: gitstart_bot <gitstart_bot@users.noreply.github.com>","sha":"d9eff3fd84c7eb9da0f3d3e1106d6054b3a4cad7"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158565","number":158565,"mergeCommit":{"message":"[Security Solution] Able to add Same Start Time and End Time in Schedule for Snooze Notifications of Rule (#158565)\n\n## What does this PR do?\r\n* It doesn't allows the user to pick the same date and time in the\r\nschedule component.\r\n\r\n## Issue References\r\n* Client: https://github.com/elastic/kibana/issues/157865\r\n\r\n## Video/Screenshot Demo \r\n\r\n###### FIX:\r\nhttps://www.loom.com/share/fc4a43eba71f485384621ecec457ce1a\r\n\r\n---\r\nThis code was written and reviewed by GitStart Community. Growing great\r\nengineers, one PR at a time.\r\n\r\nCo-authored-by: KlingerMatheus <klinger.matheus@gitstart.dev>\r\nCo-authored-by: gitstart_bot <gitstart_bot@users.noreply.github.com>","sha":"d9eff3fd84c7eb9da0f3d3e1106d6054b3a4cad7"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: GitStart <1501599+gitstart@users.noreply.github.com> |
||
|
Kibana Machine
|
16e8c8f48b
|
[8.8] [Fleet] removed package upload API enterprise license requirement (#159280) (#159321)
# Backport This will backport the following commits from `main` to `8.8`: - [[Fleet] removed package upload API enterprise license requirement (#159280)](https://github.com/elastic/kibana/pull/159280) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-08T14:51:54Z","message":"[Fleet] removed package upload API enterprise license requirement (#159280)\n\n## Summary\r\n\r\nThe package upload API was made GA, and it had a leftover enterprise\r\nlicense requirement from the time it was only intended for devs. See\r\nhttps://github.com/elastic/kibana/pull/79653\r\nThis pr removes that requirement.","sha":"b8619ec216bebbcfdd27f34c6ef632e5fc2456be","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.8.0","v8.9.0"],"number":159280,"url":"https://github.com/elastic/kibana/pull/159280","mergeCommit":{"message":"[Fleet] removed package upload API enterprise license requirement (#159280)\n\n## Summary\r\n\r\nThe package upload API was made GA, and it had a leftover enterprise\r\nlicense requirement from the time it was only intended for devs. See\r\nhttps://github.com/elastic/kibana/pull/79653\r\nThis pr removes that requirement.","sha":"b8619ec216bebbcfdd27f34c6ef632e5fc2456be"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159280","number":159280,"mergeCommit":{"message":"[Fleet] removed package upload API enterprise license requirement (#159280)\n\n## Summary\r\n\r\nThe package upload API was made GA, and it had a leftover enterprise\r\nlicense requirement from the time it was only intended for devs. See\r\nhttps://github.com/elastic/kibana/pull/79653\r\nThis pr removes that requirement.","sha":"b8619ec216bebbcfdd27f34c6ef632e5fc2456be"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
f3a3b6cbac
|
[8.8] [Fleet] Datastreams API should not query cold or frozen nodes (#159253) (#159282)
# Backport This will backport the following commits from `main` to `8.8`: - [[Fleet] Datastreams API should not query cold or frozen nodes (#159253)](https://github.com/elastic/kibana/pull/159253) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2023-06-08T07:36:52Z","message":"[Fleet] Datastreams API should not query cold or frozen nodes (#159253)\n\n## Summary\r\n\r\nResolve #157778 \r\n\r\nThe Fleet API to retrieve datastreams has some perfomance issue that PR\r\ntry to mitigate that by:\r\n* Improve the performance of the datastream API to not query cold or\r\nfrozen index.\r\n* the package policy editor UI to only query that datastream API if the\r\npackage is an input package.\r\n\r\n## Tests\r\n\r\nManual:\r\n* You can check that the datastream API is not called if the package is\r\nnot an input package on create integration policy page\r\n* You can check for input package we still have the dataset properties\r\npopulated with existing datastreams on create integration policy page\r\n\r\n\r\nAutomated:\r\nTBD\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7540ee39b88e7d16153d5482591768b9bb691d37","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","ci:cloud-deploy","v8.9.0","v8.8.2"],"number":159253,"url":"https://github.com/elastic/kibana/pull/159253","mergeCommit":{"message":"[Fleet] Datastreams API should not query cold or frozen nodes (#159253)\n\n## Summary\r\n\r\nResolve #157778 \r\n\r\nThe Fleet API to retrieve datastreams has some perfomance issue that PR\r\ntry to mitigate that by:\r\n* Improve the performance of the datastream API to not query cold or\r\nfrozen index.\r\n* the package policy editor UI to only query that datastream API if the\r\npackage is an input package.\r\n\r\n## Tests\r\n\r\nManual:\r\n* You can check that the datastream API is not called if the package is\r\nnot an input package on create integration policy page\r\n* You can check for input package we still have the dataset properties\r\npopulated with existing datastreams on create integration policy page\r\n\r\n\r\nAutomated:\r\nTBD\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7540ee39b88e7d16153d5482591768b9bb691d37"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159253","number":159253,"mergeCommit":{"message":"[Fleet] Datastreams API should not query cold or frozen nodes (#159253)\n\n## Summary\r\n\r\nResolve #157778 \r\n\r\nThe Fleet API to retrieve datastreams has some perfomance issue that PR\r\ntry to mitigate that by:\r\n* Improve the performance of the datastream API to not query cold or\r\nfrozen index.\r\n* the package policy editor UI to only query that datastream API if the\r\npackage is an input package.\r\n\r\n## Tests\r\n\r\nManual:\r\n* You can check that the datastream API is not called if the package is\r\nnot an input package on create integration policy page\r\n* You can check for input package we still have the dataset properties\r\npopulated with existing datastreams on create integration policy page\r\n\r\n\r\nAutomated:\r\nTBD\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7540ee39b88e7d16153d5482591768b9bb691d37"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
Carlos Crespo
|
87ad9bc562
|
[8.8] [Infrastructure UI] Hosts view flaky tests fix (#158884) (#159286)
# Backport This will backport the following commits from `main` to `8.8`: - [[Infrastructure UI] Hosts view flaky tests fix (#158884)](https://github.com/elastic/kibana/pull/158884) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-08T08:09:59Z","message":"[Infrastructure UI] Hosts view flaky tests fix (#158884)\n\ncloses [#157721](https://github.com/elastic/kibana/issues/157721)\r\n\r\n## Summary\r\n\r\nMore changes in an attempt to fix the flakiness of the hosts view tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2365\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ff30aa604d86a79e7d59ae03c37c1f05e70cbe0","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Infra Monitoring UI","release_note:skip","backport:prev-minor","v8.9.0"],"number":158884,"url":"https://github.com/elastic/kibana/pull/158884","mergeCommit":{"message":"[Infrastructure UI] Hosts view flaky tests fix (#158884)\n\ncloses [#157721](https://github.com/elastic/kibana/issues/157721)\r\n\r\n## Summary\r\n\r\nMore changes in an attempt to fix the flakiness of the hosts view tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2365\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ff30aa604d86a79e7d59ae03c37c1f05e70cbe0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158884","number":158884,"mergeCommit":{"message":"[Infrastructure UI] Hosts view flaky tests fix (#158884)\n\ncloses [#157721](https://github.com/elastic/kibana/issues/157721)\r\n\r\n## Summary\r\n\r\nMore changes in an attempt to fix the flakiness of the hosts view tests\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2365\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"8ff30aa604d86a79e7d59ae03c37c1f05e70cbe0"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
1b018afbe1
|
[8.8] [APM] Don't use service tx metrics on transaction detail page (#159085) (#159281)
# Backport This will backport the following commits from `main` to `8.8`: - [[APM] Don't use service tx metrics on transaction detail page (#159085)](https://github.com/elastic/kibana/pull/159085) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2023-06-08T07:20:13Z","message":"[APM] Don't use service tx metrics on transaction detail page (#159085)","sha":"74102e592f5193e9566b16d921931c2dc2a67a86","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:APM","v8.9.0","v8.8.2"],"number":159085,"url":"https://github.com/elastic/kibana/pull/159085","mergeCommit":{"message":"[APM] Don't use service tx metrics on transaction detail page (#159085)","sha":"74102e592f5193e9566b16d921931c2dc2a67a86"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159085","number":159085,"mergeCommit":{"message":"[APM] Don't use service tx metrics on transaction detail page (#159085)","sha":"74102e592f5193e9566b16d921931c2dc2a67a86"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> |
||
|
Kibana Machine
|
651819e581
|
[8.8] [Enterprise Search][Search Application]Modify indices page warning and remove conflict when all indices are unavailable (#159147) (#159263)
# Backport This will backport the following commits from `main` to `8.8`: - [[Enterprise Search][Search Application]Modify indices page warning and remove conflict when all indices are unavailable (#159147)](https://github.com/elastic/kibana/pull/159147) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saarika Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-07T19:46:57Z","message":"[Enterprise Search][Search Application]Modify indices page warning and remove conflict when all indices are unavailable (#159147)\n\n## Summary\r\nWhen all the indices are deleted, add warning in Search application and should not show conflict in Schema page\r\n\r\n\r\n### Screen Recording\r\n\r\n |
||
|
Kibana Machine
|
1c487ed6ee
|
[8.8] [Enterprise Search] Validate inference pipeline name on next (#159151) (#159261)
# Backport This will backport the following commits from `main` to `8.8`: - [[Enterprise Search] Validate inference pipeline name on next (#159151)](https://github.com/elastic/kibana/pull/159151) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rodney Norris","email":"rodney.norris@elastic.co"},"sourceCommit":{"committedDate":"2023-06-07T19:42:43Z","message":"[Enterprise Search] Validate inference pipeline name on next (#159151)\n\n## Summary\r\n\r\nUpdated the configuration step transition to check if the pipeline name\r\nis currently in use and add a form error if it is.\r\n\r\nThe UX trade-off I made here is to change the step and then take the\r\nuser back if the name is unavailable, which results in a slight blip.\r\nThis was preferable to having to store the state and disabling\r\ninteraction while we make the API call IMO.\r\n\r\n### Screenshots\r\n\r\n\r\n |
||
Dominique Clarke
|
410f7c7f5f
|
[8.8] [Synthetics] adjust synthetics api routes to use /internal prefix (#159135) (#159220)
# Backport This will backport the following commits from `main` to `8.8`: - [[Synthetics] adjust synthetics api routes to use /internal prefix (#159135)](https://github.com/elastic/kibana/pull/159135) <!--- 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":"2023-06-06T16:55:38Z","message":"[Synthetics] adjust synthetics api routes to use /internal prefix (#159135)\n\n## Summary\r\n\r\nAdds missing `/internal` prefixes to synthetics api routes","sha":"f48b742be10d1501383ba63f47777c9245f40a8b","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.9.0","v8.8.2"],"number":159135,"url":"https://github.com/elastic/kibana/pull/159135","mergeCommit":{"message":"[Synthetics] adjust synthetics api routes to use /internal prefix (#159135)\n\n## Summary\r\n\r\nAdds missing `/internal` prefixes to synthetics api routes","sha":"f48b742be10d1501383ba63f47777c9245f40a8b"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159135","number":159135,"mergeCommit":{"message":"[Synthetics] adjust synthetics api routes to use /internal prefix (#159135)\n\n## Summary\r\n\r\nAdds missing `/internal` prefixes to synthetics api routes","sha":"f48b742be10d1501383ba63f47777c9245f40a8b"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
6e1438f52e
|
[8.8] [Fleet] fixing issue of returning output api key (#159179) (#159212)
# Backport This will backport the following commits from `main` to `8.8`: - [[Fleet] fixing issue of returning output api key (#159179)](https://github.com/elastic/kibana/pull/159179) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-07T14:03:17Z","message":"[Fleet] fixing issue of returning output api key (#159179)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/ingest-dev/issues/1944\r\nAdded mapping of known fields instead of returning all fields from\r\n`.fleet-agents` in agents API.\r\n\r\nTo verify:\r\n- create an agent policy with a new output\r\n- enroll an agent to it\r\n- call agents API and verify that the outputs section doesn't have api\r\nkey\r\n\r\n```\r\nGET kbn:/api/fleet/agents\r\n{\r\n \"items\": [\r\n {\r\n \"id\": \"504b3006-52df-46a6-b7db-f3dc67aca7ac\",\r\n \"type\": \"PERMANENT\",\r\n \"active\": true,\r\n \"enrolled_at\": \"2023-06-07T07:45:30Z\",\r\n ...\r\n \"outputs\": {\r\n \"68233290-0486-11ee-97a3-c3856dd800f7\": {\r\n \"api_key_id\": \"En_RlIgBn_WkCEINb-pQ\",\r\n \"type\": \"elasticsearch\"\r\n },\r\n \"default\": {\r\n \"api_key_id\": \"FH_RlIgBn_WkCEINcOrY\",\r\n \"type\": \"elasticsearch\"\r\n }\r\n },\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e52e889503204c5a0f3b8abe680feae9d956d807","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","v8.9.0","v8.8.2"],"number":159179,"url":"https://github.com/elastic/kibana/pull/159179","mergeCommit":{"message":"[Fleet] fixing issue of returning output api key (#159179)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/ingest-dev/issues/1944\r\nAdded mapping of known fields instead of returning all fields from\r\n`.fleet-agents` in agents API.\r\n\r\nTo verify:\r\n- create an agent policy with a new output\r\n- enroll an agent to it\r\n- call agents API and verify that the outputs section doesn't have api\r\nkey\r\n\r\n```\r\nGET kbn:/api/fleet/agents\r\n{\r\n \"items\": [\r\n {\r\n \"id\": \"504b3006-52df-46a6-b7db-f3dc67aca7ac\",\r\n \"type\": \"PERMANENT\",\r\n \"active\": true,\r\n \"enrolled_at\": \"2023-06-07T07:45:30Z\",\r\n ...\r\n \"outputs\": {\r\n \"68233290-0486-11ee-97a3-c3856dd800f7\": {\r\n \"api_key_id\": \"En_RlIgBn_WkCEINb-pQ\",\r\n \"type\": \"elasticsearch\"\r\n },\r\n \"default\": {\r\n \"api_key_id\": \"FH_RlIgBn_WkCEINcOrY\",\r\n \"type\": \"elasticsearch\"\r\n }\r\n },\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e52e889503204c5a0f3b8abe680feae9d956d807"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/159179","number":159179,"mergeCommit":{"message":"[Fleet] fixing issue of returning output api key (#159179)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/ingest-dev/issues/1944\r\nAdded mapping of known fields instead of returning all fields from\r\n`.fleet-agents` in agents API.\r\n\r\nTo verify:\r\n- create an agent policy with a new output\r\n- enroll an agent to it\r\n- call agents API and verify that the outputs section doesn't have api\r\nkey\r\n\r\n```\r\nGET kbn:/api/fleet/agents\r\n{\r\n \"items\": [\r\n {\r\n \"id\": \"504b3006-52df-46a6-b7db-f3dc67aca7ac\",\r\n \"type\": \"PERMANENT\",\r\n \"active\": true,\r\n \"enrolled_at\": \"2023-06-07T07:45:30Z\",\r\n ...\r\n \"outputs\": {\r\n \"68233290-0486-11ee-97a3-c3856dd800f7\": {\r\n \"api_key_id\": \"En_RlIgBn_WkCEINb-pQ\",\r\n \"type\": \"elasticsearch\"\r\n },\r\n \"default\": {\r\n \"api_key_id\": \"FH_RlIgBn_WkCEINcOrY\",\r\n \"type\": \"elasticsearch\"\r\n }\r\n },\r\n```\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e52e889503204c5a0f3b8abe680feae9d956d807"}},{"branch":"8.8","label":"v8.8.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> Co-authored-by: Julia Bardi <julia.bardi@elastic.co> |
||
|
Kibana Machine
|
346d54c33e
|
[8.8] [Enterprise Search] Add service type to connector config code block (#159120) (#159189)
# Backport This will backport the following commits from `main` to `8.8`: - [[Enterprise Search] Add service type to connector config code block (#159120)](https://github.com/elastic/kibana/pull/159120) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-06-07T09:52:42Z","message":"[Enterprise Search] Add service type to connector config code block (#159120)\n\n## Summary\r\nThis adds the necessary service type to the code block in the connector\r\nconfiguration screen.\r\n\r\n<img width=\"797\" alt=\"Screenshot 2023-06-06 at 15 05 15\"\r\nsrc=\" |
||
Pablo Machado
|
eab6c512fe
|
[8.8] Fix hover Action showing for zero Count on D&R Dashboard (#158902) (#159108)
# Backport This will backport the following commits from `main` to `8.8`: - [Fix hover Action showing for zero Count on D&R Dashboard (#158902)](https://github.com/elastic/kibana/pull/158902) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2023-06-02T11:42:15Z","message":"Fix hover Action showing for zero Count on D&R Dashboard (#158902)\n\nissue: https://github.com/elastic/kibana/issues/158057\r\n## Summary\r\n\r\nRemove hover actions from the table when the count of alerts is zero.\r\n\r\n**BEFORE**\r\n\r\n
