mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
82780 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Benjamin Ironside Goldstein
|
e628154462 |
[docs] Adds Knowledge Base audit logs to audit events (#214809)
## Summary
Part of https://github.com/elastic/docs-content/issues/280. More info
here: https://github.com/elastic/security-team/issues/11367
Minor docs update, updates the sections where the new audit events for
AI Assistant Knowledge Base actions appear. If this is approved, a
similar change should be applied to the 9.0 docs.
(cherry picked from commit
|
||
Elena Stoeva
|
6eafb929e8
|
[8.18] Fix data streams API integration tests (#214731)
Fixes https://github.com/elastic/kibana/issues/209014 ## Summary This PR updates the 8.18 data stream API integration tests to fix the failures in the 8.x -> 9.0 forward compatibility tests. To run the forward-compatibility tests locally: ``` ES_SNAPSHOT_MANIFEST="https://storage.googleapis.com/kibana-ci-es-snapshots-daily/9.0.0/manifest-latest-verified.json" node scripts/functional_tests_server.js --config ./x-pack/test/api_integration/apis/management/config.ts ``` and ``` ES_SNAPSHOT_MANIFEST="https://storage.googleapis.com/kibana-ci-es-snapshots-daily/9.0.0/manifest-latest-verified.json" node scripts/functional_test_runner.js --config ./x-pack/test/api_integration/apis/management/config.ts --grep="Data streams" ``` |
||
Kibana Machine
|
0bceaa639d
|
[8.18] [Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552) (#214789)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)](https://github.com/elastic/kibana/pull/214552) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-17T14:27:33Z","message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Feature: Observability Onboarding","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions","number":214552,"url":"https://github.com/elastic/kibana/pull/214552","mergeCommit":{"message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214552","number":214552,"mergeCommit":{"message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> |
||
|
Kibana Machine
|
0e4696c8d4
|
[8.18] [ES|QL] Fixes the comment autocomplete when there is a space (#214696) (#214755)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fixes the comment autocomplete when there is a space (#214696)](https://github.com/elastic/kibana/pull/214696) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T13:07:09Z","message":"[ES|QL] Fixes the comment autocomplete when there is a space (#214696)\n\n## Summary\n\nFixes the problem with autocomplete been triggered in comments\n\n**Before**\n\n (#214751)
# Backport This will backport the following commits from `main` to `8.18`: - [[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)](https://github.com/elastic/kibana/pull/214159) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T13:12:17Z","message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:all-open","v9.1.0","v8.19.0","v8.18.1"],"title":"[Inference Endpoints] Fix non-required secret fields getting mangled","number":214159,"url":"https://github.com/elastic/kibana/pull/214159","mergeCommit":{"message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214159","number":214159,"mergeCommit":{"message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
88eb16d8ca
|
[8.18] [Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801) (#214743)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)](https://github.com/elastic/kibana/pull/213801) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Edgar Santos","email":"edgar.santos@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T12:56:13Z","message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:Detection Rules","Feature:Detection Rule Preview","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930)","number":213801,"url":"https://github.com/elastic/kibana/pull/213801","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213801","number":213801,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Edgar Santos <edgar.santos@elastic.co> |
||
|
Kibana Machine
|
c31e908fe7
|
[8.18] [Automatic Import] Fix chunking of samples in ecs mapping (#214702) (#214737)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Fix chunking of samples in ecs mapping (#214702)](https://github.com/elastic/kibana/pull/214702) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T12:52:37Z","message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix chunking of samples in ecs mapping","number":214702,"url":"https://github.com/elastic/kibana/pull/214702","mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214702","number":214702,"mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Jacek Kolezynski
|
80909da78f
|
[8.18] [Security Solution] Add note about removing bulk crud API in v9.0 and migrate examples (#213260) (#214710)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[Security Solution] Add note about removing bulk crud API in v9.0 and migrate examples (#213260)](https://github.com/elastic/kibana/pull/213260) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T19:55:22Z","message":"[Security Solution] Add note about removing bulk crud API in v9.0 and migrate examples (#213260)\n\n**Partially addresses:** #211808,\nhttps://github.com/elastic/security-docs/issues/5981 (internal)\n\n## Summary\n\nThis is the third part of the migration effort, containing changes for\nBULK CRUD:\n- adding a note informing of removing this API in v.9.0\n- migrating examples\n- adding infos in description\n\nThis PR will be backported only to versions for Kibana v8\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip3/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Georgii Gorbachev <banderror@gmail.com>","sha":"e334449b82da6fad82808091e860f4c2248fcb74","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","APIDocs","Team:Detection Rule Management","backport:version","8.18 candidate","v8.18.0","v8.19.0"],"title":"[Security Solution] Add note about removing bulk crud API in v9.0 and migrate examples","number":213260,"url":"https://github.com/elastic/kibana/pull/213260","mergeCommit":{"message":"[Security Solution] Add note about removing bulk crud API in v9.0 and migrate examples (#213260)\n\n**Partially addresses:** #211808,\nhttps://github.com/elastic/security-docs/issues/5981 (internal)\n\n## Summary\n\nThis is the third part of the migration effort, containing changes for\nBULK CRUD:\n- adding a note informing of removing this API in v.9.0\n- migrating examples\n- adding infos in description\n\nThis PR will be backported only to versions for Kibana v8\n\n# Testing\n1. cd x-pack/solutions/security/plugins/security_solution\n2. yarn openapi:bundle:detections \n3. Take the bundled file\n(docs/openapi/ess/security_solution_detections_api_2023_10_31.bundled.schema.yaml)\nand load it into bump.sh console to see the changes.\n4. Compare the changes with the [Legacy\ndocumentation](https://www.elastic.co/guide/en/security/current/rule-api-overview.html)\n\nYou can also use this [link](https://bump.sh/jkelas2/doc/kibana_wip3/)\nwhere I deployed the generated bundled doc.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Georgii Gorbachev <banderror@gmail.com>","sha":"e334449b82da6fad82808091e860f4c2248fcb74"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Jean-Louis Leysens
|
80ca1caf91
|
[8.18] [UA] Use reindex_required metadata to drive corrective actions (#214532) (#214643)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Use `reindex_required` metadata to drive corrective actions (#214532)](https://github.com/elastic/kibana/pull/214532) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T18:50:43Z","message":"[UA] Use `reindex_required` metadata to drive corrective actions (#214532)\n\n## Summary\n\nTested locally and critical old data deprecations are still surfaced as\nexpected\n\n<img width=\"586\" alt=\"Screenshot 2025-03-14 at 10 12 50\"\nsrc=\"https://github.com/user-attachments/assets/25d87fbd-7c98-45e0-a86a-d513ea455571\"\n/>","sha":"26aba9287821f289deb11b27079a9a7d0945c714","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","Feature:Upgrade Assistant","backport:version","v8.18.0","v8.19.0","v8.18.1"],"title":"[UA] Use `reindex_required` metadata to drive corrective actions","number":214532,"url":"https://github.com/elastic/kibana/pull/214532","mergeCommit":{"message":"[UA] Use `reindex_required` metadata to drive corrective actions (#214532)\n\n## Summary\n\nTested locally and critical old data deprecations are still surfaced as\nexpected\n\n<img width=\"586\" alt=\"Screenshot 2025-03-14 at 10 12 50\"\nsrc=\"https://github.com/user-attachments/assets/25d87fbd-7c98-45e0-a86a-d513ea455571\"\n/>","sha":"26aba9287821f289deb11b27079a9a7d0945c714"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Shahzad
|
4d203877e4
|
[8.18] [SLOs Annotations] Fix rendering issue with annotations (#214157) (#214542)
# Backport This will backport the following commits from `main` to `8.18`: - [[SLOs Annotations] Fix rendering issue with annotations (#214157)](https://github.com/elastic/kibana/pull/214157) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-13T21:20:43Z","message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SLOs Annotations] Fix rendering issue with annotations","number":214157,"url":"https://github.com/elastic/kibana/pull/214157","mergeCommit":{"message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214490","number":214490,"state":"MERGED","mergeCommit":{"sha":"2e4531093e8b6f15b22d719f724f498622ee9143","message":"[9.0] [SLOs Annotations] Fix rendering issue with annotations (#214157) (#214490)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[SLOs Annotations] Fix rendering issue with annotations\n(#214157)](https://github.com/elastic/kibana/pull/214157)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214157","number":214157,"mergeCommit":{"message":"[SLOs Annotations] Fix rendering issue with annotations (#214157)\n\n## Summary\n\nfixes https://github.com/elastic/kibana/issues/210198\n\nFix rendering issue with annotations !!\n\nThis has been done because react suspense doesn't plays nicely with\nelastic/chart rendering. And we have to render annotation with charts\ndynamically.","sha":"ea40a0a38a0a679f23a046ab5d0ce3025428c715"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Christos Nasikas
|
12996e20b2
|
[8.18] [Cases] Improve unit test flakiness (#212489) (#214676)
# Backport This will backport the following commits from `main` to `8.18`: - [[Cases] Improve unit test flakiness (#212489)](https://github.com/elastic/kibana/pull/212489) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T17:17:13Z","message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Cases] Improve unit test flakiness","number":212489,"url":"https://github.com/elastic/kibana/pull/212489","mergeCommit":{"message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212489","number":212489,"mergeCommit":{"message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Dmitrii Shevchenko
|
f6e91fbdf5
|
[8.18] [Security Solution] Remove the customization check when importing rules (#214577) (#214651)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Remove the customization check when importing rules (#214577)](https://github.com/elastic/kibana/pull/214577) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T19:14:32Z","message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Remove the customization check when importing rules","number":214577,"url":"https://github.com/elastic/kibana/pull/214577","mergeCommit":{"message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214577","number":214577,"mergeCommit":{"message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
3f9df6da70
|
[8.18] [UII] Allow creating a new agentless integration to open status flyout automatically (#214503) (#214669)
# Backport This will backport the following commits from `main` to `8.18`: - [[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)](https://github.com/elastic/kibana/pull/214503) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2025-03-14T22:10:38Z","message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[UII] Allow creating a new agentless integration to open status flyout automatically","number":214503,"url":"https://github.com/elastic/kibana/pull/214503","mergeCommit":{"message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214503","number":214503,"mergeCommit":{"message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1"}}]}] BACKPORT--> Co-authored-by: Jen Huang <its.jenetic@gmail.com> |
||
|
Kibana Machine
|
a61cb1d4b1
|
[8.18] [Security solution] Destructure telemetryMetadata from subActionParams in order not to pass to OpenAI (#214640) (#214657)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)](https://github.com/elastic/kibana/pull/214640) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T20:26:49Z","message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.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.18.0","v9.1.0","v8.19.0"],"title":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI","number":214640,"url":"https://github.com/elastic/kibana/pull/214640","mergeCommit":{"message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214640","number":214640,"mergeCommit":{"message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
elastic-renovate-prod[bot]
|
a54a7a792f
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 66d427a (8.18) (#214629)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `3f6bcf4` -> `66d427a` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
4ca5ca502c
|
[8.18] [Obs AI Assistant] Decrease log level to debug (#214598) (#214624)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Decrease log level to debug (#214598)](https://github.com/elastic/kibana/pull/214598) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T17:14:29Z","message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","v9.1.0"],"title":"[Obs AI Assistant] Decrease log level to debug","number":214598,"url":"https://github.com/elastic/kibana/pull/214598","mergeCommit":{"message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214598","number":214598,"mergeCommit":{"message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
|
Kibana Machine
|
84d29d7773
|
[8.18] [Security Solution] Siem migrations/copy changes rule translations (#214437) (#214607)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Siem migrations/copy changes rule translations (#214437)](https://github.com/elastic/kibana/pull/214437) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:15:09Z","message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Siem migrations/copy changes rule translations","number":214437,"url":"https://github.com/elastic/kibana/pull/214437","mergeCommit":{"message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214437","number":214437,"mergeCommit":{"message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
a2fea44c48
|
[8.18] [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506) (#214616)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)](https://github.com/elastic/kibana/pull/214506) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:41:40Z","message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.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.18.0","v9.1.0","v8.19.0","v8.18.1"],"title":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations","number":214506,"url":"https://github.com/elastic/kibana/pull/214506","mergeCommit":{"message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214506","number":214506,"mergeCommit":{"message":"[Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations (#214506)\n\n## [Security Solution] [Attack discovery] Display error messages for invalid Anonymization configurations\n\nThis PR detects invalid Anonymization configurations when generating Attack discoveries.\n\nIt displays an error message when:\n\n- The Security AI Anonymization settings are configured to not allow _any_ fields, as reported in <https://github.com/elastic/kibana/issues/214310>\n- The Security AI Anonymization settings are configured to not allow the `_id` field, as reported by @aarju\n\n### Out of scope: detecting configurations that don't include enough useful fields\n\nThe default fields in the Security AI Anonymization settings were chosen because they are most likely to provide relevant context for the AI Assistant and Attack discovery.\n\nHowever, there isn't a well defined threshold for the minimum set of useful fields.\n\nFor example, Attack discovery may still produce useful results (depending on the data), if the `user.name`, `host.name`, and `source.ip` fields are not allowed, but in most cases omitting these important fields will reduce the quality of results.\n\nAnother example: A configuration that **only** allows just **two** fields, for example the `_id` field AND `user.name` fields is valid, but NOT _useful_.\n\n- Detecting configurations that don't include enough _useful_ fields is beyond the scope of this PR\n- Configurations that **only** allow the `_id` field are _valid_, but not _useful_\n\n#### Desk testing\n\n1. Navigate to Stack Management > AI Assistants > Security\n\n2. Configure the Security AI Anonymization settings to deny all fields.\n\nNote: At the time of this writing, using the bulk actions to update all `102` default fields may result in an `Unable to load page` error that appears below the table when it is saved. Refreshing the page reveals the settings are not updated after clicking save. As a workaround for this separate, unrelated issue, apply bulk actions to only one page at a time, and be sure to refresh the page after saving changes to verify the update(s) before continuing to the next step.\n\n3. Navigate to Security > Attack discovery\n\n4. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow any fields. Fields must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n\n\n5. Once again, navigate to Stack Management > AI Assistants > Security\n\n6. Allow all the (`102`) default fields\n\n7. Once again, navigate to Security > Attack discovery\n\n8. Click `Generate`\n\n**Expected result**\n\n- Attack discoveries are generated\n\n9. Navigate back to Stack Management > AI Assistants > Security\n\n10. Configure the `_id` field, and another (arbitrary) field to NOT be allowed\n\n11. Navigate back to Security > Attack discovery\n\n12. Click `Generate`\n\n**Expected result**\n\n- The following error message is displayed:\n\n```\nYour Security AI Anonymization settings are configured to not allow the _id field. The _id field must be allowed to generate Attack discoveries.\n```\n\nas illustrated by the screenshot below:\n\n","sha":"c631bdd574d4c8cf3157ea64b67c0db91fc96f19"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Andrew Macri <andrew.macri@elastic.co> |
||
|
Kibana Machine
|
0cfc64b271
|
[8.18] Fix checkPrivilege to query with indicies (#214002) (#214610)
# Backport This will backport the following commits from `main` to `8.18`: - [Fix checkPrivilege to query with indicies (#214002)](https://github.com/elastic/kibana/pull/214002) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T16:10:05Z","message":"Fix checkPrivilege to query with indicies (#214002)\n\n## Summary\n`apmIndices` has the form: \n```\n \"transaction\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"span\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"error\": \"logs-apm*,apm-*,logs-*.otel-*\",\n \"metric\": \"metrics-apm*,apm-*,metrics-*.otel-*\",\n \"onboarding\": \"apm-*\",\n \"sourcemap\": \"apm-*\"\n```\n\n`mapValues(apmIndices, () => ['read']),` was producing an object that\nlooked like :\n```\n{\n \"transaction\": [\n \"read\"\n ],\n \"span\": [\n \"read\"\n ],\n \"error\": [\n \"read\"\n ],\n \"metric\": [\n \"read\"\n ],\n \"onboarding\": [\n \"read\"\n ],\n \"sourcemap\": [\n \"read\"\n ]\n}\n```\n\nIt seems this ought to check privileges on the actual indices, so this\nPR restructures the `index` parameter to this :\n \n```\n{\n \"traces-apm*\": [\n \"read\"\n ],\n \"apm-*\": [\n \"read\"\n ],\n \"traces-*.otel-*\": [\n \"read\"\n ],\n \"logs-apm*\": [\n \"read\"\n ],\n \"logs-*.otel-*\": [\n \"read\"\n ],\n \"metrics-apm*\": [\n \"read\"\n ],\n \"metrics-*.otel-*\": [\n \"read\"\n ]\n```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df90c8f2a540a04df11e760554820eec0e82f0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"Fix checkPrivilege to query with indicies","number":214002,"url":"https://github.com/elastic/kibana/pull/214002","mergeCommit":{"message":"Fix checkPrivilege to query with indicies (#214002)\n\n## Summary\n`apmIndices` has the form: \n```\n \"transaction\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"span\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"error\": \"logs-apm*,apm-*,logs-*.otel-*\",\n \"metric\": \"metrics-apm*,apm-*,metrics-*.otel-*\",\n \"onboarding\": \"apm-*\",\n \"sourcemap\": \"apm-*\"\n```\n\n`mapValues(apmIndices, () => ['read']),` was producing an object that\nlooked like :\n```\n{\n \"transaction\": [\n \"read\"\n ],\n \"span\": [\n \"read\"\n ],\n \"error\": [\n \"read\"\n ],\n \"metric\": [\n \"read\"\n ],\n \"onboarding\": [\n \"read\"\n ],\n \"sourcemap\": [\n \"read\"\n ]\n}\n```\n\nIt seems this ought to check privileges on the actual indices, so this\nPR restructures the `index` parameter to this :\n \n```\n{\n \"traces-apm*\": [\n \"read\"\n ],\n \"apm-*\": [\n \"read\"\n ],\n \"traces-*.otel-*\": [\n \"read\"\n ],\n \"logs-apm*\": [\n \"read\"\n ],\n \"logs-*.otel-*\": [\n \"read\"\n ],\n \"metrics-apm*\": [\n \"read\"\n ],\n \"metrics-*.otel-*\": [\n \"read\"\n ]\n```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df90c8f2a540a04df11e760554820eec0e82f0e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214002","number":214002,"mergeCommit":{"message":"Fix checkPrivilege to query with indicies (#214002)\n\n## Summary\n`apmIndices` has the form: \n```\n \"transaction\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"span\": \"traces-apm*,apm-*,traces-*.otel-*\",\n \"error\": \"logs-apm*,apm-*,logs-*.otel-*\",\n \"metric\": \"metrics-apm*,apm-*,metrics-*.otel-*\",\n \"onboarding\": \"apm-*\",\n \"sourcemap\": \"apm-*\"\n```\n\n`mapValues(apmIndices, () => ['read']),` was producing an object that\nlooked like :\n```\n{\n \"transaction\": [\n \"read\"\n ],\n \"span\": [\n \"read\"\n ],\n \"error\": [\n \"read\"\n ],\n \"metric\": [\n \"read\"\n ],\n \"onboarding\": [\n \"read\"\n ],\n \"sourcemap\": [\n \"read\"\n ]\n}\n```\n\nIt seems this ought to check privileges on the actual indices, so this\nPR restructures the `index` parameter to this :\n \n```\n{\n \"traces-apm*\": [\n \"read\"\n ],\n \"apm-*\": [\n \"read\"\n ],\n \"traces-*.otel-*\": [\n \"read\"\n ],\n \"logs-apm*\": [\n \"read\"\n ],\n \"logs-*.otel-*\": [\n \"read\"\n ],\n \"metrics-apm*\": [\n \"read\"\n ],\n \"metrics-*.otel-*\": [\n \"read\"\n ]\n```\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df90c8f2a540a04df11e760554820eec0e82f0e"}}]}] BACKPORT--> Co-authored-by: Bryce Buchanan <75274611+bryce-b@users.noreply.github.com> |
||
|
Kibana Machine
|
9ecdbde42d
|
[8.18] [Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510) (#214605)
# Backport This will backport the following commits from `main` to `8.18`: - [[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)](https://github.com/elastic/kibana/pull/213510) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-14T16:10:27Z","message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:Detection Engine","v9.1.0"],"title":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component","number":213510,"url":"https://github.com/elastic/kibana/pull/213510","mergeCommit":{"message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213510","number":213510,"mergeCommit":{"message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
44074fe4cb
|
[8.18] [kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185) (#214582)
# Backport This will backport the following commits from `main` to `8.18`: - [[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)](https://github.com/elastic/kibana/pull/214185) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T13:54:08Z","message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"[kbn/server-route-repository] Use appropriate log level based on HTTP status","number":214185,"url":"https://github.com/elastic/kibana/pull/214185","mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214185","number":214185,"mergeCommit":{"message":"[kbn/server-route-repository] Use appropriate log level based on HTTP status (#214185)","sha":"f2af002a5e51594b0ae2e195bac7f5a7dfe9c383"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co> |
||
Hannah Mudge
|
bf928ce52b
|
[Controls] Fix data view ID injection (#214492)
Closes https://github.com/elastic/kibana/issues/214265 ## Summary https://github.com/elastic/kibana/pull/193067 introduced a bug where the valid injected dataview ID was getting overwritten by the invalid reference ID in `controlConfig`.  This was unknowingly fixed in https://github.com/elastic/kibana/pull/211851 when we rewrote the injection logic - however, this PR was not backported to all the same versions that the bug existed on. To keep backporting simple, I have opted to simply fix the original broken injection logic rather than backporting that entire PR. |
||
Jan Monschke
|
0fef04ccc6
|
[8.18] [Threat Hunting Investigations] Improve API docs for notes/timeline (#213584) (#214528)
# Backport This will backport the following commits from `main` to `8.18`: - [[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)](https://github.com/elastic/kibana/pull/213584) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T17:55:54Z","message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Investigations","backport:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Improve API docs for notes/timeline","number":213584,"url":"https://github.com/elastic/kibana/pull/213584","mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214261","number":214261,"state":"MERGED","mergeCommit":{"sha":"77caf7c24a7424c52e5b37107768ce3d4ff15bfb","message":"[9.0] [Threat Hunting Investigations] Improve API docs for notes/timeline (#213584) (#214261)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Threat Hunting Investigations] Improve API docs for notes/timeline\n(#213584)](https://github.com/elastic/kibana/pull/213584)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jan Monschke <jan.monschke@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213584","number":213584,"mergeCommit":{"message":"[Threat Hunting Investigations] Improve API docs for notes/timeline (#213584)\n\n## Summary\n\n[META\nissue](https://github.com/elastic/security-docs-internal/issues/57)\n\nThis PR improves the API documentation for timeline/notes/pinned events\nas per the definition in the meta issue.\n\n### Notes\n#### Timeline API\n- `eventType`:\n\t- is always set to `all`\n\t- looks like it's been superseded by dataView?\n\t- I marked it as `deperecated` \n- `eventIdToNoteIds`:\n- there's a type mismatch between what the frontend expects and what is\nreturned\n\t- also it does not seem to be used anymore?\n\t- it needs to be investigated further\n#### Notes API\n- `GlobalNote`:\n\t- looks like it's not used anymore\n\t- I removed it, nothing broke\n- `eventIngested`, `eventTimestamp`, `eventDataView` and `overrideOwner`\nare all not used on the patch note endpoint, I removed them. The\n`event*` ones I have never seen before to be honest.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e3311c516b45999e875b92ff14140a3197babfc6"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
482eec6598
|
[8.18] [Security Solution] Batch prebuilt rule installation (#214441) (#214575)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Batch prebuilt rule installation (#214441)](https://github.com/elastic/kibana/pull/214441) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T13:39:32Z","message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","performance","release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Batch prebuilt rule installation","number":214441,"url":"https://github.com/elastic/kibana/pull/214441","mergeCommit":{"message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214441","number":214441,"mergeCommit":{"message":"[Security Solution] Batch prebuilt rule installation (#214441)\n\n**This is a follow-up to:https://github.com/elastic/kibana/pull/211045**\n\n## Summary \n\nThis PR removes inefficiencies in prebuilt rule installation memory\nconsumption.\n\n### Before\n\nIn the worst-case scenario: \n\n1. All currently installed prebuilt rules were fully loaded into memory.\n2. All latest rule versions from the rule packages were fully loaded\ninto memory.\n3. All base rule versions were pulled into memory, even though they were\nnot used.\n4. The algorithm then checked which rules could be installed and\ninstalled them all at once.\n\n### After\n\n1. Pull only aggregated information about installed rules (only\n`rule_id` and `versions`).\n2. Pull the same lightweight aggregated info about the latest rules in\nthe package.\n3. Using the collected `rule_id`s, fetch rule assets and install them in\nsmall batches of up to 100 rules.","sha":"6d9fc21db92dd5e02d930971a5a1cf32a97386f0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dmitrii Shevchenko <dmitrii.shevchenko@elastic.co> |
||
|
Kibana Machine
|
60674471cb
|
[8.18] [EDR Workflows] Rename enforce_registry_filters advanced option (#214106) (#214548)
# Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)](https://github.com/elastic/kibana/pull/214106) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T10:55:16Z","message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Rename `enforce_registry_filters` advanced option","number":214106,"url":"https://github.com/elastic/kibana/pull/214106","mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214106","number":214106,"mergeCommit":{"message":"[EDR Workflows] Rename `enforce_registry_filters` advanced option (#214106)\n\n## Summary\n\nThis PR renames the path for the following advanced option from\n`windows.advanced.events.registry.enforce_registry_filters` to\n`windows.advanced.events.enforce_registry_filters` in order to harmonize\nwith Endpoint.\n\nmigration is not added, see this comment for rationale:\nhttps://github.com/elastic/kibana/issues/212526#issuecomment-2724023199\n\n### Release note\n\nElastic Defend package policy's ineffective advanced option\n`enforce_registry_filters` is replaced with a new field which now\nprovides the expected effect.\nManual act is needed from users to fill the new field, while the old\nfield is still visible in policy response.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"b9a258723d06bcf29392f19e3a80c544e6550fa2"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co> |
||
|
Kibana Machine
|
dc84273918
|
[8.18] [Search] [Synonyms] Synonym Rule flyout update (#213433) (#214397)
# Backport This will backport the following commits from `main` to `8.18`: - [[Search] [Synonyms] Synonym Rule flyout update (#213433)](https://github.com/elastic/kibana/pull/213433) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:35:11Z","message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","ci:project-deploy-elasticsearch","backport:version","v9.1.0","v8.19.0","v8.18.1"],"title":"[Search] [Synonyms] Synonym Rule flyout update","number":213433,"url":"https://github.com/elastic/kibana/pull/213433","mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213433","number":213433,"mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co> |
||
Antonio
|
09fec93596
|
[8.18] [ResponseOps][MW] Use date format from settings in MW UI (#211576) (#214543)
# Backport This will backport the following commits from `main` to `8.18`: - [[ResponseOps][MW] Use date format from settings in MW UI (#211576)](https://github.com/elastic/kibana/pull/211576) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-03-07T12:45:48Z","message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][MW] Use date format from settings in MW UI","number":211576,"url":"https://github.com/elastic/kibana/pull/211576","mergeCommit":{"message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211576","number":211576,"mergeCommit":{"message":"[ResponseOps][MW] Use date format from settings in MW UI (#211576)\n\nCloses #199315\n\n## Summary\n\nThis PR changes the Maintenance Window UI to respect the date format\nconfigured in Kibana's advanced settings.\n\n3 places needed changing:\n- Maintenance window list.\n- Maintenance window creation page.\n- Event popover in the maintenance window list(for recurring MWs).","sha":"2ead636ebd3d8dc911dd870111c8e016035169c1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214438","number":214438,"state":"MERGED","mergeCommit":{"sha":"e74dfe03009087cf65fce16bf43c4053120aff46","message":"[8.x] [ResponseOps][MW] Use date format from settings in MW UI (#211576) (#214438)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ResponseOps][MW] Use date format from settings in MW UI\n(#211576)](https://github.com/elastic/kibana/pull/211576)\n\n<!--- Backport version: 9.6.6 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n<!--BACKPORT\n[{\"author\":{\"name\":\"Antonio\",\"email\":\"antonio.coelho@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-03-07T12:45:48Z\",\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"Team:ResponseOps\",\"backport\nmissing\",\"backport:version\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[ResponseOps][MW]\nUse date format from settings in MW\nUI\",\"number\":211576,\"url\":\"https://github.com/elastic/kibana/pull/211576\",\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/211576\",\"number\":211576,\"mergeCommit\":{\"message\":\"[ResponseOps][MW]\nUse date format from settings in MW UI (#211576)\\n\\nCloses #199315\\n\\n##\nSummary\\n\\nThis PR changes the Maintenance Window UI to respect the date\nformat\\nconfigured in Kibana's advanced settings.\\n\\n3 places needed\nchanging:\\n- Maintenance window list.\\n- Maintenance window creation\npage.\\n- Event popover in the maintenance window list(for recurring\nMWs).\",\"sha\":\"2ead636ebd3d8dc911dd870111c8e016035169c1\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
James Gowdy
|
fe127ae72e
|
[8.18] [ML] Fixing ML migration help URL (#214400) (#214534)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[ML] Fixing ML migration help URL (#214400)](https://github.com/elastic/kibana/pull/214400) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T16:55:43Z","message":"[ML] Fixing ML migration help URL (#214400)\n\nThe docs path has changed and the upgrade assistant link for ML is\nincorrect.","sha":"aa1c935cdb0d4cba862b27801c7dd3b7a5638ba3","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","backport:version","v8.18.0","v8.19.0"],"title":"[ML] Fixing ML migration help URL","number":214400,"url":"https://github.com/elastic/kibana/pull/214400","mergeCommit":{"message":"[ML] Fixing ML migration help URL (#214400)\n\nThe docs path has changed and the upgrade assistant link for ML is\nincorrect.","sha":"aa1c935cdb0d4cba862b27801c7dd3b7a5638ba3"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Gerard Soldevila
|
9d83ecf19a
|
[8.18] [UA] Do not allow reindexing data_stream backing indices (and other enhancements) (#213755) (#214386)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Do not allow reindexing data_stream backing indices (and other enhancements) (#213755)](https://github.com/elastic/kibana/pull/213755) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T13:34:47Z","message":"[UA] Do not allow reindexing data_stream backing indices (and other enhancements) (#213755)\n\n## Summary\n\nThe PR brings the following improvements to the UA ES deprecations\nflows:\n\n* Remove the \"Reindex\" option for _Frozen index_ deprecations that are\nrelated to a data stream's backing index (backing indices cannot be\nalias-based, see\n[thread](https://elastic.slack.com/archives/C08A04N8XHV/p1741017934359239)).\n* Propagate `\"isClosedIndex\"` information to the UI side, so that we can\nshow a warning message in the reindex flows flyouts. The [original\nfunctionality](https://github.com/elastic/kibana/pull/58890) got lost in\nthe woods.\n* Propagate `\"isClosedIndex\", \"isFrozenIndex\", \"isReadonly\"` properties\nas part of the `correctiveAction` details ONLY for _index_settings\nmigrations_, instead of doing it as top level properties for all\nmigrations. These properties did not make for most migration types.\n* Big refactor in `migrations.ts` file (server side). The logic for\nobtaining, filtering and enriching ES deprecations had become quite\nfragmented and hard to read. @Bamieh @jloleysens please take a close\nlook at this one.\n* Improve existing type definitions.","sha":"f2ae05909dd81e3cc368173b350b331587a99d8d","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v8.18.0","v8.19.0"],"title":"[UA] Do not allow reindexing data_stream backing indices (and other enhancements)","number":213755,"url":"https://github.com/elastic/kibana/pull/213755","mergeCommit":{"message":"[UA] Do not allow reindexing data_stream backing indices (and other enhancements) (#213755)\n\n## Summary\n\nThe PR brings the following improvements to the UA ES deprecations\nflows:\n\n* Remove the \"Reindex\" option for _Frozen index_ deprecations that are\nrelated to a data stream's backing index (backing indices cannot be\nalias-based, see\n[thread](https://elastic.slack.com/archives/C08A04N8XHV/p1741017934359239)).\n* Propagate `\"isClosedIndex\"` information to the UI side, so that we can\nshow a warning message in the reindex flows flyouts. The [original\nfunctionality](https://github.com/elastic/kibana/pull/58890) got lost in\nthe woods.\n* Propagate `\"isClosedIndex\", \"isFrozenIndex\", \"isReadonly\"` properties\nas part of the `correctiveAction` details ONLY for _index_settings\nmigrations_, instead of doing it as top level properties for all\nmigrations. These properties did not make for most migration types.\n* Big refactor in `migrations.ts` file (server side). The logic for\nobtaining, filtering and enriching ES deprecations had become quite\nfragmented and hard to read. @Bamieh @jloleysens please take a close\nlook at this one.\n* Improve existing type definitions.","sha":"f2ae05909dd81e3cc368173b350b331587a99d8d"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
efed88be26
|
[8.18] [Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287) (#214515)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)](https://github.com/elastic/kibana/pull/214287) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis Plumlee","email":"56367316+dplumlee@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T07:20:37Z","message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing","number":214287,"url":"https://github.com/elastic/kibana/pull/214287","mergeCommit":{"message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214287","number":214287,"mergeCommit":{"message":"[Security Solution] Reverts all remaining diff algorithm fields to return Target version when base version is missing (#214287)\n\n## Summary\n\nOriginally we had intended to have the prebuilt rule diff algorithms\nmerge non-functional fields when the field's base version was missing\nand a rule was marked as customized as described in\nhttps://github.com/elastic/kibana/issues/210358\n\n> - When the rule has a missing base version and is marked as\ncustomized:\n> - We should attempt to merge all non-functional mergeable fields (any\nfield that doesn't have consequences with how the rule runs e.g. tags)\nand return them as SOLVABLE_CONFLICT\n\nWe ended up changing this logic to return the `Target` version for every\nfield that fit that description\n(https://github.com/elastic/kibana/pull/214161 and\nhttps://github.com/elastic/kibana/pull/213757) besides `tags` and in\norder to support consistency rather than a very minor edge case, we now\njust return the target version for every field with a missing base\nversion and let users sort it out on their end\n\nThis PR reverts the changes made to accommodate this edge case and\nupdates related tests to account for the new logic\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"a2d2054148b8cd7a062cfabd477338a3fd55428b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Davis Plumlee <56367316+dplumlee@users.noreply.github.com> |
||
|
elastic-renovate-prod[bot]
|
bbc6e21dc3
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 3f6bcf4 (8.18) (#214509)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `69a0542` -> `3f6bcf4` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xOCIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Lisa Cawley
|
4e1e9e8ba3
|
[8.18] [DOCS] Add minimal upgrade assistant APIs (#213863) (#213962)
# Backport This will backport the following commits from `main` to `8.18`: - [[DOCS] Add minimal upgrade assistant APIs (#213863)](https://github.com/elastic/kibana/pull/213863) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T14:49:17Z","message":"[DOCS] Add minimal upgrade assistant APIs (#213863)","sha":"73c8a5184f0c0b2f3de786d2ad7de0ec955bd349","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Upgrade Assistant","v9.0.0","docs","backport:version","v9.1.0","v8.19.0","v8.18.1"],"title":"[DOCS] Add minimal upgrade assistant APIs","number":213863,"url":"https://github.com/elastic/kibana/pull/213863","mergeCommit":{"message":"[DOCS] Add minimal upgrade assistant APIs (#213863)","sha":"73c8a5184f0c0b2f3de786d2ad7de0ec955bd349"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/213944","number":213944,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213863","number":213863,"mergeCommit":{"message":"[DOCS] Add minimal upgrade assistant APIs (#213863)","sha":"73c8a5184f0c0b2f3de786d2ad7de0ec955bd349"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
132177a3a3
|
[8.18] [Obs AI Assistant] Forward telemetryMetadata.pluginId to the EIS use case header (#214285) (#214479)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)](https://github.com/elastic/kibana/pull/214285) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T19:29:37Z","message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header","number":214285,"url":"https://github.com/elastic/kibana/pull/214285","mergeCommit":{"message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214285","number":214285,"mergeCommit":{"message":"[Obs AI Assistant] Forward `telemetryMetadata.pluginId` to the EIS use case header (#214285)\n\n## Summary\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/217\n\nThis PR forwards the Obs AI Assistant use case header for EIS through\nthe existing `telemetryData` property.\n\nRelates to https://github.com/elastic/search-team/issues/9424\nThe header is implemented in this PR -\nhttps://github.com/elastic/kibana/pull/214269\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"d66e0b25258b0568857bf6a0882e4d40e1f7e771"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
f2c8c4c0ce
|
[8.18] [Threat Hunting Investigations] Fix timeline column width bug (#214178) (#214471)
# Backport This will backport the following commits from `main` to `8.18`: - [[Threat Hunting Investigations] Fix timeline column width bug (#214178)](https://github.com/elastic/kibana/pull/214178) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:49:16Z","message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.1.0"],"title":"[Threat Hunting Investigations] Fix timeline column width bug","number":214178,"url":"https://github.com/elastic/kibana/pull/214178","mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214178","number":214178,"mergeCommit":{"message":"[Threat Hunting Investigations] Fix timeline column width bug (#214178)\n\n## Summary\n\nFixes: https://github.com/elastic/kibana/issues/213754\n\nThe issue above describes a bug in timeline that makes it impossible to\nchange the width of a timeline column. This PR fixes that issue and\nmakes sure that timeline column width settings are saved to\nlocalStorage. This mimics the behaviour of the alerts table elsewhere in\nsecurity solution.\n\n\nhttps://github.com/user-attachments/assets/8b9803a0-406d-4f2d-ada5-4c0b76cd6ab8\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"edbc618321930e358b2e0910f1c5cb5f7606e621"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co> |
||
|
Kibana Machine
|
319e8f2ba3
|
[8.18] [Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455) (#214467)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)](https://github.com/elastic/kibana/pull/213455) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T18:43:18Z","message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fix session view navigation when in alert preview and add preview banner","number":213455,"url":"https://github.com/elastic/kibana/pull/213455","mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213455","number":213455,"mergeCommit":{"message":"[Security Solution] Fix session view navigation when in alert preview and add preview banner (#213455)\n\n## Summary\n\nBefore: when in an alert preview, clicking session preview header opens\nsession view in details panel, but the preview persists.\n\nThis PR addressed the bug by including `isPreviewMode` as an indicator\nthat the panel is opened in preview. Clicking a link in preview should\nopens a new flyout and preview should not appear.\n\n\nhttps://github.com/user-attachments/assets/484daa16-adb0-48f2-b14e-a971878817c0\n\nAdded banner to session viewer in flyout\n\n<img width=\"1468\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/e228b35f-938a-4ad1-a97f-818caf36a284\"\n/>\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"a6ceafc8916a8f6c121fcad88f9057f92523feb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com> |
||
|
Kibana Machine
|
96070ebdd7
|
[8.18] [Security Solution] UI copy for Upgrade rules confirmation modal (#213981) (#214462)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)](https://github.com/elastic/kibana/pull/213981) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T18:36:35Z","message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","impact:medium","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","ui-copy","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] UI copy for Upgrade rules confirmation modal ","number":213981,"url":"https://github.com/elastic/kibana/pull/213981","mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213981","number":213981,"mergeCommit":{"message":"[Security Solution] UI copy for Upgrade rules confirmation modal (#213981)\n\n## Summary\n\nUpdates texts according to the suggested UI copy ([source doc](https://docs.google.com/document/d/1qjSxs1aDHJ8AKj5xR4erPdNumLy9Jqu3AlL9oGXnfxo/edit?tab=t.0)).\n\n## Screenshots\n\nUpdate All rules:\n<img width=\"1722\" alt=\"image\" src=\"https://github.com/user-attachments/assets/424d4812-6a29-4205-ab5d-df2b2024507a\" />\n\nSingle rule with solvable conflicts:\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/916a264f-44ba-45de-99cb-15e337ead2bd\" />\n\nMultiple rules with solvable conflicts:\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b7684f6-978b-4511-9b8a-ccde049730b9\" />\n\nMix of conflict-free rules and rules with solvable conflicts:\n<img width=\"1716\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd2325a6-0dec-48b1-a2af-6185acf16b10\" />\n<img width=\"1714\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ecb74497-ddbb-4407-8dfd-6902642dd9c3\" />\n\nMix of conflict-free rules and rules with non-solvable conflicts:\n<img width=\"1723\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0b980dd4-4109-4b63-859f-c95cc31dd7b4\" />\n\nOnly rules with conflicts:\n<img width=\"1720\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f66cee4e-e648-4eb5-902a-db0a4bd3a423\" />\n<img width=\"1718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9d42e5d9-6a62-4c60-8aea-bb5376b2d2c5\" />\n\nMix of rules selected to update:\n<img width=\"1717\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e882cbd1-203d-499f-b51f-37691405a3a5\" />","sha":"aa3d5eb3737f4885783fa1a9e51f89e422f4f4b2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
Mark J. Hoy
|
132d757650
|
[8.18] [8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (#214404) (#214460)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (#214404)](https://github.com/elastic/kibana/pull/214404) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark J. Hoy","email":"mark.hoy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T17:34:45Z","message":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (#214404)\n\n## Summary\n\nUpdates the text for the flyout for the Enterprise Search node\ndeprecation. The text includes verbiage asking the user to remove the\nconfiguration variables for Enterprise Search - in Cloud environments,\nthis is taken care of already for the user when the node is removed from\nthe deployment. This PR just hides that text (it will still show in\nnon-Cloud environments)\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.","sha":"e7e92547656be37e1b4725e39f0d174717f57e95","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Upgrade Assistant","Team:EnterpriseSearch","v8.19.0","backport:8.18","v8.18.1"],"title":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments","number":214404,"url":"https://github.com/elastic/kibana/pull/214404","mergeCommit":{"message":"[8.x] [Enterprise Search] Update Text in UA Deprecation Flyout for Cloud Environments (#214404)\n\n## Summary\n\nUpdates the text for the flyout for the Enterprise Search node\ndeprecation. The text includes verbiage asking the user to remove the\nconfiguration variables for Enterprise Search - in Cloud environments,\nthis is taken care of already for the user when the node is removed from\nthe deployment. This PR just hides that text (it will still show in\nnon-Cloud environments)\n\n\n\n\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.","sha":"e7e92547656be37e1b4725e39f0d174717f57e95"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
a98a4c31f7
|
[8.18] [Stack Monitoring] New FTR for "view logs" link (#208351) (#214296)
# Backport This will backport the following commits from `main` to `8.18`: - [[Stack Monitoring] New FTR for "view logs" link (#208351)](https://github.com/elastic/kibana/pull/208351) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T22:35:28Z","message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","FTR","v8.18.0","v8.17.2","v9.1.0"],"title":"[Stack Monitoring] New FTR for \"view logs\" link","number":208351,"url":"https://github.com/elastic/kibana/pull/208351","mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208351","number":208351,"mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co> |
||
|
Kibana Machine
|
5c3edf5171
|
[8.18] [Fleet] fix UI bug displaying default agent binary source (#214360) (#214451)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] fix UI bug displaying default agent binary source (#214360)](https://github.com/elastic/kibana/pull/214360) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T17:01:08Z","message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] fix UI bug displaying default agent binary source","number":214360,"url":"https://github.com/elastic/kibana/pull/214360","mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214360","number":214360,"mergeCommit":{"message":"[Fleet] fix UI bug displaying default agent binary source (#214360)\n\n## Summary\n\nFix UI bug when an agent policy uses the default download source\nexplicitly. The Agent binary download UI select was empty.\n\nTo verify:\n- create a new agent binary download source\n- create an agent policy with using the default download source\n- check on Agent policy details UI that the Agent binary download UI\nselect is populated correctly\n\n```\nPOST kbn:/api/fleet/agent_policies\n{\n \"name\": \"demo-policy-5\",\n \"description\": \"\",\n \"namespace\": \"default\",\n \"monitoring_enabled\": [\n \"logs\",\n \"metrics\",\n \"traces\"\n ],\n \"inactivity_timeout\": 1209600,\n \"is_protected\": false,\n \"download_source_id\": \"fleet-default-download-source\"\n}\n```\n\nBefore:\n\n\n\n\nAfter:\n\n<img width=\"1517\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/f5d19520-317e-4df8-aaed-0e367a2e6d9b\"\n/>","sha":"eb62a047bd06ebb70c6119bf3c19145df901fdda"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
deec2c7737
|
[8.18] [APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356) (#214419)
# Backport This will backport the following commits from `main` to `8.18`: - [[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)](https://github.com/elastic/kibana/pull/214356) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:20:17Z","message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard","number":214356,"url":"https://github.com/elastic/kibana/pull/214356","mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214356","number":214356,"mergeCommit":{"message":"[APM][OTel] Fix: Pass telemetry.sdk* data when loading a dashboard (#214356)\n\nCloses #214328 \n\n## Summary\n\nThis PR fixes the issue with loading an otel native dashboard\n\n## Testing\n- Run ` node scripts/synthtrace otel_edot_simple_trace.ts`\n- ⚠️ As our test data has only a java service there is a small manual\nstep needed (it will be listed below **^**)\n- Open the metrics tab for the service (currently we don't have a\ndashboard):\n\n\n\n\n\n- **^** Go to the `dashboard_catalog.ts` and add mapping for otel native\njava case:\n - first: `'otel_native-edot-java',`\n\n\n\n - second: \n ```js \n case 'otel_native-edot-java': {\n return import(\n /* webpackChunkName: \"lazyJavaOtelNativeDashboard\" */\n './opentelemetry_java.json'\n );\n }\n ``\n\n-\n\n\n- Check the same page after refresh\n\n","sha":"ebe7ef6da0f25b09e1d576e7d8975d7b0b2a95b1"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Steph Milovic
|
1b64d12817
|
[8.18] [Stack connector] Forward telemetryMetadata.pluginId to EIS use case header (#214269) (#214429)
# Backport This will backport the following commits from `main` to `8.18`: - [[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)](https://github.com/elastic/kibana/pull/214269) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T15:44:06Z","message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.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.18.0","v9.1.0","v8.19.0"],"title":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header","number":214269,"url":"https://github.com/elastic/kibana/pull/214269","mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214269","number":214269,"mergeCommit":{"message":"[Stack connector] Forward `telemetryMetadata.pluginId` to EIS use case header (#214269)","sha":"13906cbb76a17e7226084d208b52164e00f09c0e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
ae70f3ee8b
|
[8.18] [Security Solution] Hide conflict badges when rule customization is not enabled (#214365) (#214407)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)](https://github.com/elastic/kibana/pull/214365) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:52:48Z","message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Hide conflict badges when rule customization is not enabled","number":214365,"url":"https://github.com/elastic/kibana/pull/214365","mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214365","number":214365,"mergeCommit":{"message":"[Security Solution] Hide conflict badges when rule customization is not enabled (#214365)\n\n**Resolves: https://github.com/elastic/kibana/issues/214301**\n\n## Summary\n\nThis PR removes conflict badges from the Rule Updates table for users\nwith license that is insufficient for prebuilt rule customization.\n\n**Before (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 44 07\"\nsrc=\"https://github.com/user-attachments/assets/fd830253-80d0-4250-861c-88b0a11d6786\"\n/>\n\n\n**After (on Basic license)**\n<img width=\"1014\" alt=\"Schermafbeelding 2025-03-13 om 13 39 01\"\nsrc=\"https://github.com/user-attachments/assets/f8b00964-72bf-4d0a-9f03-9e47231c5227\"\n/>\n\nSince users on Basic license can't customize rules, it doesn't make\nsense to show these badges - they are not actionable anyways.\n\nUsers will still see a callout mentioning that their modifications will\nbe erased if they open a flyout for a customized rule.\n\n<img width=\"953\" alt=\"Schermafbeelding 2025-03-13 om 13 41 21\"\nsrc=\"https://github.com/user-attachments/assets/b2a2514e-2b19-4653-9076-d742130b30b6\"\n/>","sha":"9f2e07f2dedce88e51b80afd0cb215b6467c8f37"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nikita Indik <nikita.indik@elastic.co> |
||
|
Kibana Machine
|
e1b9411764
|
[8.18] [Fleet] Never delete @custom component templates (#214232) (#214289)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Never delete @custom component templates (#214232)](https://github.com/elastic/kibana/pull/214232) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T19:58:40Z","message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:version","v9.1.0","backport:8.18","v8.18.1"],"title":"[Fleet] Never delete @custom component templates","number":214232,"url":"https://github.com/elastic/kibana/pull/214232","mergeCommit":{"message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214279","number":214279,"state":"MERGED","mergeCommit":{"sha":"ffc575724f73009d5d564b7c896ab162e7880c4e","message":"[9.0] [Fleet] Never delete @custom component templates (#214232) (#214279)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Never delete @custom component templates\n(#214232)](https://github.com/elastic/kibana/pull/214232)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214232","number":214232,"mergeCommit":{"message":"[Fleet] Never delete @custom component templates (#214232)","sha":"fc64501577284038eef59bb8fc37ea4d80b49827"}},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Steph Milovic
|
66223fbf1f
|
[8.18] [Security solution] Bedrock region fix (#214251) (#214394)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security solution] Bedrock region fix (#214251)](https://github.com/elastic/kibana/pull/214251) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T14:01:03Z","message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.4"],"title":"[Security solution] Bedrock region fix","number":214251,"url":"https://github.com/elastic/kibana/pull/214251","mergeCommit":{"message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214251","number":214251,"mergeCommit":{"message":"[Security solution] Bedrock region fix (#214251)","sha":"cf73559e2dd5ce6e793b6b92183c43e6e09fc629"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214388","number":214388,"state":"OPEN"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Lisa Cawley
|
581db9a935
|
[8.18] Add minimal user session management API docs (#212576) (#214033)
# Backport This will backport the following commits from `main` to `8.18`: - [Add minimal user session management API docs (#212576)](https://github.com/elastic/kibana/pull/212576) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T22:47:07Z","message":"Add minimal user session management API docs (#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","backport:version","v8.18.0","v9.1.0","v8.19.0","v9.0.1"],"title":"Add minimal user session management API docs","number":212576,"url":"https://github.com/elastic/kibana/pull/212576","mergeCommit":{"message":"Add minimal user session management API docs (#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212576","number":212576,"mergeCommit":{"message":"Add minimal user session management API docs (#212576)","sha":"b27f9aa5f0a42410c7e41c022624a422f502aa43"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214030","number":214030,"state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
9df7a128a4
|
[8.18] [Security Solution] Avoid showing rules update confirmation modal on basic license (#214340) (#214383)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)](https://github.com/elastic/kibana/pull/214340) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-03-13T13:47:30Z","message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Avoid showing rules update confirmation modal on basic license","number":214340,"url":"https://github.com/elastic/kibana/pull/214340","mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214340","number":214340,"mergeCommit":{"message":"[Security Solution] Avoid showing rules update confirmation modal on basic license (#214340)\n\n**Resolves:** https://github.com/elastic/kibana/issues/214302\n\n## Summary\n\nThis PR prevents showing rule upgrade confirmation modal on lower licenses where prebuilt rules customization is not allowed.\n\n## Details\n\nUsers may see a rules upgrade confirmation modal when trying to upgrade prebuilt rules even if prebuilt rules customization is disabled due to insufficient license. It happens due to improper response from `upgrade/_perform` which doesn't respect `pick_version`. It's expected rule upgrade goes smoothly when `pick_version` is one of `BASE`, `CURRENT` or `TARGET`.\n\nThe fix makes sure dry run request isn't fired and a prebuilt rules upgrade confirmation modal isn't shown when running with insufficient for prebuilt rules customization license.\n\nThere is a [ticket](https://github.com/elastic/kibana/issues/214338) to address this issue in the API endpoint.","sha":"d782b7163785acd3e1bd26a70c9a93454611b9c4"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
Sergi Massaneda
|
c0908e8f07
|
[Security Solution] Update siemMigrations doc link (#214323)
complements https://github.com/elastic/kibana/pull/213967 |
||
Alejandro Fernández Haro
|
0d89c10450
|
[8.18] [Feature Flags] ECS-compliant logger (#214231) (#214344)
# Backport This will backport the following commits from `main` to `8.18`: - [[Feature Flags] ECS-compliant logger (#214231)](https://github.com/elastic/kibana/pull/214231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T23:24:40Z","message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Feature Flags] ECS-compliant logger","number":214231,"url":"https://github.com/elastic/kibana/pull/214231","mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214304","number":214304,"state":"MERGED","mergeCommit":{"sha":"fa04dc0e0536ced502e3eb8993aa7ba227f7299d","message":"[9.0] [Feature Flags] ECS-compliant logger (#214231) (#214304)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Feature Flags] ECS-compliant logger\n(#214231)](https://github.com/elastic/kibana/pull/214231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214231","number":214231,"mergeCommit":{"message":"[Feature Flags] ECS-compliant logger (#214231)\n\n## Summary\n\nThe OpenFeature clients receive a logger, but it logs errors like\n`log('something went wrong', error)`. Our core logger then removes the\n`error.message` as it prefers the message provided as the first\nargument.\n\nThis PR wraps the logger to make sure that we handle this type of usage.\n\ncc @pmuellr as he found out about this bug\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"98986a86a1086d0047d60a14425920b3c5fbc343"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
3060550b53
|
[8.18] [Siem Migrations] Add Translated Rules Empty Page (#213438) (#214168)
# Backport This will backport the following commits from `main` to `8.18`: - [[Siem Migrations] Add Translated Rules Empty Page (#213438)](https://github.com/elastic/kibana/pull/213438) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T13:59:12Z","message":"[Siem Migrations] Add Translated Rules Empty Page (#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ExpressionLanguage","release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Siem Migrations] Add Translated Rules Empty Page","number":213438,"url":"https://github.com/elastic/kibana/pull/213438","mergeCommit":{"message":"[Siem Migrations] Add Translated Rules Empty Page (#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","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"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213438","number":213438,"mergeCommit":{"message":"[Siem Migrations] Add Translated Rules Empty Page (#213438)\n\n## Summary\n\nThis PR adds empty state for Translated Rules Page.\n\n\n\nhttps://github.com/user-attachments/assets/b8222151-526c-435e-b9bb-403e1097c056\n\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"bbc91a26917e0ad5257bfd879a0f1931d3442f25"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
elastic-vault-github-plugin-prod[bot]
|
1ff8a22420
|
[8.18] Sync bundled packages with Package Storage (#214247)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2436 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |