mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 16:29:04 -04:00
76141 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
bcee10739e
|
[8.15] [OTel Onboarding] Adjust linux snippet and warning (#187691) (#187756)
# Backport This will backport the following commits from `main` to `8.15`: - [[OTel Onboarding] Adjust linux snippet and warning (#187691)](https://github.com/elastic/kibana/pull/187691) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T14:31:42Z","message":"[OTel Onboarding] Adjust linux snippet and warning (#187691)\n\nAddress\r\nhttps://github.com/elastic/observability-dev/issues/3217#issuecomment-2210741356\r\n\r\n<img width=\"1150\" alt=\"Screenshot 2024-07-05 at 17 30 47\"\r\nsrc=\" |
||
|
Kibana Machine
|
d765ed3550
|
[8.15] [ML] Removes info callout mentioning ML nodes for serverless environment (#187583) (#187620)
# Backport This will backport the following commits from `main` to `8.15`: - [[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)](https://github.com/elastic/kibana/pull/187583) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T07:19:51Z","message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] Removes info callout mentioning ML nodes for serverless environment ","number":187583,"url":"https://github.com/elastic/kibana/pull/187583","mergeCommit":{"message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187583","number":187583,"mergeCommit":{"message":"[ML] Removes info callout mentioning ML nodes for serverless environment (#187583)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187575\r\n\r\nRemove an info callout mentioning the number of ML nodes for serverless\r\nenvironment","sha":"3a9b01cf2201d749fb7bab034d6745db93bfdc82"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
28ee74422a
|
[8.15] [Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466) (#187789)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)](https://github.com/elastic/kibana/pull/187466) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:14:57Z","message":"[Security GenAI] Use AI setting to set langsmith tracing to the Integration Assistant (#187466)\n\n## Summary\r\n\r\nEnables tracing Langchain invocations in the integrations assistant\r\nusing the Langsmith settings stored by the Security AI Settings.\r\nThe evaluation settings tab is still under an experimental flag, to see\r\nit:\r\n\r\n```\r\nxpack.securitySolution.enableExperimental: ['assistantModelEvaluation']\r\n```\r\n\r\n### Screenshots\r\n\r\n<img width=\"1317\" alt=\"Settings\"\r\nsrc=\" |
||
|
Kibana Machine
|
a6087390bc
|
[8.15] [AI Assistant] Add to dashboard (#179329) (#187827)
# Backport This will backport the following commits from `main` to `8.15`: - [[AI Assistant] Add to dashboard (#179329)](https://github.com/elastic/kibana/pull/179329) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T07:31:54Z","message":"[AI Assistant] Add to dashboard (#179329)\n\nAdds a new functionality in the AI assistant when in dashboards. If the\r\nusers ask for a question which will generate a query then then can use\r\nprompts like:\r\n\r\n- `Create a visualization from this query and add this to a dashboard`\r\n- `Create a metric from this query and add this to a dashboard`\r\n- ....\r\n\r\n\r\n (#187808)
# Backport This will backport the following commits from `main` to `8.15`: - [[ResponseOps][Cases] Edits case template text (#187610)](https://github.com/elastic/kibana/pull/187610) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T23:42:06Z","message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","ui-copy","v8.15.0","v8.16.0"],"title":"[ResponseOps][Cases] Edits case template text","number":187610,"url":"https://github.com/elastic/kibana/pull/187610","mergeCommit":{"message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187610","number":187610,"mergeCommit":{"message":"[ResponseOps][Cases] Edits case template text (#187610)","sha":"6a2abd68091b86b4e5b02359e346300371346f2a"}}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
ab6ec61c68 | skip failing test suite (#187818) | ||
|
Kibana Machine
|
db7098b1d7
|
[8.15] [Observability Onboarding] Fix onboarding nav (#187498) (#187776)
# Backport This will backport the following commits from `main` to `8.15`: - [[Observability Onboarding] Fix onboarding nav (#187498)](https://github.com/elastic/kibana/pull/187498) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T16:47:19Z","message":"[Observability Onboarding] Fix onboarding nav (#187498)\n\n## Summary\r\n\r\nAddresses some issues with navigation in the Observability solution\r\nrelated to onboarding.\r\n\r\n### Overview page add data link\r\n\r\n\r\n (#187760)
# Backport This will backport the following commits from `main` to `8.15`: - [Make it clear log stream panels shouldn't be used (#187548)](https://github.com/elastic/kibana/pull/187548) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T15:11:27Z","message":"Make it clear log stream panels shouldn't be used (#187548)\n\nAs discussed, I looked into making it clearer how to handle the log\r\nstream embeddable panel on dashboards.\r\n\r\nIt's not possible to show an info icon or a badge without bigger\r\nchanges, but there is already a tooltip which can be used for the same\r\npurpose:\r\n\r\n<img width=\"321\" alt=\"Screenshot 2024-07-04 at 11 30 27\"\r\nsrc=\" |
||
|
Kibana Machine
|
9c5f961c6b
|
[8.15] [Discover] View mode changes should trigger Unsaved changes badge in ES|QL (#187244) (#187687)
# Backport This will backport the following commits from `main` to `8.15`: - [[Discover] View mode changes should trigger Unsaved changes badge in ES|QL (#187244)](https://github.com/elastic/kibana/pull/187244) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T14:46:00Z","message":"[Discover] View mode changes should trigger Unsaved changes badge in ES|QL (#187244)\n\n- Closes https://github.com/elastic/kibana/issues/184624\r\n\r\n## Summary\r\n\r\nThis PR updates the logic to show Unsaved changes badge when view mode\r\nchanges in ES|QL mode.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"25d73466c3e1afff0c17b7f8800f92449e9480a8","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","v8.16.0"],"title":"[Discover] View mode changes should trigger Unsaved changes badge in ES|QL","number":187244,"url":"https://github.com/elastic/kibana/pull/187244","mergeCommit":{"message":"[Discover] View mode changes should trigger Unsaved changes badge in ES|QL (#187244)\n\n- Closes https://github.com/elastic/kibana/issues/184624\r\n\r\n## Summary\r\n\r\nThis PR updates the logic to show Unsaved changes badge when view mode\r\nchanges in ES|QL mode.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"25d73466c3e1afff0c17b7f8800f92449e9480a8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187244","number":187244,"mergeCommit":{"message":"[Discover] View mode changes should trigger Unsaved changes badge in ES|QL (#187244)\n\n- Closes https://github.com/elastic/kibana/issues/184624\r\n\r\n## Summary\r\n\r\nThis PR updates the logic to show Unsaved changes badge when view mode\r\nchanges in ES|QL mode.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"25d73466c3e1afff0c17b7f8800f92449e9480a8"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Tiago Costa
|
9d6491dbed
|
skip flaky suite (#187667) | ||
|
Kibana Machine
|
b3138be858
|
[8.15] [OAS][Cases] Add case templates to case configuration APIs (#187613) (#187788)
<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:10:38Z","message":"[OAS][Cases]
Add case templates to case configuration APIs
(#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","v8.15.0","v8.16.0"],"title":"[OAS][Cases]
Add case templates to case configuration
APIs","number":187613,"url":"https://github.com/elastic/kibana/pull/187613","mergeCommit":{"message":"[OAS][Cases]
Add case templates to case configuration APIs
(#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187613","number":187613,"mergeCommit":{"message":"[OAS][Cases]
Add case templates to case configuration APIs
(#187613)","sha":"35ee0ccbb0f45310525865d24ad0d5cba68d10f6"}}]}]
BACKPORT-->
|
||
|
Kibana Machine
|
17bf446e73
|
[8.15] [Security solution] Add model parameter to token telemetry (#187783) (#187793)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security solution] Add model parameter to token telemetry (#187783)](https://github.com/elastic/kibana/pull/187783) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T18:53:25Z","message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security solution] Add model parameter to token telemetry","number":187783,"url":"https://github.com/elastic/kibana/pull/187783","mergeCommit":{"message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187783","number":187783,"mergeCommit":{"message":"[Security solution] Add model parameter to token telemetry (#187783)","sha":"2b5ff7709515836b6ce91d6ce28ed3316f78d930"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
d018faaed5
|
[8.15] [Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942) (#187799)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942)](https://github.com/elastic/kibana/pull/186942) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Candace Park","email":"56409205+parkiino@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-08T19:50:54Z","message":"[Security Solution][AVC banner] Add AVC results banner to elastic defend home page and integrations (#186942)\n\n## Summary\r\n\r\n- [x] Shows a banner with the 2024 AVC results blog link in 2 places:\r\nthe Security homepage and the Elastic Defend integration page info\r\n- [x] Banner will not show again once dismissed\r\n- [x] Unit Tests \r\n\r\nTODO in another pr: have code to remove the avc banner code at the end\r\nof the year\r\n\r\n## Screenshots\r\n<img width=\"1724\" alt=\"image\"\r\nsrc=\" |
||
|
Kibana Machine
|
d11287dc97
|
[8.15] [Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559) (#187779)
# Backport This will backport the following commits from `main` to `8.15`: - [[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)](https://github.com/elastic/kibana/pull/187559) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe McElroy","email":"joseph.mcelroy@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T17:18:12Z","message":"[Search] [Playground] Gemini search playground + Robustness for Question Rewriting (#187559)\n\n## Summary\r\n\r\nWork largely based off the work @stephmilovic really nicely put together\r\nin this [draft PR](https://github.com/elastic/kibana/pull/186934)\r\n- Introduce Google Gemini Model support\r\n- Updated bedrock to use the ActionsSimpleChatModel \r\n- Updated the tests\r\n- Made the rewrite question chain more robust\r\n - the prompt is now uses the model specific tags\r\n- the system instruction has been updated to be less wordy, better for\r\nBM25 retrieval\r\n \r\n\r\n |
||
|
Kibana Machine
|
12cbac97e5
|
[8.15] [Fleet] Fix privileges to delete request diagnostics (#187678) (#187757)
# Backport This will backport the following commits from `main` to `8.15`: - [[Fleet] Fix privileges to delete request diagnostics (#187678)](https://github.com/elastic/kibana/pull/187678) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T14:33:18Z","message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","backport:prev-minor","v8.16.0"],"title":"[Fleet] Fix privileges to delete request diagnostics","number":187678,"url":"https://github.com/elastic/kibana/pull/187678","mergeCommit":{"message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187678","number":187678,"mergeCommit":{"message":"[Fleet] Fix privileges to delete request diagnostics (#187678)","sha":"6590457792143880d12f2f62fd0f5aaf2d4927a8"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
046bccc2e8
|
[8.15] [Logs UI] Fix fly-out link to the legacy Uptime app (#186328) (#187761)
# Backport This will backport the following commits from `main` to `8.15`: - [[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)](https://github.com/elastic/kibana/pull/186328) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-04T16:28:25Z","message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Logs UI","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Team:obs-ux-management","apm:review","v8.15.0","v8.16.0"],"title":"[Logs UI] Fix fly-out link to the legacy Uptime app","number":186328,"url":"https://github.com/elastic/kibana/pull/186328","mergeCommit":{"message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186328","number":186328,"mergeCommit":{"message":"[Logs UI] Fix fly-out link to the legacy Uptime app (#186328)","sha":"c3c4dca2896362b0c35419afaf4a56f92b48013b"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com> |
||
Yulia Čech
|
b10c5bca89
|
[Console] Disable the monaco migration for 8.15 release (#187237)
## Summary This PR disables the Monaco Console in 8.15 as we don't want to add it to public release yet (it's planned to be released in 8.16). **How to test:** 1. Check out the PR and start Es and Kibana 2. Verify that Console still uses the old Ace editor. Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
c47cca3e30
|
[8.15] Fix "Elastic did not load properly" message color when system in dark mode (#187653) (#187670)
# Backport This will backport the following commits from `main` to `8.15`: - [Fix "Elastic did not load properly" message color when system in dark mode (#187653)](https://github.com/elastic/kibana/pull/187653) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"anton.dosov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T12:30:42Z","message":"Fix \"Elastic did not load properly\" message color when system in dark mode (#187653)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/187570\r\n\r\nThe problem was that when the system/browser was in dark mode, the\r\ndefault text color became white, but the background was forced to a\r\nspecific bright color, so the text became unreadable. A quick fix is to\r\nalso force the text color (I used EUI text colors)\r\n\r\n\r\n<img width=\"858\" alt=\"Screenshot 2024-07-05 at 12 44 11\"\r\nsrc=\" |
||
|
Kibana Machine
|
49cba8250d
|
[8.15] [ES|QL] Fixes FROM suggestions (#187657) (#187737)
# Backport This will backport the following commits from `main` to `8.15`: - [[ES|QL] Fixes FROM suggestions (#187657)](https://github.com/elastic/kibana/pull/187657) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T11:56:48Z","message":"[ES|QL] Fixes FROM suggestions (#187657)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/187414\r\n\r\n<img width=\"788\" alt=\"image\"\r\nsrc=\" |
||
Jon
|
9ae869c547
|
[8.15] Disable serverless tests (#187708) | ||
|
Kibana Machine
|
828c2cde74
|
[8.15] [Discover] [ES|QL] Disables sorting for Document view (#187553) (#187731)
# Backport This will backport the following commits from `main` to `8.15`: - [[Discover] [ES|QL] Disables sorting for Document view (#187553)](https://github.com/elastic/kibana/pull/187553) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2024-07-08T09:14:59Z","message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-minor","Feature:ES|QL","v8.15.0","v8.16.0"],"title":"[Discover] [ES|QL] Disables sorting for Document view","number":187553,"url":"https://github.com/elastic/kibana/pull/187553","mergeCommit":{"message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187553","number":187553,"mergeCommit":{"message":"[Discover] [ES|QL] Disables sorting for Document view (#187553)\n\n## Summary\r\n\r\nDisables the `@timestamp` sorting for ES|QL Document view. \r\n\r\nThe sorting doesnt work currently. I could enable it but this causes 2\r\nproblems:\r\n\r\n- The fix is here\r\nhttps://github.com/elastic/kibana/blob/main/packages/kbn-unified-data-table/src/components/data_table.tsx#L962\r\nThe timestamp column is a special column for Discover so the\r\ncolumns.length is 0 here even if the timestamp column is being rendered.\r\nAs a result the inMemory is false and the client side sorting doesnt\r\nwork. Removing the columns.length fixes it but it makes Discover\r\nsignificantly slower.\r\n- As the data are not by default sorted by timestamp even if we enable\r\nit client side, it won't be of great help. I think that for the\r\ntimestamp column it would be better to enable server side sorting but\r\nthis needs discussion\r\n\r\nI think that hiding this for now it will fix the confusion and is a good\r\ntemporary decision before we decide what to do with sorting in general.","sha":"ab3c76dde0a6a862073e0734c95bed037262b346"}}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
63232f2a60
|
[8.15] [ES|QL] Update function metadata (#187723) (#187729)
# Backport This will backport the following commits from `main` to `8.15`: - [[ES|QL] Update function metadata (#187723)](https://github.com/elastic/kibana/pull/187723) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kibana Machine","email":"42973632+kibanamachine@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-08T07:58:05Z","message":"[ES|QL] Update function metadata (#187723)\n\nThis PR updates the function definitions and inline docs based on the\r\nlatest metadata from Elasticsearch.","sha":"e320935594afa43a89447c8328e0cba5a1821bb3","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:ESQL","v8.15.0","v8.16.0"],"title":"[ES|QL] Update function metadata","number":187723,"url":"https://github.com/elastic/kibana/pull/187723","mergeCommit":{"message":"[ES|QL] Update function metadata (#187723)\n\nThis PR updates the function definitions and inline docs based on the\r\nlatest metadata from Elasticsearch.","sha":"e320935594afa43a89447c8328e0cba5a1821bb3"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187723","number":187723,"mergeCommit":{"message":"[ES|QL] Update function metadata (#187723)\n\nThis PR updates the function definitions and inline docs based on the\r\nlatest metadata from Elasticsearch.","sha":"e320935594afa43a89447c8328e0cba5a1821bb3"}}]}] BACKPORT--> |
||
Gergő Ábrahám
|
445a9129d5
|
[EDR Workflows][8.15] Enable process descendant event filtering feature flag for 8.15 (#187627)
<img width="664" alt="image"
src="
|
||
|
Kibana Machine
|
2004c4c933
|
[8.15] [Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549) (#187661)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)](https://github.com/elastic/kibana/pull/187549) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T11:29:22Z","message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Detection Engine","v8.15.0","v8.16.0"],"title":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384)","number":187549,"url":"https://github.com/elastic/kibana/pull/187549","mergeCommit":{"message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187549","number":187549,"mergeCommit":{"message":"[Security Solution][Detections][BUG] ES|QL rule execution error when source document has a non-ECS compliant sub-field with data under event field (#187384) (#187549)\n\n## Summary\r\n\r\nTicket https://github.com/elastic/kibana/issues/187384\r\n\r\nThese changes fix the error on saving the alert\r\n> An error occurred during rule execution: message: \"[1:6778] failed to\r\nparse field [kibana.alert.original_event.action] of type [keyword] in\r\ndocument with id '027b925ae2799635a0dee97a6aa9d58dc87d9771'.\"\r\n\r\nwhich happens due to not stripping non-ECS compliant sub-fields of the\r\n`event.action` field.\r\n\r\nSee the main ticket for steps to reproduce the issue.","sha":"0a4ed6169904555b243c345267d1f476b5a02348"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
|
Kibana Machine
|
7e0626c9de
|
[8.15] [Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643) (#187726)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)](https://github.com/elastic/kibana/pull/187643) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-08T07:08:14Z","message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team: SecuritySolution","v8.15.0","v8.16.0"],"title":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs","number":187643,"url":"https://github.com/elastic/kibana/pull/187643","mergeCommit":{"message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187643","number":187643,"mergeCommit":{"message":"[Security Gen AI] [ Integration Assistant ] Modify pipeline template to handle dates as array of string in the logs (#187643)\n\n## Summary\r\n\r\nThere could be\r\n[scenario](https://docs.paloaltonetworks.com/iot/iot-security-api-reference/iot-security-api/get-vulnerability-instances)\r\nwhere a date can come in as an array -\r\n\r\n`\"detected_date\": [\r\n \"2021-04-19T23:59:59\"\r\n ],`\r\n\r\nThe `date` processor fails to handle an array with a string.\r\nThis PR adds a `script` processor as a pre processor to date processor\r\nto convert the array of string into a string.\r\n\r\nPipeline after the changes\r\n\r\n```json\r\n{\r\n \"script\": {\r\n \"tag\": \"script_convert_array_to_string\",\r\n \"description\": \"Ensures the date processor does not receive an array value.\",\r\n \"lang\": \"painless\",\r\n \"source\": \"if (ctx.palo_alto_iot.vulnerability.detected_date instanceof ArrayList){\\n ctx.palo_alto_iot.vulnerability.detected_date = ctx.palo_alto_iot.vulnerability.detected_date[0];\\n}\\n\"\r\n }\r\n },\r\n {\r\n \"date\": {\r\n \"if\": \"ctx.palo_alto_iot?.vulnerability?.detected_date != null\",\r\n \"tag\": \"date_processor_palo_alto_iot.vulnerability.detected_date\",\r\n \"field\": \"palo_alto_iot.vulnerability.detected_date\",\r\n \"target_field\": \"event.start\",\r\n \"formats\": [\r\n \"ISO8601\"\r\n ]\r\n }\r\n }\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"a347d7b5f1f7b43add64ec9e5751a41888f9afde"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Kerry Gallagher
|
2490c13086
|
Revert "[Logs] Add Log Sources advanced setting and client / server access services" (#187477)
## Summary This is just a direct revert of https://github.com/elastic/kibana/pull/186468, there are no additional changes. This is to avoid an advanced setting that doesn't do anything in 8.15 (~waiting for the 8.15 branch to be cut~). Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
7f969383ec
|
[8.15] [ML] Enable anomaly charts Accessibility tests (#187482) (#187675)
# Backport This will backport the following commits from `main` to `8.15`: - [[ML] Enable anomaly charts Accessibility tests (#187482)](https://github.com/elastic/kibana/pull/187482) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T13:13:35Z","message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","Team:ML","v8.15.0","v8.16.0"],"title":"[ML] Enable anomaly charts Accessibility tests ","number":187482,"url":"https://github.com/elastic/kibana/pull/187482","mergeCommit":{"message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187482","number":187482,"mergeCommit":{"message":"[ML] Enable anomaly charts Accessibility tests (#187482)\n\n## Summary\r\n\r\nCloses #183196 \r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"503cac3127b85f54f6242033cc9154ba872050a7"}}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
aa33d6d047
|
[8.15] [Dashboard] [Controls] Fix controls getting overwritten on navigation (#187509) (#187693)
# Backport This will backport the following commits from `main` to `8.15`: - [[Dashboard] [Controls] Fix controls getting overwritten on navigation (#187509)](https://github.com/elastic/kibana/pull/187509) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-05T15:35:24Z","message":"[Dashboard] [Controls] Fix controls getting overwritten on navigation (#187509)\n\n## Summary\r\n\r\n\r\n> [!WARNING]\r\n> Beware - the longest description ever for a one line change is\r\nincoming.\r\n>\r\n>\r\n (#187611)
# Backport This will backport the following commits from `main` to `8.15`: - [[Otel Onboarding] Adjust snippet and switch to proper release (#187480)](https://github.com/elastic/kibana/pull/187480) - https://github.com/elastic/kibana/pull/187674 <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Joe Reuter","email":"johannes.reuter@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T23:20:44Z","message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding","v8.16.0"],"title":"[Otel Onboarding] Adjust snippet and switch to proper release","number":187480,"url":"https://github.com/elastic/kibana/pull/187480","mergeCommit":{"message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187480","number":187480,"mergeCommit":{"message":"[Otel Onboarding] Adjust snippet and switch to proper release (#187480)\n\nThis PR does three things:\r\n* Try to download agent from the central repository (expected to fail\r\nfor now as 8.15.0 agent isn't released yet\r\n* Adjust snippet to also set up local data dir correctly\r\n* Update k8s manifest via\r\nhttps://github.com/elastic/opentelemetry-dev/pull/299","sha":"322248b496f2918e0df3d4de0e22bc4b30ea60a0"}}]}] BACKPORT--> --------- Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> Co-authored-by: Joe Reuter <email@johannes-reuter.de> |
||
|
Kibana Machine
|
0b3c4e184a | skip failing test suite (#184681) | ||
|
Kibana Machine
|
e306ae6d75
|
[8.15] [Obs AI assistant] Replace with double quotes (#187327) (#187655)
# Backport This will backport the following commits from `main` to `8.15`: - [[Obs AI assistant] Replace with double quotes (#187327)](https://github.com/elastic/kibana/pull/187327) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2024-07-05T10:54:45Z","message":"[Obs AI assistant] Replace with double quotes (#187327)\n\n## Summary\r\n\r\nFollow up of https://github.com/elastic/elasticsearch/pull/108395\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"7b635f3246d9f827380d4d89441cdfaf8aadd468","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:Obs AI Assistant","ci:project-deploy-observability","v8.15.0","v8.16.0"],"title":"[Obs AI assistant] Replace with double quotes","number":187327,"url":"https://github.com/elastic/kibana/pull/187327","mergeCommit":{"message":"[Obs AI assistant] Replace with double quotes (#187327)\n\n## Summary\r\n\r\nFollow up of https://github.com/elastic/elasticsearch/pull/108395\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"7b635f3246d9f827380d4d89441cdfaf8aadd468"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187327","number":187327,"mergeCommit":{"message":"[Obs AI assistant] Replace with double quotes (#187327)\n\n## Summary\r\n\r\nFollow up of https://github.com/elastic/elasticsearch/pull/108395\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>","sha":"7b635f3246d9f827380d4d89441cdfaf8aadd468"}}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
|
Kibana Machine
|
fbe21c390d
|
[8.15] [Security Solution] Readme files update (#187596) (#187604)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Readme files update (#187596)](https://github.com/elastic/kibana/pull/187596) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gloria Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T20:28:51Z","message":"[Security Solution] Readme files update (#187596)\n\n## Summary\r\n\r\nWe have been asked to stop using the `second quality gate` terminology\r\nin favor of `kibana QA quality gate`. This PR updates the readmes to\r\nreflect the new changes.","sha":"3065d56a96ece4f4b73f0fd22f0b6ec38642b910","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Defend Workflows","v8.15.0","v8.16.0"],"title":"[Security Solution] Readme files update","number":187596,"url":"https://github.com/elastic/kibana/pull/187596","mergeCommit":{"message":"[Security Solution] Readme files update (#187596)\n\n## Summary\r\n\r\nWe have been asked to stop using the `second quality gate` terminology\r\nin favor of `kibana QA quality gate`. This PR updates the readmes to\r\nreflect the new changes.","sha":"3065d56a96ece4f4b73f0fd22f0b6ec38642b910"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187596","number":187596,"mergeCommit":{"message":"[Security Solution] Readme files update (#187596)\n\n## Summary\r\n\r\nWe have been asked to stop using the `second quality gate` terminology\r\nin favor of `kibana QA quality gate`. This PR updates the readmes to\r\nreflect the new changes.","sha":"3065d56a96ece4f4b73f0fd22f0b6ec38642b910"}}]}] BACKPORT--> Co-authored-by: Gloria Hornero <gloria.hornero@elastic.co> |
||
|
Kibana Machine
|
2f4f5fff12
|
[8.15] [Fleet] Disable selecting standalone instructions for user without agent policies READ permissions (#187517) (#187605)
# Backport This will backport the following commits from `main` to `8.15`: - [[Fleet] Disable selecting standalone instructions for user without agent policies READ permissions (#187517)](https://github.com/elastic/kibana/pull/187517) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T13:45:20Z","message":"[Fleet] Disable selecting standalone instructions for user without agent policies READ permissions (#187517)","sha":"c27ca409a4fcfa4a16e44558ab1302fa26f7f3b8","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.15.0","v8.16.0"],"title":"[Fleet] Disable selecting standalone instructions for user without agent policies READ permissions","number":187517,"url":"https://github.com/elastic/kibana/pull/187517","mergeCommit":{"message":"[Fleet] Disable selecting standalone instructions for user without agent policies READ permissions (#187517)","sha":"c27ca409a4fcfa4a16e44558ab1302fa26f7f3b8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187517","number":187517,"mergeCommit":{"message":"[Fleet] Disable selecting standalone instructions for user without agent policies READ permissions (#187517)","sha":"c27ca409a4fcfa4a16e44558ab1302fa26f7f3b8"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Tiago Costa
|
c616ed3da0
|
[8.15] fix(NA): unhandled exception for junit report generation when no codeowners (#187597) (#187603)
# Backport This will backport the following commits from `main` to `8.15`: - [fix(NA): unhandled exception for junit report generation when no codeowners (#187597)](https://github.com/elastic/kibana/pull/187597) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T19:11:37Z","message":"fix(NA): unhandled exception for junit report generation when no codeowners (#187597)\n\nThis PR fixes what was brought on at\r\nhttps://github.com/elastic/kibana/pull/181711 .\r\n\r\nWhat was proposed won't work as we don't have codeowners files on\r\nbranches other than main.","sha":"228a6ffb0ff39bfdb5862071ee8cf559bb53e36a","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-minor","v8.15.0","v8.16.0"],"number":187597,"url":"https://github.com/elastic/kibana/pull/187597","mergeCommit":{"message":"fix(NA): unhandled exception for junit report generation when no codeowners (#187597)\n\nThis PR fixes what was brought on at\r\nhttps://github.com/elastic/kibana/pull/181711 .\r\n\r\nWhat was proposed won't work as we don't have codeowners files on\r\nbranches other than main.","sha":"228a6ffb0ff39bfdb5862071ee8cf559bb53e36a"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187597","number":187597,"mergeCommit":{"message":"fix(NA): unhandled exception for junit report generation when no codeowners (#187597)\n\nThis PR fixes what was brought on at\r\nhttps://github.com/elastic/kibana/pull/181711 .\r\n\r\nWhat was proposed won't work as we don't have codeowners files on\r\nbranches other than main.","sha":"228a6ffb0ff39bfdb5862071ee8cf559bb53e36a"}}]}] BACKPORT--> |
||
Lisa Cawley
|
9aeb629a93
|
[8.15] [DOCS] Edit Google Gemini connector (#187528) (#187601)
# Backport This will backport the following commits from `main` to `8.15`: - [[DOCS] Edit Google Gemini connector (#187528)](https://github.com/elastic/kibana/pull/187528) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-07-04T14:42:55Z","message":"[DOCS] Edit Google Gemini connector (#187528)","sha":"477b92444a47a4b93e50f67f3c8ff3cc89fbdaaf","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","docs","Team:Security Generative AI","v8.15.0"],"number":187528,"url":"https://github.com/elastic/kibana/pull/187528","mergeCommit":{"message":"[DOCS] Edit Google Gemini connector (#187528)","sha":"477b92444a47a4b93e50f67f3c8ff3cc89fbdaaf"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","labelRegex":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/187528","number":187528,"mergeCommit":{"message":"[DOCS] Edit Google Gemini connector (#187528)","sha":"477b92444a47a4b93e50f67f3c8ff3cc89fbdaaf"}}]}] BACKPORT--> |
||
|
Tiago Costa
|
1c1713ac2e
|
chore(NA): prepare for 8.15 branch cut | ||
Joey F. Poon
|
2c7b381089
|
[Security Solution] unskip endpoint metering tests (#187431)
## Summary unskip endpoint metering integration tests. passed 100/100 flaky test runs. ### Checklist - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) |
||
Jatin Kathuria
|
18c5f83e64
|
Unified Timeline - Fix - Docs for Event renderers (#187457)
## Summary This PR incorporates docs feedback as per : https://github.com/elastic/security-docs/issues/5341#issuecomment-2205602709 |
||
Kevin Qualters
|
0ec428bf9c
|
[Security Solution] [Timelines] Refresh notes table in thunk when deleting (#187428)
## Summary
Fixes an issue where the table was not being properly updated upon
deletion.
Paulo Henrique
|
7ae1f7a7df
|
[CloudSecurity] Converting Findings DistributionBar FTR into integration test (#186938)
## Summary It closes #176700 This PR converts the DistributionBar FTR test on the Findings page into an integration test using MSW. It also closes #176700as it was once triggering an error in the past Also, it adds the following changes: - Added a `generateMultipleCspFindings` helper to help with the writing of future tests and generating batch data. - Removed DistributionBar FTR test - Removed the extra layer of sub-components on the DistributionBar component to be simpler and added an aria-label on the distribution bar buttons. ## Screenshots 
Hannah Mudge
|
5e353a3a00
|
[Embeddables Rebuild] [Controls] Fix data control editor type selector (#187390)
Closes https://github.com/elastic/kibana/issues/187382 ## Summary This PR separates out the previously memoized `CompatibleControlTypesComponent` into a separate component that accepts **props** for the fields that it is dependant on rather than relying on the dependencies to the `useMemo` function. This is because, previously, we had an extra dependency in the dependency array (`controlType`) that was causing the memoized component to render too many times and it was causing a weird bug where the old "disabled" menu item wasn't getting unmounted properly. | Before | After | |--------|--------| | 
Philippe Oberti
|
e4a44fd23e
|
[Security Solution][Notes] - add telemetry (#187362) | ||
Jen Huang
|
f03fa06d5e
|
[UII] Fix unsupported input callout not showing for Cloud Defend (#187518)
## Summary
Resolves #186785
This PR:
- Fixes unsupported input callout in data tagging UI not showing for
Cloud Defend
- Simplifies the constants list for unsupported inputs
- Tweaks copy and UI for empty state to match closer to
[designs](https://github.com/elastic/kibana/issues/179915#issuecomment-2034365557)
<img width="1406" alt="image"
src="
|
||
Luke G
|
adc9310845
|
[SecuritySolution] remove "fields" from the BrowserField (#187066)
## Summary This is part 1/n of a wider effort:) BrowserField used to be some kind of field dictionary (!) which is obviously wrong:). Added FieldCategory type for that as an intermediate step as I dont know if it will hold up after the changes I am doing are complete. |
||
Ryland Herrick
|
184b6e2ad4
|
[Security Solution][CTI] Enable rendering of CTI indicators with flattened fields (#179395)
## Summary Our initial implementation of these components assumed a very flat, normal structure for the indicator documents we would retrieve (because we leverage the `fields` API). However, `flattened` fields do not quite fit this pattern, and there is a bug where indicator documents containing `flattened` fields with complex values would not be parsed correctly, and we attempt to render JS objects to the DOM (which React does not like, and throws an error). This issue was uncovered originally in an SDH. ### How to Review See https://github.com/elastic/kibana/issues/179483 for details on how to repro. ### Screenshots (Using the data described in https://github.com/elastic/kibana/issues/179483): <img width="820" alt="Screenshot 2024-03-26 at 3 28 00 PM" src=" |
||
Maxim Palenov
|
a7cea13300
|
[Security Solution] Fix generation of circular types using non-circular types (#187061)
**Relates to:** https://github.com/elastic/kibana/issues/186066, https://github.com/elastic/kibana/pull/186221 ## Summary This PR fixes generated TS files for circular OpenAPI schemas when non circular (internal or external) schema is used. ## Details https://github.com/elastic/kibana/pull/186221 added code generation support for circular schemas. Such schemas have input TS types generated which may depend on the other circular or non circular TS types. The problem appears when a circular schema uses a non circular schema. Generated code expects an input type for used schemas exist but it's not a case non circular schemas. Let's consider a following OpenAPI spec with a self circular schema and a field referencing `NonEmptyString` schema ```yaml ... components: x-codegen-enabled: true schemas: SelfCircular: type: object properties: circularField: $ref: '#/components/schemas/SelfCircular' stringField: $ref: '../model/primitives.schema.yaml#/components/schemas/NonEmptyString' ``` where a generated TS file looks like ```ts import type { ZodTypeDef } from 'zod'; import { z } from 'zod'; import { NonEmptyString } from '../model/primitives.gen'; export interface SelfCircular { circularField?: SelfCircular; stringField?: NonEmptyString; } export interface SelfCircularInput { circularField?: SelfCircularInput; stringField?: NonEmptyStringInput; } export const SelfCircular: z.ZodType<SelfCircular, ZodTypeDef, SelfCircularInput> = z.object({ circularField: z.lazy(() => SelfCircular).optional(), stringField: NonEmptyString.optional(), }); ``` You can notice the generated TS file contains usage of `NonEmptyStringInput` which doesn't exist. **After applying the fix the generated TS file looks like** ```ts import type { ZodTypeDef } from 'zod'; import { z } from 'zod'; import { NonEmptyString } from '../model/primitives.gen'; export interface SelfCircular { circularField?: SelfCircular; stringField?: NonEmptyString; } export interface SelfCircularInput { circularField?: SelfCircularInput; stringField?: NonEmptyString; } export const SelfCircular: z.ZodType<SelfCircular, ZodTypeDef, SelfCircularInput> = z.object({ circularField: z.lazy(() => SelfCircular).optional(), stringField: NonEmptyString.optional(), }); ``` |
||
Christiane (Tina) Heiligers
|
ee80b740fa
|
Reuse core-security-service createMockAuthenticatedUser mock (#187426)
Follow up to https://github.com/elastic/kibana/pull/187318 Implement core `createMockAuthenticatedUser` in the security plugin mock to avoid divergence. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Tim Sullivan
|
482f2a9503
|
[Logstash Plugin] Migrate authc.getCurrentUser usage to coreContext.security (#187180)
Part of https://github.com/elastic/kibana/issues/186574 ## Summary This PR migrates the Logstash Plugin's route handler for saving a pipeline, which consumes `authc.getCurrentUser`, to use `coreContext.security`. Background: This PR serves as an example of a plugin migrating away from depending on the Security plugin, which is a high priority effort for the last release before 9.0. ### Checklist Delete any items that are not applicable to this PR. - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Yuliia Naumenko
|
0a0bb1498e
|
[Security AI Assistant] Persist prompts (#187040)
Moving prompts persistence layer from the local storage to the server side data stream `.kibana-elastic-ai-assistant-prompts` --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Jan Monschke
|
aad2239c32
|
[Security] Timeline OpenAPI documentation fixes (#186458)
## Summary - Fix issues that came up during validation with `spectral lint` running with the [recommended settings](https://docs.elastic.dev/content-architecture/oas#openapi-version). - Made sure all return and request types match with the code - Fixed incorrect descriptions and links to documenation Fixes https://github.com/elastic/kibana/issues/183812. --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |