mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
34554 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
bc4427bfeb
|
[8.16] [Security Solution] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint (#199388) (#200095)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint (#199388)](https://github.com/elastic/kibana/pull/199388) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-13T20:59:15Z","message":"[Security Solution] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint (#199388)\n\n**Fixes https://github.com/elastic/kibana/issues/199290**\r\n\r\n## Summary\r\n\r\nThe current multi-line string algorithm uses a very inefficient regex to\r\nsplit and analyze string fields, and exponentially increases in time\r\ncomplexity when the strings are long. This PR substitutes a much simpler\r\ncomparison regex for far better efficiency as shown in the table below.\r\n\r\n### Performance between different regex options using sample prebuilt\r\nrule setup guide string\r\n\r\n| | `/(\\S+\\|\\s+)/g` (original) | `/(\\s+)/g` | `/(\\n)/g` |\r\n`/(\\r\\n\\|\\n\\|\\r)/g` |\r\n\r\n|-----------------------|---------------|----------|---------|-------------------|\r\n| Unit test speed | `986ms` | `96ms` | `1ms` | `2ms` |\r\n| FTR test with 1 rule | `3.0s` | `2.8s` | `2.0s` | `2.0s` |\r\n| FTR test with 5 rules | `11.6s` | `6.8s` | `6.1s` | |\r\n\r\n\r\n### Performance between different regex options using intentionally long\r\nstrings (25k characters)\r\n\r\n| | `/(\\S+\\|\\s+)/g` | `/(\\r\\n\\|\\n\\|\\r)/g` |\r\n|----------------------|-----------------------|---------------------|\r\n| Unit test speed | `1049414ms` (17 min) | `58ms` |\r\n| FTR test with 1 rule | `>360000ms` (Timeout) | `2.1 s` |\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"4f6d3570c59d30951368f601b2b59ab3b7a1ae4c","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:critical","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] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint","number":199388,"url":"https://github.com/elastic/kibana/pull/199388","mergeCommit":{"message":"[Security Solution] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint (#199388)\n\n**Fixes https://github.com/elastic/kibana/issues/199290**\r\n\r\n## Summary\r\n\r\nThe current multi-line string algorithm uses a very inefficient regex to\r\nsplit and analyze string fields, and exponentially increases in time\r\ncomplexity when the strings are long. This PR substitutes a much simpler\r\ncomparison regex for far better efficiency as shown in the table below.\r\n\r\n### Performance between different regex options using sample prebuilt\r\nrule setup guide string\r\n\r\n| | `/(\\S+\\|\\s+)/g` (original) | `/(\\s+)/g` | `/(\\n)/g` |\r\n`/(\\r\\n\\|\\n\\|\\r)/g` |\r\n\r\n|-----------------------|---------------|----------|---------|-------------------|\r\n| Unit test speed | `986ms` | `96ms` | `1ms` | `2ms` |\r\n| FTR test with 1 rule | `3.0s` | `2.8s` | `2.0s` | `2.0s` |\r\n| FTR test with 5 rules | `11.6s` | `6.8s` | `6.1s` | |\r\n\r\n\r\n### Performance between different regex options using intentionally long\r\nstrings (25k characters)\r\n\r\n| | `/(\\S+\\|\\s+)/g` | `/(\\r\\n\\|\\n\\|\\r)/g` |\r\n|----------------------|-----------------------|---------------------|\r\n| Unit test speed | `1049414ms` (17 min) | `58ms` |\r\n| FTR test with 1 rule | `>360000ms` (Timeout) | `2.1 s` |\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"4f6d3570c59d30951368f601b2b59ab3b7a1ae4c"}},"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/199388","number":199388,"mergeCommit":{"message":"[Security Solution] Fixes multi-line diff algorithm performance in the `upgrade/_review` endpoint (#199388)\n\n**Fixes https://github.com/elastic/kibana/issues/199290**\r\n\r\n## Summary\r\n\r\nThe current multi-line string algorithm uses a very inefficient regex to\r\nsplit and analyze string fields, and exponentially increases in time\r\ncomplexity when the strings are long. This PR substitutes a much simpler\r\ncomparison regex for far better efficiency as shown in the table below.\r\n\r\n### Performance between different regex options using sample prebuilt\r\nrule setup guide string\r\n\r\n| | `/(\\S+\\|\\s+)/g` (original) | `/(\\s+)/g` | `/(\\n)/g` |\r\n`/(\\r\\n\\|\\n\\|\\r)/g` |\r\n\r\n|-----------------------|---------------|----------|---------|-------------------|\r\n| Unit test speed | `986ms` | `96ms` | `1ms` | `2ms` |\r\n| FTR test with 1 rule | `3.0s` | `2.8s` | `2.0s` | `2.0s` |\r\n| FTR test with 5 rules | `11.6s` | `6.8s` | `6.1s` | |\r\n\r\n\r\n### Performance between different regex options using intentionally long\r\nstrings (25k characters)\r\n\r\n| | `/(\\S+\\|\\s+)/g` | `/(\\r\\n\\|\\n\\|\\r)/g` |\r\n|----------------------|-----------------------|---------------------|\r\n| Unit test speed | `1049414ms` (17 min) | `58ms` |\r\n| FTR test with 1 rule | `>360000ms` (Timeout) | `2.1 s` |\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"4f6d3570c59d30951368f601b2b59ab3b7a1ae4c"}},{"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: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> |
||
|
Kibana Machine
|
f60eaef1fc
|
[8.16] [Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists (#198868) (#200085)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists (#198868)](https://github.com/elastic/kibana/pull/198868) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marshall Main","email":"55718608+marshallmain@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-13T20:01:18Z","message":"[Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists (#198868)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198461\r\n\r\nWhen a rule import file has both single-namespace and namespace-agnostic\r\nexception lists, there was a bug in the logic that fetched the existing\r\nexception lists after importing them. A missing set of parentheses\r\ncaused a KQL query that should have read `(A OR B) AND (C OR D)` to be\r\n`(A OR B) AND C OR D`, meaning that the logic was satisfied by `D` alone\r\ninstead of requiring `A` or `B` to be true along with `D`. In this case\r\n`A` and `B` are filters on `exception-list` and\r\n`exception-list-agnostic` SO attributes so that we (should) only be\r\nlooking at the list container objects, i.e.\r\n`exception-list.attributes.list_type: list`. `C` and `D` are filters by\r\n`list_id`, e.g. `exception-list.attributes.list_id: (test_list_id)`.\r\nWithout the extra parentheses around `C OR D`, the query finds both\r\n`list` and `item` documents for the list IDs specified in `D`.\r\n\r\nWhen the `findExceptionList` logic encounters a list item unexpectedly,\r\nit still tries to convert the SO into our internal representation of an\r\nexception list with `transformSavedObjectToExceptionList`. Most fields\r\nare shared between lists and items, which makes it confusing to debug.\r\nHowever, the `type` of items can only be `simple`, whereas lists have a\r\nvariety of types. During the conversion, the `type` field of the\r\nresulting object is defaulted to `detection` if the `type` field of the\r\nSO doesn't match the allowed list type values. Since the related SDH\r\ninvolved importing a `rule_default` exception list instead, the list\r\ntypes didn't match up when the import route compared the exception list\r\non the rule to import vs the \"existing list\" (which was actually a list\r\nitem coerced into a list container schema with `type: detection`) and\r\nimport fails.","sha":"0cc2e5677b46393ffd066ddaa1c548c664af311b","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","sdh-linked","backport:prev-major","v8.17.0"],"title":"[Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists","number":198868,"url":"https://github.com/elastic/kibana/pull/198868","mergeCommit":{"message":"[Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists (#198868)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198461\r\n\r\nWhen a rule import file has both single-namespace and namespace-agnostic\r\nexception lists, there was a bug in the logic that fetched the existing\r\nexception lists after importing them. A missing set of parentheses\r\ncaused a KQL query that should have read `(A OR B) AND (C OR D)` to be\r\n`(A OR B) AND C OR D`, meaning that the logic was satisfied by `D` alone\r\ninstead of requiring `A` or `B` to be true along with `D`. In this case\r\n`A` and `B` are filters on `exception-list` and\r\n`exception-list-agnostic` SO attributes so that we (should) only be\r\nlooking at the list container objects, i.e.\r\n`exception-list.attributes.list_type: list`. `C` and `D` are filters by\r\n`list_id`, e.g. `exception-list.attributes.list_id: (test_list_id)`.\r\nWithout the extra parentheses around `C OR D`, the query finds both\r\n`list` and `item` documents for the list IDs specified in `D`.\r\n\r\nWhen the `findExceptionList` logic encounters a list item unexpectedly,\r\nit still tries to convert the SO into our internal representation of an\r\nexception list with `transformSavedObjectToExceptionList`. Most fields\r\nare shared between lists and items, which makes it confusing to debug.\r\nHowever, the `type` of items can only be `simple`, whereas lists have a\r\nvariety of types. During the conversion, the `type` field of the\r\nresulting object is defaulted to `detection` if the `type` field of the\r\nSO doesn't match the allowed list type values. Since the related SDH\r\ninvolved importing a `rule_default` exception list instead, the list\r\ntypes didn't match up when the import route compared the exception list\r\non the rule to import vs the \"existing list\" (which was actually a list\r\nitem coerced into a list container schema with `type: detection`) and\r\nimport fails.","sha":"0cc2e5677b46393ffd066ddaa1c548c664af311b"}},"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/198868","number":198868,"mergeCommit":{"message":"[Security Solution][Detection Engine] Fix importing rules with multiple types of exception lists (#198868)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/198461\r\n\r\nWhen a rule import file has both single-namespace and namespace-agnostic\r\nexception lists, there was a bug in the logic that fetched the existing\r\nexception lists after importing them. A missing set of parentheses\r\ncaused a KQL query that should have read `(A OR B) AND (C OR D)` to be\r\n`(A OR B) AND C OR D`, meaning that the logic was satisfied by `D` alone\r\ninstead of requiring `A` or `B` to be true along with `D`. In this case\r\n`A` and `B` are filters on `exception-list` and\r\n`exception-list-agnostic` SO attributes so that we (should) only be\r\nlooking at the list container objects, i.e.\r\n`exception-list.attributes.list_type: list`. `C` and `D` are filters by\r\n`list_id`, e.g. `exception-list.attributes.list_id: (test_list_id)`.\r\nWithout the extra parentheses around `C OR D`, the query finds both\r\n`list` and `item` documents for the list IDs specified in `D`.\r\n\r\nWhen the `findExceptionList` logic encounters a list item unexpectedly,\r\nit still tries to convert the SO into our internal representation of an\r\nexception list with `transformSavedObjectToExceptionList`. Most fields\r\nare shared between lists and items, which makes it confusing to debug.\r\nHowever, the `type` of items can only be `simple`, whereas lists have a\r\nvariety of types. During the conversion, the `type` field of the\r\nresulting object is defaulted to `detection` if the `type` field of the\r\nSO doesn't match the allowed list type values. Since the related SDH\r\ninvolved importing a `rule_default` exception list instead, the list\r\ntypes didn't match up when the import route compared the exception list\r\non the rule to import vs the \"existing list\" (which was actually a list\r\nitem coerced into a list container schema with `type: detection`) and\r\nimport fails.","sha":"0cc2e5677b46393ffd066ddaa1c548c664af311b"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marshall Main <55718608+marshallmain@users.noreply.github.com> |
||
Andrew Macri
|
58dd0876a4
|
[8.16] [Security Solution] [Attack discovery] Additional Attack discovery tests (#199659) (#200066)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)](https://github.com/elastic/kibana/pull/199659) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T17:37:54Z","message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928","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:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"number":199659,"url":"https://github.com/elastic/kibana/pull/199659","mergeCommit":{"message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199659","number":199659,"mergeCommit":{"message":"[Security Solution] [Attack discovery] Additional Attack discovery tests (#199659)\n\n### [Security Solution] [Attack discovery] Additional Attack discovery tests\r\n\r\nThis PR adds additional unit test coverage to Attack discovery.","sha":"53d4580a8959a9e4b166df4e4a4cc83de61f7928"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200061","number":200061,"state":"OPEN"},{"branch":"8.16","label":"v8.16.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ecfb386daa
|
[8.16] fix(slo): Use correct calendar period (#199873) (#200068)
# Backport This will backport the following commits from `main` to `8.16`: - [fix(slo): Use correct calendar period (#199873)](https://github.com/elastic/kibana/pull/199873) <!--- 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-13T18:39:45Z","message":"fix(slo): Use correct calendar period (#199873)","sha":"3cbdcc3609269dcf109fe787359b2504203da229","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","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-management","v8.17.0"],"title":"fix(slo): Use correct calendar period","number":199873,"url":"https://github.com/elastic/kibana/pull/199873","mergeCommit":{"message":"fix(slo): Use correct calendar period (#199873)","sha":"3cbdcc3609269dcf109fe787359b2504203da229"}},"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/199873","number":199873,"mergeCommit":{"message":"fix(slo): Use correct calendar period (#199873)","sha":"3cbdcc3609269dcf109fe787359b2504203da229"}},{"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> |
||
Anderson Queiroz
|
7b24099281
|
[8.16] Remove functionbeat tutorial and translations (#199301) (#200057)
# Backport This will backport the following commits from `main` to `8.16`: - [Remove functionbeat tutorial and translations (#199301)](https://github.com/elastic/kibana/pull/199301) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anderson Queiroz","email":"anderson.queiroz@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T13:33:56Z","message":"Remove functionbeat tutorial and translations (#199301)\n\n## Summary\r\n\r\nRemove functionbeat tutorial and translations. It's been deprecated and won't be\r\nshipped on 9.0\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n### Risk Matrix\r\n\r\nI'm not sure, its just deleting code/documentation\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## Related issues\r\n\r\n- Relates https://github.com/elastic/beats/issues/40745\r\n- https://github.com/elastic/kibana/issues/193030","sha":"710c4cc9b147260f027e5103167599f7a0fcfdec","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","auto-backport-next","backport:prev-minor","ci:project-deploy-observability","v8.16.0","backport:version","v8.17.0"],"number":199301,"url":"https://github.com/elastic/kibana/pull/199301","mergeCommit":{"message":"Remove functionbeat tutorial and translations (#199301)\n\n## Summary\r\n\r\nRemove functionbeat tutorial and translations. It's been deprecated and won't be\r\nshipped on 9.0\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n### Risk Matrix\r\n\r\nI'm not sure, its just deleting code/documentation\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## Related issues\r\n\r\n- Relates https://github.com/elastic/beats/issues/40745\r\n- https://github.com/elastic/kibana/issues/193030","sha":"710c4cc9b147260f027e5103167599f7a0fcfdec"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199301","number":199301,"mergeCommit":{"message":"Remove functionbeat tutorial and translations (#199301)\n\n## Summary\r\n\r\nRemove functionbeat tutorial and translations. It's been deprecated and won't be\r\nshipped on 9.0\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n### Risk Matrix\r\n\r\nI'm not sure, its just deleting code/documentation\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## Related issues\r\n\r\n- Relates https://github.com/elastic/beats/issues/40745\r\n- https://github.com/elastic/kibana/issues/193030","sha":"710c4cc9b147260f027e5103167599f7a0fcfdec"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Carlos Crespo <carloshenrique.leonelcrespo@elastic.co> |
||
|
Kibana Machine
|
4143d06ac2
|
[8.16] Update the elastic-connectors docker namespace to integrations (#194537) (#200035)
# Backport This will backport the following commits from `main` to `8.16`: - [Update the elastic-connectors docker namespace to integrations (#194537)](https://github.com/elastic/kibana/pull/194537) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Chenhui Wang","email":"54903978+wangch079@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-13T15:57:15Z","message":"Update the elastic-connectors docker namespace to integrations (#194537)\n\n## Summary\r\n\r\nThis PR updates the `elastic-connectors` docker namespace to\r\n`integrations`\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9a33211acab2f6c7110498f53c4de33bb89cd59c","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.16.1"],"title":"Update the elastic-connectors docker namespace to integrations","number":194537,"url":"https://github.com/elastic/kibana/pull/194537","mergeCommit":{"message":"Update the elastic-connectors docker namespace to integrations (#194537)\n\n## Summary\r\n\r\nThis PR updates the `elastic-connectors` docker namespace to\r\n`integrations`\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9a33211acab2f6c7110498f53c4de33bb89cd59c"}},"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/194537","number":194537,"mergeCommit":{"message":"Update the elastic-connectors docker namespace to integrations (#194537)\n\n## Summary\r\n\r\nThis PR updates the `elastic-connectors` docker namespace to\r\n`integrations`\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9a33211acab2f6c7110498f53c4de33bb89cd59c"}},{"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: Chenhui Wang <54903978+wangch079@users.noreply.github.com> |
||
|
Kibana Machine
|
d2dbd4cd17
|
[8.16] [Index Mgmt] Improve accessibility of templates table (#199980) (#200030)
# Backport This will backport the following commits from `main` to `8.16`: - [[Index Mgmt] Improve accessibility of templates table (#199980)](https://github.com/elastic/kibana/pull/199980) <!--- 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-13T15:38:05Z","message":"[Index Mgmt] Improve accessibility of templates table (#199980)\n\n## Summary\r\n\r\nThis improves the accessibility and understandability of the content\r\ncolumn in the index templates page by:\r\n1) Improving the tooltip text to be explicit about whether something is\r\npresent or not\r\n2) Adding an aria-label with the same content, as tooltips are not\r\nkeyboard accessible\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))","sha":"20dd7f1bbe61e6263476228d2225d68871849e25","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","release_note:skip","v9.0.0","v8.16.0","backport:version","v8.17.0","v8.18.0"],"title":"[Index Mgmt] Improve accessibility of templates table","number":199980,"url":"https://github.com/elastic/kibana/pull/199980","mergeCommit":{"message":"[Index Mgmt] Improve accessibility of templates table (#199980)\n\n## Summary\r\n\r\nThis improves the accessibility and understandability of the content\r\ncolumn in the index templates page by:\r\n1) Improving the tooltip text to be explicit about whether something is\r\npresent or not\r\n2) Adding an aria-label with the same content, as tooltips are not\r\nkeyboard accessible\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))","sha":"20dd7f1bbe61e6263476228d2225d68871849e25"}},"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/199980","number":199980,"mergeCommit":{"message":"[Index Mgmt] Improve accessibility of templates table (#199980)\n\n## Summary\r\n\r\nThis improves the accessibility and understandability of the content\r\ncolumn in the index templates page by:\r\n1) Improving the tooltip text to be explicit about whether something is\r\npresent or not\r\n2) Adding an aria-label with the same content, as tooltips are not\r\nkeyboard accessible\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))","sha":"20dd7f1bbe61e6263476228d2225d68871849e25"}},{"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: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
4c5d5fa5a4
|
[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)
# Backport This will backport the following commits from `main` to `8.16`: - [[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","backport missing","v9.0.0","Team:Defend Workflows","backport:version","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.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 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.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co> |
||
Pablo Machado
|
ed6897409b
|
[8.16] [SecuritySolution] Improve asset criticality bulk error when entities are duplicated (#199651) (#199971)
# Backport This will backport the following commits from `main` to `8.16`: - [[SecuritySolution] Improve asset criticality bulk error when entities are duplicated (#199651)](https://github.com/elastic/kibana/pull/199651) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T10:22:44Z","message":"[SecuritySolution] Improve asset criticality bulk error when entities are duplicated (#199651)\n\n## Summary\r\n\r\n* Improve asset criticality bulk error when entities are duplicated\r\n* It also fixes the server errors line to be '1' based.\r\n\r\n\r\n\r\n### Performance\r\n\r\nTest parameters: file with +33k lines and ~1 MB size.\r\n* Before 6.24 seconds\r\n* After 6.46 seconds\r\n\r\nExecution time Increased ~0.22 seconds\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"02ac5fc90f08615d877befc05f9675838ade77b4","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","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.17.0","v8.16.1"],"number":199651,"url":"https://github.com/elastic/kibana/pull/199651","mergeCommit":{"message":"[SecuritySolution] Improve asset criticality bulk error when entities are duplicated (#199651)\n\n## Summary\r\n\r\n* Improve asset criticality bulk error when entities are duplicated\r\n* It also fixes the server errors line to be '1' based.\r\n\r\n\r\n\r\n### Performance\r\n\r\nTest parameters: file with +33k lines and ~1 MB size.\r\n* Before 6.24 seconds\r\n* After 6.46 seconds\r\n\r\nExecution time Increased ~0.22 seconds\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"02ac5fc90f08615d877befc05f9675838ade77b4"}},"sourceBranch":"main","suggestedTargetBranches":["8.16"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199651","number":199651,"mergeCommit":{"message":"[SecuritySolution] Improve asset criticality bulk error when entities are duplicated (#199651)\n\n## Summary\r\n\r\n* Improve asset criticality bulk error when entities are duplicated\r\n* It also fixes the server errors line to be '1' based.\r\n\r\n\r\n\r\n### Performance\r\n\r\nTest parameters: file with +33k lines and ~1 MB size.\r\n* Before 6.24 seconds\r\n* After 6.46 seconds\r\n\r\nExecution time Increased ~0.22 seconds\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"02ac5fc90f08615d877befc05f9675838ade77b4"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/199968","number":199968,"state":"OPEN"},{"branch":"8.16","label":"v8.16.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Lisa Cawley
|
5c55bf3644
|
[8.16] [DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325) (#199896)
# Backport This will backport the following commits from `main` to `8.16`: - [[DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)](https://github.com/elastic/kibana/pull/195325) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-10-17T23:14:34Z","message":"[DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)","sha":"7b106f7235e014563ed90721791d6516a9287d3f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:skip","v9.0.0","docs","Feature:Cases","v8.16.0","v8.17.0"],"number":195325,"url":"https://github.com/elastic/kibana/pull/195325","mergeCommit":{"message":"[DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)","sha":"7b106f7235e014563ed90721791d6516a9287d3f"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195325","number":195325,"mergeCommit":{"message":"[DOCS][OpenAPI] Change x-technical-preview to x-state in case APIs (#195325)","sha":"7b106f7235e014563ed90721791d6516a9287d3f"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Lisa Cawley
|
0a4ce9ea7e
|
[8.16] [OpenAPI][Fleet] Add missing operation summaries (#199548) (#199570)
# Backport This will backport the following commits from `main` to `8.16`: - [[OpenAPI][Fleet] Add missing operation summaries (#199548)](https://github.com/elastic/kibana/pull/199548) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T22:13:10Z","message":"[OpenAPI][Fleet] Add missing operation summaries (#199548)","sha":"ef0428ffec3084777a8ff82c7191f754bad5705f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"number":199548,"url":"https://github.com/elastic/kibana/pull/199548","mergeCommit":{"message":"[OpenAPI][Fleet] Add missing operation summaries (#199548)","sha":"ef0428ffec3084777a8ff82c7191f754bad5705f"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199548","number":199548,"mergeCommit":{"message":"[OpenAPI][Fleet] Add missing operation summaries (#199548)","sha":"ef0428ffec3084777a8ff82c7191f754bad5705f"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
ada6a792c3
|
[8.16] fix(slo): remove extra field from synthetics indicator params (#199542) (#199852)
# Backport This will backport the following commits from `main` to `8.16`: - [fix(slo): remove extra field from synthetics indicator params (#199542)](https://github.com/elastic/kibana/pull/199542) <!--- 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-12T18:15:02Z","message":"fix(slo): remove extra field from synthetics indicator params (#199542)","sha":"eea4a204e40869a584f485ed52ed350f65cb57c9","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","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-management","v8.17.0"],"title":"fix(slo): remove extra field from synthetics indicator params","number":199542,"url":"https://github.com/elastic/kibana/pull/199542","mergeCommit":{"message":"fix(slo): remove extra field from synthetics indicator params (#199542)","sha":"eea4a204e40869a584f485ed52ed350f65cb57c9"}},"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/199542","number":199542,"mergeCommit":{"message":"fix(slo): remove extra field from synthetics indicator params (#199542)","sha":"eea4a204e40869a584f485ed52ed350f65cb57c9"}},{"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
|
da4d4af48a
|
[8.16] [DOCS] Remove inference connector docs (#198633) (#199845)
# Backport This will backport the following commits from `main` to `8.16`: - [[DOCS] Remove inference connector docs (#198633)](https://github.com/elastic/kibana/pull/198633) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-11-12T17:56:37Z","message":"[DOCS] Remove inference connector docs (#198633)","sha":"517063d0a42283b74b9ba15679bf4d7af393effb","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","docs","Feature:Actions/ConnectorTypes","v8.16.0","backport:version","v8.17.0"],"title":"[DOCS] Remove inference connector docs","number":198633,"url":"https://github.com/elastic/kibana/pull/198633","mergeCommit":{"message":"[DOCS] Remove inference connector docs (#198633)","sha":"517063d0a42283b74b9ba15679bf4d7af393effb"}},"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/198633","number":198633,"mergeCommit":{"message":"[DOCS] Remove inference connector docs (#198633)","sha":"517063d0a42283b74b9ba15679bf4d7af393effb"}},{"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: Lisa Cawley <lcawley@elastic.co> |
||
Mike Côté
|
6e35221e29
|
[8.16] Reduce noisy logs about claiming on all partitions (#199405) (#199530)
# Backport This will backport the following commits from `main` to `8.16`: - [Reduce noisy logs about claiming on all partitions (#199405)](https://github.com/elastic/kibana/pull/199405) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mike Côté","email":"mikecote@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-08T17:57:34Z","message":"Reduce noisy logs about claiming on all partitions (#199405)\n\nResolves https://github.com/elastic/response-ops-team/issues/257\r\n\r\nIn this PR, I'm throttling the `Background task node\r\n\"${taskPartitioner.getPodName()}\" has no assigned partitions, claiming\r\nagainst all partitions` warning logs to once per minute. I'm also adding\r\nan info log whenever the node has assigned partitions and a warning\r\nmessage was previously logged.\r\n\r\n## To verify\r\n\r\n1. Startup Kibana with a fresh Elasticsearch instance\r\n2. Notice the warning log followed by the info log\r\n3. Apply the following diff\r\n```\r\ndiff --git a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\nindex 1c4fcb00981..df6bf6ca377 100644\r\n--- a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n+++ b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n@@ -63,7 +63,7 @@ export class KibanaDiscoveryService {\r\n const lastSeenDate = new Date();\r\n const lastSeen = lastSeenDate.toISOString();\r\n try {\r\n- await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n+ // await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n if (!this.started) {\r\n this.logger.info('Kibana Discovery Service has been started');\r\n this.started = true;\r\n```\r\n4. Notice the warning log message happening every minute","sha":"32b942edfbf8ebfb891945ef3a6ca9a1794c7168","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Task Manager","Team:ResponseOps","v9.0.0","backport:version","v8.17.0"],"number":199405,"url":"https://github.com/elastic/kibana/pull/199405","mergeCommit":{"message":"Reduce noisy logs about claiming on all partitions (#199405)\n\nResolves https://github.com/elastic/response-ops-team/issues/257\r\n\r\nIn this PR, I'm throttling the `Background task node\r\n\"${taskPartitioner.getPodName()}\" has no assigned partitions, claiming\r\nagainst all partitions` warning logs to once per minute. I'm also adding\r\nan info log whenever the node has assigned partitions and a warning\r\nmessage was previously logged.\r\n\r\n## To verify\r\n\r\n1. Startup Kibana with a fresh Elasticsearch instance\r\n2. Notice the warning log followed by the info log\r\n3. Apply the following diff\r\n```\r\ndiff --git a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\nindex 1c4fcb00981..df6bf6ca377 100644\r\n--- a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n+++ b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n@@ -63,7 +63,7 @@ export class KibanaDiscoveryService {\r\n const lastSeenDate = new Date();\r\n const lastSeen = lastSeenDate.toISOString();\r\n try {\r\n- await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n+ // await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n if (!this.started) {\r\n this.logger.info('Kibana Discovery Service has been started');\r\n this.started = true;\r\n```\r\n4. Notice the warning log message happening every minute","sha":"32b942edfbf8ebfb891945ef3a6ca9a1794c7168"}},"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/199405","number":199405,"mergeCommit":{"message":"Reduce noisy logs about claiming on all partitions (#199405)\n\nResolves https://github.com/elastic/response-ops-team/issues/257\r\n\r\nIn this PR, I'm throttling the `Background task node\r\n\"${taskPartitioner.getPodName()}\" has no assigned partitions, claiming\r\nagainst all partitions` warning logs to once per minute. I'm also adding\r\nan info log whenever the node has assigned partitions and a warning\r\nmessage was previously logged.\r\n\r\n## To verify\r\n\r\n1. Startup Kibana with a fresh Elasticsearch instance\r\n2. Notice the warning log followed by the info log\r\n3. Apply the following diff\r\n```\r\ndiff --git a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\nindex 1c4fcb00981..df6bf6ca377 100644\r\n--- a/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n+++ b/x-pack/plugins/task_manager/server/kibana_discovery_service/kibana_discovery_service.ts\r\n@@ -63,7 +63,7 @@ export class KibanaDiscoveryService {\r\n const lastSeenDate = new Date();\r\n const lastSeen = lastSeenDate.toISOString();\r\n try {\r\n- await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n+ // await this.upsertCurrentNode({ id: this.currentNode, lastSeen });\r\n if (!this.started) {\r\n this.logger.info('Kibana Discovery Service has been started');\r\n this.started = true;\r\n```\r\n4. Notice the warning log message happening every minute","sha":"32b942edfbf8ebfb891945ef3a6ca9a1794c7168"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/199529","number":199529,"state":"OPEN"}]}] BACKPORT--> |
||
Mykola Harmash
|
367d479ab4
|
[8.16] [Observability Onboarding] Change CTA for System integration in Auto Detect (#197836) (#199435)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] Change CTA for System integration in Auto Detect (#197836)](https://github.com/elastic/kibana/pull/197836) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-10-30T10:54:15Z","message":"[Observability Onboarding] Change CTA for System integration in Auto Detect (#197836)\n\nCloses https://github.com/elastic/observability-dev/issues/4053 🔒\r\n\r\n* Adds an option to specify metadata for integrations installed from\r\nregistry as a third parameter in the TSV provided to the\r\n`/integrations/install` endpoint. For now only `system` integration has\r\nmetadata with a hostname, but it's made generic to support other\r\nintegrations when needed.\r\n* Changes CTA for the System integration to point to the Host details\r\n* Adds sorting in the detected integrations in the UI to alway show\r\nSystem integration at the top","sha":"0ee968480cac02640939a552276aaf4213fbd43d","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-major","ci:project-deploy-observability"],"number":197836,"url":"https://github.com/elastic/kibana/pull/197836","mergeCommit":{"message":"[Observability Onboarding] Change CTA for System integration in Auto Detect (#197836)\n\nCloses https://github.com/elastic/observability-dev/issues/4053 🔒\r\n\r\n* Adds an option to specify metadata for integrations installed from\r\nregistry as a third parameter in the TSV provided to the\r\n`/integrations/install` endpoint. For now only `system` integration has\r\nmetadata with a hostname, but it's made generic to support other\r\nintegrations when needed.\r\n* Changes CTA for the System integration to point to the Host details\r\n* Adds sorting in the detected integrations in the UI to alway show\r\nSystem integration at the top","sha":"0ee968480cac02640939a552276aaf4213fbd43d"}},"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/197836","number":197836,"mergeCommit":{"message":"[Observability Onboarding] Change CTA for System integration in Auto Detect (#197836)\n\nCloses https://github.com/elastic/observability-dev/issues/4053 🔒\r\n\r\n* Adds an option to specify metadata for integrations installed from\r\nregistry as a third parameter in the TSV provided to the\r\n`/integrations/install` endpoint. For now only `system` integration has\r\nmetadata with a hostname, but it's made generic to support other\r\nintegrations when needed.\r\n* Changes CTA for the System integration to point to the Host details\r\n* Adds sorting in the detected integrations in the UI to alway show\r\nSystem integration at the top","sha":"0ee968480cac02640939a552276aaf4213fbd43d"}},{"url":"https://github.com/elastic/kibana/pull/199133","number":199133,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
bf1087ee8a
|
[8.16] [Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog (#199613) (#199739)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog (#199613)](https://github.com/elastic/kibana/pull/199613) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2024-11-12T09:56:52Z","message":"[Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog (#199613)\n\n## Summary\r\n\r\nThis PR closes this issue:\r\nhttps://github.com/elastic/kibana/issues/197623\r\n\r\nNow we don't close the Popover content when clicking in any of the\r\noptions listed in order to keep this content visible. And to solve the\r\nz-index issue where the Popover were displayed on top of the Flyout we\r\nare modifying the Flyout z-index to become exactly the same as the\r\nPopover + 1 to overlap this content.\r\n\r\nNow we keep the same tab index focus we got before opening the Flyout\r\nfrom the Popover options.\r\n\r\n","sha":"8a7514f5e2478e8793e54a9de591286a0414ea60","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","v9.0.0","Team:Search","backport:version","v8.17.0","v8.16.1"],"title":"[Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog","number":199613,"url":"https://github.com/elastic/kibana/pull/199613","mergeCommit":{"message":"[Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog (#199613)\n\n## Summary\r\n\r\nThis PR closes this issue:\r\nhttps://github.com/elastic/kibana/issues/197623\r\n\r\nNow we don't close the Popover content when clicking in any of the\r\noptions listed in order to keep this content visible. And to solve the\r\nz-index issue where the Popover were displayed on top of the Flyout we\r\nare modifying the Flyout z-index to become exactly the same as the\r\nPopover + 1 to overlap this content.\r\n\r\nNow we keep the same tab index focus we got before opening the Flyout\r\nfrom the Popover options.\r\n\r\n","sha":"8a7514f5e2478e8793e54a9de591286a0414ea60"}},"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/199613","number":199613,"mergeCommit":{"message":"[Search][Connectors][a11y] Fixing wrong navigation sequence after closing Manual configuration dialog (#199613)\n\n## Summary\r\n\r\nThis PR closes this issue:\r\nhttps://github.com/elastic/kibana/issues/197623\r\n\r\nNow we don't close the Popover content when clicking in any of the\r\noptions listed in order to keep this content visible. And to solve the\r\nz-index issue where the Popover were displayed on top of the Flyout we\r\nare modifying the Flyout z-index to become exactly the same as the\r\nPopover + 1 to overlap this content.\r\n\r\nNow we keep the same tab index focus we got before opening the Flyout\r\nfrom the Popover options.\r\n\r\n","sha":"8a7514f5e2478e8793e54a9de591286a0414ea60"}},{"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: José Luis González <joseluisgj@gmail.com> |
||
|
Kibana Machine
|
e1acc72d92
|
[8.16] [Security solution] Knowledge base entry telemetry (#199225) (#199723)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security solution] Knowledge base entry telemetry (#199225)](https://github.com/elastic/kibana/pull/199225) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-11-12T00:10:07Z","message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["WIP","release_note:skip","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security solution] Knowledge base entry telemetry","number":199225,"url":"https://github.com/elastic/kibana/pull/199225","mergeCommit":{"message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8"}},"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/199225","number":199225,"mergeCommit":{"message":"[Security solution] Knowledge base entry telemetry (#199225)","sha":"1127bf491d78b7ce2319a13257dbf0b1e84226e8"}},{"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: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
f20c1c8262
|
[8.16] [Data Views] Fix color of button group in 'Share Data View to Spaces' (#196004) (#199534)
# Backport This will backport the following commits from `main` to `8.16`: - [[Data Views] Fix color of button group in 'Share Data View to Spaces' (#196004)](https://github.com/elastic/kibana/pull/196004) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Oyelola Victoria","email":"123843734+VriaA@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-08T18:13:14Z","message":"[Data Views] Fix color of button group in 'Share Data View to Spaces' (#196004)\n\n### Summary\r\n- This PR fixes #194734 \r\n- Changed the button group color value from `success` to `text`\r\n\r\n### Before\r\n\r\n\r\n\r\n### After\r\n\r\n\r\n\r\nSigned-off-by: Oyelola Victoria <oyelolaabimbola23@gmail.com>\r\nCo-authored-by: Larry Gregory <larry.gregory@elastic.co>","sha":"c92775a5b68f4fadadb8c7cf04a4567bb3ed8863","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","💝community","v9.0.0","backport:all-open"],"title":"[Data Views] Fix color of button group in 'Share Data View to Spaces'","number":196004,"url":"https://github.com/elastic/kibana/pull/196004","mergeCommit":{"message":"[Data Views] Fix color of button group in 'Share Data View to Spaces' (#196004)\n\n### Summary\r\n- This PR fixes #194734 \r\n- Changed the button group color value from `success` to `text`\r\n\r\n### Before\r\n\r\n\r\n\r\n### After\r\n\r\n\r\n\r\nSigned-off-by: Oyelola Victoria <oyelolaabimbola23@gmail.com>\r\nCo-authored-by: Larry Gregory <larry.gregory@elastic.co>","sha":"c92775a5b68f4fadadb8c7cf04a4567bb3ed8863"}},"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/196004","number":196004,"mergeCommit":{"message":"[Data Views] Fix color of button group in 'Share Data View to Spaces' (#196004)\n\n### Summary\r\n- This PR fixes #194734 \r\n- Changed the button group color value from `success` to `text`\r\n\r\n### Before\r\n\r\n\r\n\r\n### After\r\n\r\n\r\n\r\nSigned-off-by: Oyelola Victoria <oyelolaabimbola23@gmail.com>\r\nCo-authored-by: Larry Gregory <larry.gregory@elastic.co>","sha":"c92775a5b68f4fadadb8c7cf04a4567bb3ed8863"}}]}] BACKPORT--> Co-authored-by: Oyelola Victoria <123843734+VriaA@users.noreply.github.com> |
||
|
Kibana Machine
|
89825cbd38
|
[8.16] Open links in new tabs from pages in Fleet integrations (#199468) (#199525)
# Backport This will backport the following commits from `main` to `8.16`: - [Open links in new tabs from pages in Fleet integrations (#199468)](https://github.com/elastic/kibana/pull/199468) <!--- 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-08T17:33:55Z","message":"Open links in new tabs from pages in Fleet integrations (#199468)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10987.\r\n\r\nFleet integrations render pages whose source content is written in\r\nMarkdown format. Links in markdown were being converted into regular\r\n`<a>` tags rather than in `<EuiLink>` components that include styling\r\nfor external links and open in new tabs.\r\n\r\nAlso, the \"API Reference\" page rendered a \"Learn more\" link using a\r\n`<EuiLink>` component with external styling but missed\r\n`target=\"_blank\"`, so it wasn't acting as an external link and didn't\r\nopen in a new tab either.\r\n\r\n\r\n### Bug origin\r\n\r\nThis bug has dragged for the last 3 years since `react-markdown`\r\nupgraded to `v6.0` and introduced a [breaking\r\nchange](https://github.com/remarkjs/react-markdown/blob/main/changelog.md#600---2021-04-15)\r\nin custom renderers\r\n\r\n\r\n\r\n### Screenshots\r\n\r\n<details><summary>Overview page</summary>\r\n<img width=\"1406\" alt=\"Screenshot 2024-11-08 at 13 35 43\"\r\nsrc=\"https://github.com/user-attachments/assets/b11262f1-0b1e-45e5-baa9-d69727643b08\">\r\n</details> \r\n\r\n<details><summary>API Reference page</summary>\r\n<img width=\"2021\" alt=\"Screenshot 2024-11-08 at 13 35 07\"\r\nsrc=\"https://github.com/user-attachments/assets/7e073df2-0451-4e9d-b80c-878cfcdd6c58\">\r\n</details> \r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] 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- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"763410c8ab0fed547571431c27a0d5d2f5fd4a7b","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:Cloud Security","backport:prev-minor","csp: quick win","v8.16.0","backport:version","v8.17.0"],"title":"Open links in new tabs from pages in Fleet integrations","number":199468,"url":"https://github.com/elastic/kibana/pull/199468","mergeCommit":{"message":"Open links in new tabs from pages in Fleet integrations (#199468)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10987.\r\n\r\nFleet integrations render pages whose source content is written in\r\nMarkdown format. Links in markdown were being converted into regular\r\n`<a>` tags rather than in `<EuiLink>` components that include styling\r\nfor external links and open in new tabs.\r\n\r\nAlso, the \"API Reference\" page rendered a \"Learn more\" link using a\r\n`<EuiLink>` component with external styling but missed\r\n`target=\"_blank\"`, so it wasn't acting as an external link and didn't\r\nopen in a new tab either.\r\n\r\n\r\n### Bug origin\r\n\r\nThis bug has dragged for the last 3 years since `react-markdown`\r\nupgraded to `v6.0` and introduced a [breaking\r\nchange](https://github.com/remarkjs/react-markdown/blob/main/changelog.md#600---2021-04-15)\r\nin custom renderers\r\n\r\n\r\n\r\n### Screenshots\r\n\r\n<details><summary>Overview page</summary>\r\n<img width=\"1406\" alt=\"Screenshot 2024-11-08 at 13 35 43\"\r\nsrc=\"https://github.com/user-attachments/assets/b11262f1-0b1e-45e5-baa9-d69727643b08\">\r\n</details> \r\n\r\n<details><summary>API Reference page</summary>\r\n<img width=\"2021\" alt=\"Screenshot 2024-11-08 at 13 35 07\"\r\nsrc=\"https://github.com/user-attachments/assets/7e073df2-0451-4e9d-b80c-878cfcdd6c58\">\r\n</details> \r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] 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- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"763410c8ab0fed547571431c27a0d5d2f5fd4a7b"}},"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/199468","number":199468,"mergeCommit":{"message":"Open links in new tabs from pages in Fleet integrations (#199468)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/security-team/issues/10987.\r\n\r\nFleet integrations render pages whose source content is written in\r\nMarkdown format. Links in markdown were being converted into regular\r\n`<a>` tags rather than in `<EuiLink>` components that include styling\r\nfor external links and open in new tabs.\r\n\r\nAlso, the \"API Reference\" page rendered a \"Learn more\" link using a\r\n`<EuiLink>` component with external styling but missed\r\n`target=\"_blank\"`, so it wasn't acting as an external link and didn't\r\nopen in a new tab either.\r\n\r\n\r\n### Bug origin\r\n\r\nThis bug has dragged for the last 3 years since `react-markdown`\r\nupgraded to `v6.0` and introduced a [breaking\r\nchange](https://github.com/remarkjs/react-markdown/blob/main/changelog.md#600---2021-04-15)\r\nin custom renderers\r\n\r\n\r\n\r\n### Screenshots\r\n\r\n<details><summary>Overview page</summary>\r\n<img width=\"1406\" alt=\"Screenshot 2024-11-08 at 13 35 43\"\r\nsrc=\"https://github.com/user-attachments/assets/b11262f1-0b1e-45e5-baa9-d69727643b08\">\r\n</details> \r\n\r\n<details><summary>API Reference page</summary>\r\n<img width=\"2021\" alt=\"Screenshot 2024-11-08 at 13 35 07\"\r\nsrc=\"https://github.com/user-attachments/assets/7e073df2-0451-4e9d-b80c-878cfcdd6c58\">\r\n</details> \r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [x] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [x] 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- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"763410c8ab0fed547571431c27a0d5d2f5fd4a7b"}},{"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: Alberto Blázquez <albertoblaz@users.noreply.github.com> |
||
|
Kibana Machine
|
c9f6d60e0b
|
[8.16] [Search] [Onboarding] Fix colors for dark theme (#199331) (#199490)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search] [Onboarding] Fix colors for dark theme (#199331)](https://github.com/elastic/kibana/pull/199331) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yan Savitski","email":"yan.savitski@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T14:39:03Z","message":"[Search] [Onboarding] Fix colors for dark theme (#199331)\n\nIn dark mode, colors are not changed for some components in\r\nindexManagement\r\n\r\n- Change according background color base on theme\r\n- Change icons color base on theme\r\n\r\n<img width=\"1030\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f448b522-03cc-4e17-89dd-4a460983bbac\">","sha":"619f330aa9fbcddf2ddd306555a7b5f0d7d3fbd6","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:prev-minor","v8.16.0"],"title":"[Search] [Onboarding] Fix colors for dark theme","number":199331,"url":"https://github.com/elastic/kibana/pull/199331","mergeCommit":{"message":"[Search] [Onboarding] Fix colors for dark theme (#199331)\n\nIn dark mode, colors are not changed for some components in\r\nindexManagement\r\n\r\n- Change according background color base on theme\r\n- Change icons color base on theme\r\n\r\n<img width=\"1030\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f448b522-03cc-4e17-89dd-4a460983bbac\">","sha":"619f330aa9fbcddf2ddd306555a7b5f0d7d3fbd6"}},"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/199331","number":199331,"mergeCommit":{"message":"[Search] [Onboarding] Fix colors for dark theme (#199331)\n\nIn dark mode, colors are not changed for some components in\r\nindexManagement\r\n\r\n- Change according background color base on theme\r\n- Change icons color base on theme\r\n\r\n<img width=\"1030\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f448b522-03cc-4e17-89dd-4a460983bbac\">","sha":"619f330aa9fbcddf2ddd306555a7b5f0d7d3fbd6"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yan Savitski <yan.savitski@elastic.co> |
||
|
Kibana Machine
|
2e03cd1a97
|
[8.16] [Synthetics] Fixes annotation update after event change !! (#199330) (#199444)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fixes annotation update after event change !! (#199330)](https://github.com/elastic/kibana/pull/199330) <!--- 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-08T10:37:39Z","message":"[Synthetics] Fixes annotation update after event change !! (#199330)\n\n## Summary\r\n\r\nFixes annotation update after event change !!\r\n\r\nFixes https://github.com/elastic/kibana/issues/199418\r\n\r\nIn SLO details page, create an annotation by holding Command+Dragging on\r\nchart, save and try to change the annotation type and it should be able\r\nto save it/update it\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a1ac92f6-1c0c-4544-b405-1c3c45c63739\">","sha":"3094dc45c6350f030dc1b5590b02d8d7979fdddc","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0","backport:version","v8.17.0"],"title":"[Synthetics] Fixes annotation update after event change !!","number":199330,"url":"https://github.com/elastic/kibana/pull/199330","mergeCommit":{"message":"[Synthetics] Fixes annotation update after event change !! (#199330)\n\n## Summary\r\n\r\nFixes annotation update after event change !!\r\n\r\nFixes https://github.com/elastic/kibana/issues/199418\r\n\r\nIn SLO details page, create an annotation by holding Command+Dragging on\r\nchart, save and try to change the annotation type and it should be able\r\nto save it/update it\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a1ac92f6-1c0c-4544-b405-1c3c45c63739\">","sha":"3094dc45c6350f030dc1b5590b02d8d7979fdddc"}},"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/199330","number":199330,"mergeCommit":{"message":"[Synthetics] Fixes annotation update after event change !! (#199330)\n\n## Summary\r\n\r\nFixes annotation update after event change !!\r\n\r\nFixes https://github.com/elastic/kibana/issues/199418\r\n\r\nIn SLO details page, create an annotation by holding Command+Dragging on\r\nchart, save and try to change the annotation type and it should be able\r\nto save it/update it\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/a1ac92f6-1c0c-4544-b405-1c3c45c63739\">","sha":"3094dc45c6350f030dc1b5590b02d8d7979fdddc"}},{"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: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
8ca694359e
|
[8.16] [SecuritySolution][Navigation] Unify Notes link (#199374) (#199431)
# Backport This will backport the following commits from `main` to `8.16`: - [[SecuritySolution][Navigation] Unify Notes link (#199374)](https://github.com/elastic/kibana/pull/199374) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T09:43:30Z","message":"[SecuritySolution][Navigation] Unify Notes link (#199374)\n\n## Summary\r\n\r\nBug Issue: https://github.com/elastic/kibana/issues/197694\r\n\r\nUnify the Notes link configuration.\r\n\r\n- ESS classic nav (default) -> subLink of the `Manage` section\r\n- ESS solution nav / Serverless -> `Manage` section is removed and the\r\n`Notes` link is relocated as a sublink of the `Investigations` section\r\n \r\nBreadcrumbs and global search results are now consistent with the page's\r\nlocation in each environment.\r\n\r\n### Screenshots\r\n\r\nClassic nav:\r\n\r\n (#199358)
# Backport This will backport the following commits from `main` to `8.16`: - [[AI Assistant] Enable Search in Solution View (#199137)](https://github.com/elastic/kibana/pull/199137) <!--- 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-07T18:12:33Z","message":"[AI Assistant] Enable Search in Solution View (#199137)\n\n## Summary\r\n\r\nThis enables the Search solution in the Observability solution view, so\r\nthat connectors (which are required for the AI Assistant) are available.","sha":"17db651a058795ef866ee610d950bfada91c840a","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","v8.16.0","backport:version","v8.17.0"],"title":"[AI Assistant] Enable Search in Solution View","number":199137,"url":"https://github.com/elastic/kibana/pull/199137","mergeCommit":{"message":"[AI Assistant] Enable Search in Solution View (#199137)\n\n## Summary\r\n\r\nThis enables the Search solution in the Observability solution view, so\r\nthat connectors (which are required for the AI Assistant) are available.","sha":"17db651a058795ef866ee610d950bfada91c840a"}},"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/199137","number":199137,"mergeCommit":{"message":"[AI Assistant] Enable Search in Solution View (#199137)\n\n## Summary\r\n\r\nThis enables the Search solution in the Observability solution view, so\r\nthat connectors (which are required for the AI Assistant) are available.","sha":"17db651a058795ef866ee610d950bfada91c840a"}},{"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: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
e079cab541
|
[8.16] [Fleet] Ignore missing policies when fetching agent data (#199325) (#199348)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] Ignore missing policies when fetching agent data (#199325)](https://github.com/elastic/kibana/pull/199325) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T16:29:37Z","message":"[Fleet] Ignore missing policies when fetching agent data (#199325)","sha":"52d7eaf6d71775f7e25f5661175e2d4603164f00","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","v8.16.0"],"title":"[Fleet] Ignore missing policies when fetching agent data","number":199325,"url":"https://github.com/elastic/kibana/pull/199325","mergeCommit":{"message":"[Fleet] Ignore missing policies when fetching agent data (#199325)","sha":"52d7eaf6d71775f7e25f5661175e2d4603164f00"}},"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/199325","number":199325,"mergeCommit":{"message":"[Fleet] Ignore missing policies when fetching agent data (#199325)","sha":"52d7eaf6d71775f7e25f5661175e2d4603164f00"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
1bcd05c88a
|
[8.16] [Security Solution][Serverless] Github tickets / notifications (#197265) (#199313)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Serverless] Github tickets / notifications (#197265)](https://github.com/elastic/kibana/pull/197265) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"dkirchan","email":"55240027+dkirchan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-07T13:17:54Z","message":"[Security Solution][Serverless] Github tickets / notifications (#197265)\n\n## Summary\r\n\r\nThis PR is accompanied with the [PR in kibana-operations\r\nrepo](https://github.com/elastic/kibana-operations/pull/236) and\r\nintegrates the security solution quality gate pipelines with the\r\nfunctionality to create ticket when a test fails and then notify the\r\nrespective **codeowner** team with a _Test failed alert_. Also when a\r\ntest fails a second time and a ticket exist a new comment is added in\r\nthe same issue that the test failed again in a given pipeline.\r\n\r\nLast a similar flow exist when a test is skipped by a team. \r\n\r\n**Specifications:**\r\n\r\n- In the `failed_test_reporter_cli.ts` [a new field is introduced\r\n](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-bb801c18fd2e1a3a36a3b39fbf02c1abe337c46c201ad5a01239a9d2501d4b56R47)`prependTitle`\r\nwhich is initialized by the environmental variable\r\n`process.env.PREPEND_FAILURE_TITLE` if exists, in order to add a custom\r\ntext of preference before the issue title.\r\n\r\nThe scope of this is to be able to give the team the opportunity to add\r\nsome tags or any convention agreed within the team in the issue created\r\nin order to easily understand the context without opening the ticket. If\r\nthis field is not initialized, the normal existing flow proceeds.\r\n[Here](https://github.com/elastic/kibana/issues/197133) an example of\r\nthe prependTitle usage can be seen where the tags `[MKI][QA]` are\r\nprepended in order to identify where did the test fail, having the same\r\nexactly tests running on both CI and MKI. This means that a github issue\r\nwith the exact same title would be created for both cases if this\r\nprepend title field would not exist.\r\n\r\n- In the\r\n[junit_transformer/lib.ts](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-31c5651af613c7d02139f3e9fccd00ddb997f2502523372dd19db9e0659a66d6R278)\r\na new functionality is introduced to cover an existing issue. The\r\nexisting issue is: the fact that we are retrying the failed test in\r\ncypress in the `parallel_serverless` script, leads to two junit xml\r\nresult files completely identical with only difference the execution\r\ntime and the timestamps. This change will take one by one the xml\r\noutputs, transform them exactly as it was happening before and then save\r\nthe file, but also remove the time and timestamp fields, convert it to a\r\nstring and add it to a \"state\" list. Then in a next file if it is\r\nalready parsed and saved to the list having the exact same results\r\nwithin, it deletes the file instead of saving it transformed.\r\n\r\nThe problem before this fix was the fact that when two xml outputs\r\nexisted, a github ticket was created and when parsing-uploading the\r\nsecond file it was immediately failing for a second time as well. This\r\nmeans that `new-failure` notification was never triggered after the\r\ngithub actions flow split, and the existing failure was always\r\ntriggered, something that most teams have disabled.\r\n\r\nWith the fix, the identical files are parsed but only once uploaded and\r\nthe new failure flow works again.","sha":"9353497d0adea457c13643bc8fa1a26a05422e8f","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","backport:prev-minor","v8.16.0","v8.17.0"],"title":"[Security Solution][Serverless] Github tickets / notifications","number":197265,"url":"https://github.com/elastic/kibana/pull/197265","mergeCommit":{"message":"[Security Solution][Serverless] Github tickets / notifications (#197265)\n\n## Summary\r\n\r\nThis PR is accompanied with the [PR in kibana-operations\r\nrepo](https://github.com/elastic/kibana-operations/pull/236) and\r\nintegrates the security solution quality gate pipelines with the\r\nfunctionality to create ticket when a test fails and then notify the\r\nrespective **codeowner** team with a _Test failed alert_. Also when a\r\ntest fails a second time and a ticket exist a new comment is added in\r\nthe same issue that the test failed again in a given pipeline.\r\n\r\nLast a similar flow exist when a test is skipped by a team. \r\n\r\n**Specifications:**\r\n\r\n- In the `failed_test_reporter_cli.ts` [a new field is introduced\r\n](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-bb801c18fd2e1a3a36a3b39fbf02c1abe337c46c201ad5a01239a9d2501d4b56R47)`prependTitle`\r\nwhich is initialized by the environmental variable\r\n`process.env.PREPEND_FAILURE_TITLE` if exists, in order to add a custom\r\ntext of preference before the issue title.\r\n\r\nThe scope of this is to be able to give the team the opportunity to add\r\nsome tags or any convention agreed within the team in the issue created\r\nin order to easily understand the context without opening the ticket. If\r\nthis field is not initialized, the normal existing flow proceeds.\r\n[Here](https://github.com/elastic/kibana/issues/197133) an example of\r\nthe prependTitle usage can be seen where the tags `[MKI][QA]` are\r\nprepended in order to identify where did the test fail, having the same\r\nexactly tests running on both CI and MKI. This means that a github issue\r\nwith the exact same title would be created for both cases if this\r\nprepend title field would not exist.\r\n\r\n- In the\r\n[junit_transformer/lib.ts](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-31c5651af613c7d02139f3e9fccd00ddb997f2502523372dd19db9e0659a66d6R278)\r\na new functionality is introduced to cover an existing issue. The\r\nexisting issue is: the fact that we are retrying the failed test in\r\ncypress in the `parallel_serverless` script, leads to two junit xml\r\nresult files completely identical with only difference the execution\r\ntime and the timestamps. This change will take one by one the xml\r\noutputs, transform them exactly as it was happening before and then save\r\nthe file, but also remove the time and timestamp fields, convert it to a\r\nstring and add it to a \"state\" list. Then in a next file if it is\r\nalready parsed and saved to the list having the exact same results\r\nwithin, it deletes the file instead of saving it transformed.\r\n\r\nThe problem before this fix was the fact that when two xml outputs\r\nexisted, a github ticket was created and when parsing-uploading the\r\nsecond file it was immediately failing for a second time as well. This\r\nmeans that `new-failure` notification was never triggered after the\r\ngithub actions flow split, and the existing failure was always\r\ntriggered, something that most teams have disabled.\r\n\r\nWith the fix, the identical files are parsed but only once uploaded and\r\nthe new failure flow works again.","sha":"9353497d0adea457c13643bc8fa1a26a05422e8f"}},"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/197265","number":197265,"mergeCommit":{"message":"[Security Solution][Serverless] Github tickets / notifications (#197265)\n\n## Summary\r\n\r\nThis PR is accompanied with the [PR in kibana-operations\r\nrepo](https://github.com/elastic/kibana-operations/pull/236) and\r\nintegrates the security solution quality gate pipelines with the\r\nfunctionality to create ticket when a test fails and then notify the\r\nrespective **codeowner** team with a _Test failed alert_. Also when a\r\ntest fails a second time and a ticket exist a new comment is added in\r\nthe same issue that the test failed again in a given pipeline.\r\n\r\nLast a similar flow exist when a test is skipped by a team. \r\n\r\n**Specifications:**\r\n\r\n- In the `failed_test_reporter_cli.ts` [a new field is introduced\r\n](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-bb801c18fd2e1a3a36a3b39fbf02c1abe337c46c201ad5a01239a9d2501d4b56R47)`prependTitle`\r\nwhich is initialized by the environmental variable\r\n`process.env.PREPEND_FAILURE_TITLE` if exists, in order to add a custom\r\ntext of preference before the issue title.\r\n\r\nThe scope of this is to be able to give the team the opportunity to add\r\nsome tags or any convention agreed within the team in the issue created\r\nin order to easily understand the context without opening the ticket. If\r\nthis field is not initialized, the normal existing flow proceeds.\r\n[Here](https://github.com/elastic/kibana/issues/197133) an example of\r\nthe prependTitle usage can be seen where the tags `[MKI][QA]` are\r\nprepended in order to identify where did the test fail, having the same\r\nexactly tests running on both CI and MKI. This means that a github issue\r\nwith the exact same title would be created for both cases if this\r\nprepend title field would not exist.\r\n\r\n- In the\r\n[junit_transformer/lib.ts](https://github.com/elastic/kibana/compare/main...security-mki-github-tickets#diff-31c5651af613c7d02139f3e9fccd00ddb997f2502523372dd19db9e0659a66d6R278)\r\na new functionality is introduced to cover an existing issue. The\r\nexisting issue is: the fact that we are retrying the failed test in\r\ncypress in the `parallel_serverless` script, leads to two junit xml\r\nresult files completely identical with only difference the execution\r\ntime and the timestamps. This change will take one by one the xml\r\noutputs, transform them exactly as it was happening before and then save\r\nthe file, but also remove the time and timestamp fields, convert it to a\r\nstring and add it to a \"state\" list. Then in a next file if it is\r\nalready parsed and saved to the list having the exact same results\r\nwithin, it deletes the file instead of saving it transformed.\r\n\r\nThe problem before this fix was the fact that when two xml outputs\r\nexisted, a github ticket was created and when parsing-uploading the\r\nsecond file it was immediately failing for a second time as well. This\r\nmeans that `new-failure` notification was never triggered after the\r\ngithub actions flow split, and the existing failure was always\r\ntriggered, something that most teams have disabled.\r\n\r\nWith the fix, the identical files are parsed but only once uploaded and\r\nthe new failure flow works again.","sha":"9353497d0adea457c13643bc8fa1a26a05422e8f"}},{"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: dkirchan <55240027+dkirchan@users.noreply.github.com> |
||
|
Kibana Machine
|
8fe43eebb6
|
[8.16] [Synthetics] Fix location remove via public API !! (#199170) (#199326)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] Fix location remove via public API !! (#199170)](https://github.com/elastic/kibana/pull/199170) <!--- 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-07T14:37:55Z","message":"[Synthetics] Fix location remove via public API !! (#199170)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/199108\r\n\r\nFix location remove via public API !!\r\n\r\n### Testing \r\n\r\nCreate a Monitor that is configured in two locations:\r\n```\r\nPOST kbn:/api/synthetics/monitors\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\", \"germany\"]\r\n}\r\n```\r\nExtract from the response the config_id\r\nUpdate the monitor to remove one location\r\n```\r\nPUT kbn:/api/synthetics/monitors/<config-id>\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\"]\r\n}\r\n```\r\n\r\n\r\nThis should remove Germany location from monitor !!","sha":"4a341055cf374761f4b1b247d702f9e759b03d92","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0","backport:version","v8.17.0"],"title":"[Synthetics] Fix location remove via public API !!","number":199170,"url":"https://github.com/elastic/kibana/pull/199170","mergeCommit":{"message":"[Synthetics] Fix location remove via public API !! (#199170)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/199108\r\n\r\nFix location remove via public API !!\r\n\r\n### Testing \r\n\r\nCreate a Monitor that is configured in two locations:\r\n```\r\nPOST kbn:/api/synthetics/monitors\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\", \"germany\"]\r\n}\r\n```\r\nExtract from the response the config_id\r\nUpdate the monitor to remove one location\r\n```\r\nPUT kbn:/api/synthetics/monitors/<config-id>\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\"]\r\n}\r\n```\r\n\r\n\r\nThis should remove Germany location from monitor !!","sha":"4a341055cf374761f4b1b247d702f9e759b03d92"}},"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/199170","number":199170,"mergeCommit":{"message":"[Synthetics] Fix location remove via public API !! (#199170)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/199108\r\n\r\nFix location remove via public API !!\r\n\r\n### Testing \r\n\r\nCreate a Monitor that is configured in two locations:\r\n```\r\nPOST kbn:/api/synthetics/monitors\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\", \"germany\"]\r\n}\r\n```\r\nExtract from the response the config_id\r\nUpdate the monitor to remove one location\r\n```\r\nPUT kbn:/api/synthetics/monitors/<config-id>\r\n{\r\n \"type\": \"http\",\r\n \"name\": \"healthcheck\",\r\n \"url\": \"https://www.elastic.co\",\r\n \"locations\": [\"united_kingdom\"]\r\n}\r\n```\r\n\r\n\r\nThis should remove Germany location from monitor !!","sha":"4a341055cf374761f4b1b247d702f9e759b03d92"}},{"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: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
06fc36884e
|
[8.16] [SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh (#199278) (#199328)
# Backport This will backport the following commits from `main` to `8.16`: - [[SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh (#199278)](https://github.com/elastic/kibana/pull/199278) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T14:39:13Z","message":"[SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh (#199278)\n\n## Summary\r\n\r\nUse in-app navigation to prevent page refresh.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/cdb1ab08-62ab-4e51-b92f-2afafa56476d","sha":"2911ed414165462c43beb5c13569aab4f4ca3eda","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","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","v8.16.0","backport:version","v8.17.0"],"title":"[SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh","number":199278,"url":"https://github.com/elastic/kibana/pull/199278","mergeCommit":{"message":"[SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh (#199278)\n\n## Summary\r\n\r\nUse in-app navigation to prevent page refresh.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/cdb1ab08-62ab-4e51-b92f-2afafa56476d","sha":"2911ed414165462c43beb5c13569aab4f4ca3eda"}},"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/199278","number":199278,"mergeCommit":{"message":"[SecuritySolution] [EntityStore] Use SecuritySolution link to prevent page refresh (#199278)\n\n## Summary\r\n\r\nUse in-app navigation to prevent page refresh.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/cdb1ab08-62ab-4e51-b92f-2afafa56476d","sha":"2911ed414165462c43beb5c13569aab4f4ca3eda"}},{"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: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
a8a07dfc58
|
[8.16] [Entity Store] Aligning mappings with ECS (#199001) (#199282)
# Backport This will backport the following commits from `main` to `8.16`: - [[Entity Store] Aligning mappings with ECS (#199001)](https://github.com/elastic/kibana/pull/199001) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"tiago.vilaverde@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T10:06:59Z","message":"[Entity Store] Aligning mappings with ECS (#199001)\n\n## Summary\r\n\r\nThis PR corrects some of the mappings set in the component template to\r\nfollow ECS guidelines.\r\n\r\n#### How to test\r\n\r\nInitialise an entity engine via devtools:\r\n```\r\nPOST kbn:/api/entity_store/engines/host/init\r\n{}\r\n```\r\n\r\nCheck the mappings with:\r\n```\r\nGET .entities.v1.latest.security_<entityType>_default/_mapping\r\n```","sha":"3fff48a2cad951cfc531e0f61e9939ae4436a77b","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:Entity Analytics","v8.16.0","backport:version","v8.17.0"],"title":"[Entity Store] Aligning mappings with ECS","number":199001,"url":"https://github.com/elastic/kibana/pull/199001","mergeCommit":{"message":"[Entity Store] Aligning mappings with ECS (#199001)\n\n## Summary\r\n\r\nThis PR corrects some of the mappings set in the component template to\r\nfollow ECS guidelines.\r\n\r\n#### How to test\r\n\r\nInitialise an entity engine via devtools:\r\n```\r\nPOST kbn:/api/entity_store/engines/host/init\r\n{}\r\n```\r\n\r\nCheck the mappings with:\r\n```\r\nGET .entities.v1.latest.security_<entityType>_default/_mapping\r\n```","sha":"3fff48a2cad951cfc531e0f61e9939ae4436a77b"}},"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/199001","number":199001,"mergeCommit":{"message":"[Entity Store] Aligning mappings with ECS (#199001)\n\n## Summary\r\n\r\nThis PR corrects some of the mappings set in the component template to\r\nfollow ECS guidelines.\r\n\r\n#### How to test\r\n\r\nInitialise an entity engine via devtools:\r\n```\r\nPOST kbn:/api/entity_store/engines/host/init\r\n{}\r\n```\r\n\r\nCheck the mappings with:\r\n```\r\nGET .entities.v1.latest.security_<entityType>_default/_mapping\r\n```","sha":"3fff48a2cad951cfc531e0f61e9939ae4436a77b"}},{"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: Tiago Vila Verde <tiago.vilaverde@elastic.co> |
||
|
Kibana Machine
|
d75024f6d4
|
[8.16] [Observability Onboarding] fix docker integration double detection (#199237) (#199266)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] fix docker integration double detection (#199237)](https://github.com/elastic/kibana/pull/199237) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T09:08:27Z","message":"[Observability Onboarding] fix docker integration double detection (#199237)\n\nCloses https://github.com/elastic/kibana/issues/195912\r\n\r\nSee:\r\nhttps://github.com/elastic/kibana/issues/195912#issuecomment-2460870604","sha":"4c61876a3a8abb8471cba3e2848cf603351a78ad","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-logs","Feature: Observability Onboarding","v8.16.0","v8.17.0"],"title":"[Observability Onboarding] fix docker integration double detection","number":199237,"url":"https://github.com/elastic/kibana/pull/199237","mergeCommit":{"message":"[Observability Onboarding] fix docker integration double detection (#199237)\n\nCloses https://github.com/elastic/kibana/issues/195912\r\n\r\nSee:\r\nhttps://github.com/elastic/kibana/issues/195912#issuecomment-2460870604","sha":"4c61876a3a8abb8471cba3e2848cf603351a78ad"}},"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/199237","number":199237,"mergeCommit":{"message":"[Observability Onboarding] fix docker integration double detection (#199237)\n\nCloses https://github.com/elastic/kibana/issues/195912\r\n\r\nSee:\r\nhttps://github.com/elastic/kibana/issues/195912#issuecomment-2460870604","sha":"4c61876a3a8abb8471cba3e2848cf603351a78ad"}},{"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: Joe Reuter <johannes.reuter@elastic.co> |
||
Ash
|
5d1e09524e
|
[8.16] [Security Solution] Removing cypress folder (#197273) (#199261)
> [!Warning] > `.github/CODEOWNERS` and `.buildkite/pipelines/pull_request/security_solution/defend_workflows.yml` were updated as part of merge conflicts so would need a thorough review. # Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution] Removing cypress folder (#197273)](https://github.com/elastic/kibana/pull/197273) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gloria Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2024-10-24T15:26:33Z","message":"[Security Solution] Removing cypress folder (#197273)\n\n## Summary\r\n\r\nDeleting the Cypress folder that was added in `test_serverless` as a\r\nPOC.\r\n\r\nCurrently is not used and this can create misunderstandings regarding\r\nownership of it.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"86e6c74f7c39a512eaa43cc025434dc6a53d55f6","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","Team: SecuritySolution","v8.16.0","backport:version","v8.17.0"],"number":197273,"url":"https://github.com/elastic/kibana/pull/197273","mergeCommit":{"message":"[Security Solution] Removing cypress folder (#197273)\n\n## Summary\r\n\r\nDeleting the Cypress folder that was added in `test_serverless` as a\r\nPOC.\r\n\r\nCurrently is not used and this can create misunderstandings regarding\r\nownership of it.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"86e6c74f7c39a512eaa43cc025434dc6a53d55f6"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197273","number":197273,"mergeCommit":{"message":"[Security Solution] Removing cypress folder (#197273)\n\n## Summary\r\n\r\nDeleting the Cypress folder that was added in `test_serverless` as a\r\nPOC.\r\n\r\nCurrently is not used and this can create misunderstandings regarding\r\nownership of it.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"86e6c74f7c39a512eaa43cc025434dc6a53d55f6"}},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Ahmad Bamieh
|
af3ddd0c3c
|
[i18n] [8.16] Integrate 8.16.0 Translations (#199151)
Integrating latest translations extracted from 8.16 branch. Skipping backports from main to target branches since the `i18n_check` might trim unused translations that are still used in different branches. Integration script is ran against each target branch separately. |
||
|
Kibana Machine
|
e63d4ec2d6
|
[8.16] [Canvas] Fix bug when trying to move elements (#199211) (#199245)
# Backport This will backport the following commits from `main` to `8.16`: - [[Canvas] Fix bug when trying to move elements (#199211)](https://github.com/elastic/kibana/pull/199211) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-06T23:54:44Z","message":"[Canvas] Fix bug when trying to move elements (#199211)\n\nCloses https://github.com/elastic/kibana/issues/199110\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/194634, we switched to\r\nhard-coded strings for the reducers to prevent an import circular\r\ndependency - see\r\nhttps://github.com/elastic/kibana/pull/194634/files#diff-12e4182415d9eb779aadf492d2b777393e2794c7ac2eb39c48310ab6493ab233L115-R120\r\nfor the relevant change.\r\n\r\nWhat we didn't realize at the time, however, is that there was actually\r\na typo in the original creation of the set position action - the\r\n`actionType` was set to the singular `setMultiplePosition` rather than\r\n`setMultiplePositions`, so there was actually **no** reducer tied to the\r\n`setMultiplePositions` action type after our change - i.e. the reducer\r\nmap was expecting `setMultiplePosition` and did nothing for\r\n`setMultiplePositions`. By changing the `actionType` to the proper\r\nplural `setMultiplePositions`, the reducer map now has a match, so the\r\nreducer gets called as expected.\r\n\r\n| Before | After |\r\n|--------|--------|\r\n| \r\n| \r\n|\r\n\r\nI looked through the other changes we made to reducer map keys, and\r\nevery `actionType` defined via `createAction` seems to have a matching\r\nreducer map key - so this appears to be a one-off 🙈\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_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)","sha":"1fa30899ab2ba3f534ebb6620a34513a1431e0ed","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","loe:small","impact:critical","v9.0.0","Feature:Canvas","backport:version","v8.17.0","v8.16.1","v8.18.0"],"title":"[Canvas] Fix bug when trying to move elements","number":199211,"url":"https://github.com/elastic/kibana/pull/199211","mergeCommit":{"message":"[Canvas] Fix bug when trying to move elements (#199211)\n\nCloses https://github.com/elastic/kibana/issues/199110\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/194634, we switched to\r\nhard-coded strings for the reducers to prevent an import circular\r\ndependency - see\r\nhttps://github.com/elastic/kibana/pull/194634/files#diff-12e4182415d9eb779aadf492d2b777393e2794c7ac2eb39c48310ab6493ab233L115-R120\r\nfor the relevant change.\r\n\r\nWhat we didn't realize at the time, however, is that there was actually\r\na typo in the original creation of the set position action - the\r\n`actionType` was set to the singular `setMultiplePosition` rather than\r\n`setMultiplePositions`, so there was actually **no** reducer tied to the\r\n`setMultiplePositions` action type after our change - i.e. the reducer\r\nmap was expecting `setMultiplePosition` and did nothing for\r\n`setMultiplePositions`. By changing the `actionType` to the proper\r\nplural `setMultiplePositions`, the reducer map now has a match, so the\r\nreducer gets called as expected.\r\n\r\n| Before | After |\r\n|--------|--------|\r\n| \r\n| \r\n|\r\n\r\nI looked through the other changes we made to reducer map keys, and\r\nevery `actionType` defined via `createAction` seems to have a matching\r\nreducer map key - so this appears to be a one-off 🙈\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_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)","sha":"1fa30899ab2ba3f534ebb6620a34513a1431e0ed"}},"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/199211","number":199211,"mergeCommit":{"message":"[Canvas] Fix bug when trying to move elements (#199211)\n\nCloses https://github.com/elastic/kibana/issues/199110\r\n\r\n## Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/194634, we switched to\r\nhard-coded strings for the reducers to prevent an import circular\r\ndependency - see\r\nhttps://github.com/elastic/kibana/pull/194634/files#diff-12e4182415d9eb779aadf492d2b777393e2794c7ac2eb39c48310ab6493ab233L115-R120\r\nfor the relevant change.\r\n\r\nWhat we didn't realize at the time, however, is that there was actually\r\na typo in the original creation of the set position action - the\r\n`actionType` was set to the singular `setMultiplePosition` rather than\r\n`setMultiplePositions`, so there was actually **no** reducer tied to the\r\n`setMultiplePositions` action type after our change - i.e. the reducer\r\nmap was expecting `setMultiplePosition` and did nothing for\r\n`setMultiplePositions`. By changing the `actionType` to the proper\r\nplural `setMultiplePositions`, the reducer map now has a match, so the\r\nreducer gets called as expected.\r\n\r\n| Before | After |\r\n|--------|--------|\r\n| \r\n| \r\n|\r\n\r\nI looked through the other changes we made to reducer map keys, and\r\nevery `actionType` defined via `createAction` seems to have a matching\r\nreducer map key - so this appears to be a one-off 🙈\r\n\r\n### Checklist\r\n\r\n- [x] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_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)","sha":"1fa30899ab2ba3f534ebb6620a34513a1431e0ed"}},{"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: Hannah Mudge <Heenawter@users.noreply.github.com> |
||
|
Kibana Machine
|
353ad661fc
|
[8.16] [Fleet] Improve input template API yaml comments (#199168) (#199238)
# Backport This will backport the following commits from `main` to `8.16`: - [[Fleet] Improve input template API yaml comments (#199168)](https://github.com/elastic/kibana/pull/199168) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-11-06T22:01:19Z","message":"[Fleet] Improve input template API yaml comments (#199168)","sha":"8041372868f732530d7fecf1c44fad1f61b631fc","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","ci:project-deploy-observability","v8.16.0","v8.17.0"],"title":"[Fleet] Improve input template API yaml comments","number":199168,"url":"https://github.com/elastic/kibana/pull/199168","mergeCommit":{"message":"[Fleet] Improve input template API yaml comments (#199168)","sha":"8041372868f732530d7fecf1c44fad1f61b631fc"}},"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/199168","number":199168,"mergeCommit":{"message":"[Fleet] Improve input template API yaml comments (#199168)","sha":"8041372868f732530d7fecf1c44fad1f61b631fc"}},{"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: Nicolas Chaulet <nicolas.chaulet@elastic.co> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> |
||
|
Kibana Machine
|
661f90707d
|
[8.16] [Dashboard] Remove modal for inter app from dashboard (#198619) (#199234)
# Backport This will backport the following commits from `main` to `8.16`: - [[Dashboard] Remove modal for inter app from dashboard (#198619)](https://github.com/elastic/kibana/pull/198619) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Rachel Shen","email":"rshen@elastic.co"},"sourceCommit":{"committedDate":"2024-11-06T21:33:25Z","message":"[Dashboard] Remove modal for inter app from dashboard (#198619)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/184257\r\nThis PR removes the modal warning users that unsaved changes would be\r\nlost when navigating away from dashboard to other apps within Kibana.\r\nThe modal is not necessary since unsaved changes are saved in session\r\nstorage. The benefit is that this removes the unnecessary click for\r\nusers.\r\n\r\n\r\nThis does not impact the modal for switching to view mode from edit mode\r\nwith unsaved changes as shown below.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c5bdb0ec-b040-40b0-a511-fd16ad084b90\r\n\r\n\r\n### Checklist\r\n\r\n - [x] Update tests","sha":"4f14c4af416ca5010f9db0ec699c4f8541539f6f","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:prev-major","papercut"],"title":"[Dashboard] Remove modal for inter app from dashboard","number":198619,"url":"https://github.com/elastic/kibana/pull/198619","mergeCommit":{"message":"[Dashboard] Remove modal for inter app from dashboard (#198619)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/184257\r\nThis PR removes the modal warning users that unsaved changes would be\r\nlost when navigating away from dashboard to other apps within Kibana.\r\nThe modal is not necessary since unsaved changes are saved in session\r\nstorage. The benefit is that this removes the unnecessary click for\r\nusers.\r\n\r\n\r\nThis does not impact the modal for switching to view mode from edit mode\r\nwith unsaved changes as shown below.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c5bdb0ec-b040-40b0-a511-fd16ad084b90\r\n\r\n\r\n### Checklist\r\n\r\n - [x] Update tests","sha":"4f14c4af416ca5010f9db0ec699c4f8541539f6f"}},"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/198619","number":198619,"mergeCommit":{"message":"[Dashboard] Remove modal for inter app from dashboard (#198619)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/184257\r\nThis PR removes the modal warning users that unsaved changes would be\r\nlost when navigating away from dashboard to other apps within Kibana.\r\nThe modal is not necessary since unsaved changes are saved in session\r\nstorage. The benefit is that this removes the unnecessary click for\r\nusers.\r\n\r\n\r\nThis does not impact the modal for switching to view mode from edit mode\r\nwith unsaved changes as shown below.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/c5bdb0ec-b040-40b0-a511-fd16ad084b90\r\n\r\n\r\n### Checklist\r\n\r\n - [x] Update tests","sha":"4f14c4af416ca5010f9db0ec699c4f8541539f6f"}}]}] BACKPORT--> Co-authored-by: Rachel Shen <rshen@elastic.co> |
||
|
Kibana Machine
|
4791085e2c
|
[8.16] [Security Solution][Notes] - disable note buttons in the right panel header when in preview mode (#199189) (#199231)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security Solution][Notes] - disable note buttons in the right panel header when in preview mode (#199189)](https://github.com/elastic/kibana/pull/199189) <!--- 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-06T21:14:14Z","message":"[Security Solution][Notes] - disable note buttons in the right panel header when in preview mode (#199189)\n\n## Summary\r\n\r\nThis PR fixes a issue where the `Add note` button and the `+` icon\r\nbutton are clickable when an alert is viewed in preview mode. Users\r\nshould not be able to perform actions here, as the action expands the\r\nflyouts and opens the left panel Notes tab, but the issue is the left\r\npanel now shows a different alert from the right panel. If the user\r\ncloses the preview panel, they now see a different alerts on the left\r\nand right panels but they have no way to know this.\r\n\r\n#### Add note button disabled\r\n\r\nhttps://github.com/user-attachments/assets/20554b60-39a1-4c6d-b215-e502b5b24dbd\r\n\r\n#### + button disabled\r\n\r\nhttps://github.com/user-attachments/assets/df540aed-b583-457d-a9f4-0093a171ddaa\r\n\r\nAlso adding notes should be disabled when in the rule creation page, as\r\nwe do not want to generate notes for alerts that actually do not exist\r\nyet. To be consistent with the other blocks in the flyout header, we\r\nshow a `-`.\r\n\r\nhttps://github.com/user-attachments/assets/b62ecf85-ee0f-4bee-853c-ff1034b5bf25","sha":"53acbab23b29e8aac7d7fdb0dfebac690640339c","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","v8.16.0","backport:version"],"title":"[Security Solution][Notes] - disable note buttons in the right panel header when in preview mode","number":199189,"url":"https://github.com/elastic/kibana/pull/199189","mergeCommit":{"message":"[Security Solution][Notes] - disable note buttons in the right panel header when in preview mode (#199189)\n\n## Summary\r\n\r\nThis PR fixes a issue where the `Add note` button and the `+` icon\r\nbutton are clickable when an alert is viewed in preview mode. Users\r\nshould not be able to perform actions here, as the action expands the\r\nflyouts and opens the left panel Notes tab, but the issue is the left\r\npanel now shows a different alert from the right panel. If the user\r\ncloses the preview panel, they now see a different alerts on the left\r\nand right panels but they have no way to know this.\r\n\r\n#### Add note button disabled\r\n\r\nhttps://github.com/user-attachments/assets/20554b60-39a1-4c6d-b215-e502b5b24dbd\r\n\r\n#### + button disabled\r\n\r\nhttps://github.com/user-attachments/assets/df540aed-b583-457d-a9f4-0093a171ddaa\r\n\r\nAlso adding notes should be disabled when in the rule creation page, as\r\nwe do not want to generate notes for alerts that actually do not exist\r\nyet. To be consistent with the other blocks in the flyout header, we\r\nshow a `-`.\r\n\r\nhttps://github.com/user-attachments/assets/b62ecf85-ee0f-4bee-853c-ff1034b5bf25","sha":"53acbab23b29e8aac7d7fdb0dfebac690640339c"}},"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/199189","number":199189,"mergeCommit":{"message":"[Security Solution][Notes] - disable note buttons in the right panel header when in preview mode (#199189)\n\n## Summary\r\n\r\nThis PR fixes a issue where the `Add note` button and the `+` icon\r\nbutton are clickable when an alert is viewed in preview mode. Users\r\nshould not be able to perform actions here, as the action expands the\r\nflyouts and opens the left panel Notes tab, but the issue is the left\r\npanel now shows a different alert from the right panel. If the user\r\ncloses the preview panel, they now see a different alerts on the left\r\nand right panels but they have no way to know this.\r\n\r\n#### Add note button disabled\r\n\r\nhttps://github.com/user-attachments/assets/20554b60-39a1-4c6d-b215-e502b5b24dbd\r\n\r\n#### + button disabled\r\n\r\nhttps://github.com/user-attachments/assets/df540aed-b583-457d-a9f4-0093a171ddaa\r\n\r\nAlso adding notes should be disabled when in the rule creation page, as\r\nwe do not want to generate notes for alerts that actually do not exist\r\nyet. To be consistent with the other blocks in the flyout header, we\r\nshow a `-`.\r\n\r\nhttps://github.com/user-attachments/assets/b62ecf85-ee0f-4bee-853c-ff1034b5bf25","sha":"53acbab23b29e8aac7d7fdb0dfebac690640339c"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
bbbeb3c9d0
|
[8.16] [SecuritySolution] Change copy (#199160) (#199229)
# Backport This will backport the following commits from `main` to `8.16`: - [[SecuritySolution] Change copy (#199160)](https://github.com/elastic/kibana/pull/199160) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2024-11-06T21:11:44Z","message":"[SecuritySolution] Change copy (#199160)\n\n## Summary\r\n\r\nChange Entity Store enablement copy because it doesn't make sense for\r\nESS.","sha":"05bcf0811892f01c3f637f41df46517d54de70dc","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","v8.16.0","backport:version","v8.17.0"],"title":"[SecuritySolution] Change copy","number":199160,"url":"https://github.com/elastic/kibana/pull/199160","mergeCommit":{"message":"[SecuritySolution] Change copy (#199160)\n\n## Summary\r\n\r\nChange Entity Store enablement copy because it doesn't make sense for\r\nESS.","sha":"05bcf0811892f01c3f637f41df46517d54de70dc"}},"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/199160","number":199160,"mergeCommit":{"message":"[SecuritySolution] Change copy (#199160)\n\n## Summary\r\n\r\nChange Entity Store enablement copy because it doesn't make sense for\r\nESS.","sha":"05bcf0811892f01c3f637f41df46517d54de70dc"}},{"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: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
2095008dd3
|
[8.16] [Search][Index Management] Removing Model deployment from Kibana (#198409) (#199201)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search][Index Management] Removing Model deployment from Kibana (#198409)](https://github.com/elastic/kibana/pull/198409) <!--- 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-06T18:04:24Z","message":"[Search][Index Management] Removing Model deployment from Kibana (#198409)\n\n## Summary\r\n\r\nClicking on the `Try Again` button tries to redeploy and receives an\r\nerror. We tried to disable the `Try Again` button if there are no errors\r\nin deployment stage.\r\n\r\n\r\n### Before\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b1c7b7ce-afba-42ba-a958-d9ad7cbc8777\r\n\r\n### After\r\n\r\n\r\nhttps://github.com/user-attachments/assets/15ca3a78-a1fc-4079-8ab6-f4b54e7ed333\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"bc313f4b48680624a0f778eb02eb10158f604a15","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","v8.16.0","backport:version","v8.17.0"],"title":"[Search][Index Management] Removing Model deployment from Kibana","number":198409,"url":"https://github.com/elastic/kibana/pull/198409","mergeCommit":{"message":"[Search][Index Management] Removing Model deployment from Kibana (#198409)\n\n## Summary\r\n\r\nClicking on the `Try Again` button tries to redeploy and receives an\r\nerror. We tried to disable the `Try Again` button if there are no errors\r\nin deployment stage.\r\n\r\n\r\n### Before\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b1c7b7ce-afba-42ba-a958-d9ad7cbc8777\r\n\r\n### After\r\n\r\n\r\nhttps://github.com/user-attachments/assets/15ca3a78-a1fc-4079-8ab6-f4b54e7ed333\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"bc313f4b48680624a0f778eb02eb10158f604a15"}},"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/198409","number":198409,"mergeCommit":{"message":"[Search][Index Management] Removing Model deployment from Kibana (#198409)\n\n## Summary\r\n\r\nClicking on the `Try Again` button tries to redeploy and receives an\r\nerror. We tried to disable the `Try Again` button if there are no errors\r\nin deployment stage.\r\n\r\n\r\n### Before\r\n\r\n\r\nhttps://github.com/user-attachments/assets/b1c7b7ce-afba-42ba-a958-d9ad7cbc8777\r\n\r\n### After\r\n\r\n\r\nhttps://github.com/user-attachments/assets/15ca3a78-a1fc-4079-8ab6-f4b54e7ed333\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"bc313f4b48680624a0f778eb02eb10158f604a15"}},{"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: Samiul Monir <150824886+Samiul-TheSoccerFan@users.noreply.github.com> |
||
|
Kibana Machine
|
e3e6bd786d
|
[8.16] [Observability] Fix integrations detected twice (#198670) (#199183)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability] Fix integrations detected twice (#198670)](https://github.com/elastic/kibana/pull/198670) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thom Heymann","email":"190132+thomheymann@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-06T16:55:33Z","message":"[Observability] Fix integrations detected twice (#198670)\n\nResolves [#195912](https://github.com/elastic/kibana/issues/195912)\r\n\r\n## Summary\r\n\r\nFixes an issue where integrations were displayed twice in the list of\r\ndetected log files.\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"f410085ffc6e37f284ff72b034ca177f536f7121","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding","v8.16.0","v8.17.0"],"title":"[Observability] Fix integrations detected twice","number":198670,"url":"https://github.com/elastic/kibana/pull/198670","mergeCommit":{"message":"[Observability] Fix integrations detected twice (#198670)\n\nResolves [#195912](https://github.com/elastic/kibana/issues/195912)\r\n\r\n## Summary\r\n\r\nFixes an issue where integrations were displayed twice in the list of\r\ndetected log files.\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"f410085ffc6e37f284ff72b034ca177f536f7121"}},"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/198670","number":198670,"mergeCommit":{"message":"[Observability] Fix integrations detected twice (#198670)\n\nResolves [#195912](https://github.com/elastic/kibana/issues/195912)\r\n\r\n## Summary\r\n\r\nFixes an issue where integrations were displayed twice in the list of\r\ndetected log files.\r\n\r\nCo-authored-by: Joe Reuter <johannes.reuter@elastic.co>","sha":"f410085ffc6e37f284ff72b034ca177f536f7121"}},{"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: Thom Heymann <190132+thomheymann@users.noreply.github.com> |
||
|
Kibana Machine
|
c9292405ee
|
[8.16] [Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812) (#199141)
# Backport This will backport the following commits from `main` to `8.16`: - [[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)](https://github.com/elastic/kibana/pull/198812) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jordan","email":"51442161+JordanSh@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-06T13:52:30Z","message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37","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","v8.16.0","backport:version","v8.17.0"],"title":"[Cloud Security] Fixes SVG flickering and adding insight telemetry","number":198812,"url":"https://github.com/elastic/kibana/pull/198812","mergeCommit":{"message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37"}},"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/198812","number":198812,"mergeCommit":{"message":"[Cloud Security] Fixes SVG flickering and adding insight telemetry (#198812)","sha":"de46e7f0739eb14138655e204d4be77d8e24ff37"}},{"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: Jordan <51442161+JordanSh@users.noreply.github.com> |
||
|
Kibana Machine
|
c1e816018d
|
[8.16] [Search] [Playground] Update use source indices fields hook tests (#198393) (#199139)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search] [Playground] Update use source indices fields hook tests (#198393)](https://github.com/elastic/kibana/pull/198393) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yan Savitski","email":"yan.savitski@elastic.co"},"sourceCommit":{"committedDate":"2024-11-06T13:48:04Z","message":"[Search] [Playground] Update use source indices fields hook tests (#198393)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\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#_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)","sha":"cdb9ef37e67d23c1a5bec27789a4d0398a4f2250","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:prev-minor","v8.16.0"],"title":"[Search] [Playground] Update use source indices fields hook tests","number":198393,"url":"https://github.com/elastic/kibana/pull/198393","mergeCommit":{"message":"[Search] [Playground] Update use source indices fields hook tests (#198393)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\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#_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)","sha":"cdb9ef37e67d23c1a5bec27789a4d0398a4f2250"}},"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/198393","number":198393,"mergeCommit":{"message":"[Search] [Playground] Update use source indices fields hook tests (#198393)\n\n## Summary\r\n\r\nSummarize your PR. If it involves visual changes include a screenshot or\r\ngif.\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#_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)","sha":"cdb9ef37e67d23c1a5bec27789a4d0398a4f2250"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yan Savitski <yan.savitski@elastic.co> |
||
Shahzad
|
817aa96157
|
[8.16] [Fleet/Synthetics] Async bumpRevision to improve performance !! (#198658) (#199080)
# Backport
This will backport the following commits from `main` to `8.16`:
- [Fleet/Synthetics] Async bumpRevision to improve performance !!
(#198658) (
|
||
|
Kibana Machine
|
afcdf0472a
|
[8.16] [Search] Enable AI Assistant in Search solution view (#198941) (#199041)
# Backport This will backport the following commits from `main` to `8.16`: - [[Search] Enable AI Assistant in Search solution view (#198941)](https://github.com/elastic/kibana/pull/198941) <!--- 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-05T18:19:11Z","message":"[Search] Enable AI Assistant in Search solution view (#198941)\n\n## Summary\r\n\r\nThis enables the Observability AI Assistant (which is also the Search AI\r\nAssistant) in the Search solution view.","sha":"62d16709e42e9282dc7235bb4a4fb6b008483021","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","v8.16.0","backport:version","v8.17.0"],"title":"[Search] Enable AI Assistant in Search solution view","number":198941,"url":"https://github.com/elastic/kibana/pull/198941","mergeCommit":{"message":"[Search] Enable AI Assistant in Search solution view (#198941)\n\n## Summary\r\n\r\nThis enables the Observability AI Assistant (which is also the Search AI\r\nAssistant) in the Search solution view.","sha":"62d16709e42e9282dc7235bb4a4fb6b008483021"}},"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/198941","number":198941,"mergeCommit":{"message":"[Search] Enable AI Assistant in Search solution view (#198941)\n\n## Summary\r\n\r\nThis enables the Observability AI Assistant (which is also the Search AI\r\nAssistant) in the Search solution view.","sha":"62d16709e42e9282dc7235bb4a4fb6b008483021"}},{"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: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
Cee Chen
|
1241e78292
|
[8.16] [ML] Fix page header right side items flex responsiveness (#198625) (#198882)
# Backport
This will backport the following commits from `main` to `8.16`:
- [ML] Fix page header right side items flex responsiveness (#198625)
(
|
||
|
Kibana Machine
|
6889c8ecb2
|
[8.16] [Observability] [Alerts table] Fix cannot display alerts error (#198914) (#198939)
# Backport This will backport the following commits from `main` to `8.16`: - [[Observability] [Alerts table] Fix cannot display alerts error (#198914)](https://github.com/elastic/kibana/pull/198914) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bena Kansara","email":"69037875+benakansara@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-05T12:57:32Z","message":"[Observability] [Alerts table] Fix cannot display alerts error (#198914)\n\nResolves https://github.com/elastic/kibana/issues/198912\r\n\r\n### Testing\r\n- Create ES query rule in Observability\r\n- Open Alert flyout of the ES query alert\r\n- Verify that Alert flyout opens as expected","sha":"f8c01d41d2dc6c4c4d096c485b48dc7decafd873","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0","backport:version","v8.17.0","v8.15.4"],"title":"[Observability] [Alerts table] Fix cannot display alerts error","number":198914,"url":"https://github.com/elastic/kibana/pull/198914","mergeCommit":{"message":"[Observability] [Alerts table] Fix cannot display alerts error (#198914)\n\nResolves https://github.com/elastic/kibana/issues/198912\r\n\r\n### Testing\r\n- Create ES query rule in Observability\r\n- Open Alert flyout of the ES query alert\r\n- Verify that Alert flyout opens as expected","sha":"f8c01d41d2dc6c4c4d096c485b48dc7decafd873"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198914","number":198914,"mergeCommit":{"message":"[Observability] [Alerts table] Fix cannot display alerts error (#198914)\n\nResolves https://github.com/elastic/kibana/issues/198912\r\n\r\n### Testing\r\n- Create ES query rule in Observability\r\n- Open Alert flyout of the ES query alert\r\n- Verify that Alert flyout opens as expected","sha":"f8c01d41d2dc6c4c4d096c485b48dc7decafd873"}},{"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.15","label":"v8.15.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Bena Kansara <69037875+benakansara@users.noreply.github.com> |
||
|
Kibana Machine
|
fe73a24e96
|
[8.16] [Synthetics] URL validation softens to allow vars usage !! (#197797) (#197838)
# Backport This will backport the following commits from `main` to `8.16`: - [[Synthetics] URL validation softens to allow vars usage !! (#197797)](https://github.com/elastic/kibana/pull/197797) <!--- 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-10-25T14:33:26Z","message":"[Synthetics] URL validation softens to allow vars usage !! (#197797)\n\n## Summary\r\n\r\nURL validation softens to allow vars usage !!\r\n\r\nFor example \r\n\r\n` should urls: \"${url}\" interpolate --params '{\"url\": \"my-url\"}'`","sha":"3b05b6a7a83df7ff8b929dbbb60c639cc11101d8","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-major","ci:project-deploy-observability","Team:obs-ux-management"],"title":"[Synthetics] URL validation softens to allow vars usage !!","number":197797,"url":"https://github.com/elastic/kibana/pull/197797","mergeCommit":{"message":"[Synthetics] URL validation softens to allow vars usage !! (#197797)\n\n## Summary\r\n\r\nURL validation softens to allow vars usage !!\r\n\r\nFor example \r\n\r\n` should urls: \"${url}\" interpolate --params '{\"url\": \"my-url\"}'`","sha":"3b05b6a7a83df7ff8b929dbbb60c639cc11101d8"}},"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/197797","number":197797,"mergeCommit":{"message":"[Synthetics] URL validation softens to allow vars usage !! (#197797)\n\n## Summary\r\n\r\nURL validation softens to allow vars usage !!\r\n\r\nFor example \r\n\r\n` should urls: \"${url}\" interpolate --params '{\"url\": \"my-url\"}'`","sha":"3b05b6a7a83df7ff8b929dbbb60c639cc11101d8"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> |
||
|
Kibana Machine
|
563c7f1193
|
[8.16] [Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707) (#198906)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)](https://github.com/elastic/kibana/pull/198707) <!--- Backport version: 9.4.3 --> ### 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-05T10:12:33Z","message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179","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:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields","number":198707,"url":"https://github.com/elastic/kibana/pull/198707","mergeCommit":{"message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179"}},"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/198707","number":198707,"mergeCommit":{"message":"[Security GenAI][BUG] Knowledge Base: Show only indices with `semantic_text` fields (#198707)\n\n## Summary\r\n\r\nThis is a fix the next issue:\r\n\r\n> Index input should only list indices with semantic_text fields, not\r\nall indices.\r\n\r\n### Current behaviour\r\n\r\nWe show all available indices\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 14 36\"\r\nsrc=\"https://github.com/user-attachments/assets/cf9d08fd-a809-4530-b653-d12b8e643e45\">\r\n\r\n### Behaviour after the fix\r\n\r\nWe show only indices with `semantic_text` fields\r\n\r\n<img width=\"1311\" alt=\"Screenshot 2024-11-01 at 18 08 29\"\r\nsrc=\"https://github.com/user-attachments/assets/864b5552-aece-4cc6-848a-8f73f88f55dc\">\r\n\r\n### Testing notes\r\n\r\nCreate some indices with `semantic_text` fields. For example, you can do\r\nthat via uploading and indexing a PDF file:\r\n\r\n1. Navigate to Integrations page\r\n2. Select \"Upload a file\"\r\n3. Select and upload a PDF file\r\n4. Press Import button\r\n5. Switch to Advanced tab\r\n6. Fill in \"Index name\"\r\n7. Add additional field > Add semantic text field > Fill in form\r\n * Field: `attachment.content`\r\n * Copy to field: `content`\r\n * Inference endpoint: `elser_model_2`\r\n8. Press Add button\r\n9. Press Import button\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b122722d886b66431108a33d0eac2447a63da179"}},{"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: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
cecf31daf0
|
[8.16] [Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861) (#198889)
# Backport This will backport the following commits from `main` to `8.16`: - [[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)](https://github.com/elastic/kibana/pull/198861) <!--- Backport version: 9.4.3 --> ### 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-05T07:40:59Z","message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee","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:Security Generative AI","backport:version","v8.17.0","v8.16.1"],"title":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests","number":198861,"url":"https://github.com/elastic/kibana/pull/198861","mergeCommit":{"message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee"}},"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/198861","number":198861,"mergeCommit":{"message":"[Security GenAI] Fix and un-skip Knowledge Base Integration Tests (#198861)\n\n## Summary\r\n\r\nThis is a followup to https://github.com/elastic/kibana/pull/198178\r\nwhere we skipped KB integration tests. We enable it with this PR.\r\n\r\nSince it takes a lot of time to setup all Security Labs docs, the idea\r\nis to skip installing those docs when it is not needed. For these tests\r\nwe need to make sure that inference endpoint is setup correctly - labs\r\ndocs are not required in this case.\r\n\r\ncc @stephmilovic","sha":"69c1e5a7dda2708773dfeed2314b0ef74f4537ee"}},{"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: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
mohamedhamed-ahmed
|
93c75219ac
|
[8.16] [Logs Explorer] Fix logs side nav default navigation (#198773) (#198830)
# Backport This will backport the following commits from `main` to `8.16`: - [[Logs Explorer] Fix logs side nav default navigation (#198773)](https://github.com/elastic/kibana/pull/198773) <!--- Backport version: 8.9.8 --> ### 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-04T17:06:13Z","message":"[Logs Explorer] Fix logs side nav default navigation (#198773)\n\ncloses https://github.com/elastic/kibana/issues/198766","sha":"0e4b9e0b60e5fe3346a5336b0f7ccca6e08b9eca","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-logs","v8.15.0","v8.16.0","backport:version","v8.17.0"],"number":198773,"url":"https://github.com/elastic/kibana/pull/198773","mergeCommit":{"message":"[Logs Explorer] Fix logs side nav default navigation (#198773)\n\ncloses https://github.com/elastic/kibana/issues/198766","sha":"0e4b9e0b60e5fe3346a5336b0f7ccca6e08b9eca"}},"sourceBranch":"main","suggestedTargetBranches":["8.15","8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198773","number":198773,"mergeCommit":{"message":"[Logs Explorer] Fix logs side nav default navigation (#198773)\n\ncloses https://github.com/elastic/kibana/issues/198766","sha":"0e4b9e0b60e5fe3346a5336b0f7ccca6e08b9eca"}},{"branch":"8.15","label":"v8.15.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ac40495c04
|
[8.16] [ML] Enable change point detection functional tests (#198702) (#198817)
# Backport This will backport the following commits from `main` to `8.16`: - [[ML] Enable change point detection functional tests (#198702)](https://github.com/elastic/kibana/pull/198702) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-11-04T16:10:24Z","message":"[ML] Enable change point detection functional tests (#198702)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/178258\r\n\r\nEnable change point detection functional tests \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"1411604dd0caaba4ab2b6e46dcd9df0544e245c3","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","v9.0.0","Team:ML","Feature:ML/AIOps","v8.16.0","backport:version","v8.17.0"],"title":"[ML] Enable change point detection functional tests ","number":198702,"url":"https://github.com/elastic/kibana/pull/198702","mergeCommit":{"message":"[ML] Enable change point detection functional tests (#198702)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/178258\r\n\r\nEnable change point detection functional tests \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"1411604dd0caaba4ab2b6e46dcd9df0544e245c3"}},"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/198702","number":198702,"mergeCommit":{"message":"[ML] Enable change point detection functional tests (#198702)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/178258\r\n\r\nEnable change point detection functional tests \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"1411604dd0caaba4ab2b6e46dcd9df0544e245c3"}},{"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: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
fe9df7f39c
|
[8.16] Reducing vulnerability runtime mappings (#198739) (#198787)
# Backport This will backport the following commits from `main` to `8.16`: - [Reducing vulnerability runtime mappings (#198739)](https://github.com/elastic/kibana/pull/198739) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Paulo Silva","email":"paulo.henrique@elastic.co"},"sourceCommit":{"committedDate":"2024-11-04T14:00:35Z","message":"Reducing vulnerability runtime mappings (#198739)\n\n## Summary\r\n\r\nIt closes https://github.com/elastic/security-team/issues/11034\r\n\r\nThis PR removes runtime mappings for vulnerabilities, since they will be\r\nadded on the third party integration on [this\r\nPR](https://github.com/elastic/integrations/pull/11614) before the 8.16\r\nrelease, we can remove the runtime mappings in Kibana in favour of not\r\ncompromising performance.\r\n\r\nCo-authored-by: Maxim Kholod <maxim.kholod@elastic.co>","sha":"10d7926e3b2a943250d0ec2437c8d645486b84bd","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","v8.16.0","backport:version","v8.17.0"],"title":"Reducing vulnerability runtime mappings","number":198739,"url":"https://github.com/elastic/kibana/pull/198739","mergeCommit":{"message":"Reducing vulnerability runtime mappings (#198739)\n\n## Summary\r\n\r\nIt closes https://github.com/elastic/security-team/issues/11034\r\n\r\nThis PR removes runtime mappings for vulnerabilities, since they will be\r\nadded on the third party integration on [this\r\nPR](https://github.com/elastic/integrations/pull/11614) before the 8.16\r\nrelease, we can remove the runtime mappings in Kibana in favour of not\r\ncompromising performance.\r\n\r\nCo-authored-by: Maxim Kholod <maxim.kholod@elastic.co>","sha":"10d7926e3b2a943250d0ec2437c8d645486b84bd"}},"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/198739","number":198739,"mergeCommit":{"message":"Reducing vulnerability runtime mappings (#198739)\n\n## Summary\r\n\r\nIt closes https://github.com/elastic/security-team/issues/11034\r\n\r\nThis PR removes runtime mappings for vulnerabilities, since they will be\r\nadded on the third party integration on [this\r\nPR](https://github.com/elastic/integrations/pull/11614) before the 8.16\r\nrelease, we can remove the runtime mappings in Kibana in favour of not\r\ncompromising performance.\r\n\r\nCo-authored-by: Maxim Kholod <maxim.kholod@elastic.co>","sha":"10d7926e3b2a943250d0ec2437c8d645486b84bd"}},{"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: Paulo Silva <paulo.henrique@elastic.co> |