mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
80344 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
577c5dece4
|
[8.x] [Docs] 8.15.5 release notes (#201050) (#201088)
# Backport This will backport the following commits from `main` to `8.x`: - [[Docs] 8.15.5 release notes (#201050)](https://github.com/elastic/kibana/pull/201050) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"wajihaparvez","email":"wajiha.parvez@elastic.co"},"sourceCommit":{"committedDate":"2024-11-21T09:06:29Z","message":"[Docs] 8.15.5 release notes (#201050)\n\n## Summary\r\n\r\nAdding a section for 8.15.5 release notes.\r\n\r\nCloses: [#567](https://github.com/elastic/platform-docs-team/issues/567)","sha":"7f880cce09abeb1b28bf46a3caa7bcb2958ceda4","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","v8.15.0","v8.16.0","backport:version","v8.17.0","v8.18.0","v8.15.5"],"title":"[Docs] 8.15.5 release notes","number":201050,"url":"https://github.com/elastic/kibana/pull/201050","mergeCommit":{"message":"[Docs] 8.15.5 release notes (#201050)\n\n## Summary\r\n\r\nAdding a section for 8.15.5 release notes.\r\n\r\nCloses: [#567](https://github.com/elastic/platform-docs-team/issues/567)","sha":"7f880cce09abeb1b28bf46a3caa7bcb2958ceda4"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","8.16","8.17","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201050","number":201050,"mergeCommit":{"message":"[Docs] 8.15.5 release notes (#201050)\n\n## Summary\r\n\r\nAdding a section for 8.15.5 release notes.\r\n\r\nCloses: [#567](https://github.com/elastic/platform-docs-team/issues/567)","sha":"7f880cce09abeb1b28bf46a3caa7bcb2958ceda4"}},{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co> |
||
Tiago Costa
|
deed753848
|
chore(NA): bump version to 8.18.0 (#201064)
Usually bump from 8.17.0 to 8.18.0 |
||
|
Kibana Machine
|
10db504da8
|
[8.x] Preconfigured Endpoints in Semantic_text field (#200659) (#201063)
# Backport This will backport the following commits from `main` to `8.x`: - [Preconfigured Endpoints in Semantic_text field (#200659)](https://github.com/elastic/kibana/pull/200659) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Samiul Monir","email":"150824886+Samiul-TheSoccerFan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-21T00:48:56Z","message":"Preconfigured Endpoints in Semantic_text field (#200659)\n\n## Summary\r\n\r\n1. Removed default endpoints from the `Select inference id` dropdown\r\n2. Linked preconfigured endpoints properly with fields.\r\n3. Added support to remove `index` errors regarding models.\r\n\r\n### ESS:\r\n\r\nhttps://github.com/user-attachments/assets/4c13f5b3-a00a-4aac-a1c2-ca94e5b2c293\r\n\r\n### ES3\r\n\r\n\r\nhttps://github.com/user-attachments/assets/83f1bd74-0973-4225-907b-89e7c372fa5f\r\n\r\n### ingest and data with the preconfigured endpoint:\r\n```\r\nPOST /search-jmo0/_doc\r\n{\r\n \"content\": \"park_rocky-mountain\"\r\n}\r\n```\r\n```\r\nGET /search-jmo0/_search\r\n```\r\n\r\nwill return something like this:\r\n\r\n```\r\n{\r\n \"took\": 3,\r\n \"timed_out\": false,\r\n \"_shards\": {\r\n \"total\": 3,\r\n \"successful\": 3,\r\n \"skipped\": 0,\r\n \"failed\": 0\r\n },\r\n \"hits\": {\r\n \"total\": {\r\n \"value\": 1,\r\n \"relation\": \"eq\"\r\n },\r\n \"max_score\": 1,\r\n \"hits\": [\r\n {\r\n \"_index\": \"search-jmo0\",\r\n \"_id\": \"712LRpMBqdKCj6yG9iFJ\",\r\n \"_score\": 1,\r\n \"_source\": {\r\n \"openai_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \"my-test-1-openai-endpoint\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 1536,\r\n \"similarity\": \"dot_product\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"elser_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".elser-2-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"sparse_embedding\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": {...}\r\n }\r\n ]\r\n }\r\n },\r\n \"e5_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".multilingual-e5-small-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 384,\r\n \"similarity\": \"cosine\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"content\": \"park_rocky-mountain\"\r\n }\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"052f527ee7acf3393a0b9bfa2ad2f41de29015a9","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","ci:project-deploy-elasticsearch","backport:version","v8.17.0"],"title":"Preconfigured Endpoints in Semantic_text field","number":200659,"url":"https://github.com/elastic/kibana/pull/200659","mergeCommit":{"message":"Preconfigured Endpoints in Semantic_text field (#200659)\n\n## Summary\r\n\r\n1. Removed default endpoints from the `Select inference id` dropdown\r\n2. Linked preconfigured endpoints properly with fields.\r\n3. Added support to remove `index` errors regarding models.\r\n\r\n### ESS:\r\n\r\nhttps://github.com/user-attachments/assets/4c13f5b3-a00a-4aac-a1c2-ca94e5b2c293\r\n\r\n### ES3\r\n\r\n\r\nhttps://github.com/user-attachments/assets/83f1bd74-0973-4225-907b-89e7c372fa5f\r\n\r\n### ingest and data with the preconfigured endpoint:\r\n```\r\nPOST /search-jmo0/_doc\r\n{\r\n \"content\": \"park_rocky-mountain\"\r\n}\r\n```\r\n```\r\nGET /search-jmo0/_search\r\n```\r\n\r\nwill return something like this:\r\n\r\n```\r\n{\r\n \"took\": 3,\r\n \"timed_out\": false,\r\n \"_shards\": {\r\n \"total\": 3,\r\n \"successful\": 3,\r\n \"skipped\": 0,\r\n \"failed\": 0\r\n },\r\n \"hits\": {\r\n \"total\": {\r\n \"value\": 1,\r\n \"relation\": \"eq\"\r\n },\r\n \"max_score\": 1,\r\n \"hits\": [\r\n {\r\n \"_index\": \"search-jmo0\",\r\n \"_id\": \"712LRpMBqdKCj6yG9iFJ\",\r\n \"_score\": 1,\r\n \"_source\": {\r\n \"openai_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \"my-test-1-openai-endpoint\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 1536,\r\n \"similarity\": \"dot_product\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"elser_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".elser-2-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"sparse_embedding\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": {...}\r\n }\r\n ]\r\n }\r\n },\r\n \"e5_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".multilingual-e5-small-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 384,\r\n \"similarity\": \"cosine\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"content\": \"park_rocky-mountain\"\r\n }\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"052f527ee7acf3393a0b9bfa2ad2f41de29015a9"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200659","number":200659,"mergeCommit":{"message":"Preconfigured Endpoints in Semantic_text field (#200659)\n\n## Summary\r\n\r\n1. Removed default endpoints from the `Select inference id` dropdown\r\n2. Linked preconfigured endpoints properly with fields.\r\n3. Added support to remove `index` errors regarding models.\r\n\r\n### ESS:\r\n\r\nhttps://github.com/user-attachments/assets/4c13f5b3-a00a-4aac-a1c2-ca94e5b2c293\r\n\r\n### ES3\r\n\r\n\r\nhttps://github.com/user-attachments/assets/83f1bd74-0973-4225-907b-89e7c372fa5f\r\n\r\n### ingest and data with the preconfigured endpoint:\r\n```\r\nPOST /search-jmo0/_doc\r\n{\r\n \"content\": \"park_rocky-mountain\"\r\n}\r\n```\r\n```\r\nGET /search-jmo0/_search\r\n```\r\n\r\nwill return something like this:\r\n\r\n```\r\n{\r\n \"took\": 3,\r\n \"timed_out\": false,\r\n \"_shards\": {\r\n \"total\": 3,\r\n \"successful\": 3,\r\n \"skipped\": 0,\r\n \"failed\": 0\r\n },\r\n \"hits\": {\r\n \"total\": {\r\n \"value\": 1,\r\n \"relation\": \"eq\"\r\n },\r\n \"max_score\": 1,\r\n \"hits\": [\r\n {\r\n \"_index\": \"search-jmo0\",\r\n \"_id\": \"712LRpMBqdKCj6yG9iFJ\",\r\n \"_score\": 1,\r\n \"_source\": {\r\n \"openai_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \"my-test-1-openai-endpoint\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 1536,\r\n \"similarity\": \"dot_product\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"elser_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".elser-2-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"sparse_embedding\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": {...}\r\n }\r\n ]\r\n }\r\n },\r\n \"e5_semantic_text\": {\r\n \"inference\": {\r\n \"inference_id\": \".multilingual-e5-small-elasticsearch\",\r\n \"model_settings\": {\r\n \"task_type\": \"text_embedding\",\r\n \"dimensions\": 384,\r\n \"similarity\": \"cosine\",\r\n \"element_type\": \"float\"\r\n },\r\n \"chunks\": [\r\n {\r\n \"text\": \"park_rocky-mountain\",\r\n \"embeddings\": [...]\r\n }\r\n ]\r\n }\r\n },\r\n \"content\": \"park_rocky-mountain\"\r\n }\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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":"052f527ee7acf3393a0b9bfa2ad2f41de29015a9"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Samiul Monir <150824886+Samiul-TheSoccerFan@users.noreply.github.com> |
||
|
Kibana Machine
|
82d34c804d
|
[8.x] [data usage] add line series for totals (#201038) (#201057)
# Backport This will backport the following commits from `main` to `8.x`: - [[data usage] add line series for totals (#201038)](https://github.com/elastic/kibana/pull/201038) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-21T00:03:59Z","message":"[data usage] add line series for totals (#201038)\n\n## Summary\r\n\r\nadd line series for totals\r\n\r\n<img width=\"2294\" alt=\"Screenshot 2024-11-20 at 3 04 11 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/275214b9-a1c5-45a9-ae1e-d42c4ef31cb9\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"d39d0d67a516abd5f4be63577f58c833962f27e6","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:build-serverless-image"],"title":"[data usage] add line series for totals","number":201038,"url":"https://github.com/elastic/kibana/pull/201038","mergeCommit":{"message":"[data usage] add line series for totals (#201038)\n\n## Summary\r\n\r\nadd line series for totals\r\n\r\n<img width=\"2294\" alt=\"Screenshot 2024-11-20 at 3 04 11 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/275214b9-a1c5-45a9-ae1e-d42c4ef31cb9\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"d39d0d67a516abd5f4be63577f58c833962f27e6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201038","number":201038,"mergeCommit":{"message":"[data usage] add line series for totals (#201038)\n\n## Summary\r\n\r\nadd line series for totals\r\n\r\n<img width=\"2294\" alt=\"Screenshot 2024-11-20 at 3 04 11 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/275214b9-a1c5-45a9-ae1e-d42c4ef31cb9\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"d39d0d67a516abd5f4be63577f58c833962f27e6"}}]}] BACKPORT--> Co-authored-by: Sandra G <neptunian@users.noreply.github.com> |
||
|
Kibana Machine
|
9dc5e87b34
|
[8.x] deps: Bump ironbank version to 9.5 (#200863) (#201052)
# Backport This will backport the following commits from `main` to `8.x`: - [deps: Bump ironbank version to 9.5 (#200863)](https://github.com/elastic/kibana/pull/200863) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"github-actions[bot]","email":"41898282+github-actions[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T23:35:19Z","message":"deps: Bump ironbank version to 9.5 (#200863)\n\n<Actions>\r\n<action\r\nid=\"ad27da7f660d61c82c61599e0e6945827ced1590f4bf36a5f74db07e99c04215\">\r\n <h3>deps: Bump ironbank version</h3>\r\n<details\r\nid=\"21fe544f0edf8039d0165187f8204a62da22d72e50fa57839d823beb83c0df2e\">\r\n <summary>deps(ironbank): Bump ubi version to 9.5</summary>\r\n<p>changed lines [7] of file\r\n"/tmp/updatecli/github/elastic/kibana/src/dev/build/tasks/os_packages/docker_generator/templates/ironbank/Dockerfile"</p>\r\n </details>\r\n<details\r\nid=\"99cabf4d5a2b44b2d93b4c18590b8ccd5df3002e8d9d506c038c9011e8e93734\">\r\n <summary>deps(ironbank): Bump ubi version to 9.5</summary>\r\n<p>change detected:
	* key "$.args.BASE_TAG" updated\r\nfrom "\\"9.4\\"" to "\\"9.5\\"", in file\r\n"src/dev/build/tasks/os_packages/docker_generator/templates/ironbank/hardening_manifest.yaml"</p>\r\n </details>\r\n<a\r\nhref=\" |
||
|
Kibana Machine
|
0892dd42f7
|
[8.x] [Security Solution] Fix flaky test for multiline diff algorithm (#201019) (#201044)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Fix flaky test for multiline diff algorithm (#201019)](https://github.com/elastic/kibana/pull/201019) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-20T21:12:02Z","message":"[Security Solution] Fix flaky test for multiline diff algorithm (#201019)\n\n**Fixes: https://github.com/elastic/kibana/issues/201014**\r\n**Related to:** https://github.com/elastic/kibana/pull/199388\r\n\r\n## Summary\r\n\r\nThis PR increases the threshold (time limit) value for the test by 2x\r\nfrom 500 ms to 1000 ms. Hope it should be enough to eliminate flakiness\r\non CI.","sha":"c9e782030a768da471616d626096eb325e12c38c","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.17.0","v8.16.1"],"title":"[Security Solution] Fix flaky test for multiline diff algorithm","number":201019,"url":"https://github.com/elastic/kibana/pull/201019","mergeCommit":{"message":"[Security Solution] Fix flaky test for multiline diff algorithm (#201019)\n\n**Fixes: https://github.com/elastic/kibana/issues/201014**\r\n**Related to:** https://github.com/elastic/kibana/pull/199388\r\n\r\n## Summary\r\n\r\nThis PR increases the threshold (time limit) value for the test by 2x\r\nfrom 500 ms to 1000 ms. Hope it should be enough to eliminate flakiness\r\non CI.","sha":"c9e782030a768da471616d626096eb325e12c38c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201019","number":201019,"mergeCommit":{"message":"[Security Solution] Fix flaky test for multiline diff algorithm (#201019)\n\n**Fixes: https://github.com/elastic/kibana/issues/201014**\r\n**Related to:** https://github.com/elastic/kibana/pull/199388\r\n\r\n## Summary\r\n\r\nThis PR increases the threshold (time limit) value for the test by 2x\r\nfrom 500 ms to 1000 ms. Hope it should be enough to eliminate flakiness\r\non CI.","sha":"c9e782030a768da471616d626096eb325e12c38c"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> |
||
|
Kibana Machine
|
121d94ff08
|
[8.x] fix: kibana dev server not restarting for external plugin #171260 (#198246) (#201040)
# Backport This will backport the following commits from `main` to `8.x`: - [fix: kibana dev server not restarting for external plugin #171260 (#198246)](https://github.com/elastic/kibana/pull/198246) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jordan McAlpine","email":"128929391+mickalpine@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T20:24:58Z","message":"fix: kibana dev server not restarting for external plugin #171260 (#198246)\n\n## Summary\r\n\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n### Checklist\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#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n## Release note\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n---------\r\n\r\nCo-authored-by: Brad White <Ikuni17@users.noreply.github.com>","sha":"83b282a63a3748a07a0d9e69f2cafa44b9439af7","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","💝community","v9.0.0","backport:prev-minor"],"title":"fix: kibana dev server not restarting for external plugin #171260","number":198246,"url":"https://github.com/elastic/kibana/pull/198246","mergeCommit":{"message":"fix: kibana dev server not restarting for external plugin #171260 (#198246)\n\n## Summary\r\n\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n### Checklist\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#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n## Release note\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n---------\r\n\r\nCo-authored-by: Brad White <Ikuni17@users.noreply.github.com>","sha":"83b282a63a3748a07a0d9e69f2cafa44b9439af7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198246","number":198246,"mergeCommit":{"message":"fix: kibana dev server not restarting for external plugin #171260 (#198246)\n\n## Summary\r\n\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n### Checklist\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#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n## Release note\r\nFixes #171260 the Kibana dev server not restarting during external\r\nplugin development for server side code.\r\n\r\n---------\r\n\r\nCo-authored-by: Brad White <Ikuni17@users.noreply.github.com>","sha":"83b282a63a3748a07a0d9e69f2cafa44b9439af7"}}]}] BACKPORT--> Co-authored-by: Jordan McAlpine <128929391+mickalpine@users.noreply.github.com> |
||
Jen Huang
|
fd6dc18b3a
|
[8.x] [UII] Expose advanced file logging config in UI (#200274) (#201021)
# Backport This will backport the following commits from `main` to `8.x`: - [[UII] Expose advanced file logging config in UI (#200274)](https://github.com/elastic/kibana/pull/200274) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T17:41:50Z","message":"[UII] Expose advanced file logging config in UI (#200274)\n\n## Summary\r\n\r\nResolves [#192237](https://github.com/elastic/kibana/issues/192237).\r\nThis PR exposes the following Elastic Agent file logging configuration\r\noptions in the agent policy advanced settings UI:\r\n\r\n```\r\nagent.logging.to_files\r\nagent.logging.files.rotateeverybytes \r\nagent.logging.files.keepfiles\r\nagent.logging.files.interval\r\n```\r\n\r\n<img width=\"1237\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8de9023c-29a0-4ecf-803a-d8c0c4b87616\">\r\n\r\nThis PR also does some clean up on the default values for all these\r\nconfigured advanced settings so that when user has not touched them, the\r\ndefault values do not get written into the agent policy saved object.\r\n[More info\r\nhere](https://github.com/elastic/kibana/pull/200274#discussion_r1849142612).\r\n\r\nIt also fixes adds missing response schemas for the advanced settings.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0aa63a7eccea009174db782c57577226ea252bff","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Fleet","v9.0.0","release_note:feature","backport:prev-minor"],"number":200274,"url":"https://github.com/elastic/kibana/pull/200274","mergeCommit":{"message":"[UII] Expose advanced file logging config in UI (#200274)\n\n## Summary\r\n\r\nResolves [#192237](https://github.com/elastic/kibana/issues/192237).\r\nThis PR exposes the following Elastic Agent file logging configuration\r\noptions in the agent policy advanced settings UI:\r\n\r\n```\r\nagent.logging.to_files\r\nagent.logging.files.rotateeverybytes \r\nagent.logging.files.keepfiles\r\nagent.logging.files.interval\r\n```\r\n\r\n<img width=\"1237\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8de9023c-29a0-4ecf-803a-d8c0c4b87616\">\r\n\r\nThis PR also does some clean up on the default values for all these\r\nconfigured advanced settings so that when user has not touched them, the\r\ndefault values do not get written into the agent policy saved object.\r\n[More info\r\nhere](https://github.com/elastic/kibana/pull/200274#discussion_r1849142612).\r\n\r\nIt also fixes adds missing response schemas for the advanced settings.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0aa63a7eccea009174db782c57577226ea252bff"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200274","number":200274,"mergeCommit":{"message":"[UII] Expose advanced file logging config in UI (#200274)\n\n## Summary\r\n\r\nResolves [#192237](https://github.com/elastic/kibana/issues/192237).\r\nThis PR exposes the following Elastic Agent file logging configuration\r\noptions in the agent policy advanced settings UI:\r\n\r\n```\r\nagent.logging.to_files\r\nagent.logging.files.rotateeverybytes \r\nagent.logging.files.keepfiles\r\nagent.logging.files.interval\r\n```\r\n\r\n<img width=\"1237\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/8de9023c-29a0-4ecf-803a-d8c0c4b87616\">\r\n\r\nThis PR also does some clean up on the default values for all these\r\nconfigured advanced settings so that when user has not touched them, the\r\ndefault values do not get written into the agent policy saved object.\r\n[More info\r\nhere](https://github.com/elastic/kibana/pull/200274#discussion_r1849142612).\r\n\r\nIt also fixes adds missing response schemas for the advanced settings.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0aa63a7eccea009174db782c57577226ea252bff"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
058ea381ff
|
[8.x] Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 32099b9 (main) (#199974) (#201039)
# Backport This will backport the following commits from `main` to `8.x`: - [Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 32099b9 (main) (#199974)](https://github.com/elastic/kibana/pull/199974) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T20:06:19Z","message":"Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 32099b9 (main) (#199974)\n\nThis PR contains the following updates:\r\n\r\n| Package | Update | Change |\r\n|---|---|---|\r\n| docker.elastic.co/wolfi/chainguard-base | digest | ` |
||
|
Kibana Machine
|
a52ec627a8
|
[8.x] [Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate (#200820) (#201036)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate (#200820)](https://github.com/elastic/kibana/pull/200820) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T19:53:40Z","message":"[Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables the Threat Hunting Investigations api integration tests\r\nto the release quality gate.\r\n\r\nhttps://github.com/elastic/kibana/issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.17.0"],"title":"[Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate","number":200820,"url":"https://github.com/elastic/kibana/pull/200820","mergeCommit":{"message":"[Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables the Threat Hunting Investigations api integration tests\r\nto the release quality gate.\r\n\r\nhttps://github.com/elastic/kibana/issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200820","number":200820,"mergeCommit":{"message":"[Security Solution] - enable running threat hunting investigations api integration tests in QA quality gate (#200820)\n\n## Summary\r\n\r\nThis PR enables the Threat Hunting Investigations api integration tests\r\nto the release quality gate.\r\n\r\nhttps://github.com/elastic/kibana/issues/181687","sha":"cb02853d14bfbfb4946b2e725777290e56aac696"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
ab77df1e1e
|
[8.x] [Docs] Update feature privilege docs to reflect new route authorization (#201017) (#201042)
# Backport This will backport the following commits from `main` to `8.x`: - [[Docs] Update feature privilege docs to reflect new route authorization (#201017)](https://github.com/elastic/kibana/pull/201017) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T20:52:58Z","message":"[Docs] Update feature privilege docs to reflect new route authorization (#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on Feature privileges to reflect changes\r\nto Route Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52 02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49 26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v9.0.0","docs","DevDocs","backport:prev-minor","v8.17.0"],"title":"[Docs] Update feature privilege docs to reflect new route authorization","number":201017,"url":"https://github.com/elastic/kibana/pull/201017","mergeCommit":{"message":"[Docs] Update feature privilege docs to reflect new route authorization (#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on Feature privileges to reflect changes\r\nto Route Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52 02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49 26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201017","number":201017,"mergeCommit":{"message":"[Docs] Update feature privilege docs to reflect new route authorization (#201017)\n\n## Summary\r\n\r\nUpdates developer documentation on Feature privileges to reflect changes\r\nto Route Authorization.\r\n\r\n\r\n### Screenshots\r\nBefore\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 52 02\"\r\nsrc=\"https://github.com/user-attachments/assets/0bb01bd0-e41a-48ee-bcaf-bd4119037f1b\">\r\n\r\nAfter\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 18 49 26\"\r\nsrc=\"https://github.com/user-attachments/assets/2d5712ce-c277-4ecd-831e-750df8309933\">\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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","sha":"4ffdb35b14c1a19cf0ade972b198a6e6e7f06ba5"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com> |
||
|
Kibana Machine
|
29209cbfbf
|
[8.x] [inference] add pre-bound versions of `chatComplete` and `output` APIs (#200568) (#201028)
# Backport This will backport the following commits from `main` to `8.x`: - [[inference] add pre-bound versions of `chatComplete` and `output` APIs (#200568)](https://github.com/elastic/kibana/pull/200568) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pierre Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T19:09:11Z","message":"[inference] add pre-bound versions of `chatComplete` and `output` APIs (#200568)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/199084\r\n\r\nIntroduce pre-bound versions of the inference APIs.\r\n\r\nAccessing the bound versions can be done using the same `getClient` API,\r\nvia an additional `bindTo` parameter:\r\n\r\n**without bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({ request });\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n**with bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({\r\n request,\r\n bindTo: {\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n }\r\n});\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n*Note: this is only done for the server-side, as there isn't much value\r\nin scoping APIs on the browser side in my opinion*\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3c8f0777f4a4563824d0fb1f545524bf4346e3a2","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:AI Infra","v8.17.0"],"title":"[inference] add pre-bound versions of `chatComplete` and `output` APIs","number":200568,"url":"https://github.com/elastic/kibana/pull/200568","mergeCommit":{"message":"[inference] add pre-bound versions of `chatComplete` and `output` APIs (#200568)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/199084\r\n\r\nIntroduce pre-bound versions of the inference APIs.\r\n\r\nAccessing the bound versions can be done using the same `getClient` API,\r\nvia an additional `bindTo` parameter:\r\n\r\n**without bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({ request });\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n**with bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({\r\n request,\r\n bindTo: {\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n }\r\n});\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n*Note: this is only done for the server-side, as there isn't much value\r\nin scoping APIs on the browser side in my opinion*\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3c8f0777f4a4563824d0fb1f545524bf4346e3a2"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200568","number":200568,"mergeCommit":{"message":"[inference] add pre-bound versions of `chatComplete` and `output` APIs (#200568)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/199084\r\n\r\nIntroduce pre-bound versions of the inference APIs.\r\n\r\nAccessing the bound versions can be done using the same `getClient` API,\r\nvia an additional `bindTo` parameter:\r\n\r\n**without bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({ request });\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n**with bindings**\r\n```ts\r\nconst inferenceClient = myStartDeps.inference.getClient({\r\n request,\r\n bindTo: {\r\n connectorId: 'my-connector-id',\r\n functionCalling: 'simulated',\r\n }\r\n});\r\n\r\nconst chatResponse = inferenceClient.chatComplete({\r\n messages: [{ role: MessageRole.User, content: 'Do something' }],\r\n});\r\n```\r\n\r\n*Note: this is only done for the server-side, as there isn't much value\r\nin scoping APIs on the browser side in my opinion*\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3c8f0777f4a4563824d0fb1f545524bf4346e3a2"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pierre Gayvallet <pierre.gayvallet@elastic.co> |
||
|
Kibana Machine
|
63934e8d32
|
[8.x] [Data Usage] remove autoops.api.tls.ca config (#200808) (#201026)
# Backport This will backport the following commits from `main` to `8.x`: - [[Data Usage] remove autoops.api.tls.ca config (#200808)](https://github.com/elastic/kibana/pull/200808) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T18:59:45Z","message":"[Data Usage] remove autoops.api.tls.ca config (#200808)\n\n## Summary\r\n\r\nRemove unused `autoops.api.tls.ca` config.\r\n\r\n\r\n### Checklist\r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\nCo-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>","sha":"5d1a30aae997fe0a4fa91f20ba391266668deb11","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:build-serverless-image"],"title":"[Data Usage] remove autoops.api.tls.ca config","number":200808,"url":"https://github.com/elastic/kibana/pull/200808","mergeCommit":{"message":"[Data Usage] remove autoops.api.tls.ca config (#200808)\n\n## Summary\r\n\r\nRemove unused `autoops.api.tls.ca` config.\r\n\r\n\r\n### Checklist\r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\nCo-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>","sha":"5d1a30aae997fe0a4fa91f20ba391266668deb11"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200808","number":200808,"mergeCommit":{"message":"[Data Usage] remove autoops.api.tls.ca config (#200808)\n\n## Summary\r\n\r\nRemove unused `autoops.api.tls.ca` config.\r\n\r\n\r\n### Checklist\r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] 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 was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...\r\n\r\nCo-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com>","sha":"5d1a30aae997fe0a4fa91f20ba391266668deb11"}}]}] BACKPORT--> Co-authored-by: Sandra G <neptunian@users.noreply.github.com> |
||
|
Kibana Machine
|
dbe6c7b73d
|
[8.x] [Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang (#200476) (#201025)
# Backport This will backport the following commits from `main` to `8.x`: - [[Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang (#200476)](https://github.com/elastic/kibana/pull/200476) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T18:52:47Z","message":"[Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang (#200476)\n\n## Summary\r\n\r\nThis PR mitigates an issue where the `has_es_data` check can hang when\r\nsome remote clusters are unresponsive, leaving users stuck in a loading\r\nstate in some apps (e.g. Discover and Dashboard) until the request times\r\nout. There are two main changes that help mitigate this issue:\r\n- The `resolve/cluster` request in the `has_es_data` endpoint has been\r\nsplit into two requests -- one for local data first, then another for\r\nremote data second. In cases where remote clusters are unresponsive but\r\nthere is data available in the local cluster, the remote check is never\r\nperformed and the check completes quickly. This likely resolves the\r\nmajority of cases and is also likely faster in general than checking\r\nboth local and remote clusters in a single request.\r\n- In cases where there is no local data and the remote `resolve/cluster`\r\nrequest hangs, a new `data_views.hasEsDataTimeout` config has been added\r\nto `kibana.yml` (defaults to 5 seconds) to abort the request after a\r\nshort delay. This scenario is handled in the front end by displaying an\r\nerror toast to the user informing them of the issue, and assuming there\r\nis data available to avoid blocking them. When this occurs, a warning is\r\nalso logged to the Kibana server logs.\r\n\r\n\r\n\r\nFixes #200280.\r\n\r\n### Notes\r\n- Modifying the existing version of the `has_es_data` endpoint in this\r\nway should be backward compatible since the behaviour should remain\r\nunchanged from before when the client and server versions don't match\r\n(please validate if this seems accurate during review).\r\n- For a long term fix, the ES team is investigating the issue with\r\n`resolve/cluster` and will aim to have it behave like `resolve/index`,\r\nwhich fails quickly when remote clusters are unresponsive. They may also\r\nimplement other mitigations like a configurable timeout in ES:\r\nhttps://github.com/elastic/elasticsearch/issues/114020. The purpose of\r\nthis PR is to provide an immediate solution in Kibana that mitigates the\r\nissue as much as possible.\r\n- If ES ends up providing another performant method for checking if\r\nindices exist instead of `resolve/cluster`, Kibana should migrate to\r\nthat. More details in\r\nhttps://github.com/elastic/elasticsearch/issues/112307.\r\n\r\n### Testing notes\r\n\r\nTo reproduce the issue locally, follow these steps:\r\n- Follow [these\r\ninstructions](https://gist.github.com/lukasolson/d0861aa3e6ee476ac8dd7189ed476756)\r\nto set up a local CCS environment.\r\n- Stop the remote cluster process.\r\n- Use Netcat on the remote cluster port to listen to requests but not\r\nrespond (e.g. on macOS: `nc -l 9600`), simulating an unresponsive\r\ncluster. See https://github.com/elastic/elasticsearch/issues/32678 for\r\nmore context.\r\n- Navigate to Discover and observe that the `has_es_data` request hangs.\r\nWhen testing in this PR branch, the request will only wait for 5 seconds\r\nbefore assuming data exists and displaying a toast.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[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- [ ] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"96fd4b682b77f6c1d6d1c6ab0742462d9e9d2589","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:DataDiscovery","backport:prev-major"],"title":"[Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang","number":200476,"url":"https://github.com/elastic/kibana/pull/200476","mergeCommit":{"message":"[Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang (#200476)\n\n## Summary\r\n\r\nThis PR mitigates an issue where the `has_es_data` check can hang when\r\nsome remote clusters are unresponsive, leaving users stuck in a loading\r\nstate in some apps (e.g. Discover and Dashboard) until the request times\r\nout. There are two main changes that help mitigate this issue:\r\n- The `resolve/cluster` request in the `has_es_data` endpoint has been\r\nsplit into two requests -- one for local data first, then another for\r\nremote data second. In cases where remote clusters are unresponsive but\r\nthere is data available in the local cluster, the remote check is never\r\nperformed and the check completes quickly. This likely resolves the\r\nmajority of cases and is also likely faster in general than checking\r\nboth local and remote clusters in a single request.\r\n- In cases where there is no local data and the remote `resolve/cluster`\r\nrequest hangs, a new `data_views.hasEsDataTimeout` config has been added\r\nto `kibana.yml` (defaults to 5 seconds) to abort the request after a\r\nshort delay. This scenario is handled in the front end by displaying an\r\nerror toast to the user informing them of the issue, and assuming there\r\nis data available to avoid blocking them. When this occurs, a warning is\r\nalso logged to the Kibana server logs.\r\n\r\n\r\n\r\nFixes #200280.\r\n\r\n### Notes\r\n- Modifying the existing version of the `has_es_data` endpoint in this\r\nway should be backward compatible since the behaviour should remain\r\nunchanged from before when the client and server versions don't match\r\n(please validate if this seems accurate during review).\r\n- For a long term fix, the ES team is investigating the issue with\r\n`resolve/cluster` and will aim to have it behave like `resolve/index`,\r\nwhich fails quickly when remote clusters are unresponsive. They may also\r\nimplement other mitigations like a configurable timeout in ES:\r\nhttps://github.com/elastic/elasticsearch/issues/114020. The purpose of\r\nthis PR is to provide an immediate solution in Kibana that mitigates the\r\nissue as much as possible.\r\n- If ES ends up providing another performant method for checking if\r\nindices exist instead of `resolve/cluster`, Kibana should migrate to\r\nthat. More details in\r\nhttps://github.com/elastic/elasticsearch/issues/112307.\r\n\r\n### Testing notes\r\n\r\nTo reproduce the issue locally, follow these steps:\r\n- Follow [these\r\ninstructions](https://gist.github.com/lukasolson/d0861aa3e6ee476ac8dd7189ed476756)\r\nto set up a local CCS environment.\r\n- Stop the remote cluster process.\r\n- Use Netcat on the remote cluster port to listen to requests but not\r\nrespond (e.g. on macOS: `nc -l 9600`), simulating an unresponsive\r\ncluster. See https://github.com/elastic/elasticsearch/issues/32678 for\r\nmore context.\r\n- Navigate to Discover and observe that the `has_es_data` request hangs.\r\nWhen testing in this PR branch, the request will only wait for 5 seconds\r\nbefore assuming data exists and displaying a toast.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[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- [ ] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"96fd4b682b77f6c1d6d1c6ab0742462d9e9d2589"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200476","number":200476,"mergeCommit":{"message":"[Data Views] Mitigate issue where `has_es_data` check can cause Kibana to hang (#200476)\n\n## Summary\r\n\r\nThis PR mitigates an issue where the `has_es_data` check can hang when\r\nsome remote clusters are unresponsive, leaving users stuck in a loading\r\nstate in some apps (e.g. Discover and Dashboard) until the request times\r\nout. There are two main changes that help mitigate this issue:\r\n- The `resolve/cluster` request in the `has_es_data` endpoint has been\r\nsplit into two requests -- one for local data first, then another for\r\nremote data second. In cases where remote clusters are unresponsive but\r\nthere is data available in the local cluster, the remote check is never\r\nperformed and the check completes quickly. This likely resolves the\r\nmajority of cases and is also likely faster in general than checking\r\nboth local and remote clusters in a single request.\r\n- In cases where there is no local data and the remote `resolve/cluster`\r\nrequest hangs, a new `data_views.hasEsDataTimeout` config has been added\r\nto `kibana.yml` (defaults to 5 seconds) to abort the request after a\r\nshort delay. This scenario is handled in the front end by displaying an\r\nerror toast to the user informing them of the issue, and assuming there\r\nis data available to avoid blocking them. When this occurs, a warning is\r\nalso logged to the Kibana server logs.\r\n\r\n\r\n\r\nFixes #200280.\r\n\r\n### Notes\r\n- Modifying the existing version of the `has_es_data` endpoint in this\r\nway should be backward compatible since the behaviour should remain\r\nunchanged from before when the client and server versions don't match\r\n(please validate if this seems accurate during review).\r\n- For a long term fix, the ES team is investigating the issue with\r\n`resolve/cluster` and will aim to have it behave like `resolve/index`,\r\nwhich fails quickly when remote clusters are unresponsive. They may also\r\nimplement other mitigations like a configurable timeout in ES:\r\nhttps://github.com/elastic/elasticsearch/issues/114020. The purpose of\r\nthis PR is to provide an immediate solution in Kibana that mitigates the\r\nissue as much as possible.\r\n- If ES ends up providing another performant method for checking if\r\nindices exist instead of `resolve/cluster`, Kibana should migrate to\r\nthat. More details in\r\nhttps://github.com/elastic/elasticsearch/issues/112307.\r\n\r\n### Testing notes\r\n\r\nTo reproduce the issue locally, follow these steps:\r\n- Follow [these\r\ninstructions](https://gist.github.com/lukasolson/d0861aa3e6ee476ac8dd7189ed476756)\r\nto set up a local CCS environment.\r\n- Stop the remote cluster process.\r\n- Use Netcat on the remote cluster port to listen to requests but not\r\nrespond (e.g. on macOS: `nc -l 9600`), simulating an unresponsive\r\ncluster. See https://github.com/elastic/elasticsearch/issues/32678 for\r\nmore context.\r\n- Navigate to Discover and observe that the `has_es_data` request hangs.\r\nWhen testing in this PR branch, the request will only wait for 5 seconds\r\nbefore assuming data exists and displaying a toast.\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[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- [ ] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"96fd4b682b77f6c1d6d1c6ab0742462d9e9d2589"}}]}] BACKPORT--> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
20cbae54df | skip failing test suite (#191707) | ||
|
Tiago Costa
|
a80d1c25c3
|
skip flaky suite (#197985) | ||
|
Kibana Machine
|
18d4a5af7f
|
[8.x] update docs on automatically generating a report (#191067) (#201034)
# Backport This will backport the following commits from `main` to `8.x`: - [update docs on automatically generating a report (#191067)](https://github.com/elastic/kibana/pull/191067) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eyo O. Eyo","email":"7893459+eokoneyo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T19:49:37Z","message":"update docs on automatically generating a report (#191067)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/188640\r\n\r\n\r\nUpdates steps in docs for automatically generating a report to match the\r\nUI expectation especially that the share experience got an overhaul\r\nsince 8.14.\r\n\r\n<!--\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n-->\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"3648a33adf952dac283f64b471e5903898f78b4e","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor","v8.16.0","Feature:Reporting:Framework","v8.17.0"],"title":"update docs on automatically generating a report","number":191067,"url":"https://github.com/elastic/kibana/pull/191067","mergeCommit":{"message":"update docs on automatically generating a report (#191067)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/188640\r\n\r\n\r\nUpdates steps in docs for automatically generating a report to match the\r\nUI expectation especially that the share experience got an overhaul\r\nsince 8.14.\r\n\r\n<!--\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n-->\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"3648a33adf952dac283f64b471e5903898f78b4e"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191067","number":191067,"mergeCommit":{"message":"update docs on automatically generating a report (#191067)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/188640\r\n\r\n\r\nUpdates steps in docs for automatically generating a report to match the\r\nUI expectation especially that the share experience got an overhaul\r\nsince 8.14.\r\n\r\n<!--\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n-->\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>","sha":"3648a33adf952dac283f64b471e5903898f78b4e"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Eyo O. Eyo <7893459+eokoneyo@users.noreply.github.com> |
||
|
Kibana Machine
|
e2c0c94b52
|
[8.x] [Discover] Unskip Discover-Lens functional test suite (#200687) (#201013)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Unskip Discover-Lens functional test suite (#200687)](https://github.com/elastic/kibana/pull/200687) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"ankertal@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T17:38:05Z","message":"[Discover] Unskip Discover-Lens functional test suite (#200687)\n\nCatching an invalid state of properties propagated to the UnifiedHistogram which is using the Lens embeddable in Discover, that causes a rendering error when e.g. ad hoc data views are being edited. Therefore the skipped testview can be unskipped.","sha":"e082cd1dfaa79c6fdfc5d7f1d2842b6ca0a5db6c","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-major"],"title":"[Discover] Unskip Discover-Lens functional test suite ","number":200687,"url":"https://github.com/elastic/kibana/pull/200687","mergeCommit":{"message":"[Discover] Unskip Discover-Lens functional test suite (#200687)\n\nCatching an invalid state of properties propagated to the UnifiedHistogram which is using the Lens embeddable in Discover, that causes a rendering error when e.g. ad hoc data views are being edited. Therefore the skipped testview can be unskipped.","sha":"e082cd1dfaa79c6fdfc5d7f1d2842b6ca0a5db6c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200687","number":200687,"mergeCommit":{"message":"[Discover] Unskip Discover-Lens functional test suite (#200687)\n\nCatching an invalid state of properties propagated to the UnifiedHistogram which is using the Lens embeddable in Discover, that causes a rendering error when e.g. ad hoc data views are being edited. Therefore the skipped testview can be unskipped.","sha":"e082cd1dfaa79c6fdfc5d7f1d2842b6ca0a5db6c"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <ankertal@gmail.com> |
||
|
Kibana Machine
|
9b137edd77
|
[8.x] Search rename to elasticsearch (#200774) (#201011)
# Backport This will backport the following commits from `main` to `8.x`: - [Search rename to elasticsearch (#200774)](https://github.com/elastic/kibana/pull/200774) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-20T17:14:26Z","message":"Search rename to elasticsearch (#200774)\n\nThis renames the Search solution to Elasticsearch to fit with our\r\nrebranding efforts.","sha":"0cafc7be9eadc97bfe9d93e169a2b25e55c1afa1","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:version","v8.17.0","v8.18.0"],"title":"Search rename to elasticsearch","number":200774,"url":"https://github.com/elastic/kibana/pull/200774","mergeCommit":{"message":"Search rename to elasticsearch (#200774)\n\nThis renames the Search solution to Elasticsearch to fit with our\r\nrebranding efforts.","sha":"0cafc7be9eadc97bfe9d93e169a2b25e55c1afa1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200774","number":200774,"mergeCommit":{"message":"Search rename to elasticsearch (#200774)\n\nThis renames the Search solution to Elasticsearch to fit with our\r\nrebranding efforts.","sha":"0cafc7be9eadc97bfe9d93e169a2b25e55c1afa1"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
63f1de7e1b
|
[8.x] [inference] add support for openAI native stream token count (#200745) (#201007)
# Backport This will backport the following commits from `main` to `8.x`: - [[inference] add support for openAI native stream token count (#200745)](https://github.com/elastic/kibana/pull/200745) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pierre Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T16:53:44Z","message":"[inference] add support for openAI native stream token count (#200745)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/192962\r\n\r\nAdd support for native openAI token count for streaming APIs.\r\n\r\nThis is done by adding the `stream_options: {\"include_usage\": true}`\r\nparameter when `stream: true` is being used\r\n([doc](https://platform.openai.com/docs/api-reference/chat/create#chat-create-stream_options)),\r\nand then using the `usage` entry for the last emitted chunk.\r\n\r\n**Note**: this was done only for the `OpenAI` and `AzureAI`\r\n[providers]( |
||
|
Tiago Costa
|
43d4730ebd
|
skip flaky suite (#200154) | ||
|
Tiago Costa
|
c224d060a9
|
skip flaky suite (#200888) | ||
|
Kibana Machine
|
0381bfdf18
|
[8.x] [Security Solution] - fixes small issues in ftr security configs (#199389) (#200999)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] - fixes small issues in ftr security configs (#199389)](https://github.com/elastic/kibana/pull/199389) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T16:39:18Z","message":"[Security Solution] - fixes small issues in ftr security configs (#199389)\n\n## Summary\r\n\r\nThis PR moves a couple of entries from\r\n`.buildkite/ftr_security_stateful_configs.yml` to\r\n`.buildkite/ftr_security_serverless_configs.yml` as they seemed to be\r\nrelated to serverless.","sha":"7ee9f0065ee860ae75d656794e7e492ce566da09","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.17.0"],"title":"[Security Solution] - fixes small issues in ftr security configs","number":199389,"url":"https://github.com/elastic/kibana/pull/199389","mergeCommit":{"message":"[Security Solution] - fixes small issues in ftr security configs (#199389)\n\n## Summary\r\n\r\nThis PR moves a couple of entries from\r\n`.buildkite/ftr_security_stateful_configs.yml` to\r\n`.buildkite/ftr_security_serverless_configs.yml` as they seemed to be\r\nrelated to serverless.","sha":"7ee9f0065ee860ae75d656794e7e492ce566da09"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199389","number":199389,"mergeCommit":{"message":"[Security Solution] - fixes small issues in ftr security configs (#199389)\n\n## Summary\r\n\r\nThis PR moves a couple of entries from\r\n`.buildkite/ftr_security_stateful_configs.yml` to\r\n`.buildkite/ftr_security_serverless_configs.yml` as they seemed to be\r\nrelated to serverless.","sha":"7ee9f0065ee860ae75d656794e7e492ce566da09"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
3ca8840a47
|
[8.x] Remove Container Workload Protection link from Assets page (#200895) (#200994)
# Backport This will backport the following commits from `main` to `8.x`: - [Remove Container Workload Protection link from Assets page (#200895)](https://github.com/elastic/kibana/pull/200895) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alberto Blázquez","email":"albertoblaz@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T16:30:57Z","message":"Remove Container Workload Protection link from Assets page (#200895)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10741.\r\n\r\nAs the name suggests, it simply removes the link to the \"Container\r\nWorkload Protection\" link from the Cloud section in the Assets page. The\r\nCloud section is kept though, since the screenshot in the ticket doesn't\r\nhighlight it.\r\n\r\n### Testing\r\n\r\n> [!NOTE]\r\n> Note this page is only accessible in Serverless.\r\n\r\nAuthenticate to Docker Registry with\r\n```bash\r\ndocker login -u albertoblaz -p <YOUR_PASSWORD> docker.elastic.co\r\n```\r\n\r\nThen run ES with\r\n\r\n```bash\r\nyarn es serverless --projectType security --kill\r\n```\r\n\r\nAlternatively, run Kibana with\r\n```bash\r\nyarn serverless-security\r\n```\r\n\r\n### Screenshot\r\n\r\nLink removed, but Cloud section is kept:\r\n\r\n<details><summary>Before</summary>\r\n<img width=\"2043\" alt=\"before\"\r\nsrc=\"https://github.com/user-attachments/assets/e0421c83-6f62-49f9-bb46-26e8e828f10b\">\r\n</details> \r\n\r\n<details><summary>After</summary>\r\n<img width=\"2514\" alt=\"Screenshot 2024-11-20 at 12 05 01\"\r\nsrc=\"https://github.com/user-attachments/assets/51ac7f1f-086a-4fe2-846a-5511fc8e0f82\">\r\n</details> \r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2bef2c0d2c23f393902c0a607ef8f45221990081","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor","Feature:Cloud-Security","ci:project-deploy-security","backport:version","v8.18.0"],"title":"Remove Container Workload Protection link from Assets page","number":200895,"url":"https://github.com/elastic/kibana/pull/200895","mergeCommit":{"message":"Remove Container Workload Protection link from Assets page (#200895)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10741.\r\n\r\nAs the name suggests, it simply removes the link to the \"Container\r\nWorkload Protection\" link from the Cloud section in the Assets page. The\r\nCloud section is kept though, since the screenshot in the ticket doesn't\r\nhighlight it.\r\n\r\n### Testing\r\n\r\n> [!NOTE]\r\n> Note this page is only accessible in Serverless.\r\n\r\nAuthenticate to Docker Registry with\r\n```bash\r\ndocker login -u albertoblaz -p <YOUR_PASSWORD> docker.elastic.co\r\n```\r\n\r\nThen run ES with\r\n\r\n```bash\r\nyarn es serverless --projectType security --kill\r\n```\r\n\r\nAlternatively, run Kibana with\r\n```bash\r\nyarn serverless-security\r\n```\r\n\r\n### Screenshot\r\n\r\nLink removed, but Cloud section is kept:\r\n\r\n<details><summary>Before</summary>\r\n<img width=\"2043\" alt=\"before\"\r\nsrc=\"https://github.com/user-attachments/assets/e0421c83-6f62-49f9-bb46-26e8e828f10b\">\r\n</details> \r\n\r\n<details><summary>After</summary>\r\n<img width=\"2514\" alt=\"Screenshot 2024-11-20 at 12 05 01\"\r\nsrc=\"https://github.com/user-attachments/assets/51ac7f1f-086a-4fe2-846a-5511fc8e0f82\">\r\n</details> \r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2bef2c0d2c23f393902c0a607ef8f45221990081"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200895","number":200895,"mergeCommit":{"message":"Remove Container Workload Protection link from Assets page (#200895)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10741.\r\n\r\nAs the name suggests, it simply removes the link to the \"Container\r\nWorkload Protection\" link from the Cloud section in the Assets page. The\r\nCloud section is kept though, since the screenshot in the ticket doesn't\r\nhighlight it.\r\n\r\n### Testing\r\n\r\n> [!NOTE]\r\n> Note this page is only accessible in Serverless.\r\n\r\nAuthenticate to Docker Registry with\r\n```bash\r\ndocker login -u albertoblaz -p <YOUR_PASSWORD> docker.elastic.co\r\n```\r\n\r\nThen run ES with\r\n\r\n```bash\r\nyarn es serverless --projectType security --kill\r\n```\r\n\r\nAlternatively, run Kibana with\r\n```bash\r\nyarn serverless-security\r\n```\r\n\r\n### Screenshot\r\n\r\nLink removed, but Cloud section is kept:\r\n\r\n<details><summary>Before</summary>\r\n<img width=\"2043\" alt=\"before\"\r\nsrc=\"https://github.com/user-attachments/assets/e0421c83-6f62-49f9-bb46-26e8e828f10b\">\r\n</details> \r\n\r\n<details><summary>After</summary>\r\n<img width=\"2514\" alt=\"Screenshot 2024-11-20 at 12 05 01\"\r\nsrc=\"https://github.com/user-attachments/assets/51ac7f1f-086a-4fe2-846a-5511fc8e0f82\">\r\n</details> \r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"2bef2c0d2c23f393902c0a607ef8f45221990081"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Alberto Blázquez <albertoblaz@users.noreply.github.com> |
||
|
Kibana Machine
|
1dcdf8c1d5
|
[8.x] Authorized route migration for routes owned by @elastic/security-defend-workflows (#198197) (#200995)
# Backport This will backport the following commits from `main` to `8.x`: - [Authorized route migration for routes owned by @elastic/security-defend-workflows (#198197)](https://github.com/elastic/kibana/pull/198197) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kibana Machine","email":"42973632+kibanamachine@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T16:31:19Z","message":"Authorized route migration for routes owned by @elastic/security-defend-workflows (#198197)\n\n### Authz API migration for authorized routes\r\n\r\nThis PR migrates `access:<privilege>` tags used in route definitions to\r\nnew security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### What to do next?\r\n1. Review the changes in this PR.\r\n2. You might need to update your tests to reflect the new security\r\nconfiguration:\r\n - If you have tests that rely on checking `access` tags.\r\n - If you have snapshot tests that include the route definition.\r\n- If you have FTR tests that rely on checking unauthorized error\r\nmessage. The error message changed to also include missing privileges.\r\n\r\n## Any questions?\r\nIf you have any questions or need help with API authorization, please\r\nreach out to the `@elastic/kibana-security` team.\r\n\r\nCo-authored-by: Joey F. Poon <joey.poon@elastic.co>\r\nCo-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>\r\nCo-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>","sha":"0043379b9881eb6107df485aad2396ddfe952f34","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","v9.0.0","Team:Defend Workflows","backport:prev-minor","ci:cloud-deploy","Authz: API migration"],"title":"Authorized route migration for routes owned by @elastic/security-defend-workflows","number":198197,"url":"https://github.com/elastic/kibana/pull/198197","mergeCommit":{"message":"Authorized route migration for routes owned by @elastic/security-defend-workflows (#198197)\n\n### Authz API migration for authorized routes\r\n\r\nThis PR migrates `access:<privilege>` tags used in route definitions to\r\nnew security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### What to do next?\r\n1. Review the changes in this PR.\r\n2. You might need to update your tests to reflect the new security\r\nconfiguration:\r\n - If you have tests that rely on checking `access` tags.\r\n - If you have snapshot tests that include the route definition.\r\n- If you have FTR tests that rely on checking unauthorized error\r\nmessage. The error message changed to also include missing privileges.\r\n\r\n## Any questions?\r\nIf you have any questions or need help with API authorization, please\r\nreach out to the `@elastic/kibana-security` team.\r\n\r\nCo-authored-by: Joey F. Poon <joey.poon@elastic.co>\r\nCo-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>\r\nCo-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>","sha":"0043379b9881eb6107df485aad2396ddfe952f34"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198197","number":198197,"mergeCommit":{"message":"Authorized route migration for routes owned by @elastic/security-defend-workflows (#198197)\n\n### Authz API migration for authorized routes\r\n\r\nThis PR migrates `access:<privilege>` tags used in route definitions to\r\nnew security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### What to do next?\r\n1. Review the changes in this PR.\r\n2. You might need to update your tests to reflect the new security\r\nconfiguration:\r\n - If you have tests that rely on checking `access` tags.\r\n - If you have snapshot tests that include the route definition.\r\n- If you have FTR tests that rely on checking unauthorized error\r\nmessage. The error message changed to also include missing privileges.\r\n\r\n## Any questions?\r\nIf you have any questions or need help with API authorization, please\r\nreach out to the `@elastic/kibana-security` team.\r\n\r\nCo-authored-by: Joey F. Poon <joey.poon@elastic.co>\r\nCo-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>\r\nCo-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co>","sha":"0043379b9881eb6107df485aad2396ddfe952f34"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
e40f09dc46
|
[8.x] [Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests (#200712) (#200992)
# Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests (#200712)](https://github.com/elastic/kibana/pull/200712) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"mark.hopkin@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T16:27:42Z","message":"[Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests (#200712)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/189067\n\nThese asset criticality tests were failing in serverless because it\nseems queries without a specified sort order behave differently in\nserverless vs ESS.\n\nI have made it so that asset criticality sorts by timestamp by default,\nthis makes serverless the same as ESS.\n\nI have backported to 8.16 as I think the more tests that run, the\nbetter.","sha":"4c295893ba8ead829c1f0ad01c9d46741420d66f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","Team:Entity Analytics","backport:version","v8.17.0","v8.16.1","v8.18.0"],"title":"[Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests","number":200712,"url":"https://github.com/elastic/kibana/pull/200712","mergeCommit":{"message":"[Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests (#200712)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/189067\n\nThese asset criticality tests were failing in serverless because it\nseems queries without a specified sort order behave differently in\nserverless vs ESS.\n\nI have made it so that asset criticality sorts by timestamp by default,\nthis makes serverless the same as ESS.\n\nI have backported to 8.16 as I think the more tests that run, the\nbetter.","sha":"4c295893ba8ead829c1f0ad01c9d46741420d66f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200712","number":200712,"mergeCommit":{"message":"[Entity Analytics] Sort asset criticality by `@timestamp` by default + unskip serverless tests (#200712)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/189067\n\nThese asset criticality tests were failing in serverless because it\nseems queries without a specified sort order behave differently in\nserverless vs ESS.\n\nI have made it so that asset criticality sorts by timestamp by default,\nthis makes serverless the same as ESS.\n\nI have backported to 8.16 as I think the more tests that run, the\nbetter.","sha":"4c295893ba8ead829c1f0ad01c9d46741420d66f"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co> |
||
Dzmitry Lemechko
|
825cb5b68b
|
[8.x] [chore] remove unused nyc configs and dependencies (#200909) (#200983)
# Backport This will backport the following commits from `main` to `8.x`: - [[chore] remove unused nyc configs and dependencies (#200909)](https://github.com/elastic/kibana/pull/200909) <!--- Backport version: 8.9.8 --> ### 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":"2024-11-20T15:41:30Z","message":"[chore] remove unused nyc configs and dependencies (#200909)\n\n## Summary\r\n\r\nnyc (istanbuljs) cleanup as we no longer collect code coverage for\r\nfunctional tests","sha":"88a280c2505759d4fb0c64a00845ea17633d2f03","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","v9.0.0","backport:version","v8.17.0"],"number":200909,"url":"https://github.com/elastic/kibana/pull/200909","mergeCommit":{"message":"[chore] remove unused nyc configs and dependencies (#200909)\n\n## Summary\r\n\r\nnyc (istanbuljs) cleanup as we no longer collect code coverage for\r\nfunctional tests","sha":"88a280c2505759d4fb0c64a00845ea17633d2f03"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200909","number":200909,"mergeCommit":{"message":"[chore] remove unused nyc configs and dependencies (#200909)\n\n## Summary\r\n\r\nnyc (istanbuljs) cleanup as we no longer collect code coverage for\r\nfunctional tests","sha":"88a280c2505759d4fb0c64a00845ea17633d2f03"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Sergi Romeu
|
c1cdcd5291
|
[8.x] [APM] Migrate /transactions to deployment agnostic test (#200694) (#200975)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Migrate `/transactions` to deployment agnostic test (#200694)](https://github.com/elastic/kibana/pull/200694) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T15:48:14Z","message":"[APM] Migrate `/transactions` to deployment agnostic test (#200694)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/198997\r\nPart of https://github.com/elastic/kibana/issues/193245\r\n\r\nThis PR contains the changes to migrate `transactions` test folder to\r\nDeployment-agnostic testing strategy.\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\n```\r\n\r\n## Checks\r\n\r\n- [x] (OPTIONAL, only if a test has been unskipped) Run flaky test suite\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless \r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->","sha":"d0b5a57ccaf14025d68a206cc742b994f8ad8bee","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","apm","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"number":200694,"url":"https://github.com/elastic/kibana/pull/200694","mergeCommit":{"message":"[APM] Migrate `/transactions` to deployment agnostic test (#200694)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/198997\r\nPart of https://github.com/elastic/kibana/issues/193245\r\n\r\nThis PR contains the changes to migrate `transactions` test folder to\r\nDeployment-agnostic testing strategy.\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\n```\r\n\r\n## Checks\r\n\r\n- [x] (OPTIONAL, only if a test has been unskipped) Run flaky test suite\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless \r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->","sha":"d0b5a57ccaf14025d68a206cc742b994f8ad8bee"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200694","number":200694,"mergeCommit":{"message":"[APM] Migrate `/transactions` to deployment agnostic test (#200694)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/198997\r\nPart of https://github.com/elastic/kibana/issues/193245\r\n\r\nThis PR contains the changes to migrate `transactions` test folder to\r\nDeployment-agnostic testing strategy.\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.apm.serverless.config.ts\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.apm.stateful.config.ts\r\n```\r\n\r\n## Checks\r\n\r\n- [x] (OPTIONAL, only if a test has been unskipped) Run flaky test suite\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless \r\n\r\n<!--ONMERGE {\"backportTargets\":[\"8.x\"]} ONMERGE-->","sha":"d0b5a57ccaf14025d68a206cc742b994f8ad8bee"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
0318a5966f
|
[8.x] [Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !! (#199308) (#200970)
# Backport This will backport the following commits from `main` to `8.x`: - [[Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !! (#199308)](https://github.com/elastic/kibana/pull/199308) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T15:36:33Z","message":"[Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !! (#199308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/196548\r\n\r\nSLO Availability sync delay field to use `@timestamp` instead of\r\n`event.ingested` !!\r\n\r\n\r\n### Testing\r\n\r\n- Make sure Synthetics availability SLOs works as expected in serverless\r\nand stateful\r\n- Make sure when SLO is updated, it continues to work","sha":"c9540d9d545c1974927d57f195b77f0c180a78c3","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !!","number":199308,"url":"https://github.com/elastic/kibana/pull/199308","mergeCommit":{"message":"[Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !! (#199308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/196548\r\n\r\nSLO Availability sync delay field to use `@timestamp` instead of\r\n`event.ingested` !!\r\n\r\n\r\n### Testing\r\n\r\n- Make sure Synthetics availability SLOs works as expected in serverless\r\nand stateful\r\n- Make sure when SLO is updated, it continues to work","sha":"c9540d9d545c1974927d57f195b77f0c180a78c3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199308","number":199308,"mergeCommit":{"message":"[Synthetics] SLO Availability sync delay field to use timestamp instead of event.ingested !! (#199308)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/196548\r\n\r\nSLO Availability sync delay field to use `@timestamp` instead of\r\n`event.ingested` !!\r\n\r\n\r\n### Testing\r\n\r\n- Make sure Synthetics availability SLOs works as expected in serverless\r\nand stateful\r\n- Make sure when SLO is updated, it continues to work","sha":"c9540d9d545c1974927d57f195b77f0c180a78c3"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
398086c68b
|
[8.x] [Index Management] Feature add button handler for the ilm banner via extension service (#199077) (#200965)
# Backport This will backport the following commits from `main` to `8.x`: - [[Index Management] Feature add button handler for the ilm banner via extension service (#199077)](https://github.com/elastic/kibana/pull/199077) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jusheng Huang","email":"117657272+viajes7@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T15:28:50Z","message":"[Index Management] Feature add button handler for the ilm banner via extension service (#199077)\n\n## Summary\r\n\r\nClose #27159 \r\n\r\nAdd a button handler for the ilm banner. \r\n\r\n\r\n\r\n\r\nUI reference Eui callout component style.\r\n[ |
||
|
Kibana Machine
|
e00f9b7c74
|
[8.x] chore(slo): remove deprecated theme provider and usage of styled-components (#200248) (#200969)
# Backport This will backport the following commits from `main` to `8.x`: - [chore(slo): remove deprecated theme provider and usage of styled-components (#200248)](https://github.com/elastic/kibana/pull/200248) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T15:37:32Z","message":"chore(slo): remove deprecated theme provider and usage of styled-components (#200248)","sha":"684a1308d279acbdff7f49bcce204854c2a95681","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.17.0"],"title":"chore(slo): remove deprecated theme provider and usage of styled-components","number":200248,"url":"https://github.com/elastic/kibana/pull/200248","mergeCommit":{"message":"chore(slo): remove deprecated theme provider and usage of styled-components (#200248)","sha":"684a1308d279acbdff7f49bcce204854c2a95681"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200248","number":200248,"mergeCommit":{"message":"chore(slo): remove deprecated theme provider and usage of styled-components (#200248)","sha":"684a1308d279acbdff7f49bcce204854c2a95681"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co> |
||
|
Kibana Machine
|
4e4c0140a8
|
[8.x] [Docs] Add release notes for 8.16.1 (#200693) (#200980)
# Backport This will backport the following commits from `main` to `8.x`: - [[Docs] Add release notes for 8.16.1 (#200693)](https://github.com/elastic/kibana/pull/200693) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T16:04:18Z","message":"[Docs] Add release notes for 8.16.1 (#200693)\n\nThis PR adds release notes for the 8.16.1 release of Kibana.\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/566\r\nRel: https://github.com/elastic/dev/issues/2884","sha":"d2dac36116a674ccbbc3e05f545736c92efbc834","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","backport:version","v8.17.0","v8.16.1"],"title":"[Docs] Add release notes for 8.16.1","number":200693,"url":"https://github.com/elastic/kibana/pull/200693","mergeCommit":{"message":"[Docs] Add release notes for 8.16.1 (#200693)\n\nThis PR adds release notes for the 8.16.1 release of Kibana.\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/566\r\nRel: https://github.com/elastic/dev/issues/2884","sha":"d2dac36116a674ccbbc3e05f545736c92efbc834"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200693","number":200693,"mergeCommit":{"message":"[Docs] Add release notes for 8.16.1 (#200693)\n\nThis PR adds release notes for the 8.16.1 release of Kibana.\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/566\r\nRel: https://github.com/elastic/dev/issues/2884","sha":"d2dac36116a674ccbbc3e05f545736c92efbc834"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
6e4e86f75c
|
[8.x] fix: make panel top nav menu item button full width on mobile (#200823) (#200927)
# Backport This will backport the following commits from `main` to `8.x`: - [fix: make panel top nav menu item button full width on mobile (#200823)](https://github.com/elastic/kibana/pull/200823) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Paulina Shakirova","email":"paulina.shakirova@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T13:56:41Z","message":"fix: make panel top nav menu item button full width on mobile (#200823)\n\n## Summary\r\n\r\nThis PR solves [[Dashboard] Center Save top nav button for small\r\nviewport](https://github.com/elastic/kibana/issues/180093#top) issue.\r\n\r\n\r\n\r\n\r\n\r\nThe change only affects the mobile menu.","sha":"971c1f3c350cd36c6e21441deb5b473f839963cd","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:SharedUX","backport:prev-minor","papercut","v8.17.0"],"title":"fix: make panel top nav menu item button full width on mobile","number":200823,"url":"https://github.com/elastic/kibana/pull/200823","mergeCommit":{"message":"fix: make panel top nav menu item button full width on mobile (#200823)\n\n## Summary\r\n\r\nThis PR solves [[Dashboard] Center Save top nav button for small\r\nviewport](https://github.com/elastic/kibana/issues/180093#top) issue.\r\n\r\n\r\n\r\n\r\n\r\nThe change only affects the mobile menu.","sha":"971c1f3c350cd36c6e21441deb5b473f839963cd"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200823","number":200823,"mergeCommit":{"message":"fix: make panel top nav menu item button full width on mobile (#200823)\n\n## Summary\r\n\r\nThis PR solves [[Dashboard] Center Save top nav button for small\r\nviewport](https://github.com/elastic/kibana/issues/180093#top) issue.\r\n\r\n\r\n\r\n\r\n\r\nThe change only affects the mobile menu.","sha":"971c1f3c350cd36c6e21441deb5b473f839963cd"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Paulina Shakirova <paulina.shakirova@elastic.co> |
||
|
Kibana Machine
|
fd4ea587ac
|
[8.x] [UA] Fix reindex docs in README.md (#200893) (#200925)
# Backport This will backport the following commits from `main` to `8.x`: - [[UA] Fix reindex docs in README.md (#200893)](https://github.com/elastic/kibana/pull/200893) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T13:48:22Z","message":"[UA] Fix reindex docs in README.md (#200893)\n\n## Summary\r\n\r\nUpdates overview of Upgrade Assistant's reindexing actions. Also updates\r\nsome doc comments.\r\n\r\nClose https://github.com/elastic/kibana/issues/121237\r\n\r\n<img width=\"1163\" alt=\"Screenshot 2024-11-20 at 12 07 25\"\r\nsrc=\"https://github.com/user-attachments/assets/2b16e6e2-cee9-456b-b854-26ee658c3648\">\r\n\r\n---------\r\n\r\nCo-authored-by: Rudolf Meijering <skaapgif@gmail.com>","sha":"3a6224f8594fa21a5f37a94542523fa6b77f2149","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Kibana Management","release_note:skip","Feature:Upgrade Assistant","v9.0.0","backport:version","v8.17.0","v8.18.0"],"title":"[UA] Fix reindex docs in README.md","number":200893,"url":"https://github.com/elastic/kibana/pull/200893","mergeCommit":{"message":"[UA] Fix reindex docs in README.md (#200893)\n\n## Summary\r\n\r\nUpdates overview of Upgrade Assistant's reindexing actions. Also updates\r\nsome doc comments.\r\n\r\nClose https://github.com/elastic/kibana/issues/121237\r\n\r\n<img width=\"1163\" alt=\"Screenshot 2024-11-20 at 12 07 25\"\r\nsrc=\"https://github.com/user-attachments/assets/2b16e6e2-cee9-456b-b854-26ee658c3648\">\r\n\r\n---------\r\n\r\nCo-authored-by: Rudolf Meijering <skaapgif@gmail.com>","sha":"3a6224f8594fa21a5f37a94542523fa6b77f2149"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200893","number":200893,"mergeCommit":{"message":"[UA] Fix reindex docs in README.md (#200893)\n\n## Summary\r\n\r\nUpdates overview of Upgrade Assistant's reindexing actions. Also updates\r\nsome doc comments.\r\n\r\nClose https://github.com/elastic/kibana/issues/121237\r\n\r\n<img width=\"1163\" alt=\"Screenshot 2024-11-20 at 12 07 25\"\r\nsrc=\"https://github.com/user-attachments/assets/2b16e6e2-cee9-456b-b854-26ee658c3648\">\r\n\r\n---------\r\n\r\nCo-authored-by: Rudolf Meijering <skaapgif@gmail.com>","sha":"3a6224f8594fa21a5f37a94542523fa6b77f2149"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jean-Louis Leysens <jeanlouis.leysens@elastic.co> |
||
|
Kibana Machine
|
9bfe548295
|
[8.x] [Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload (#200897) (#200920)
# Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload (#200897)](https://github.com/elastic/kibana/pull/200897) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"mark.hopkin@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T13:25:31Z","message":"[Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload (#200897)\n\n## Summary\r\n\r\nWe were unintentionally refreshing all indices after an asset\r\ncriticality bulk upload was performed, this fix makes it so we only\r\nrefresh the asset criticality index.\r\n\r\nbackporting to all 8.x versions\r\n\r\n## Test steps\r\n\r\n- 1. I created an index by uploading a document, the content isn't\r\nimportant:\r\n```\r\nPOST /logs-test-hello/_doc\r\n{\r\n \"host\" : {\r\n \"name\" : \"my_host\",\r\n \"domain\" : \"my_domain\",\r\n \"ip\" : [\"1.1.1.1\", \"2.2.2.2\", \"3.3.3.3\"]\r\n }\r\n}\r\n```\r\n\r\n- 2. I then used the refresh stats API to see how many refreshes have\r\nhappened on that index:\r\n\r\n```\r\nGET /_stats/refresh\r\n\r\n// lots ommited here:\r\n\r\n \".ds-logs-test-hello-2024.11.20-000001\": {\r\n \"uuid\": \"DRxQd3rgQC2YSMIahzDCrw\",\r\n \"health\": \"yellow\",\r\n \"status\": \"open\",\r\n \"primaries\": {\r\n \"refresh\": {\r\n \"total\": 10,\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n },\r\n \"total\": {\r\n \"refresh\": {\r\n \"total\": 10, // <--------------------------------- Index has had 10 refreshes\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n }\r\n },\r\n```\r\n3. perform an asset criticality bulk upload\r\n4. call the `GET /_stats/refresh` API again, before the fix notice the\r\nnumber has gone up on the logs index (I did this a few times just to\r\nmake sure) OR after the fix, this number does not go up.","sha":"d95fa7263a74d7fb45fdff7718011e75e560536e","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team: SecuritySolution","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v8.15.5","v8.16.2"],"title":"[Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload","number":200897,"url":"https://github.com/elastic/kibana/pull/200897","mergeCommit":{"message":"[Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload (#200897)\n\n## Summary\r\n\r\nWe were unintentionally refreshing all indices after an asset\r\ncriticality bulk upload was performed, this fix makes it so we only\r\nrefresh the asset criticality index.\r\n\r\nbackporting to all 8.x versions\r\n\r\n## Test steps\r\n\r\n- 1. I created an index by uploading a document, the content isn't\r\nimportant:\r\n```\r\nPOST /logs-test-hello/_doc\r\n{\r\n \"host\" : {\r\n \"name\" : \"my_host\",\r\n \"domain\" : \"my_domain\",\r\n \"ip\" : [\"1.1.1.1\", \"2.2.2.2\", \"3.3.3.3\"]\r\n }\r\n}\r\n```\r\n\r\n- 2. I then used the refresh stats API to see how many refreshes have\r\nhappened on that index:\r\n\r\n```\r\nGET /_stats/refresh\r\n\r\n// lots ommited here:\r\n\r\n \".ds-logs-test-hello-2024.11.20-000001\": {\r\n \"uuid\": \"DRxQd3rgQC2YSMIahzDCrw\",\r\n \"health\": \"yellow\",\r\n \"status\": \"open\",\r\n \"primaries\": {\r\n \"refresh\": {\r\n \"total\": 10,\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n },\r\n \"total\": {\r\n \"refresh\": {\r\n \"total\": 10, // <--------------------------------- Index has had 10 refreshes\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n }\r\n },\r\n```\r\n3. perform an asset criticality bulk upload\r\n4. call the `GET /_stats/refresh` API again, before the fix notice the\r\nnumber has gone up on the logs index (I did this a few times just to\r\nmake sure) OR after the fix, this number does not go up.","sha":"d95fa7263a74d7fb45fdff7718011e75e560536e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","8.15","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200897","number":200897,"mergeCommit":{"message":"[Entity Analytics][Bug] Only refresh the asset criticality index after bulk upload (#200897)\n\n## Summary\r\n\r\nWe were unintentionally refreshing all indices after an asset\r\ncriticality bulk upload was performed, this fix makes it so we only\r\nrefresh the asset criticality index.\r\n\r\nbackporting to all 8.x versions\r\n\r\n## Test steps\r\n\r\n- 1. I created an index by uploading a document, the content isn't\r\nimportant:\r\n```\r\nPOST /logs-test-hello/_doc\r\n{\r\n \"host\" : {\r\n \"name\" : \"my_host\",\r\n \"domain\" : \"my_domain\",\r\n \"ip\" : [\"1.1.1.1\", \"2.2.2.2\", \"3.3.3.3\"]\r\n }\r\n}\r\n```\r\n\r\n- 2. I then used the refresh stats API to see how many refreshes have\r\nhappened on that index:\r\n\r\n```\r\nGET /_stats/refresh\r\n\r\n// lots ommited here:\r\n\r\n \".ds-logs-test-hello-2024.11.20-000001\": {\r\n \"uuid\": \"DRxQd3rgQC2YSMIahzDCrw\",\r\n \"health\": \"yellow\",\r\n \"status\": \"open\",\r\n \"primaries\": {\r\n \"refresh\": {\r\n \"total\": 10,\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n },\r\n \"total\": {\r\n \"refresh\": {\r\n \"total\": 10, // <--------------------------------- Index has had 10 refreshes\r\n \"total_time_in_millis\": 66,\r\n \"external_total\": 9,\r\n \"external_total_time_in_millis\": 67,\r\n \"listeners\": 0\r\n }\r\n }\r\n },\r\n```\r\n3. perform an asset criticality bulk upload\r\n4. call the `GET /_stats/refresh` API again, before the fix notice the\r\nnumber has gone up on the logs index (I did this a few times just to\r\nmake sure) OR after the fix, this number does not go up.","sha":"d95fa7263a74d7fb45fdff7718011e75e560536e"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co> |
||
|
Kibana Machine
|
ea3ff91379
|
[8.x] [ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach (#200226) (#200916)
# Backport This will backport the following commits from `main` to `8.x`: - [[ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach (#200226)](https://github.com/elastic/kibana/pull/200226) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gonçalo Rica Pais da Silva","email":"goncalo.rica@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T13:17:24Z","message":"[ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach (#200226)\n\n## Summary\r\n\r\nPart of #193245\r\nCloses #198986\r\n\r\nThis PR moves all compatible/supported test cases for Service Overview.\r\nUnsupported cases are kept in the old test section to run on stateful\r\nfor now.\r\n\r\n## How to Test\r\n\r\n### Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n### Stateful\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"185fa2a7dc086a0b30925ea4447f9ec3de1c8651","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.17.0"],"title":"[ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach","number":200226,"url":"https://github.com/elastic/kibana/pull/200226","mergeCommit":{"message":"[ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach (#200226)\n\n## Summary\r\n\r\nPart of #193245\r\nCloses #198986\r\n\r\nThis PR moves all compatible/supported test cases for Service Overview.\r\nUnsupported cases are kept in the old test section to run on stateful\r\nfor now.\r\n\r\n## How to Test\r\n\r\n### Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n### Stateful\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"185fa2a7dc086a0b30925ea4447f9ec3de1c8651"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200226","number":200226,"mergeCommit":{"message":"[ObsUX][APM] Migration of Service Overview tests to deployment agnostic approach (#200226)\n\n## Summary\r\n\r\nPart of #193245\r\nCloses #198986\r\n\r\nThis PR moves all compatible/supported test cases for Service Overview.\r\nUnsupported cases are kept in the old test section to run on stateful\r\nfor now.\r\n\r\n## How to Test\r\n\r\n### Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n### Stateful\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM API tests\"\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"185fa2a7dc086a0b30925ea4447f9ec3de1c8651"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gonçalo Rica Pais da Silva <goncalo.rica@elastic.co> |
||
|
Kibana Machine
|
096a3cd310
|
[8.x] [EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071) (#200915)
# Backport This will backport the following commits from `main` to `8.x`: - [[EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071)](https://github.com/elastic/kibana/pull/196071) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2024-10-23T10:29:32Z","message":"[EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071)\n\nThese changes ensure that the warning displayed to the user for\r\nduplicate values remains visible after onBlur. I’ve opted to keep it as\r\na warning rather than an error since entering a duplicate value doesn’t\r\nallow the user to “save” it as a selected item in the combo box—it\r\nremains an active string in the input field. We don’t block form\r\nsubmission due to this warning; any unselected value in the combo box is\r\nstripped out. The red border on the combo box is part of EUI’s behavior\r\nwhen attempting to select a duplicate, and I don’t see an easy way to\r\nmodify this at the moment.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098","sha":"99a19e762daf08376828032e593a9e88befe6d23","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v8.17.0","v8.16.1"],"title":"[EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab","number":196071,"url":"https://github.com/elastic/kibana/pull/196071","mergeCommit":{"message":"[EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071)\n\nThese changes ensure that the warning displayed to the user for\r\nduplicate values remains visible after onBlur. I’ve opted to keep it as\r\na warning rather than an error since entering a duplicate value doesn’t\r\nallow the user to “save” it as a selected item in the combo box—it\r\nremains an active string in the input field. We don’t block form\r\nsubmission due to this warning; any unselected value in the combo box is\r\nstripped out. The red border on the combo box is part of EUI’s behavior\r\nwhen attempting to select a duplicate, and I don’t see an easy way to\r\nmodify this at the moment.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098","sha":"99a19e762daf08376828032e593a9e88befe6d23"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196071","number":196071,"mergeCommit":{"message":"[EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071)\n\nThese changes ensure that the warning displayed to the user for\r\nduplicate values remains visible after onBlur. I’ve opted to keep it as\r\na warning rather than an error since entering a duplicate value doesn’t\r\nallow the user to “save” it as a selected item in the combo box—it\r\nremains an active string in the input field. We don’t block form\r\nsubmission due to this warning; any unselected value in the combo box is\r\nstripped out. The red border on the combo box is part of EUI’s behavior\r\nwhen attempting to select a duplicate, and I don’t see an easy way to\r\nmodify this at the moment.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098","sha":"99a19e762daf08376828032e593a9e88befe6d23"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/199992","number":199992,"state":"MERGED","mergeCommit":{"sha":"4c5d5fa5a40014b0d8b09d0a9d07b7a7eec899a1","message":"[8.16] [EDR Workflows] Error message 'the value already exists' shown for duplicate values with the 'is one of' operator on Blocklist tab (#196071) (#199992)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[EDR Workflows] Error message 'the value already exists'\nshown for duplicate values with the 'is one of' operator on\nBlocklist tab (#196071)](https://github.com/elastic/kibana/pull/196071)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Konrad\nSzwarc\",\"email\":\"konrad.szwarc@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2024-10-23T10:29:32Z\",\"message\":\"[EDR\nWorkflows] Error message 'the value already exists' shown for duplicate\nvalues with the 'is one of' operator on Blocklist tab (#196071)\\n\\nThese\nchanges ensure that the warning displayed to the user for\\r\\nduplicate\nvalues remains visible after onBlur. I’ve opted to keep it as\\r\\na\nwarning rather than an error since entering a duplicate value\ndoesn’t\\r\\nallow the user to “save” it as a selected item in the combo\nbox—it\\r\\nremains an active string in the input field. We don’t block\nform\\r\\nsubmission due to this warning; any unselected value in the\ncombo box is\\r\\nstripped out. The red border on the combo box is part of\nEUI’s behavior\\r\\nwhen attempting to select a duplicate, and I don’t see\nan easy way to\\r\\nmodify this at the\nmoment.\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098\",\"sha\":\"99a19e762daf08376828032e593a9e88befe6d23\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"backport\nmissing\",\"v9.0.0\",\"Team:Defend\nWorkflows\",\"backport:version\",\"v8.16.1\"],\"title\":\"[EDR Workflows] Error\nmessage 'the value already exists' shown for duplicate values with the\n'is one of' operator on Blocklist\ntab\",\"number\":196071,\"url\":\"https://github.com/elastic/kibana/pull/196071\",\"mergeCommit\":{\"message\":\"[EDR\nWorkflows] Error message 'the value already exists' shown for duplicate\nvalues with the 'is one of' operator on Blocklist tab (#196071)\\n\\nThese\nchanges ensure that the warning displayed to the user for\\r\\nduplicate\nvalues remains visible after onBlur. I’ve opted to keep it as\\r\\na\nwarning rather than an error since entering a duplicate value\ndoesn’t\\r\\nallow the user to “save” it as a selected item in the combo\nbox—it\\r\\nremains an active string in the input field. We don’t block\nform\\r\\nsubmission due to this warning; any unselected value in the\ncombo box is\\r\\nstripped out. The red border on the combo box is part of\nEUI’s behavior\\r\\nwhen attempting to select a duplicate, and I don’t see\nan easy way to\\r\\nmodify this at the\nmoment.\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098\",\"sha\":\"99a19e762daf08376828032e593a9e88befe6d23\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/196071\",\"number\":196071,\"mergeCommit\":{\"message\":\"[EDR\nWorkflows] Error message 'the value already exists' shown for duplicate\nvalues with the 'is one of' operator on Blocklist tab (#196071)\\n\\nThese\nchanges ensure that the warning displayed to the user for\\r\\nduplicate\nvalues remains visible after onBlur. I’ve opted to keep it as\\r\\na\nwarning rather than an error since entering a duplicate value\ndoesn’t\\r\\nallow the user to “save” it as a selected item in the combo\nbox—it\\r\\nremains an active string in the input field. We don’t block\nform\\r\\nsubmission due to this warning; any unselected value in the\ncombo box is\\r\\nstripped out. The red border on the combo box is part of\nEUI’s behavior\\r\\nwhen attempting to select a duplicate, and I don’t see\nan easy way to\\r\\nmodify this at the\nmoment.\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/84b6d8af-02a8-41f3-88dc-892ed408a098\",\"sha\":\"99a19e762daf08376828032e593a9e88befe6d23\"}},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>"}}]}] BACKPORT--> Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co> |
||
Rudolf Meijering
|
b476f7fb4b
|
Limit bytesizevalue length for 8.x/7.x (#200733)
## Summary Inspired by https://github.com/elastic/kibana/pull/193529 but does not change the regular expression, it only limits the string length which is anyway the biggest performance improvement. This makes it a lot safer to backport since it's less likely that we could break existing kibana configurations that had typos. ### Checklist ### Identify risks - [ ] Could cause a Kibana to refuse to start up after an upgrade if it had a byte size configuration value that was excessively long. |
||
|
Kibana Machine
|
4a0ccdb6c4
|
[8.x] feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO (#199233) (#199875)
# Backport This will backport the following commits from `main` to `8.x`: - [feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO (#199233)](https://github.com/elastic/kibana/pull/199233) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2024-11-12T20:08:40Z","message":"feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO (#199233)","sha":"da85efe5093c148d4b91bcd3e21fd93c9f182a4f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.17.0"],"title":"feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO","number":199233,"url":"https://github.com/elastic/kibana/pull/199233","mergeCommit":{"message":"feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO (#199233)","sha":"da85efe5093c148d4b91bcd3e21fd93c9f182a4f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199233","number":199233,"mergeCommit":{"message":"feat(slo): Assert user has correct source index privileges when creating, updating or reseting an SLO (#199233)","sha":"da85efe5093c148d4b91bcd3e21fd93c9f182a4f"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Ievgen Sorokopud
|
33263b25c2
|
[8.x] [Rules migration] Add rules migrations update route (#11209) (#200815) (#200910)
# Backport This will backport the following commits from `main` to `8.x`: - [[Rules migration] Add rules migrations update route (#11209) (#200815)](https://github.com/elastic/kibana/pull/200815) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T12:36:37Z","message":"[Rules migration] Add rules migrations update route (#11209) (#200815)\n\n## Summary\r\n\r\nChanges in this PR:\r\n* Added `update` route to handle bulk rule migrations docs updates\r\n* Exposed `id` field in `RuleMigration` object needed for ES bulk update\r\noperation\r\n* Updated SIEM migrations schemas to use `NonEmptyString` when it is\r\nneeded\r\n\r\n## Testing locally\r\n\r\nEnable the flag\r\n```\r\nxpack.securitySolution.enableExperimental: ['siemMigrationsEnabled']\r\n```\r\n\r\nCreate and start a rule migration. Then use `update` API to updated\r\ncorresponding docs.\r\n\r\ncURL request examples:\r\n\r\n<details>\r\n <summary>Rules migration `create` POST request</summary>\r\n\r\n```\r\ncurl --location --request POST 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '[\r\n {\r\n \"id\": \"f8c325ea-506e-4105-8ccf-da1492e90115\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Add User Account Type\",\r\n \"description\": \"The following analytic detects the suspicious add user account type. This behavior is critical for a SOC to monitor because it may indicate attempts to gain unauthorized access or maintain control over a system. Such actions could be signs of malicious activity. If confirmed, this could lead to serious consequences, including a compromised system, unauthorized access to sensitive data, or even a wider breach affecting the entire network. Detecting and responding to these signs early is essential to prevent potential security incidents.\",\r\n \"query\": \"sourcetype=\\\"linux:audit\\\" type=ADD_USER \\n| rename hostname as dest \\n| stats count min(_time) as firstTime max(_time) as lastTime by exe pid dest res UID type \\n| `security_content_ctime(firstTime)` \\n| `security_content_ctime(lastTime)`\\n| search *\",\r\n \"query_language\":\"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1136\"\r\n ]\r\n },\r\n {\r\n \"id\": \"7b87c556-0ca4-47e0-b84c-6cd62a0a3e90\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Change File Owner To Root\",\r\n \"description\": \"The following analytic detects the use of the '\\''chown'\\'' command to change a file owner to '\\''root'\\'' on a Linux system. It leverages Linux Auditd telemetry, specifically monitoring command-line executions and process details. This activity is significant as it may indicate an attempt to escalate privileges by adversaries, malware, or red teamers. If confirmed malicious, this action could allow an attacker to gain root-level access, leading to full control over the compromised host and potential persistence within the environment.\",\r\n \"query\": \"`linux_auditd` `linux_auditd_normalized_proctitle_process`\\r\\n| rename host as dest \\r\\n| where LIKE (process_exec, \\\"%chown %root%\\\") \\r\\n| stats count min(_time) as firstTime max(_time) as lastTime by process_exec proctitle normalized_proctitle_delimiter dest \\r\\n| `security_content_ctime(firstTime)` \\r\\n| `security_content_ctime(lastTime)`\\r\\n| `linux_auditd_change_file_owner_to_root_filter`\",\r\n \"query_language\": \"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1222\"\r\n ]\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `start` task request</summary>\r\n\r\n- Assuming the connector `azureOpenAiGPT4o` is already created in the\r\nlocal environment.\r\n- Using the {{`migration_id`}} from the first POST request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}/start' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '{\r\n \"connectorId\": \"azureOpenAiGPT4o\"\r\n}'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration rules documents request</summary>\r\n\r\n- Using the {{`migration_id`}} from the first POST request response.\r\n\r\n```\r\ncurl --location --request GET 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `update` PUT request</summary>\r\n\r\n- Using the {{`rule_migration_id_1`}} and {{`rule_migration_id_2`}} from\r\nprevious GET request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n--data '[\r\n {\r\n \"comments\": [\r\n \"## Migration Summary\\n- The `FROM` command is used to select the `logs-*` index pattern.\\n- The `RENAME` command is used to rename the `host` field to `dest`.\\n- The `WHERE` command filters the rows where `process_exec` contains the pattern `*chown *root*`.\\n- The `STATS` command is used to aggregate the data, counting the number of occurrences and finding the minimum and maximum timestamps, grouped by `process_exec`, `proctitle`, `normalized_proctitle_delimiter`, and `dest`.\\n- The macros `security_content_ctime` and `linux_auditd_change_file_owner_to_root_filter` are placeholders for the corresponding Splunk macros.\",\r\n \"Additional comment 2.0\"\r\n ],\r\n \"translation_result\": \"full\",\r\n \"id\": \"{{rule_migration_id_1}}\"\r\n },\r\n {\r\n \"created_by\": \"elastic2.0\",\r\n \"elastic_rule\": {\r\n \"severity\": \"high\",\r\n \"title\": \"Linux Auditd Change File Owner To Root (UPDATED)\"\r\n },\r\n \"id\": \"{{rule_migration_id_2}}\"\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f6ac2cf8603ca633070e719f69b4fcef45ea92cb","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:prev-minor"],"number":200815,"url":"https://github.com/elastic/kibana/pull/200815","mergeCommit":{"message":"[Rules migration] Add rules migrations update route (#11209) (#200815)\n\n## Summary\r\n\r\nChanges in this PR:\r\n* Added `update` route to handle bulk rule migrations docs updates\r\n* Exposed `id` field in `RuleMigration` object needed for ES bulk update\r\noperation\r\n* Updated SIEM migrations schemas to use `NonEmptyString` when it is\r\nneeded\r\n\r\n## Testing locally\r\n\r\nEnable the flag\r\n```\r\nxpack.securitySolution.enableExperimental: ['siemMigrationsEnabled']\r\n```\r\n\r\nCreate and start a rule migration. Then use `update` API to updated\r\ncorresponding docs.\r\n\r\ncURL request examples:\r\n\r\n<details>\r\n <summary>Rules migration `create` POST request</summary>\r\n\r\n```\r\ncurl --location --request POST 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '[\r\n {\r\n \"id\": \"f8c325ea-506e-4105-8ccf-da1492e90115\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Add User Account Type\",\r\n \"description\": \"The following analytic detects the suspicious add user account type. This behavior is critical for a SOC to monitor because it may indicate attempts to gain unauthorized access or maintain control over a system. Such actions could be signs of malicious activity. If confirmed, this could lead to serious consequences, including a compromised system, unauthorized access to sensitive data, or even a wider breach affecting the entire network. Detecting and responding to these signs early is essential to prevent potential security incidents.\",\r\n \"query\": \"sourcetype=\\\"linux:audit\\\" type=ADD_USER \\n| rename hostname as dest \\n| stats count min(_time) as firstTime max(_time) as lastTime by exe pid dest res UID type \\n| `security_content_ctime(firstTime)` \\n| `security_content_ctime(lastTime)`\\n| search *\",\r\n \"query_language\":\"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1136\"\r\n ]\r\n },\r\n {\r\n \"id\": \"7b87c556-0ca4-47e0-b84c-6cd62a0a3e90\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Change File Owner To Root\",\r\n \"description\": \"The following analytic detects the use of the '\\''chown'\\'' command to change a file owner to '\\''root'\\'' on a Linux system. It leverages Linux Auditd telemetry, specifically monitoring command-line executions and process details. This activity is significant as it may indicate an attempt to escalate privileges by adversaries, malware, or red teamers. If confirmed malicious, this action could allow an attacker to gain root-level access, leading to full control over the compromised host and potential persistence within the environment.\",\r\n \"query\": \"`linux_auditd` `linux_auditd_normalized_proctitle_process`\\r\\n| rename host as dest \\r\\n| where LIKE (process_exec, \\\"%chown %root%\\\") \\r\\n| stats count min(_time) as firstTime max(_time) as lastTime by process_exec proctitle normalized_proctitle_delimiter dest \\r\\n| `security_content_ctime(firstTime)` \\r\\n| `security_content_ctime(lastTime)`\\r\\n| `linux_auditd_change_file_owner_to_root_filter`\",\r\n \"query_language\": \"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1222\"\r\n ]\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `start` task request</summary>\r\n\r\n- Assuming the connector `azureOpenAiGPT4o` is already created in the\r\nlocal environment.\r\n- Using the {{`migration_id`}} from the first POST request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}/start' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '{\r\n \"connectorId\": \"azureOpenAiGPT4o\"\r\n}'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration rules documents request</summary>\r\n\r\n- Using the {{`migration_id`}} from the first POST request response.\r\n\r\n```\r\ncurl --location --request GET 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `update` PUT request</summary>\r\n\r\n- Using the {{`rule_migration_id_1`}} and {{`rule_migration_id_2`}} from\r\nprevious GET request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n--data '[\r\n {\r\n \"comments\": [\r\n \"## Migration Summary\\n- The `FROM` command is used to select the `logs-*` index pattern.\\n- The `RENAME` command is used to rename the `host` field to `dest`.\\n- The `WHERE` command filters the rows where `process_exec` contains the pattern `*chown *root*`.\\n- The `STATS` command is used to aggregate the data, counting the number of occurrences and finding the minimum and maximum timestamps, grouped by `process_exec`, `proctitle`, `normalized_proctitle_delimiter`, and `dest`.\\n- The macros `security_content_ctime` and `linux_auditd_change_file_owner_to_root_filter` are placeholders for the corresponding Splunk macros.\",\r\n \"Additional comment 2.0\"\r\n ],\r\n \"translation_result\": \"full\",\r\n \"id\": \"{{rule_migration_id_1}}\"\r\n },\r\n {\r\n \"created_by\": \"elastic2.0\",\r\n \"elastic_rule\": {\r\n \"severity\": \"high\",\r\n \"title\": \"Linux Auditd Change File Owner To Root (UPDATED)\"\r\n },\r\n \"id\": \"{{rule_migration_id_2}}\"\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f6ac2cf8603ca633070e719f69b4fcef45ea92cb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200815","number":200815,"mergeCommit":{"message":"[Rules migration] Add rules migrations update route (#11209) (#200815)\n\n## Summary\r\n\r\nChanges in this PR:\r\n* Added `update` route to handle bulk rule migrations docs updates\r\n* Exposed `id` field in `RuleMigration` object needed for ES bulk update\r\noperation\r\n* Updated SIEM migrations schemas to use `NonEmptyString` when it is\r\nneeded\r\n\r\n## Testing locally\r\n\r\nEnable the flag\r\n```\r\nxpack.securitySolution.enableExperimental: ['siemMigrationsEnabled']\r\n```\r\n\r\nCreate and start a rule migration. Then use `update` API to updated\r\ncorresponding docs.\r\n\r\ncURL request examples:\r\n\r\n<details>\r\n <summary>Rules migration `create` POST request</summary>\r\n\r\n```\r\ncurl --location --request POST 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '[\r\n {\r\n \"id\": \"f8c325ea-506e-4105-8ccf-da1492e90115\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Add User Account Type\",\r\n \"description\": \"The following analytic detects the suspicious add user account type. This behavior is critical for a SOC to monitor because it may indicate attempts to gain unauthorized access or maintain control over a system. Such actions could be signs of malicious activity. If confirmed, this could lead to serious consequences, including a compromised system, unauthorized access to sensitive data, or even a wider breach affecting the entire network. Detecting and responding to these signs early is essential to prevent potential security incidents.\",\r\n \"query\": \"sourcetype=\\\"linux:audit\\\" type=ADD_USER \\n| rename hostname as dest \\n| stats count min(_time) as firstTime max(_time) as lastTime by exe pid dest res UID type \\n| `security_content_ctime(firstTime)` \\n| `security_content_ctime(lastTime)`\\n| search *\",\r\n \"query_language\":\"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1136\"\r\n ]\r\n },\r\n {\r\n \"id\": \"7b87c556-0ca4-47e0-b84c-6cd62a0a3e90\",\r\n \"vendor\": \"splunk\",\r\n \"title\": \"Linux Auditd Change File Owner To Root\",\r\n \"description\": \"The following analytic detects the use of the '\\''chown'\\'' command to change a file owner to '\\''root'\\'' on a Linux system. It leverages Linux Auditd telemetry, specifically monitoring command-line executions and process details. This activity is significant as it may indicate an attempt to escalate privileges by adversaries, malware, or red teamers. If confirmed malicious, this action could allow an attacker to gain root-level access, leading to full control over the compromised host and potential persistence within the environment.\",\r\n \"query\": \"`linux_auditd` `linux_auditd_normalized_proctitle_process`\\r\\n| rename host as dest \\r\\n| where LIKE (process_exec, \\\"%chown %root%\\\") \\r\\n| stats count min(_time) as firstTime max(_time) as lastTime by process_exec proctitle normalized_proctitle_delimiter dest \\r\\n| `security_content_ctime(firstTime)` \\r\\n| `security_content_ctime(lastTime)`\\r\\n| `linux_auditd_change_file_owner_to_root_filter`\",\r\n \"query_language\": \"spl\",\r\n \"mitre_attack_ids\": [\r\n \"T1222\"\r\n ]\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `start` task request</summary>\r\n\r\n- Assuming the connector `azureOpenAiGPT4o` is already created in the\r\nlocal environment.\r\n- Using the {{`migration_id`}} from the first POST request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}/start' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \\\r\n--header 'Content-Type: application/json' \\\r\n--data '{\r\n \"connectorId\": \"azureOpenAiGPT4o\"\r\n}'\r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration rules documents request</summary>\r\n\r\n- Using the {{`migration_id`}} from the first POST request response.\r\n\r\n```\r\ncurl --location --request GET 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules/{{migration_id}}' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n```\r\n</details>\r\n\r\n<details>\r\n <summary>Rules migration `update` PUT request</summary>\r\n\r\n- Using the {{`rule_migration_id_1`}} and {{`rule_migration_id_2`}} from\r\nprevious GET request response\r\n\r\n```\r\ncurl --location --request PUT 'http://elastic:changeme@localhost:5601/internal/siem_migrations/rules' \\\r\n--header 'kbn-xsrf;' \\\r\n--header 'x-elastic-internal-origin: security-solution' \\\r\n--header 'elastic-api-version: 1' \r\n--data '[\r\n {\r\n \"comments\": [\r\n \"## Migration Summary\\n- The `FROM` command is used to select the `logs-*` index pattern.\\n- The `RENAME` command is used to rename the `host` field to `dest`.\\n- The `WHERE` command filters the rows where `process_exec` contains the pattern `*chown *root*`.\\n- The `STATS` command is used to aggregate the data, counting the number of occurrences and finding the minimum and maximum timestamps, grouped by `process_exec`, `proctitle`, `normalized_proctitle_delimiter`, and `dest`.\\n- The macros `security_content_ctime` and `linux_auditd_change_file_owner_to_root_filter` are placeholders for the corresponding Splunk macros.\",\r\n \"Additional comment 2.0\"\r\n ],\r\n \"translation_result\": \"full\",\r\n \"id\": \"{{rule_migration_id_1}}\"\r\n },\r\n {\r\n \"created_by\": \"elastic2.0\",\r\n \"elastic_rule\": {\r\n \"severity\": \"high\",\r\n \"title\": \"Linux Auditd Change File Owner To Root (UPDATED)\"\r\n },\r\n \"id\": \"{{rule_migration_id_2}}\"\r\n }\r\n]'\r\n```\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"f6ac2cf8603ca633070e719f69b4fcef45ea92cb"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
784cbc8f8b
|
[8.x] [Dataset Quality] Fix Privilege Failing Test (#200890) (#200906)
# Backport This will backport the following commits from `main` to `8.x`: - [[Dataset Quality] Fix Privilege Failing Test (#200890)](https://github.com/elastic/kibana/pull/200890) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"mohamedhamed-ahmed","email":"mohamed.ahmed@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T12:29:27Z","message":"[Dataset Quality] Fix Privilege Failing Test (#200890)\n\ncloses https://github.com/elastic/kibana/issues/198865","sha":"8c7724fe9a89393ab2a990a097a0a109344ce888","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-logs","backport:version","v8.17.0","v8.16.1"],"title":"[Dataset Quality] Fix Privilege Failing Test","number":200890,"url":"https://github.com/elastic/kibana/pull/200890","mergeCommit":{"message":"[Dataset Quality] Fix Privilege Failing Test (#200890)\n\ncloses https://github.com/elastic/kibana/issues/198865","sha":"8c7724fe9a89393ab2a990a097a0a109344ce888"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200890","number":200890,"mergeCommit":{"message":"[Dataset Quality] Fix Privilege Failing Test (#200890)\n\ncloses https://github.com/elastic/kibana/issues/198865","sha":"8c7724fe9a89393ab2a990a097a0a109344ce888"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: mohamedhamed-ahmed <mohamed.ahmed@elastic.co> |
||
|
Kibana Machine
|
4bbe24c0c3
|
[8.x] [APM] Migrate service group alert test (#200789) (#200894)
# Backport This will backport the following commits from `main` to `8.x`: - [[APM] Migrate service group alert test (#200789)](https://github.com/elastic/kibana/pull/200789) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-20T10:58:45Z","message":"[APM] Migrate service group alert test (#200789)\n\ncloses https://github.com/elastic/kibana/issues/198982\r\n\r\n## Summary\r\n\r\nMigrates a test covering alerts on service group feature. It's possible\r\nto migrate it with `alertingApi` service.\r\n\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM\"\r\n```\r\n\r\n- [ ] ~(OPTIONAL, only if a test has been unskipped) Run flaky test\r\nsuite~\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless","sha":"8ba6839715bcd69440ca9dc5be448bc5e95b4475","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[APM] Migrate service group alert test","number":200789,"url":"https://github.com/elastic/kibana/pull/200789","mergeCommit":{"message":"[APM] Migrate service group alert test (#200789)\n\ncloses https://github.com/elastic/kibana/issues/198982\r\n\r\n## Summary\r\n\r\nMigrates a test covering alerts on service group feature. It's possible\r\nto migrate it with `alertingApi` service.\r\n\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM\"\r\n```\r\n\r\n- [ ] ~(OPTIONAL, only if a test has been unskipped) Run flaky test\r\nsuite~\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless","sha":"8ba6839715bcd69440ca9dc5be448bc5e95b4475"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200789","number":200789,"mergeCommit":{"message":"[APM] Migrate service group alert test (#200789)\n\ncloses https://github.com/elastic/kibana/issues/198982\r\n\r\n## Summary\r\n\r\nMigrates a test covering alerts on service group feature. It's possible\r\nto migrate it with `alertingApi` service.\r\n\r\n\r\n### How to test\r\n\r\n- Serverless\r\n\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.serverless.config.ts --grep=\"APM\"\r\n```\r\n\r\nIt's recommended to be run against\r\n[MKI](https://github.com/crespocarlos/kibana/blob/main/x-pack/test_serverless/README.md#run-tests-on-mki)\r\n\r\n- Stateful\r\n```\r\nnode scripts/functional_tests_server --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts\r\nnode scripts/functional_test_runner --config x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts --grep=\"APM\"\r\n```\r\n\r\n- [ ] ~(OPTIONAL, only if a test has been unskipped) Run flaky test\r\nsuite~\r\n- [x] local run for serverless\r\n- [x] local run for stateful\r\n- [x] MKI run for serverless","sha":"8ba6839715bcd69440ca9dc5be448bc5e95b4475"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
Robert Jaszczurek
|
336e6fe563
|
[8.x] [ML] AiOps: Action for adding Log Rate analysis embeddable to a dashboard (#200557) (#200891)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] AiOps: Action for adding Log Rate analysis embeddable to a dashboard (#200557)](https://github.com/elastic/kibana/pull/200557) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Jaszczurek","email":"92210485+rbrtj@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-20T00:29:40Z","message":"[ML] AiOps: Action for adding Log Rate analysis embeddable to a dashboard (#200557)\n\n## Summary\r\n\r\nPart of: [#197247](https://github.com/elastic/kibana/issues/197247)\r\n\r\n- Added the ability to add a Log Rate Analysis embeddable to a dashboard\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/37efd83e-9196-434d-a80d-9249623f3222\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"50a262692fc55ea513f1781eee9d14a7073f0368","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","v9.0.0","Team:ML","Feature:ML/AIOps","backport:version","v8.17.0"],"number":200557,"url":"https://github.com/elastic/kibana/pull/200557","mergeCommit":{"message":"[ML] AiOps: Action for adding Log Rate analysis embeddable to a dashboard (#200557)\n\n## Summary\r\n\r\nPart of: [#197247](https://github.com/elastic/kibana/issues/197247)\r\n\r\n- Added the ability to add a Log Rate Analysis embeddable to a dashboard\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/37efd83e-9196-434d-a80d-9249623f3222\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"50a262692fc55ea513f1781eee9d14a7073f0368"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200557","number":200557,"mergeCommit":{"message":"[ML] AiOps: Action for adding Log Rate analysis embeddable to a dashboard (#200557)\n\n## Summary\r\n\r\nPart of: [#197247](https://github.com/elastic/kibana/issues/197247)\r\n\r\n- Added the ability to add a Log Rate Analysis embeddable to a dashboard\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/37efd83e-9196-434d-a80d-9249623f3222\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"50a262692fc55ea513f1781eee9d14a7073f0368"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200835","number":200835,"state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
2bfbf58e0e
|
[8.x] [Discover][Field caps] Align with the ES responses for closed indices (#199717) (#200697)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover][Field caps] Align with the ES responses for closed indices (#199717)](https://github.com/elastic/kibana/pull/199717) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2024-11-19T10:42:28Z","message":"[Discover][Field caps] Align with the ES responses for closed indices (#199717)\n\n- Closes: https://github.com/elastic/kibana/issues/199413\r\n- Related: https://github.com/elastic/kibana/pull/199654\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116021\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116656\r\n\r\n## Summary\r\n\r\nThis PR unskips tests and updates the Kibana API to the updated ES\r\nresponses.\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":"f61c043bf6b00c26a2226537d6d7ad14a1dbc1c9","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"[Discover][Field caps] Align with the ES responses for closed indices","number":199717,"url":"https://github.com/elastic/kibana/pull/199717","mergeCommit":{"message":"[Discover][Field caps] Align with the ES responses for closed indices (#199717)\n\n- Closes: https://github.com/elastic/kibana/issues/199413\r\n- Related: https://github.com/elastic/kibana/pull/199654\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116021\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116656\r\n\r\n## Summary\r\n\r\nThis PR unskips tests and updates the Kibana API to the updated ES\r\nresponses.\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":"f61c043bf6b00c26a2226537d6d7ad14a1dbc1c9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199717","number":199717,"mergeCommit":{"message":"[Discover][Field caps] Align with the ES responses for closed indices (#199717)\n\n- Closes: https://github.com/elastic/kibana/issues/199413\r\n- Related: https://github.com/elastic/kibana/pull/199654\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116021\r\n- Related ES PR: https://github.com/elastic/elasticsearch/pull/116656\r\n\r\n## Summary\r\n\r\nThis PR unskips tests and updates the Kibana API to the updated ES\r\nresponses.\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":"f61c043bf6b00c26a2226537d6d7ad14a1dbc1c9"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Dario Gieselaar
|
b7d06a222e
|
[8.x] [Observability] Split up observability-utils package (#199801) (#200886)
# Backport This will backport the following commits from `main` to `8.x`: - [[Observability] Split up observability-utils package (#199801)](https://github.com/elastic/kibana/pull/199801) <!--- Backport version: 8.9.8 --> ### 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":"2024-11-13T18:51:42Z","message":"[Observability] Split up observability-utils package (#199801)\n\nSplit up observability-utils package in browser, common, server. Also\r\nmade a small change to `withSpan` to automatically log operation times\r\nwhen the debug level for the logger is enabled.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"11a752da8751f447a083f050e0c4eeb85073fa56","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.17.0","v8.18.0"],"number":199801,"url":"https://github.com/elastic/kibana/pull/199801","mergeCommit":{"message":"[Observability] Split up observability-utils package (#199801)\n\nSplit up observability-utils package in browser, common, server. Also\r\nmade a small change to `withSpan` to automatically log operation times\r\nwhen the debug level for the logger is enabled.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"11a752da8751f447a083f050e0c4eeb85073fa56"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199801","number":199801,"mergeCommit":{"message":"[Observability] Split up observability-utils package (#199801)\n\nSplit up observability-utils package in browser, common, server. Also\r\nmade a small change to `withSpan` to automatically log operation times\r\nwhen the debug level for the logger is enabled.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"11a752da8751f447a083f050e0c4eeb85073fa56"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
71cf9c8305
|
[8.x] Add @elastic/request-converter to renovate.json (#200588) (#200884)
# Backport This will backport the following commits from `main` to `8.x`: - [Add @elastic/request-converter to renovate.json (#200588)](https://github.com/elastic/kibana/pull/200588) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ignacio Rivas","email":"rivasign@gmail.com"},"sourceCommit":{"committedDate":"2024-11-20T10:23:38Z","message":"Add @elastic/request-converter to renovate.json (#200588)","sha":"0bb62939f09b98ea51cbf998e60f5e796d6176f2","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Add @elastic/request-converter to renovate.json ","number":200588,"url":"https://github.com/elastic/kibana/pull/200588","mergeCommit":{"message":"Add @elastic/request-converter to renovate.json (#200588)","sha":"0bb62939f09b98ea51cbf998e60f5e796d6176f2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200588","number":200588,"mergeCommit":{"message":"Add @elastic/request-converter to renovate.json (#200588)","sha":"0bb62939f09b98ea51cbf998e60f5e796d6176f2"}}]}] BACKPORT--> Co-authored-by: Ignacio Rivas <rivasign@gmail.com> |
||
|
Kibana Machine
|
5bd5fe02e5
|
[8.x] [Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available (#200621) (#200877)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available (#200621)](https://github.com/elastic/kibana/pull/200621) <!--- Backport version: 9.4.3 --> ### 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":"2024-11-20T10:00:16Z","message":"[Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available (#200621)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11117\r\n\r\n### How to test\r\n\r\n\r\n1. Create a deployment with cold and frozen data tiers and use following\r\ncommands to create index and ILM\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n```JSON\r\n\r\nPUT /_cluster/settings\r\n{\r\n \"persistent\": {\r\n \"indices.lifecycle.poll_interval\": \"10s\"\r\n }\r\n}\r\n\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"10s\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /_index_template/filtering_data_tiers_template\r\n{\r\n \"index_patterns\": [\r\n \"filtering_data_tiers*\"\r\n ],\r\n \"template\": {\r\n \"settings\": {\r\n \"index.lifecycle.name\": \"filtering_data_tiers\",\r\n \"index.lifecycle.rollover_alias\": \"test-filtering_data_tiers\"\r\n },\r\n \"mappings\": {\r\n \"_meta\": {\r\n \"version\": \"1.6.0\"\r\n },\r\n \"properties\": {\r\n \"@timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"host\": {\r\n \"properties\": {\r\n \"name\": {\r\n \"type\": \"keyword\",\r\n \"ignore_above\": 1024\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\nPUT /filtering_data_tiers-000001\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-07-08T17:00:01.000Z\",\r\n \"host.name\": \"test-0\"\r\n}\r\n\r\n\r\n```\r\n\r\n</details>\r\n\r\n2. Wait until document moves to frozen tier\r\n3. Run another set of commands to persist document in hot tier\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n\r\n```JSON\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"100h\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /filtering_data_tiers-000002\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-11-08T17:00:01.000Z\",\r\n \"host.name\": \"test-1\"\r\n}\r\n\r\n\r\n```\r\n</details>\r\n\r\n4. Pause frozen tier node (admin permissions needed for this) or\r\nincrease memory of it, forcing node to become unavailable for short\r\nperiod of time.\r\n5. Run IM rule with [advanced\r\nsetting](https://www.elastic.co/guide/en/security/current/advanced-settings.html#exclude-cold-frozen-data-rule-executions)\r\nfiltering out frozen data tier\r\n6. Rule should not fail and generate an alert from document in a hot\r\ntier\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee397d66b8325f25582eb610826991365a4b5f71","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team:Detection Engine","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available","number":200621,"url":"https://github.com/elastic/kibana/pull/200621","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available (#200621)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11117\r\n\r\n### How to test\r\n\r\n\r\n1. Create a deployment with cold and frozen data tiers and use following\r\ncommands to create index and ILM\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n```JSON\r\n\r\nPUT /_cluster/settings\r\n{\r\n \"persistent\": {\r\n \"indices.lifecycle.poll_interval\": \"10s\"\r\n }\r\n}\r\n\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"10s\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /_index_template/filtering_data_tiers_template\r\n{\r\n \"index_patterns\": [\r\n \"filtering_data_tiers*\"\r\n ],\r\n \"template\": {\r\n \"settings\": {\r\n \"index.lifecycle.name\": \"filtering_data_tiers\",\r\n \"index.lifecycle.rollover_alias\": \"test-filtering_data_tiers\"\r\n },\r\n \"mappings\": {\r\n \"_meta\": {\r\n \"version\": \"1.6.0\"\r\n },\r\n \"properties\": {\r\n \"@timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"host\": {\r\n \"properties\": {\r\n \"name\": {\r\n \"type\": \"keyword\",\r\n \"ignore_above\": 1024\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\nPUT /filtering_data_tiers-000001\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-07-08T17:00:01.000Z\",\r\n \"host.name\": \"test-0\"\r\n}\r\n\r\n\r\n```\r\n\r\n</details>\r\n\r\n2. Wait until document moves to frozen tier\r\n3. Run another set of commands to persist document in hot tier\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n\r\n```JSON\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"100h\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /filtering_data_tiers-000002\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-11-08T17:00:01.000Z\",\r\n \"host.name\": \"test-1\"\r\n}\r\n\r\n\r\n```\r\n</details>\r\n\r\n4. Pause frozen tier node (admin permissions needed for this) or\r\nincrease memory of it, forcing node to become unavailable for short\r\nperiod of time.\r\n5. Run IM rule with [advanced\r\nsetting](https://www.elastic.co/guide/en/security/current/advanced-settings.html#exclude-cold-frozen-data-rule-executions)\r\nfiltering out frozen data tier\r\n6. Rule should not fail and generate an alert from document in a hot\r\ntier\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee397d66b8325f25582eb610826991365a4b5f71"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200621","number":200621,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes IM rule failure when frozen tier node is not available (#200621)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11117\r\n\r\n### How to test\r\n\r\n\r\n1. Create a deployment with cold and frozen data tiers and use following\r\ncommands to create index and ILM\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n```JSON\r\n\r\nPUT /_cluster/settings\r\n{\r\n \"persistent\": {\r\n \"indices.lifecycle.poll_interval\": \"10s\"\r\n }\r\n}\r\n\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"10s\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /_index_template/filtering_data_tiers_template\r\n{\r\n \"index_patterns\": [\r\n \"filtering_data_tiers*\"\r\n ],\r\n \"template\": {\r\n \"settings\": {\r\n \"index.lifecycle.name\": \"filtering_data_tiers\",\r\n \"index.lifecycle.rollover_alias\": \"test-filtering_data_tiers\"\r\n },\r\n \"mappings\": {\r\n \"_meta\": {\r\n \"version\": \"1.6.0\"\r\n },\r\n \"properties\": {\r\n \"@timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"host\": {\r\n \"properties\": {\r\n \"name\": {\r\n \"type\": \"keyword\",\r\n \"ignore_above\": 1024\r\n }\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\nPUT /filtering_data_tiers-000001\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-07-08T17:00:01.000Z\",\r\n \"host.name\": \"test-0\"\r\n}\r\n\r\n\r\n```\r\n\r\n</details>\r\n\r\n2. Wait until document moves to frozen tier\r\n3. Run another set of commands to persist document in hot tier\r\n\r\n<details>\r\n<summary>Data tiers commands</summary>\r\n\r\n\r\n```JSON\r\n\r\nPUT /_ilm/policy/filtering_data_tiers\r\n{\r\n \"policy\": {\r\n \"phases\": {\r\n \"frozen\": {\r\n \"min_age\": \"100h\",\r\n \"actions\": {\r\n \"searchable_snapshot\": {\r\n \"snapshot_repository\": \"found-snapshots\",\r\n \"force_merge_index\": true\r\n }\r\n }\r\n },\r\n \"hot\": {\r\n \"min_age\": \"0ms\",\r\n \"actions\": {\r\n \"set_priority\": {\r\n \"priority\": 100\r\n }\r\n }\r\n }\r\n }\r\n }\r\n}\r\n\r\n\r\nPUT /filtering_data_tiers-000002\r\n{\r\n \"aliases\": {\r\n \"filtering_data_tiers\": {\r\n \"is_write_index\": true\r\n }\r\n }\r\n}\r\n\r\n\r\nPOST filtering_data_tiers/_doc\r\n{\r\n \"@timestamp\": \"2024-11-08T17:00:01.000Z\",\r\n \"host.name\": \"test-1\"\r\n}\r\n\r\n\r\n```\r\n</details>\r\n\r\n4. Pause frozen tier node (admin permissions needed for this) or\r\nincrease memory of it, forcing node to become unavailable for short\r\nperiod of time.\r\n5. Run IM rule with [advanced\r\nsetting](https://www.elastic.co/guide/en/security/current/advanced-settings.html#exclude-cold-frozen-data-rule-executions)\r\nfiltering out frozen data tier\r\n6. Rule should not fail and generate an alert from document in a hot\r\ntier\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee397d66b8325f25582eb610826991365a4b5f71"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
06fec91d91
|
[8.x] Add terminate processor (#199674) (#200874)
# Backport This will backport the following commits from `main` to `8.x`: - [Add terminate processor (#199674)](https://github.com/elastic/kibana/pull/199674) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sonia Sanz Vivas","email":"sonia.sanzvivas@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T09:52:43Z","message":"Add terminate processor (#199674)\n\nCloses [#195782](https://github.com/elastic/kibana/issues/195782)\r\n## Summary\r\n\r\nThis PR adds UI support for the Terminate Processor\r\n[[docs](https://www.elastic.co/guide/en/elasticsearch/reference/master/terminate-processor.html)].\r\nThis processor only has the default fields.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/12b5e677-78e8-4f40-8427-e2482b47249a","sha":"b320a37d8b703b2fa101a93b6971b36ee2c37f06","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","Feature:Ingest Node Pipelines","backport:prev-minor"],"title":"Add terminate processor","number":199674,"url":"https://github.com/elastic/kibana/pull/199674","mergeCommit":{"message":"Add terminate processor (#199674)\n\nCloses [#195782](https://github.com/elastic/kibana/issues/195782)\r\n## Summary\r\n\r\nThis PR adds UI support for the Terminate Processor\r\n[[docs](https://www.elastic.co/guide/en/elasticsearch/reference/master/terminate-processor.html)].\r\nThis processor only has the default fields.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/12b5e677-78e8-4f40-8427-e2482b47249a","sha":"b320a37d8b703b2fa101a93b6971b36ee2c37f06"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199674","number":199674,"mergeCommit":{"message":"Add terminate processor (#199674)\n\nCloses [#195782](https://github.com/elastic/kibana/issues/195782)\r\n## Summary\r\n\r\nThis PR adds UI support for the Terminate Processor\r\n[[docs](https://www.elastic.co/guide/en/elasticsearch/reference/master/terminate-processor.html)].\r\nThis processor only has the default fields.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/12b5e677-78e8-4f40-8427-e2482b47249a","sha":"b320a37d8b703b2fa101a93b6971b36ee2c37f06"}}]}] BACKPORT--> Co-authored-by: Sonia Sanz Vivas <sonia.sanzvivas@elastic.co> |
||
|
Kibana Machine
|
e79aa82e89
|
[8.x] [ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes (#200559) (#200872)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes (#200559)](https://github.com/elastic/kibana/pull/200559) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T09:37:27Z","message":"[ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes (#200559)\n\nCloses https://github.com/elastic/kibana/issues/153606\r\n\r\n## Summary\r\n\r\n- the \"Discard unsaved changes\" warning was triggered unnecessarily when\r\nthe user clicked on \"Cancel\" or \"X\" on the edit rule form without making\r\nany changes. The problem was caused by the \"touched\" property of\r\n\"useRuleFormState\" being set to true by default when the page was\r\nopened.\r\n- updated the logic so that \"touched\" is only set to true if actual\r\nchanges are made\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b20b5c94-5d53-42cd-a7cf-5f951a1ed43e","sha":"caee6c658551001565bb465b943539b84dd4e725","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-minor","v8.17.0"],"title":"[ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes","number":200559,"url":"https://github.com/elastic/kibana/pull/200559","mergeCommit":{"message":"[ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes (#200559)\n\nCloses https://github.com/elastic/kibana/issues/153606\r\n\r\n## Summary\r\n\r\n- the \"Discard unsaved changes\" warning was triggered unnecessarily when\r\nthe user clicked on \"Cancel\" or \"X\" on the edit rule form without making\r\nany changes. The problem was caused by the \"touched\" property of\r\n\"useRuleFormState\" being set to true by default when the page was\r\nopened.\r\n- updated the logic so that \"touched\" is only set to true if actual\r\nchanges are made\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b20b5c94-5d53-42cd-a7cf-5f951a1ed43e","sha":"caee6c658551001565bb465b943539b84dd4e725"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200559","number":200559,"mergeCommit":{"message":"[ResponseOps][Rules]Discard unsaved changes warning gets triggered unnecessarily when user clicks on cancel or x without making any changes (#200559)\n\nCloses https://github.com/elastic/kibana/issues/153606\r\n\r\n## Summary\r\n\r\n- the \"Discard unsaved changes\" warning was triggered unnecessarily when\r\nthe user clicked on \"Cancel\" or \"X\" on the edit rule form without making\r\nany changes. The problem was caused by the \"touched\" property of\r\n\"useRuleFormState\" being set to true by default when the page was\r\nopened.\r\n- updated the logic so that \"touched\" is only set to true if actual\r\nchanges are made\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b20b5c94-5d53-42cd-a7cf-5f951a1ed43e","sha":"caee6c658551001565bb465b943539b84dd4e725"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co> |
||
|
Kibana Machine
|
7126046618
|
[8.x] [Discover] Unskip get_render_app_wrapper test (#199456) (#200868)
# Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Unskip get_render_app_wrapper test (#199456)](https://github.com/elastic/kibana/pull/199456) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2024-11-20T09:19:24Z","message":"[Discover] Unskip get_render_app_wrapper test (#199456)\n\n- Closes https://github.com/elastic/kibana/issues/199356","sha":"b512ee4803f4383f4592dc1cc015f5c550866130","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor"],"title":"[Discover] Unskip get_render_app_wrapper test","number":199456,"url":"https://github.com/elastic/kibana/pull/199456","mergeCommit":{"message":"[Discover] Unskip get_render_app_wrapper test (#199456)\n\n- Closes https://github.com/elastic/kibana/issues/199356","sha":"b512ee4803f4383f4592dc1cc015f5c550866130"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199456","number":199456,"mergeCommit":{"message":"[Discover] Unskip get_render_app_wrapper test (#199456)\n\n- Closes https://github.com/elastic/kibana/issues/199356","sha":"b512ee4803f4383f4592dc1cc015f5c550866130"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
