mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 01:13:23 -04:00
76141 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Andreas Gkizas
|
dd61de8673 | updating manifests with hints path | ||
Kibana Machine
|
e07506bc00
|
[8.15] [Docs][Playground] Update supported model list (#188096) (#188418)
# Backport This will backport the following commits from `main` to `8.15`: - [[Docs][Playground] Update supported model list (#188096)](https://github.com/elastic/kibana/pull/188096) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Liam Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-16T10:34:37Z","message":"[Docs][Playground] Update supported model list (#188096)\n\nPer PR title","sha":"db001d9d4f27ba4b3d4699bc876c1a18b9ea7beb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","v8.15.0","v8.16.0"],"title":"[Docs][Playground] Update supported model list ","number":188096,"url":"https://github.com/elastic/kibana/pull/188096","mergeCommit":{"message":"[Docs][Playground] Update supported model list (#188096)\n\nPer PR title","sha":"db001d9d4f27ba4b3d4699bc876c1a18b9ea7beb"}},"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/188096","number":188096,"mergeCommit":{"message":"[Docs][Playground] Update supported model list (#188096)\n\nPer PR title","sha":"db001d9d4f27ba4b3d4699bc876c1a18b9ea7beb"}}]}] BACKPORT--> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> |
||
Vitalii Dmyterko
|
db5486b0f1
|
[Security Solution][Detection Engine] removes feature flag for ES|QL suppression in 8.15 (#188296)
## Summary - removes feature flag `alertSuppressionForEsqlRuleEnabled` for ES|QL suppression in 8.15 for ESS |
||
Jatin Kathuria
|
bb0aeff31a
|
[8.15] [Security Solution] Fix - Notes Flyout Product Feedback (#188129) (#188401)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Fix - Notes Flyout Product Feedback (#188129)](https://github.com/elastic/kibana/pull/188129) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2024-07-12T17:20:19Z","message":"[Security Solution] Fix - Notes Flyout Product Feedback (#188129)\n\n# Summary\r\n\r\nFixes below bugs based on feedback from @paulewing.\r\n\r\n\r\n## Event Details Toggle in Notes\r\n\r\n@paulewing requested to remove the event toggle \r\n\r\n|Before|After|\r\n|---|---|\r\n|
Pablo Machado
|
02533fa7e7
|
[8.15] [Security Solutions] Add a preview button to alerts inside the risk contribution panel (#187148) (#188219)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solutions] Add a preview button to alerts inside the risk contribution panel (#187148)](https://github.com/elastic/kibana/pull/187148) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2024-07-09T09:54:47Z","message":"[Security Solutions] Add a preview button to alerts inside the risk contribution panel (#187148)\n\n## Summary\r\n\r\nThe feature is hidden behind the flag `entityAlertPreviewEnabled`\r\n\r\n* It adds the extra column to the risk contribution panel with a button\r\nthat opens the alert preview panel\r\n\r\n\r\n\r\n |
||
|
Kibana Machine
|
779668816d
|
[8.15] OTel Onboarding: Add feedback button (#188216) (#188399)
# Backport This will backport the following commits from `main` to `8.15`: - [OTel Onboarding: Add feedback button (#188216)](https://github.com/elastic/kibana/pull/188216) <!--- 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-16T07:57:12Z","message":"OTel Onboarding: Add feedback button (#188216)\n\nAs a last-minute addition, this is adding a feedback button to the OTel\r\nflow so users have a way of leaving feedback:\r\n\r\n<img width=\"1413\" alt=\"Screenshot 2024-07-12 at 15 16 38\"\r\nsrc=\"https://github.com/user-attachments/assets/61c5529d-8956-49f4-84b7-b977eb179f74\">\r\n\r\nThe button is linking to https://ela.st/otel-onboarding-feedback which\r\nwill redirect to a targeted google form feedback form.\r\n\r\nThis PR is not attempting to close\r\nhttps://github.com/elastic/observability-dev/issues/3734 - for this, we\r\nneed to add a few other things and I would like to decouple this from\r\nthe 8.15 release.","sha":"735eb52dd6cdfc47109dd1fcaf22b1a9a264f7cf","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","v8.15.0","Feature: Observability Onboarding","v8.16.0"],"title":"OTel Onboarding: Add feedback button","number":188216,"url":"https://github.com/elastic/kibana/pull/188216","mergeCommit":{"message":"OTel Onboarding: Add feedback button (#188216)\n\nAs a last-minute addition, this is adding a feedback button to the OTel\r\nflow so users have a way of leaving feedback:\r\n\r\n<img width=\"1413\" alt=\"Screenshot 2024-07-12 at 15 16 38\"\r\nsrc=\"https://github.com/user-attachments/assets/61c5529d-8956-49f4-84b7-b977eb179f74\">\r\n\r\nThe button is linking to https://ela.st/otel-onboarding-feedback which\r\nwill redirect to a targeted google form feedback form.\r\n\r\nThis PR is not attempting to close\r\nhttps://github.com/elastic/observability-dev/issues/3734 - for this, we\r\nneed to add a few other things and I would like to decouple this from\r\nthe 8.15 release.","sha":"735eb52dd6cdfc47109dd1fcaf22b1a9a264f7cf"}},"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/188216","number":188216,"mergeCommit":{"message":"OTel Onboarding: Add feedback button (#188216)\n\nAs a last-minute addition, this is adding a feedback button to the OTel\r\nflow so users have a way of leaving feedback:\r\n\r\n<img width=\"1413\" alt=\"Screenshot 2024-07-12 at 15 16 38\"\r\nsrc=\"https://github.com/user-attachments/assets/61c5529d-8956-49f4-84b7-b977eb179f74\">\r\n\r\nThe button is linking to https://ela.st/otel-onboarding-feedback which\r\nwill redirect to a targeted google form feedback form.\r\n\r\nThis PR is not attempting to close\r\nhttps://github.com/elastic/observability-dev/issues/3734 - for this, we\r\nneed to add a few other things and I would like to decouple this from\r\nthe 8.15 release.","sha":"735eb52dd6cdfc47109dd1fcaf22b1a9a264f7cf"}}]}] BACKPORT--> Co-authored-by: Joe Reuter <johannes.reuter@elastic.co> |
||
|
Kibana Machine
|
e15976c8ae
|
[8.15] [ResponseOps][Cases] Add tech preview badge to create case page template section (#188081) (#188394)
# Backport This will backport the following commits from `main` to `8.15`: - [[ResponseOps][Cases] Add tech preview badge to create case page template section (#188081)](https://github.com/elastic/kibana/pull/188081) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-16T07:28:24Z","message":"[ResponseOps][Cases] Add tech preview badge to create case page template section (#188081)\n\n## Summary\r\n\r\nAdds a `Technical Preview` badge to the template section of the create\r\ncase page.\r\n\r\n### Checklist\r\n\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n\r\n---------\r\n\r\nCo-authored-by: Antonio <antoniodcoelho@gmail.com>","sha":"890958ec8c47e8de1f46794c69381f2a8ecfb0a4","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Cases","v8.15.0","v8.16.0"],"title":"[ResponseOps][Cases] Add tech preview badge to create case page template section","number":188081,"url":"https://github.com/elastic/kibana/pull/188081","mergeCommit":{"message":"[ResponseOps][Cases] Add tech preview badge to create case page template section (#188081)\n\n## Summary\r\n\r\nAdds a `Technical Preview` badge to the template section of the create\r\ncase page.\r\n\r\n### Checklist\r\n\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n\r\n---------\r\n\r\nCo-authored-by: Antonio <antoniodcoelho@gmail.com>","sha":"890958ec8c47e8de1f46794c69381f2a8ecfb0a4"}},"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/188081","number":188081,"mergeCommit":{"message":"[ResponseOps][Cases] Add tech preview badge to create case page template section (#188081)\n\n## Summary\r\n\r\nAdds a `Technical Preview` badge to the template section of the create\r\ncase page.\r\n\r\n### Checklist\r\n\r\n- [x] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n\r\n---------\r\n\r\nCo-authored-by: Antonio <antoniodcoelho@gmail.com>","sha":"890958ec8c47e8de1f46794c69381f2a8ecfb0a4"}}]}] BACKPORT--> Co-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com> |
||
|
Kibana Machine
|
8bbbe4d3c8
|
[8.15] [Security GenAI] Make langsmith UI settings take precedence over env vars. (#188297) (#188392)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security GenAI] Make langsmith UI settings take precedence over env vars. (#188297)](https://github.com/elastic/kibana/pull/188297) <!--- 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-16T07:19:45Z","message":"[Security GenAI] Make langsmith UI settings take precedence over env vars. (#188297)","sha":"02d5176b72e964dbab4e7ff28e4e601c32e8f55f","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security GenAI] Make langsmith UI settings take precedence over env vars.","number":188297,"url":"https://github.com/elastic/kibana/pull/188297","mergeCommit":{"message":"[Security GenAI] Make langsmith UI settings take precedence over env vars. (#188297)","sha":"02d5176b72e964dbab4e7ff28e4e601c32e8f55f"}},"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/188297","number":188297,"mergeCommit":{"message":"[Security GenAI] Make langsmith UI settings take precedence over env vars. (#188297)","sha":"02d5176b72e964dbab4e7ff28e4e601c32e8f55f"}}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
Michael Olorunnisola
|
321aac72b0
|
[8.15] [Bug][Investigations] - Fix timeline column reset (#188240) (#188386)
# Backport This will backport the following commits from `main` to `8.15`: - [[Bug][Investigations] - Fix timeline column reset (#188240)](https://github.com/elastic/kibana/pull/188240) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Michael Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T16:23:45Z","message":"[Bug][Investigations] - Fix timeline column reset (#188240)\n\n## Summary\r\n\r\n**Bug:**\r\nWithin the new timeline, we have default columns that show whenever an\r\nempty array for columns are provided.\r\nThis was causing columns to re-appear in the `Selected fields` section\r\neven though the columns were not actually selected anymore leading to\r\nmismatched state between the browser ui and the table preventing the\r\ndefault columns from being removed again without page refresh. _The old\r\ntimeline table is not affected_.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7d16b8c3-be1a-4bc7-87b0-62fcac563f15\r\n\r\n\r\n\r\n**Fix:**\r\nThe logic used to default an empty array of columns to the default\r\ntimeline columns has been updated to allow the empty array to be passed.\r\nWith the old timeline experience this just means all columns _can_ be\r\nremoved and you'd see an empty table, but with the new unified table\r\n(which will be the default in 8.15 after\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e5fbaf48-77e3-4363-8232-35d256729b7e","sha":"385884d98b21e5613eadb613ef984aa87da282ae","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","v8.15.0","v8.16.0"],"number":188240,"url":"https://github.com/elastic/kibana/pull/188240","mergeCommit":{"message":"[Bug][Investigations] - Fix timeline column reset (#188240)\n\n## Summary\r\n\r\n**Bug:**\r\nWithin the new timeline, we have default columns that show whenever an\r\nempty array for columns are provided.\r\nThis was causing columns to re-appear in the `Selected fields` section\r\neven though the columns were not actually selected anymore leading to\r\nmismatched state between the browser ui and the table preventing the\r\ndefault columns from being removed again without page refresh. _The old\r\ntimeline table is not affected_.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7d16b8c3-be1a-4bc7-87b0-62fcac563f15\r\n\r\n\r\n\r\n**Fix:**\r\nThe logic used to default an empty array of columns to the default\r\ntimeline columns has been updated to allow the empty array to be passed.\r\nWith the old timeline experience this just means all columns _can_ be\r\nremoved and you'd see an empty table, but with the new unified table\r\n(which will be the default in 8.15 after\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e5fbaf48-77e3-4363-8232-35d256729b7e","sha":"385884d98b21e5613eadb613ef984aa87da282ae"}},"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/188240","number":188240,"mergeCommit":{"message":"[Bug][Investigations] - Fix timeline column reset (#188240)\n\n## Summary\r\n\r\n**Bug:**\r\nWithin the new timeline, we have default columns that show whenever an\r\nempty array for columns are provided.\r\nThis was causing columns to re-appear in the `Selected fields` section\r\neven though the columns were not actually selected anymore leading to\r\nmismatched state between the browser ui and the table preventing the\r\ndefault columns from being removed again without page refresh. _The old\r\ntimeline table is not affected_.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7d16b8c3-be1a-4bc7-87b0-62fcac563f15\r\n\r\n\r\n\r\n**Fix:**\r\nThe logic used to default an empty array of columns to the default\r\ntimeline columns has been updated to allow the empty array to be passed.\r\nWith the old timeline experience this just means all columns _can_ be\r\nremoved and you'd see an empty table, but with the new unified table\r\n(which will be the default in 8.15 after\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e5fbaf48-77e3-4363-8232-35d256729b7e","sha":"385884d98b21e5613eadb613ef984aa87da282ae"}}]}] BACKPORT--> |
||
|
Vitalii Dmyterko
|
42d76f9f1c
|
[Security Solution][Detection Engine] removes feature flag for AI assistant on rule create form in 8.15 (#188294)
## Summary - removes feature flag `AIAssistantOnRuleCreationFormEnabled` for 8.15 ESS release |
||
|
Kibana Machine
|
fa883058cc
|
[8.15] [Security Solution] Fix showing integration status for single integration per package (#187200) (#188336)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Fix showing integration status for single integration per package (#187200)](https://github.com/elastic/kibana/pull/187200) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T17:13:14Z","message":"[Security Solution] Fix showing integration status for single integration per package (#187200)\n\n**Resolves:** https://github.com/elastic/kibana/issues/187199\r\n\r\n## Summary\r\n\r\nThis PR fixes displaying related integration status for rules referring packages with a single integration. A good example is `Web Application Suspicious Activity: Unauthorized Method` rule which refers `APM` integration. Package and integration names don't match but the prebuilt rule only refers a package name omitting the integration name.\r\n\r\n## Details\r\n\r\nThis fix changes response from `GET /internal/detection_engine/fleet/integrations/all` internal API endpoint by adding an additional integration for packages having a single integration which name doesn't match the package name.\r\n\r\nFor packages with a single integration and matching package and integration names there is only one integration returned with integration name and title omitted.\r\n\r\nThere are different packages with integrations\r\n\r\n- a package with multiple integrations\r\n- a package without integrations\r\n- a package with only one integration which name matches with the package name\r\n- a package with only one integration which name doesn't match with the package name\r\n\r\nThe latter case is `apm` package which has `apmServer` integration. For example `Web Application Suspicious Activity: Unauthorized Method` prebuilt rule specifies only `apm` package name which integration name is empty.\r\n\r\n### Screenshots before\r\n\r\nInstallation rule preview popover:\r\n<img width=\"1715\" alt=\"image\" src=\" |
||
|
Kibana Machine
|
6e852ceed5
|
[8.15] [Security solution] Fix LangGraph stream with `SimpleChatModel` (#187994) (#188378)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security solution] Fix LangGraph stream with `SimpleChatModel` (#187994)](https://github.com/elastic/kibana/pull/187994) <!--- 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-15T21:35:42Z","message":"[Security solution] Fix LangGraph stream with `SimpleChatModel` (#187994)","sha":"d5843b351e6307e25524242fc7a7416c8a81189d","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security solution] Fix LangGraph stream with `SimpleChatModel`","number":187994,"url":"https://github.com/elastic/kibana/pull/187994","mergeCommit":{"message":"[Security solution] Fix LangGraph stream with `SimpleChatModel` (#187994)","sha":"d5843b351e6307e25524242fc7a7416c8a81189d"}},"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/187994","number":187994,"mergeCommit":{"message":"[Security solution] Fix LangGraph stream with `SimpleChatModel` (#187994)","sha":"d5843b351e6307e25524242fc7a7416c8a81189d"}}]}] BACKPORT--> --------- Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
b0d4adb41a
|
[8.15] Fix support for IME in Assistant prompt (#184874) (#188384)
# Backport This will backport the following commits from `main` to `8.15`: - [Fix support for IME in Assistant prompt (#184874)](https://github.com/elastic/kibana/pull/184874) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2024-07-16T00:21:59Z","message":"Fix support for IME in Assistant prompt (#184874)\n\n## Summary\r\n\r\nKudos to @sakurai-youhei for providing a fix 🙇\r\n \r\nTested on Chrome, Firefox, Safari\r\n\r\n\r\n |
||
|
Kibana Machine
|
c2ae24f1bd
|
[8.15] [Search][Playground] Fix playground selected fields (#188278) (#188380)
# Backport This will backport the following commits from `main` to `8.15`: - [[Search][Playground] Fix playground selected fields (#188278)](https://github.com/elastic/kibana/pull/188278) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yan Savitski","email":"yan.savitski@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T22:37:41Z","message":"[Search][Playground] Fix playground selected fields (#188278)\n\nWhen user selected fields in query mode, goes to chat mode and then back\r\nto query mode. Some fields may return to default value\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"37845b04e8df7e61a2606634df28b6800cf55ed7","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"title":"[Search][Playground] Fix playground selected fields","number":188278,"url":"https://github.com/elastic/kibana/pull/188278","mergeCommit":{"message":"[Search][Playground] Fix playground selected fields (#188278)\n\nWhen user selected fields in query mode, goes to chat mode and then back\r\nto query mode. Some fields may return to default value\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"37845b04e8df7e61a2606634df28b6800cf55ed7"}},"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/188278","number":188278,"mergeCommit":{"message":"[Search][Playground] Fix playground selected fields (#188278)\n\nWhen user selected fields in query mode, goes to chat mode and then back\r\nto query mode. Some fields may return to default value\r\n\r\n---------\r\n\r\nCo-authored-by: Joseph McElroy <joseph.mcelroy@elastic.co>","sha":"37845b04e8df7e61a2606634df28b6800cf55ed7"}}]}] BACKPORT--> Co-authored-by: Yan Savitski <yan.savitski@elastic.co> |
||
|
Kibana Machine
|
cc7df3dce5
|
[8.15] [ci] skip flaky test (#188313) (#188381)
# Backport This will backport the following commits from `main` to `8.15`: - [[ci] skip flaky test (#188313)](https://github.com/elastic/kibana/pull/188313) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T14:33:15Z","message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","skip-ci","backport:prev-minor","v8.16.0"],"title":"[ci] skip flaky test","number":188313,"url":"https://github.com/elastic/kibana/pull/188313","mergeCommit":{"message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad"}},"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/188313","number":188313,"mergeCommit":{"message":"[ci] skip flaky test (#188313)\n\n## Summary\r\nRe: https://github.com/elastic/kibana/issues/188234","sha":"d5345e442dce28b0ee5ef057988b156ba78784ad"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
Alex Szabo
|
53c706932e
|
[8.15] [BK] Migrate es-forward (+add versions.json dependent triggering) (#184018) (#187983)
# Backport This will backport the following commits from `main` to `8.15`: - [[BK] Migrate es-forward (+add versions.json dependent triggering) (#184018)](https://github.com/elastic/kibana/pull/184018) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2024-07-10T10:08:16Z","message":"[BK] Migrate es-forward (+add versions.json dependent triggering) (#184018)\n\n## Goal\r\nWe'd like to introduce a way to run pipelines that have a dependency on\r\nthe currently active branch set (managed in\r\n[versions.json](./versions.json)).\r\n\r\nWith this, we'd like to migrate over the `es-forward` pipelines\r\n(currently:\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-15-forward-compatibility),\r\nand\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-14-forward-compatibility))\r\nto the new buildkite infra.\r\n\r\n## Summary\r\nThis PR introduces a new pipeline:\r\nhttps://buildkite.com/elastic/kibana-trigger-version-dependent-jobs\r\n(through\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml)).\r\n\r\nThe purpose of this new pipeline is to take the name of a \"pipelineSet\"\r\nthat refers to a pipeline, and based on the `versions.json` file, work\r\nout what are the branches on which the referred pipeline should be\r\ntriggered.\r\n\r\n### Example: `Trigger ES forward compatibility tests`\r\n- a scheduled run on\r\n[kibana-trigger-version-dependent-jobs](https://buildkite.com/elastic/kibana-trigger-version-dependent-jobs)\r\nwith the env var `TRIGGER_PIPELINE_SET=es-forward` runs\r\n- the pipeline implementation for\r\n`kibana-trigger-version-dependent-jobs` works out (looking at\r\n`versions.json`), that the `es-forward` set should trigger\r\nhttps://buildkite.com/elastic/kibana-es-forward (doesn't exist prior to\r\nthe PR) for (7.17+8.14) and (7.17+8.15)\r\n- the pipeline implementation uploads two trigger steps, running\r\nhttps://buildkite.com/elastic/kibana-es-forward in two instances with\r\nthe relevant parameterization.\r\n\r\nSince the trigger parameters are derived from the `versions.json` file,\r\nif we move on and close `8.14`, and open up `8.16`, this will follow,\r\nwithout having to update the pipeline resources or schedules.\r\n\r\n## Changes\r\n- 2 pipelines created:\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml),\r\n[kibana-es-forward.yml](.buildkite/pipeline-resource-definitions/kibana-es-forward.yml)\r\n - [x] add kibana-es-forward.yml\r\n - implementation for `trigger-version-dependent-jobs` added\r\n- branch configuration removed from pipelines (kibana-artifacts-staging,\r\nkibana-artifacts-snapshot, kibana-artifacts-trigger)\r\n - added a script for checking RREs validity (moved a few files)\r\n\r\n## Verification\r\nI've used the migration staging pipeline (*) to run this:\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/130\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-trigger\"`\r\n- Result:\r\n[(success):](https://buildkite.com/elastic/kibana-artifacts-trigger/builds/10806)\r\nit triggered for 8.14 only (as expected)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/131\r\n - Env: `TRIGGER_PIPELINE_SET=\"es-forward\"`\r\n- Result: (success): it generated 2 trigger steps, but since the\r\nes-forward pipeline doesn't exist, the upload step failed\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/132\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-snapshot\"`\r\n- Result: (success): it triggered jobs for all 3 open branches\r\n(main/8.14/7.17)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/134\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-staging\"`\r\n - Result: (success): it triggered 8.14 / 7.14, but not for main\r\n\r\n\r\n(*note: this migration staging pipeline will come in handy even after\r\nthe migration, to stage newly created pipelines without creating the\r\nresource up-front)","sha":"ea2509914f2238c646bb63eb5bbbb240365fd04d","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.15.0","v8.16.0"],"number":184018,"url":"https://github.com/elastic/kibana/pull/184018","mergeCommit":{"message":"[BK] Migrate es-forward (+add versions.json dependent triggering) (#184018)\n\n## Goal\r\nWe'd like to introduce a way to run pipelines that have a dependency on\r\nthe currently active branch set (managed in\r\n[versions.json](./versions.json)).\r\n\r\nWith this, we'd like to migrate over the `es-forward` pipelines\r\n(currently:\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-15-forward-compatibility),\r\nand\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-14-forward-compatibility))\r\nto the new buildkite infra.\r\n\r\n## Summary\r\nThis PR introduces a new pipeline:\r\nhttps://buildkite.com/elastic/kibana-trigger-version-dependent-jobs\r\n(through\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml)).\r\n\r\nThe purpose of this new pipeline is to take the name of a \"pipelineSet\"\r\nthat refers to a pipeline, and based on the `versions.json` file, work\r\nout what are the branches on which the referred pipeline should be\r\ntriggered.\r\n\r\n### Example: `Trigger ES forward compatibility tests`\r\n- a scheduled run on\r\n[kibana-trigger-version-dependent-jobs](https://buildkite.com/elastic/kibana-trigger-version-dependent-jobs)\r\nwith the env var `TRIGGER_PIPELINE_SET=es-forward` runs\r\n- the pipeline implementation for\r\n`kibana-trigger-version-dependent-jobs` works out (looking at\r\n`versions.json`), that the `es-forward` set should trigger\r\nhttps://buildkite.com/elastic/kibana-es-forward (doesn't exist prior to\r\nthe PR) for (7.17+8.14) and (7.17+8.15)\r\n- the pipeline implementation uploads two trigger steps, running\r\nhttps://buildkite.com/elastic/kibana-es-forward in two instances with\r\nthe relevant parameterization.\r\n\r\nSince the trigger parameters are derived from the `versions.json` file,\r\nif we move on and close `8.14`, and open up `8.16`, this will follow,\r\nwithout having to update the pipeline resources or schedules.\r\n\r\n## Changes\r\n- 2 pipelines created:\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml),\r\n[kibana-es-forward.yml](.buildkite/pipeline-resource-definitions/kibana-es-forward.yml)\r\n - [x] add kibana-es-forward.yml\r\n - implementation for `trigger-version-dependent-jobs` added\r\n- branch configuration removed from pipelines (kibana-artifacts-staging,\r\nkibana-artifacts-snapshot, kibana-artifacts-trigger)\r\n - added a script for checking RREs validity (moved a few files)\r\n\r\n## Verification\r\nI've used the migration staging pipeline (*) to run this:\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/130\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-trigger\"`\r\n- Result:\r\n[(success):](https://buildkite.com/elastic/kibana-artifacts-trigger/builds/10806)\r\nit triggered for 8.14 only (as expected)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/131\r\n - Env: `TRIGGER_PIPELINE_SET=\"es-forward\"`\r\n- Result: (success): it generated 2 trigger steps, but since the\r\nes-forward pipeline doesn't exist, the upload step failed\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/132\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-snapshot\"`\r\n- Result: (success): it triggered jobs for all 3 open branches\r\n(main/8.14/7.17)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/134\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-staging\"`\r\n - Result: (success): it triggered 8.14 / 7.14, but not for main\r\n\r\n\r\n(*note: this migration staging pipeline will come in handy even after\r\nthe migration, to stage newly created pipelines without creating the\r\nresource up-front)","sha":"ea2509914f2238c646bb63eb5bbbb240365fd04d"}},"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/184018","number":184018,"mergeCommit":{"message":"[BK] Migrate es-forward (+add versions.json dependent triggering) (#184018)\n\n## Goal\r\nWe'd like to introduce a way to run pipelines that have a dependency on\r\nthe currently active branch set (managed in\r\n[versions.json](./versions.json)).\r\n\r\nWith this, we'd like to migrate over the `es-forward` pipelines\r\n(currently:\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-15-forward-compatibility),\r\nand\r\n[this](https://buildkite.com/elastic/kibana-7-dot-17-es-8-dot-14-forward-compatibility))\r\nto the new buildkite infra.\r\n\r\n## Summary\r\nThis PR introduces a new pipeline:\r\nhttps://buildkite.com/elastic/kibana-trigger-version-dependent-jobs\r\n(through\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml)).\r\n\r\nThe purpose of this new pipeline is to take the name of a \"pipelineSet\"\r\nthat refers to a pipeline, and based on the `versions.json` file, work\r\nout what are the branches on which the referred pipeline should be\r\ntriggered.\r\n\r\n### Example: `Trigger ES forward compatibility tests`\r\n- a scheduled run on\r\n[kibana-trigger-version-dependent-jobs](https://buildkite.com/elastic/kibana-trigger-version-dependent-jobs)\r\nwith the env var `TRIGGER_PIPELINE_SET=es-forward` runs\r\n- the pipeline implementation for\r\n`kibana-trigger-version-dependent-jobs` works out (looking at\r\n`versions.json`), that the `es-forward` set should trigger\r\nhttps://buildkite.com/elastic/kibana-es-forward (doesn't exist prior to\r\nthe PR) for (7.17+8.14) and (7.17+8.15)\r\n- the pipeline implementation uploads two trigger steps, running\r\nhttps://buildkite.com/elastic/kibana-es-forward in two instances with\r\nthe relevant parameterization.\r\n\r\nSince the trigger parameters are derived from the `versions.json` file,\r\nif we move on and close `8.14`, and open up `8.16`, this will follow,\r\nwithout having to update the pipeline resources or schedules.\r\n\r\n## Changes\r\n- 2 pipelines created:\r\n[trigger-version-dependent-jobs.yml](.buildkite/pipeline-resource-definitions/trigger-version-dependent-jobs.yml),\r\n[kibana-es-forward.yml](.buildkite/pipeline-resource-definitions/kibana-es-forward.yml)\r\n - [x] add kibana-es-forward.yml\r\n - implementation for `trigger-version-dependent-jobs` added\r\n- branch configuration removed from pipelines (kibana-artifacts-staging,\r\nkibana-artifacts-snapshot, kibana-artifacts-trigger)\r\n - added a script for checking RREs validity (moved a few files)\r\n\r\n## Verification\r\nI've used the migration staging pipeline (*) to run this:\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/130\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-trigger\"`\r\n- Result:\r\n[(success):](https://buildkite.com/elastic/kibana-artifacts-trigger/builds/10806)\r\nit triggered for 8.14 only (as expected)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/131\r\n - Env: `TRIGGER_PIPELINE_SET=\"es-forward\"`\r\n- Result: (success): it generated 2 trigger steps, but since the\r\nes-forward pipeline doesn't exist, the upload step failed\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/132\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-snapshot\"`\r\n- Result: (success): it triggered jobs for all 3 open branches\r\n(main/8.14/7.17)\r\n-\r\nhttps://buildkite.com/elastic/kibana-migration-pipeline-staging/builds/134\r\n - Env: `TRIGGER_PIPELINE_SET=\"artifacts-staging\"`\r\n - Result: (success): it triggered 8.14 / 7.14, but not for main\r\n\r\n\r\n(*note: this migration staging pipeline will come in handy even after\r\nthe migration, to stage newly created pipelines without creating the\r\nresource up-front)","sha":"ea2509914f2238c646bb63eb5bbbb240365fd04d"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
b3f9c35760
|
[8.15] chore(NA): remove usage of re2 and replace it with a non native module (#188134) (#188366)
# Backport This will backport the following commits from `main` to `8.15`: - [chore(NA): remove usage of re2 and replace it with a non native module (#188134)](https://github.com/elastic/kibana/pull/188134) <!--- Backport version: 9.4.3 --> ### 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-15T19:33:28Z","message":"chore(NA): remove usage of re2 and replace it with a non native module (#188134)\n\nThis PR removes the usage of the native module version of `re2` and\r\nreplaces it with a js port called `re2js`.\r\nIt also ends our usage of native node modules in production and it\r\nremoves the task from the build as well. Further steps will be taken\r\nalong our strategy to avoid future usages of native node modules in prod\r\nenvironments.","sha":"3c338a82c2d6d59c91f0f3b74f725231c69c5b13","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:all-open","v8.16.0"],"title":"chore(NA): remove usage of re2 and replace it with a non native module","number":188134,"url":"https://github.com/elastic/kibana/pull/188134","mergeCommit":{"message":"chore(NA): remove usage of re2 and replace it with a non native module (#188134)\n\nThis PR removes the usage of the native module version of `re2` and\r\nreplaces it with a js port called `re2js`.\r\nIt also ends our usage of native node modules in production and it\r\nremoves the task from the build as well. Further steps will be taken\r\nalong our strategy to avoid future usages of native node modules in prod\r\nenvironments.","sha":"3c338a82c2d6d59c91f0f3b74f725231c69c5b13"}},"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/188134","number":188134,"mergeCommit":{"message":"chore(NA): remove usage of re2 and replace it with a non native module (#188134)\n\nThis PR removes the usage of the native module version of `re2` and\r\nreplaces it with a js port called `re2js`.\r\nIt also ends our usage of native node modules in production and it\r\nremoves the task from the build as well. Further steps will be taken\r\nalong our strategy to avoid future usages of native node modules in prod\r\nenvironments.","sha":"3c338a82c2d6d59c91f0f3b74f725231c69c5b13"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
|
Kibana Machine
|
8acbabf640
|
[8.15] [Build] Fix Windows Node path (#188271) (#188348)
# Backport This will backport the following commits from `main` to `8.15`: - [[Build] Fix Windows Node path (#188271)](https://github.com/elastic/kibana/pull/188271) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-15T18:02:27Z","message":"[Build] Fix Windows Node path (#188271)\n\n## Summary\r\n\r\nCloses #188175\r\n\r\nThis path wasn't updated as part of #184675","sha":"58c82e8f81e7768dbe92f0bd7c6a6ddb2f76d526","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.15.0","v8.16.0"],"title":"[Build] Fix Windows Node path","number":188271,"url":"https://github.com/elastic/kibana/pull/188271","mergeCommit":{"message":"[Build] Fix Windows Node path (#188271)\n\n## Summary\r\n\r\nCloses #188175\r\n\r\nThis path wasn't updated as part of #184675","sha":"58c82e8f81e7768dbe92f0bd7c6a6ddb2f76d526"}},"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/188271","number":188271,"mergeCommit":{"message":"[Build] Fix Windows Node path (#188271)\n\n## Summary\r\n\r\nCloses #188175\r\n\r\nThis path wasn't updated as part of #184675","sha":"58c82e8f81e7768dbe92f0bd7c6a6ddb2f76d526"}}]}] BACKPORT--> Co-authored-by: Brad White <Ikuni17@users.noreply.github.com> |
||
|
Kibana Machine
|
269f0bc35f
|
[8.15] [Obs AI Assistant] Fix AI Assistant Settings when plugin disabled (#188160) (#188347)
# Backport This will backport the following commits from `main` to `8.15`: - [[Obs AI Assistant] Fix AI Assistant Settings when plugin disabled (#188160)](https://github.com/elastic/kibana/pull/188160) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-15T17:58:02Z","message":"[Obs AI Assistant] Fix AI Assistant Settings when plugin disabled (#188160)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187977\r\n\r\nAI Assistant settings page doesn't load when the plugin is disabled. \r\n\r\n### Changes\r\n\r\n- fixes not checking for object before accessing property\r\n- simplifies message so it makes sense for all possible states (read\r\nonly, disabled in space, plugin disabled)\r\n\r\n### Testing steps\r\n- create a Viewer user\r\n- go to Stack Management -> Advanced Settings -> AI Assistant\r\n- page should load with message that the feature is disabled\r\n\r\n<img width=\"804\" alt=\"Screenshot 2024-07-11 at 4 57 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/98cf85a2-913f-43fd-a5f0-df4494faaf1f\">","sha":"d4ba87988da61dc793ba5982fa0bbc28034bf449","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Obs AI Assistant","v8.15.0","v8.16.0"],"title":"[Obs AI Assistant] Fix AI Assistant Settings when plugin disabled","number":188160,"url":"https://github.com/elastic/kibana/pull/188160","mergeCommit":{"message":"[Obs AI Assistant] Fix AI Assistant Settings when plugin disabled (#188160)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187977\r\n\r\nAI Assistant settings page doesn't load when the plugin is disabled. \r\n\r\n### Changes\r\n\r\n- fixes not checking for object before accessing property\r\n- simplifies message so it makes sense for all possible states (read\r\nonly, disabled in space, plugin disabled)\r\n\r\n### Testing steps\r\n- create a Viewer user\r\n- go to Stack Management -> Advanced Settings -> AI Assistant\r\n- page should load with message that the feature is disabled\r\n\r\n<img width=\"804\" alt=\"Screenshot 2024-07-11 at 4 57 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/98cf85a2-913f-43fd-a5f0-df4494faaf1f\">","sha":"d4ba87988da61dc793ba5982fa0bbc28034bf449"}},"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/188160","number":188160,"mergeCommit":{"message":"[Obs AI Assistant] Fix AI Assistant Settings when plugin disabled (#188160)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/187977\r\n\r\nAI Assistant settings page doesn't load when the plugin is disabled. \r\n\r\n### Changes\r\n\r\n- fixes not checking for object before accessing property\r\n- simplifies message so it makes sense for all possible states (read\r\nonly, disabled in space, plugin disabled)\r\n\r\n### Testing steps\r\n- create a Viewer user\r\n- go to Stack Management -> Advanced Settings -> AI Assistant\r\n- page should load with message that the feature is disabled\r\n\r\n<img width=\"804\" alt=\"Screenshot 2024-07-11 at 4 57 59 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/98cf85a2-913f-43fd-a5f0-df4494faaf1f\">","sha":"d4ba87988da61dc793ba5982fa0bbc28034bf449"}}]}] BACKPORT--> Co-authored-by: Sandra G <neptunian@users.noreply.github.com> |
||
|
Kibana Machine
|
3a35a1ed94
|
[8.15] Upgrade Node.js to 20.15.1 (#187791) (#188339)
# Backport This will backport the following commits from `main` to `8.15`: - [Upgrade Node.js to 20.15.1 (#187791)](https://github.com/elastic/kibana/pull/187791) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T17:34:07Z","message":"Upgrade Node.js to 20.15.1 (#187791)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"7891410d12b8c26fdc11595342e9d0fc05140482","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.16.0"],"title":"Upgrade Node.js to 20.15.1","number":187791,"url":"https://github.com/elastic/kibana/pull/187791","mergeCommit":{"message":"Upgrade Node.js to 20.15.1 (#187791)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"7891410d12b8c26fdc11595342e9d0fc05140482"}},"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/187791","number":187791,"mergeCommit":{"message":"Upgrade Node.js to 20.15.1 (#187791)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"7891410d12b8c26fdc11595342e9d0fc05140482"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
|
Kibana Machine
|
4a9ca6f8d7
|
[8.15] [Data Forge] Add artificial delay feature (#187901) (#188333)
# Backport This will backport the following commits from `main` to `8.15`: - [[Data Forge] Add artificial delay feature (#187901)](https://github.com/elastic/kibana/pull/187901) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Chris Cowan","email":"chris@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T16:49:34Z","message":"[Data Forge] Add artificial delay feature (#187901)\n\n## Summary\r\n\r\nThis PR adds a new setting, `indexing.artificialIndexDelay`, to the\r\nindexing configuration to control how much artificial delay to add to\r\nthe timestamps. This PR also adds a \"final\" ingest pipeline to each data\r\nsource along with injecting a new base `component_template` which\r\nincludes the `event.ingested` field.\r\n\r\nThe artificial delay is useful for testing transforms on data that has a\r\nsignificant delays. It also allows us to test if we miss data when\r\nsyncing on the transforms using `event.ingested`.\r\n\r\n- Installs default ingest pipeline to add event.ingested to each\r\ndocument\r\n- Adds final_pipeline to each install_index_template\r\n- Inject base component_template to each index_template at install time\r\n- Add artificial delay for \"current\" events, historical events are\r\ningested without delay.\r\n- Change index math to produce monthly indices\r\n\r\n### How to test:\r\n\r\nCopy the following to `fake_logs.delayed.yaml`:\r\n\r\n```YAML\r\n---\r\nelasticsearch:\r\n installKibanaUser: false\r\n\r\nkibana:\r\n installAssets: true\r\n host: \"http://localhost:5601/kibana\"\r\n\r\nindexing:\r\n dataset: \"fake_logs\"\r\n eventsPerCycle: 100\r\n artificialIndexDelay: 300000\r\n\r\nschedule:\r\n - template: \"good\"\r\n start: \"now-1h\"\r\n end: false\r\n eventsPerCycle: 100\r\n```\r\nThen run `node x-pack/scripts/data_forge.js --config\r\nfake_logs.delayed.yaml`. This should index an hour of data immediately,\r\nthen add a 300s delay when indexing in \"real time\". The logs will look\r\nlike:\r\n\r\n```\r\n info Starting index to http://localhost:9200 with a payload size of 10000 using 5 workers to index 100 events per cycle\r\n info Installing index templates (fake_logs)\r\n info Installing components for fake_logs (fake_logs_8.0.0_base,fake_logs_8.0.0_event,fake_logs_8.0.0_log,fake_logs_8.0.0_host,fake_logs_8.0.0_metricset)\r\n info Installing index template (fake_logs)\r\n info Indexing \"good\" events from 2024-07-09T16:23:36.803Z to indefinitely\r\n info Delaying 100 by 300000ms\r\n info Waiting 60000ms\r\n info { took: 2418721239, latency: 541, indexed: 6000 } Indexing 6000 documents.\r\n...\r\n```\r\nThen after `300s`, it will index another `100` documents every `60s`.\r\nYou can also inspect the delay per minute using the following ES|QL in\r\nDiscover:\r\n```\r\nFROM kbn-data-forge-fake_logs.fake_logs-* | eval diff=DATE_DIFF(\"seconds\", @timestamp, event.ingested) | STATS delay=AVG(diff) by timestamp=BUCKET(@timestamp, 1 minute)\r\n```\r\nThis should give you a chart that looks something like this:\r\n\r\n<img width=\"1413\" alt=\"image\"\r\nsrc=\" |
||
|
Jatin Kathuria
|
1fadaaf8eb
|
[8.15] [Security Solution] Fix - Unified Timeline Style fixes (#187937) (#188328)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Fix - Unified Timeline Style fixes (#187937)](https://github.com/elastic/kibana/pull/187937) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T10:21:56Z","message":"[Security Solution] Fix - Unified Timeline Style fixes (#187937)\n\n## Summary\r\n\r\n## Unified Timeline\r\n\r\n### Before \r\n
Kaarina Tungseth
|
b29d62eb57
|
[8.15] [Integrations/Docs] Remove version from Integrations Dev Guide link (#188257) | ||
|
Kibana Machine
|
4689d709c1
|
[8.15] `yarn kbn reset` will clean data/ as well to avoid stale state (#188298) (#188316)
# Backport This will backport the following commits from `main` to `8.15`: - [`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)](https://github.com/elastic/kibana/pull/188298) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T14:38:57Z","message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.16.0"],"title":"`yarn kbn reset` will clean data/ as well to avoid stale state","number":188298,"url":"https://github.com/elastic/kibana/pull/188298","mergeCommit":{"message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb"}},"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/188298","number":188298,"mergeCommit":{"message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
ec48c9efcb
|
[8.15] [Infra] services test fix (#187961) (#188312)
# Backport This will backport the following commits from `main` to `8.15`: - [[Infra] services test fix (#187961)](https://github.com/elastic/kibana/pull/187961) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-15T13:58:10Z","message":"[Infra] services test fix (#187961)\n\nfixes [#176967](https://github.com/elastic/kibana/issues/176967)\r\n\r\n## Summary\r\n\r\nIt seems like the problem here is caused by async teardowns running\r\nwhile the test is about to run.\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6507\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3e863aa8b0a58e88e8b841268458a50abd5b5bc3","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-infra_services","v8.16.0"],"title":"[Infra] services test fix","number":187961,"url":"https://github.com/elastic/kibana/pull/187961","mergeCommit":{"message":"[Infra] services test fix (#187961)\n\nfixes [#176967](https://github.com/elastic/kibana/issues/176967)\r\n\r\n## Summary\r\n\r\nIt seems like the problem here is caused by async teardowns running\r\nwhile the test is about to run.\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6507\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3e863aa8b0a58e88e8b841268458a50abd5b5bc3"}},"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/187961","number":187961,"mergeCommit":{"message":"[Infra] services test fix (#187961)\n\nfixes [#176967](https://github.com/elastic/kibana/issues/176967)\r\n\r\n## Summary\r\n\r\nIt seems like the problem here is caused by async teardowns running\r\nwhile the test is about to run.\r\n\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6507\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3e863aa8b0a58e88e8b841268458a50abd5b5bc3"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
|
Kibana Machine
|
88524f21df
|
[8.15] [Security Solution] Fix non-responsive rule details page (#187953) (#188305)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Fix non-responsive rule details page (#187953)](https://github.com/elastic/kibana/pull/187953) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2024-07-15T11:37:26Z","message":"[Security Solution] Fix non-responsive rule details page (#187953)\n\n**Resolves:** https://github.com/elastic/kibana/issues/177734\r\n\r\n## Summary\r\n\r\nThis PR fixes a non-responsive rule details page under non default space.\r\n\r\n## Details\r\n\r\n**[Security Solution] Rule details page is not responsive and leads to page crash for rule in non-default spaces [#177734](https://github.com/elastic/kibana/issues/177734)** resurfaced back. Investigation has show that **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** is the cause.\r\n\r\nThe problem is quite subtle to comprehend it just by looking at the code. In fact it boils down to an unstable `useAsync()` hook dependency. Every re-render `useAsync()` resolves a promise causing an additional re-render to show updated results and the cycle repeats. Such hook is used in `x-pack/plugins/security_solution/public/common/components/visualization_actions/actions.tsx`\r\n\r\n```ts\r\n const panels = useAsync(\r\n () =>\r\n buildContextMenuForActions({\r\n actions: contextMenuActions.map((action) => ({\r\n action,\r\n context: {},\r\n trigger: VISUALIZATION_CONTEXT_MENU_TRIGGER,\r\n })),\r\n }),\r\n [contextMenuActions]\r\n );\r\n```\r\n\r\nwhere `contextMenuActions` is an unstable dependency. This is the case due to refactoring to `useSaveToLibrary()` hook by **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** which started retuning a new object every render. The dependency chain is `contextMenuActions` -> `useActions()` -> `useSaveToLibrary()`.\r\n\r\nThe actual fix is to replace\r\n\r\n```ts\r\nconst { lens, ...startServices } = useKibana().services;\r\n```\r\n\r\nwith\r\n\r\n```ts\r\nconst startServices = useKibana().services;\r\n```\r\n\r\nSince `startServices` is used as a hook dependency it must be stable. A rest property in object destruction expression is always a new object and can't be used as a dependency as is. Using stable `useKibana().services` fixes the problem.","sha":"8a539a8a4ce483d2e5d3aa484d8ec78887f338b8","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:critical","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Rule Details","v8.15.0","v8.16.0"],"title":"[Security Solution] Fix non-responsive rule details page","number":187953,"url":"https://github.com/elastic/kibana/pull/187953","mergeCommit":{"message":"[Security Solution] Fix non-responsive rule details page (#187953)\n\n**Resolves:** https://github.com/elastic/kibana/issues/177734\r\n\r\n## Summary\r\n\r\nThis PR fixes a non-responsive rule details page under non default space.\r\n\r\n## Details\r\n\r\n**[Security Solution] Rule details page is not responsive and leads to page crash for rule in non-default spaces [#177734](https://github.com/elastic/kibana/issues/177734)** resurfaced back. Investigation has show that **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** is the cause.\r\n\r\nThe problem is quite subtle to comprehend it just by looking at the code. In fact it boils down to an unstable `useAsync()` hook dependency. Every re-render `useAsync()` resolves a promise causing an additional re-render to show updated results and the cycle repeats. Such hook is used in `x-pack/plugins/security_solution/public/common/components/visualization_actions/actions.tsx`\r\n\r\n```ts\r\n const panels = useAsync(\r\n () =>\r\n buildContextMenuForActions({\r\n actions: contextMenuActions.map((action) => ({\r\n action,\r\n context: {},\r\n trigger: VISUALIZATION_CONTEXT_MENU_TRIGGER,\r\n })),\r\n }),\r\n [contextMenuActions]\r\n );\r\n```\r\n\r\nwhere `contextMenuActions` is an unstable dependency. This is the case due to refactoring to `useSaveToLibrary()` hook by **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** which started retuning a new object every render. The dependency chain is `contextMenuActions` -> `useActions()` -> `useSaveToLibrary()`.\r\n\r\nThe actual fix is to replace\r\n\r\n```ts\r\nconst { lens, ...startServices } = useKibana().services;\r\n```\r\n\r\nwith\r\n\r\n```ts\r\nconst startServices = useKibana().services;\r\n```\r\n\r\nSince `startServices` is used as a hook dependency it must be stable. A rest property in object destruction expression is always a new object and can't be used as a dependency as is. Using stable `useKibana().services` fixes the problem.","sha":"8a539a8a4ce483d2e5d3aa484d8ec78887f338b8"}},"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/187953","number":187953,"mergeCommit":{"message":"[Security Solution] Fix non-responsive rule details page (#187953)\n\n**Resolves:** https://github.com/elastic/kibana/issues/177734\r\n\r\n## Summary\r\n\r\nThis PR fixes a non-responsive rule details page under non default space.\r\n\r\n## Details\r\n\r\n**[Security Solution] Rule details page is not responsive and leads to page crash for rule in non-default spaces [#177734](https://github.com/elastic/kibana/issues/177734)** resurfaced back. Investigation has show that **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** is the cause.\r\n\r\nThe problem is quite subtle to comprehend it just by looking at the code. In fact it boils down to an unstable `useAsync()` hook dependency. Every re-render `useAsync()` resolves a promise causing an additional re-render to show updated results and the cycle repeats. Such hook is used in `x-pack/plugins/security_solution/public/common/components/visualization_actions/actions.tsx`\r\n\r\n```ts\r\n const panels = useAsync(\r\n () =>\r\n buildContextMenuForActions({\r\n actions: contextMenuActions.map((action) => ({\r\n action,\r\n context: {},\r\n trigger: VISUALIZATION_CONTEXT_MENU_TRIGGER,\r\n })),\r\n }),\r\n [contextMenuActions]\r\n );\r\n```\r\n\r\nwhere `contextMenuActions` is an unstable dependency. This is the case due to refactoring to `useSaveToLibrary()` hook by **[Security Solution] Remove usage of deprecated React rendering utilities [#181099](https://github.com/elastic/kibana/pull/181099)** which started retuning a new object every render. The dependency chain is `contextMenuActions` -> `useActions()` -> `useSaveToLibrary()`.\r\n\r\nThe actual fix is to replace\r\n\r\n```ts\r\nconst { lens, ...startServices } = useKibana().services;\r\n```\r\n\r\nwith\r\n\r\n```ts\r\nconst startServices = useKibana().services;\r\n```\r\n\r\nSince `startServices` is used as a hook dependency it must be stable. A rest property in object destruction expression is always a new object and can't be used as a dependency as is. Using stable `useKibana().services` fixes the problem.","sha":"8a539a8a4ce483d2e5d3aa484d8ec78887f338b8"}}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
3baf161e18
|
[8.15] [Playground] [Bug] Continue to use text_expansion when rank_features field (#188232) (#188303)
# Backport This will backport the following commits from `main` to `8.15`: - [[Playground] [Bug] Continue to use text_expansion when rank_features field (#188232)](https://github.com/elastic/kibana/pull/188232) <!--- 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-15T11:26:46Z","message":"[Playground] [Bug] Continue to use text_expansion when rank_features field (#188232)\n\n## Summary\r\n\r\nwe switched over to use `sparse_vector` query clause for both\r\n`sparse_vector` and `rank_features`. Due to a recent design\r\ndecision,`rank_features` fields no longer supports `sparse_vector` query\r\nclause and we therefore need to fallback to the `text_expansion` query\r\ninstead.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dc577c0bf1e02116287e2c5c617223094d34af45","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"title":"[Playground] [Bug] Continue to use text_expansion when rank_features field","number":188232,"url":"https://github.com/elastic/kibana/pull/188232","mergeCommit":{"message":"[Playground] [Bug] Continue to use text_expansion when rank_features field (#188232)\n\n## Summary\r\n\r\nwe switched over to use `sparse_vector` query clause for both\r\n`sparse_vector` and `rank_features`. Due to a recent design\r\ndecision,`rank_features` fields no longer supports `sparse_vector` query\r\nclause and we therefore need to fallback to the `text_expansion` query\r\ninstead.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dc577c0bf1e02116287e2c5c617223094d34af45"}},"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/188232","number":188232,"mergeCommit":{"message":"[Playground] [Bug] Continue to use text_expansion when rank_features field (#188232)\n\n## Summary\r\n\r\nwe switched over to use `sparse_vector` query clause for both\r\n`sparse_vector` and `rank_features`. Due to a recent design\r\ndecision,`rank_features` fields no longer supports `sparse_vector` query\r\nclause and we therefore need to fallback to the `text_expansion` query\r\ninstead.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n### Risk Matrix\r\n\r\nDelete this section if it is not applicable to this PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other developers to\r\nidentify risks that should be tested prior to the change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider some of the following examples\r\nand how they may potentially impact the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes |\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n| Multiple Spaces—unexpected behavior in non-default Kibana Space.\r\n| Low | High | Integration tests will verify that all features are still\r\nsupported in non-default Kibana Space and when user switches between\r\nspaces. |\r\n| Multiple nodes—Elasticsearch polling might have race conditions\r\nwhen multiple Kibana nodes are polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so executing them multiple times will not result\r\nin logical error, but will degrade performance. To test for this case we\r\nadd plenty of unit tests around this logic and document manual testing\r\nprocedure. |\r\n| Code should gracefully handle cases when feature X or plugin Y are\r\ndisabled. | Medium | High | Unit tests will verify that any feature flag\r\nor plugin combination still results in our service operational. |\r\n| [See more potential risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"dc577c0bf1e02116287e2c5c617223094d34af45"}}]}] BACKPORT--> Co-authored-by: Joe McElroy <joseph.mcelroy@elastic.co> |
||
|
Kibana Machine
|
6b02af8877
|
[8.15] [Security Solution][Detection Engine] fixes misaligned dropdown for page selector on shared exception lists page (#187956) (#188299)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution][Detection Engine] fixes misaligned dropdown for page selector on shared exception lists page (#187956)](https://github.com/elastic/kibana/pull/187956) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-15T11:10:32Z","message":"[Security Solution][Detection Engine] fixes misaligned dropdown for page selector on shared exception lists page (#187956)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/kibana/issues/180459\r\n\r\n### Before\r\n<img width=\"2464\" alt=\"Screenshot 2024-07-10 at 11 51 45\"\r\nsrc=\" |
||
|
Alex Szabo
|
3478bd15c6
|
[8.15] remove pipeline resource definitions on non-main (#187746)
## Summary These are not needed in non-main |
||
|
Kibana Machine
|
98cd57d9c9
|
[8.15] [EDR Workflows] Add warning for duplicated `event.category` for Process Descendant event filter (#187844) (#188071)
# Backport This will backport the following commits from `main` to `8.15`: - [[EDR Workflows] Add warning for duplicated `event.category` for Process Descendant event filter (#187844)](https://github.com/elastic/kibana/pull/187844) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T09:40:56Z","message":"[EDR Workflows] Add warning for duplicated `event.category` for Process Descendant event filter (#187844)\n\n## Summary\r\n\r\n\r\n (#188276)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security solution] Fix regenerate button with LangGraph (#188249)](https://github.com/elastic/kibana/pull/188249) <!--- 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-13T14:16:12Z","message":"[Security solution] Fix regenerate button with LangGraph (#188249)","sha":"f72a321a9c80b8c9ccb30f30a5870200989e3ae1","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","v8.15.0","v8.16.0"],"title":"[Security solution] Fix regenerate button with LangGraph","number":188249,"url":"https://github.com/elastic/kibana/pull/188249","mergeCommit":{"message":"[Security solution] Fix regenerate button with LangGraph (#188249)","sha":"f72a321a9c80b8c9ccb30f30a5870200989e3ae1"}},"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/188249","number":188249,"mergeCommit":{"message":"[Security solution] Fix regenerate button with LangGraph (#188249)","sha":"f72a321a9c80b8c9ccb30f30a5870200989e3ae1"}}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
Ryland Herrick
|
38677570cb
|
[8.15] [Detection Engine] Addresses Flakiness in ML FTR tests (#188155) (#188259)
# Backport This will backport the following commits from `main` to `8.15`: - [[Detection Engine] Addresses Flakiness in ML FTR tests (#188155)](https://github.com/elastic/kibana/pull/188155) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2024-07-12T19:10:25Z","message":"[Detection Engine] Addresses Flakiness in ML FTR tests (#188155)\n\n## Summary\r\n\r\nThe full chronicle of this endeavor can be found\r\n[here](https://github.com/elastic/kibana/pull/182183), but [this\r\ncomment](https://github.com/elastic/kibana/pull/182183#issuecomment-2221517519)\r\nsummarizes the identified issue:\r\n\r\n> I [finally\r\nfound](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6516#01909dde-a3e8-4e47-b255-b1ff7cac8f8d/6-2368)\r\nthe cause of these failures in the response to our \"setup modules\"\r\nrequest to ML. Attaching here for posterity:\r\n>\r\n> <details>\r\n> <summary>Setup Modules Failure Response</summary>\r\n> \r\n> ```json\r\n> {\r\n> \"jobs\": [\r\n> { \"id\": \"v3_linux_anomalous_network_port_activity\", \"success\": true },\r\n> {\r\n> \"id\": \"v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> ],\r\n> \"type\": \"search_phase_execution_exception\",\r\n> \"reason\": \"all shards failed\",\r\n> \"phase\": \"query\",\r\n> \"grouped\": true,\r\n> \"failed_shards\": [\r\n> {\r\n> \"shard\": 0,\r\n> \"index\":\r\n\".ml-anomalies-custom-v3_linux_network_configuration_discovery\",\r\n> \"node\": \"dKzpvp06ScO0OxqHilETEA\",\r\n> \"reason\": {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> }\r\n> ]\r\n> },\r\n> \"status\": 503\r\n> }\r\n> }\r\n> ],\r\n> \"datafeeds\": [\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_port_activity\",\r\n> \"success\": true,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false\r\n> },\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> }\r\n> ],\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> },\r\n> \"status\": 404\r\n> }\r\n> }\r\n> ],\r\n> \"kibana\": {}\r\n> }\r\n> \r\n> ```\r\n> </details>\r\n\r\nThis branch, then, fixes said issue by (relatively simply) retrying the\r\nfailed API call until it succeeds.\r\n\r\n### Related Issues\r\nAddresses:\r\n- https://github.com/elastic/kibana/issues/171426\r\n- https://github.com/elastic/kibana/issues/187478\r\n- https://github.com/elastic/kibana/issues/187614\r\n- https://github.com/elastic/kibana/issues/182009\r\n- https://github.com/elastic/kibana/issues/171426\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] [ESS Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6528)\r\n- [x] [Serverless Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6529)\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df635ef4a8c86c41c91ac5f59198a9b67d1dc8b","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Feature:Detection Rules","Feature:ML Rule","Feature:Security ML Jobs","Feature:Rule Creation","Team:Detection Engine","Feature:Rule Edit","v8.16.0"],"number":188155,"url":"https://github.com/elastic/kibana/pull/188155","mergeCommit":{"message":"[Detection Engine] Addresses Flakiness in ML FTR tests (#188155)\n\n## Summary\r\n\r\nThe full chronicle of this endeavor can be found\r\n[here](https://github.com/elastic/kibana/pull/182183), but [this\r\ncomment](https://github.com/elastic/kibana/pull/182183#issuecomment-2221517519)\r\nsummarizes the identified issue:\r\n\r\n> I [finally\r\nfound](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6516#01909dde-a3e8-4e47-b255-b1ff7cac8f8d/6-2368)\r\nthe cause of these failures in the response to our \"setup modules\"\r\nrequest to ML. Attaching here for posterity:\r\n>\r\n> <details>\r\n> <summary>Setup Modules Failure Response</summary>\r\n> \r\n> ```json\r\n> {\r\n> \"jobs\": [\r\n> { \"id\": \"v3_linux_anomalous_network_port_activity\", \"success\": true },\r\n> {\r\n> \"id\": \"v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> ],\r\n> \"type\": \"search_phase_execution_exception\",\r\n> \"reason\": \"all shards failed\",\r\n> \"phase\": \"query\",\r\n> \"grouped\": true,\r\n> \"failed_shards\": [\r\n> {\r\n> \"shard\": 0,\r\n> \"index\":\r\n\".ml-anomalies-custom-v3_linux_network_configuration_discovery\",\r\n> \"node\": \"dKzpvp06ScO0OxqHilETEA\",\r\n> \"reason\": {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> }\r\n> ]\r\n> },\r\n> \"status\": 503\r\n> }\r\n> }\r\n> ],\r\n> \"datafeeds\": [\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_port_activity\",\r\n> \"success\": true,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false\r\n> },\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> }\r\n> ],\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> },\r\n> \"status\": 404\r\n> }\r\n> }\r\n> ],\r\n> \"kibana\": {}\r\n> }\r\n> \r\n> ```\r\n> </details>\r\n\r\nThis branch, then, fixes said issue by (relatively simply) retrying the\r\nfailed API call until it succeeds.\r\n\r\n### Related Issues\r\nAddresses:\r\n- https://github.com/elastic/kibana/issues/171426\r\n- https://github.com/elastic/kibana/issues/187478\r\n- https://github.com/elastic/kibana/issues/187614\r\n- https://github.com/elastic/kibana/issues/182009\r\n- https://github.com/elastic/kibana/issues/171426\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] [ESS Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6528)\r\n- [x] [Serverless Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6529)\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df635ef4a8c86c41c91ac5f59198a9b67d1dc8b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188155","number":188155,"mergeCommit":{"message":"[Detection Engine] Addresses Flakiness in ML FTR tests (#188155)\n\n## Summary\r\n\r\nThe full chronicle of this endeavor can be found\r\n[here](https://github.com/elastic/kibana/pull/182183), but [this\r\ncomment](https://github.com/elastic/kibana/pull/182183#issuecomment-2221517519)\r\nsummarizes the identified issue:\r\n\r\n> I [finally\r\nfound](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6516#01909dde-a3e8-4e47-b255-b1ff7cac8f8d/6-2368)\r\nthe cause of these failures in the response to our \"setup modules\"\r\nrequest to ML. Attaching here for posterity:\r\n>\r\n> <details>\r\n> <summary>Setup Modules Failure Response</summary>\r\n> \r\n> ```json\r\n> {\r\n> \"jobs\": [\r\n> { \"id\": \"v3_linux_anomalous_network_port_activity\", \"success\": true },\r\n> {\r\n> \"id\": \"v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> ],\r\n> \"type\": \"search_phase_execution_exception\",\r\n> \"reason\": \"all shards failed\",\r\n> \"phase\": \"query\",\r\n> \"grouped\": true,\r\n> \"failed_shards\": [\r\n> {\r\n> \"shard\": 0,\r\n> \"index\":\r\n\".ml-anomalies-custom-v3_linux_network_configuration_discovery\",\r\n> \"node\": \"dKzpvp06ScO0OxqHilETEA\",\r\n> \"reason\": {\r\n> \"type\": \"no_shard_available_action_exception\",\r\n> \"reason\":\r\n\"[ftr][127.0.0.1:9300][indices:data/read/search[phase/query]]\"\r\n> }\r\n> }\r\n> ]\r\n> },\r\n> \"status\": 503\r\n> }\r\n> }\r\n> ],\r\n> \"datafeeds\": [\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_port_activity\",\r\n> \"success\": true,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false\r\n> },\r\n> {\r\n> \"id\": \"datafeed-v3_linux_anomalous_network_activity\",\r\n> \"success\": false,\r\n> \"started\": false,\r\n> \"awaitingMlNodeAllocation\": false,\r\n> \"error\": {\r\n> \"error\": {\r\n> \"root_cause\": [\r\n> {\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> }\r\n> ],\r\n> \"type\": \"resource_not_found_exception\",\r\n> \"reason\": \"No known job with id 'v3_linux_anomalous_network_activity'\"\r\n> },\r\n> \"status\": 404\r\n> }\r\n> }\r\n> ],\r\n> \"kibana\": {}\r\n> }\r\n> \r\n> ```\r\n> </details>\r\n\r\nThis branch, then, fixes said issue by (relatively simply) retrying the\r\nfailed API call until it succeeds.\r\n\r\n### Related Issues\r\nAddresses:\r\n- https://github.com/elastic/kibana/issues/171426\r\n- https://github.com/elastic/kibana/issues/187478\r\n- https://github.com/elastic/kibana/issues/187614\r\n- https://github.com/elastic/kibana/issues/182009\r\n- https://github.com/elastic/kibana/issues/171426\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [x] [ESS Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6528)\r\n- [x] [Serverless Rule Execution FTR x\r\n200](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6529)\r\n\r\n\r\n### For maintainers\r\n\r\n- [x] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"3df635ef4a8c86c41c91ac5f59198a9b67d1dc8b"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
bc5b5da7fd
|
[8.15] [Security AI Assistant] Changing chat related internal APIs to become public (#188139) (#188260)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security AI Assistant] Changing chat related internal APIs to become public (#188139)](https://github.com/elastic/kibana/pull/188139) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Yuliia Naumenko","email":"jo.naumenko@gmail.com"},"sourceCommit":{"committedDate":"2024-07-12T19:23:09Z","message":"[Security AI Assistant] Changing chat related internal APIs to become public (#188139)\n\n## Summary\r\n\r\nIn this PR Security Gen AI related APIs are changed from internal to\r\npublic.\r\n\r\nConversations APIs:\r\n- POST/PUT/GET/DELETE\r\n`\"/api/security_ai_assistant/current_user/conversations/{id}\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nPrompts APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/prompts/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nAnonymization APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/anonymization_fields/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/anonymization_fields/_find\"`","sha":"1d5cf48a9700ee769f64256c23278fcfd8cecc5d","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.15.0","v8.16.0"],"title":"[Security AI Assistant] Changing chat related internal APIs to become public","number":188139,"url":"https://github.com/elastic/kibana/pull/188139","mergeCommit":{"message":"[Security AI Assistant] Changing chat related internal APIs to become public (#188139)\n\n## Summary\r\n\r\nIn this PR Security Gen AI related APIs are changed from internal to\r\npublic.\r\n\r\nConversations APIs:\r\n- POST/PUT/GET/DELETE\r\n`\"/api/security_ai_assistant/current_user/conversations/{id}\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nPrompts APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/prompts/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nAnonymization APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/anonymization_fields/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/anonymization_fields/_find\"`","sha":"1d5cf48a9700ee769f64256c23278fcfd8cecc5d"}},"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/188139","number":188139,"mergeCommit":{"message":"[Security AI Assistant] Changing chat related internal APIs to become public (#188139)\n\n## Summary\r\n\r\nIn this PR Security Gen AI related APIs are changed from internal to\r\npublic.\r\n\r\nConversations APIs:\r\n- POST/PUT/GET/DELETE\r\n`\"/api/security_ai_assistant/current_user/conversations/{id}\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nPrompts APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/prompts/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/current_user/conversations/_find\"`\r\n\r\nAnonymization APIs:\r\n\r\n- POST `\"/api/security_ai_assistant/anonymization_fields/_bulk_action\"`\r\n- GET `\"/api/security_ai_assistant/anonymization_fields/_find\"`","sha":"1d5cf48a9700ee769f64256c23278fcfd8cecc5d"}}]}] BACKPORT--> Co-authored-by: Yuliia Naumenko <jo.naumenko@gmail.com> |
||
|
Kibana Machine
|
c37905cab9
|
[8.15] [UII] Remove action links and buttons when secrets field is disabled (#188252) (#188258)
# Backport This will backport the following commits from `main` to `8.15`: - [[UII] Remove action links and buttons when secrets field is disabled (#188252)](https://github.com/elastic/kibana/pull/188252) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2024-07-12T18:31:16Z","message":"[UII] Remove action links and buttons when secrets field is disabled (#188252)\n\n## Summary\r\n\r\nResolves #187642 \r\n\r\nThis PR removes action links and buttons to replace and convert secrets\r\nfields if the field itself is disabled, for cases like the user not\r\nhaving write permissions:\r\n\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/957ad858-74bf-4f28-a212-148253e4ca0f\">\r\n\r\n<img width=\"716\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d70f7946-8b62-4e13-9d16-98ddac26b826\">\r\n\r\nAlso applies sentence casing to `Service token` label.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"4c0db61e6d92ada57833471a33daa5eb40c38e44","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.16.0"],"title":"[UII] Remove action links and buttons when secrets field is disabled","number":188252,"url":"https://github.com/elastic/kibana/pull/188252","mergeCommit":{"message":"[UII] Remove action links and buttons when secrets field is disabled (#188252)\n\n## Summary\r\n\r\nResolves #187642 \r\n\r\nThis PR removes action links and buttons to replace and convert secrets\r\nfields if the field itself is disabled, for cases like the user not\r\nhaving write permissions:\r\n\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/957ad858-74bf-4f28-a212-148253e4ca0f\">\r\n\r\n<img width=\"716\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d70f7946-8b62-4e13-9d16-98ddac26b826\">\r\n\r\nAlso applies sentence casing to `Service token` label.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"4c0db61e6d92ada57833471a33daa5eb40c38e44"}},"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/188252","number":188252,"mergeCommit":{"message":"[UII] Remove action links and buttons when secrets field is disabled (#188252)\n\n## Summary\r\n\r\nResolves #187642 \r\n\r\nThis PR removes action links and buttons to replace and convert secrets\r\nfields if the field itself is disabled, for cases like the user not\r\nhaving write permissions:\r\n\r\n<img width=\"730\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/957ad858-74bf-4f28-a212-148253e4ca0f\">\r\n\r\n<img width=\"716\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/d70f7946-8b62-4e13-9d16-98ddac26b826\">\r\n\r\nAlso applies sentence casing to `Service token` label.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"4c0db61e6d92ada57833471a33daa5eb40c38e44"}}]}] BACKPORT--> Co-authored-by: Jen Huang <its.jenetic@gmail.com> |
||
|
Kibana Machine
|
98895c5a1b
|
[8.15] [Playground] [Bug] Previous messages now sent to LLM (#188123) (#188244)
# Backport This will backport the following commits from `main` to `8.15`: - [[Playground] [Bug] Previous messages now sent to LLM (#188123)](https://github.com/elastic/kibana/pull/188123) <!--- 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-12T15:37:04Z","message":"[Playground] [Bug] Previous messages now sent to LLM (#188123)\n\n## Summary\r\n\r\nNow that we are using ChatModel, we should be sending previous messages\r\nin the conversation history.\r\n\r\nThis change:\r\n- defines the prompt as a system prompt\r\n- sends all previous conversations into the ChatModel\r\n- sends the question as a separate message\r\n- update the examples to showcase this flow\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"aca82181a81841acbcaa92ae22cb16aa51f4a735","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.15.0","v8.16.0"],"title":"[Playground] [Bug] Previous messages now sent to LLM","number":188123,"url":"https://github.com/elastic/kibana/pull/188123","mergeCommit":{"message":"[Playground] [Bug] Previous messages now sent to LLM (#188123)\n\n## Summary\r\n\r\nNow that we are using ChatModel, we should be sending previous messages\r\nin the conversation history.\r\n\r\nThis change:\r\n- defines the prompt as a system prompt\r\n- sends all previous conversations into the ChatModel\r\n- sends the question as a separate message\r\n- update the examples to showcase this flow\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"aca82181a81841acbcaa92ae22cb16aa51f4a735"}},"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/188123","number":188123,"mergeCommit":{"message":"[Playground] [Bug] Previous messages now sent to LLM (#188123)\n\n## Summary\r\n\r\nNow that we are using ChatModel, we should be sending previous messages\r\nin the conversation history.\r\n\r\nThis change:\r\n- defines the prompt as a system prompt\r\n- sends all previous conversations into the ChatModel\r\n- sends the question as a separate message\r\n- update the examples to showcase this flow\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] Any UI touched in this PR is usable by keyboard only (learn more\r\nabout [keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n- [ ] Any UI touched in this PR does not create any new axe failures\r\n(run axe in browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This renders correctly on smaller devices using a responsive\r\nlayout. (You can test this [in your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n- [ ] This was checked for [cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)","sha":"aca82181a81841acbcaa92ae22cb16aa51f4a735"}}]}] BACKPORT--> Co-authored-by: Joe McElroy <joseph.mcelroy@elastic.co> |
||
|
Kibana Machine
|
e6c0563419
|
[8.15] [Telemetry][Security Solution] Use the proper index to query builtin alerts (#187859) (#188217)
# Backport This will backport the following commits from `main` to `8.15`: - [[Telemetry][Security Solution] Use the proper index to query builtin alerts (#187859)](https://github.com/elastic/kibana/pull/187859) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sebastián Zaffarano","email":"sebastian.zaffarano@elastic.co"},"sourceCommit":{"committedDate":"2024-07-12T13:17:43Z","message":"[Telemetry][Security Solution] Use the proper index to query builtin alerts (#187859)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/177263 changed the way\r\n`telemetry-prebuilt-rule-alerts` get data from elastic, but it changed\r\nthe index used to run the queries. This PR fixes it using the proper\r\nindex.","sha":"a120c510b9738aab0fb5f9296515a82f6f0792a6","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","v8.14.0","v8.15.0","v8.16.0"],"title":"[Telemetry][Security Solution] Use the proper index to query builtin alerts","number":187859,"url":"https://github.com/elastic/kibana/pull/187859","mergeCommit":{"message":"[Telemetry][Security Solution] Use the proper index to query builtin alerts (#187859)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/177263 changed the way\r\n`telemetry-prebuilt-rule-alerts` get data from elastic, but it changed\r\nthe index used to run the queries. This PR fixes it using the proper\r\nindex.","sha":"a120c510b9738aab0fb5f9296515a82f6f0792a6"}},"sourceBranch":"main","suggestedTargetBranches":["8.14","8.15"],"targetPullRequestStates":[{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"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/187859","number":187859,"mergeCommit":{"message":"[Telemetry][Security Solution] Use the proper index to query builtin alerts (#187859)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/pull/177263 changed the way\r\n`telemetry-prebuilt-rule-alerts` get data from elastic, but it changed\r\nthe index used to run the queries. This PR fixes it using the proper\r\nindex.","sha":"a120c510b9738aab0fb5f9296515a82f6f0792a6"}}]}] BACKPORT--> Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co> |
||
|
Kibana Machine
|
3354dbaba4
|
[8.15] [Infra] Limit the number of metrics accepted by Snapshot API (#188181) (#188231)
# Backport This will backport the following commits from `main` to `8.15`: - [[Infra] Limit the number of metrics accepted by Snapshot API (#188181)](https://github.com/elastic/kibana/pull/188181) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-12T13:53:53Z","message":"[Infra] Limit the number of metrics accepted by Snapshot API (#188181)\n\npart of [3628](https://github.com/elastic/observability-dev/issues/3628)\r\n- private\r\n\r\n\r\n## Summary\r\n\r\nAfter adding 20 items, users can no longer add more metrics and will see\r\nthe \"Add metric\" button disabled with a tooltip\r\n\r\n<img width=\"1713\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c784b08b-e118-4491-b53d-46bfde898216\">\r\n\r\n\r\n### How to test\r\n\r\n- Start a local Kibana instance pointing to an oblt cluster\r\n- Navigate to Infrastructure\r\n- Try to add more than 20 metrics in the Metrics dropdown.","sha":"f2d1a8b6d24486cedb0dad97e71cd660845f353c","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:project-deploy-observability","Team:obs-ux-infra_services","v8.16.0"],"title":"[Infra] Limit the number of metrics accepted by Snapshot API","number":188181,"url":"https://github.com/elastic/kibana/pull/188181","mergeCommit":{"message":"[Infra] Limit the number of metrics accepted by Snapshot API (#188181)\n\npart of [3628](https://github.com/elastic/observability-dev/issues/3628)\r\n- private\r\n\r\n\r\n## Summary\r\n\r\nAfter adding 20 items, users can no longer add more metrics and will see\r\nthe \"Add metric\" button disabled with a tooltip\r\n\r\n<img width=\"1713\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c784b08b-e118-4491-b53d-46bfde898216\">\r\n\r\n\r\n### How to test\r\n\r\n- Start a local Kibana instance pointing to an oblt cluster\r\n- Navigate to Infrastructure\r\n- Try to add more than 20 metrics in the Metrics dropdown.","sha":"f2d1a8b6d24486cedb0dad97e71cd660845f353c"}},"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/188181","number":188181,"mergeCommit":{"message":"[Infra] Limit the number of metrics accepted by Snapshot API (#188181)\n\npart of [3628](https://github.com/elastic/observability-dev/issues/3628)\r\n- private\r\n\r\n\r\n## Summary\r\n\r\nAfter adding 20 items, users can no longer add more metrics and will see\r\nthe \"Add metric\" button disabled with a tooltip\r\n\r\n<img width=\"1713\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c784b08b-e118-4491-b53d-46bfde898216\">\r\n\r\n\r\n### How to test\r\n\r\n- Start a local Kibana instance pointing to an oblt cluster\r\n- Navigate to Infrastructure\r\n- Try to add more than 20 metrics in the Metrics dropdown.","sha":"f2d1a8b6d24486cedb0dad97e71cd660845f353c"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com> |
||
Khristinin Nikita
|
27685e9782
|
Enable manual rule run in 8.15 branch (#188073)
## Enable manual rule run in 8.15 (this PR target in 8.15, not main) As we want to enable manual rule run in 8.15, but we can't yet do it in main, as docs not ready. We want to enable in 8.15 to be able test in BC |
||
|
Kibana Machine
|
37c981937d
|
[8.15] [Obs AI Assistant] Support for Gemini connector (#188002) (#188174)
# Backport This will backport the following commits from `main` to `8.15`: - [[Obs AI Assistant] Support for Gemini connector (#188002)](https://github.com/elastic/kibana/pull/188002) <!--- 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-12T05:53:23Z","message":"[Obs AI Assistant] Support for Gemini connector (#188002)\n\nImplements support for the Gemini connector:\r\n\r\n- Adds the `.gemini` connector type id to the allowlisted connectors\r\n- Create an adapter for the Gemini connector type that formats and\r\nparses requests/responses in the format of Gemini on Vertex\r\n\r\nWhat's still missing:\r\n- Native function calling. We use simulated function calling for now.\r\nThere are some changes in the function schemas to prepare for this\r\n(Gemini blows up when there are dots in property names).\r\n- E2E tests. The Gemini connector always calls out to an external\r\nendpoint, which causes the call to fail because we cannot hardcode\r\nactual credentials.","sha":"5b8967884b1eb8e0339ce8031ea8b21f9facb29e","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Obs AI Assistant","ci:project-deploy-observability","Team:obs-ux-infra_services","apm:review","v8.15.0","v8.16.0"],"title":"[Obs AI Assistant] Support for Gemini connector","number":188002,"url":"https://github.com/elastic/kibana/pull/188002","mergeCommit":{"message":"[Obs AI Assistant] Support for Gemini connector (#188002)\n\nImplements support for the Gemini connector:\r\n\r\n- Adds the `.gemini` connector type id to the allowlisted connectors\r\n- Create an adapter for the Gemini connector type that formats and\r\nparses requests/responses in the format of Gemini on Vertex\r\n\r\nWhat's still missing:\r\n- Native function calling. We use simulated function calling for now.\r\nThere are some changes in the function schemas to prepare for this\r\n(Gemini blows up when there are dots in property names).\r\n- E2E tests. The Gemini connector always calls out to an external\r\nendpoint, which causes the call to fail because we cannot hardcode\r\nactual credentials.","sha":"5b8967884b1eb8e0339ce8031ea8b21f9facb29e"}},"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/188002","number":188002,"mergeCommit":{"message":"[Obs AI Assistant] Support for Gemini connector (#188002)\n\nImplements support for the Gemini connector:\r\n\r\n- Adds the `.gemini` connector type id to the allowlisted connectors\r\n- Create an adapter for the Gemini connector type that formats and\r\nparses requests/responses in the format of Gemini on Vertex\r\n\r\nWhat's still missing:\r\n- Native function calling. We use simulated function calling for now.\r\nThere are some changes in the function schemas to prepare for this\r\n(Gemini blows up when there are dots in property names).\r\n- E2E tests. The Gemini connector always calls out to an external\r\nendpoint, which causes the call to fail because we cannot hardcode\r\nactual credentials.","sha":"5b8967884b1eb8e0339ce8031ea8b21f9facb29e"}}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> |
||
|
Kibana Machine
|
6302a65c80
|
[8.15] [UII] Fill in empty values for `constant_keyword` fields from existing mappings (#188145) (#188170)
# Backport This will backport the following commits from `main` to `8.15`: - [[UII] Fill in empty values for `constant_keyword` fields from existing mappings (#188145)](https://github.com/elastic/kibana/pull/188145) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2024-07-12T03:05:03Z","message":"[UII] Fill in empty values for `constant_keyword` fields from existing mappings (#188145)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/178528.\r\n\r\nSome packages declare `constant_keyword` type fields without an explicit\r\nvalue. This causes ES to fill in the value in the mappings using the\r\nfirst ingested value.\r\n\r\nWhen upgrading this type of package & field after the value has already\r\nbeen populated in this way, the mappings update fail due to pushing a\r\n`null` value into an existing value, triggering unnecessary rollovers.\r\n\r\nThis PR fixes that by filling in the empty values from the existing\r\nmappings.\r\n\r\n## Test\r\n1. On an empty cluster, turn on debug logs\r\n2. Set up Fleet Server policy and Fleet Server agent\r\n3. Force install old version of Elastic Agent integration, v1.19.2:\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.19.2\r\n{\r\n \"force\": true\r\n}\r\n```\r\n4. Create a new empty policy, **deselect system and agent monitoring**\r\n(otherwise the integration will be upgraded, we do not want this yet)\r\n5. Manually add Elastic Agent integration v1.19.2 to the new policy\r\n6. Edit the policy to enable logs and metrics monitoring\r\n7. Enroll agent into the policy, confirm that monitoring logs and\r\nmetrics are being ingested and that a value exists for `event.dataset`\r\nmapping for the logs:\r\n```\r\nGET logs-elastic_agent*/_mappings\r\n```\r\n```\r\n \"dataset\": {\r\n \"type\": \"constant_keyword\",\r\n \"value\": \"elastic_agent\"\r\n }\r\n```\r\n9. Upgrade Elastic Agent integration to v1.20.0 (note we are not\r\nupgrading to the newest versions, 2.0+, because these **are** expected\r\nto trigger rollovers for some data streams):\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.20.0\r\n{\r\n \"force\": true\r\n}\r\n```\r\n10. Confirm in Kibana logs that no rollovers triggered during the\r\nupgrade\r\n11. Confirm that there is still only 1 backing index for monitoring\r\nlogs:\r\n```\r\nGET logs-elastic_agent*\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b7c96f4c09e88b820664bbd0bb996844dd50a0e6","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.16.0"],"title":"[UII] Fill in empty values for `constant_keyword` fields from existing mappings","number":188145,"url":"https://github.com/elastic/kibana/pull/188145","mergeCommit":{"message":"[UII] Fill in empty values for `constant_keyword` fields from existing mappings (#188145)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/178528.\r\n\r\nSome packages declare `constant_keyword` type fields without an explicit\r\nvalue. This causes ES to fill in the value in the mappings using the\r\nfirst ingested value.\r\n\r\nWhen upgrading this type of package & field after the value has already\r\nbeen populated in this way, the mappings update fail due to pushing a\r\n`null` value into an existing value, triggering unnecessary rollovers.\r\n\r\nThis PR fixes that by filling in the empty values from the existing\r\nmappings.\r\n\r\n## Test\r\n1. On an empty cluster, turn on debug logs\r\n2. Set up Fleet Server policy and Fleet Server agent\r\n3. Force install old version of Elastic Agent integration, v1.19.2:\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.19.2\r\n{\r\n \"force\": true\r\n}\r\n```\r\n4. Create a new empty policy, **deselect system and agent monitoring**\r\n(otherwise the integration will be upgraded, we do not want this yet)\r\n5. Manually add Elastic Agent integration v1.19.2 to the new policy\r\n6. Edit the policy to enable logs and metrics monitoring\r\n7. Enroll agent into the policy, confirm that monitoring logs and\r\nmetrics are being ingested and that a value exists for `event.dataset`\r\nmapping for the logs:\r\n```\r\nGET logs-elastic_agent*/_mappings\r\n```\r\n```\r\n \"dataset\": {\r\n \"type\": \"constant_keyword\",\r\n \"value\": \"elastic_agent\"\r\n }\r\n```\r\n9. Upgrade Elastic Agent integration to v1.20.0 (note we are not\r\nupgrading to the newest versions, 2.0+, because these **are** expected\r\nto trigger rollovers for some data streams):\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.20.0\r\n{\r\n \"force\": true\r\n}\r\n```\r\n10. Confirm in Kibana logs that no rollovers triggered during the\r\nupgrade\r\n11. Confirm that there is still only 1 backing index for monitoring\r\nlogs:\r\n```\r\nGET logs-elastic_agent*\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b7c96f4c09e88b820664bbd0bb996844dd50a0e6"}},"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/188145","number":188145,"mergeCommit":{"message":"[UII] Fill in empty values for `constant_keyword` fields from existing mappings (#188145)\n\n## Summary\r\n\r\nResolves https://github.com/elastic/kibana/issues/178528.\r\n\r\nSome packages declare `constant_keyword` type fields without an explicit\r\nvalue. This causes ES to fill in the value in the mappings using the\r\nfirst ingested value.\r\n\r\nWhen upgrading this type of package & field after the value has already\r\nbeen populated in this way, the mappings update fail due to pushing a\r\n`null` value into an existing value, triggering unnecessary rollovers.\r\n\r\nThis PR fixes that by filling in the empty values from the existing\r\nmappings.\r\n\r\n## Test\r\n1. On an empty cluster, turn on debug logs\r\n2. Set up Fleet Server policy and Fleet Server agent\r\n3. Force install old version of Elastic Agent integration, v1.19.2:\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.19.2\r\n{\r\n \"force\": true\r\n}\r\n```\r\n4. Create a new empty policy, **deselect system and agent monitoring**\r\n(otherwise the integration will be upgraded, we do not want this yet)\r\n5. Manually add Elastic Agent integration v1.19.2 to the new policy\r\n6. Edit the policy to enable logs and metrics monitoring\r\n7. Enroll agent into the policy, confirm that monitoring logs and\r\nmetrics are being ingested and that a value exists for `event.dataset`\r\nmapping for the logs:\r\n```\r\nGET logs-elastic_agent*/_mappings\r\n```\r\n```\r\n \"dataset\": {\r\n \"type\": \"constant_keyword\",\r\n \"value\": \"elastic_agent\"\r\n }\r\n```\r\n9. Upgrade Elastic Agent integration to v1.20.0 (note we are not\r\nupgrading to the newest versions, 2.0+, because these **are** expected\r\nto trigger rollovers for some data streams):\r\n```\r\nPOST kbn:/api/fleet/epm/packages/elastic_agent/1.20.0\r\n{\r\n \"force\": true\r\n}\r\n```\r\n10. Confirm in Kibana logs that no rollovers triggered during the\r\nupgrade\r\n11. Confirm that there is still only 1 backing index for monitoring\r\nlogs:\r\n```\r\nGET logs-elastic_agent*\r\n```\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"b7c96f4c09e88b820664bbd0bb996844dd50a0e6"}}]}] BACKPORT--> Co-authored-by: Jen Huang <its.jenetic@gmail.com> |
||
|
Kibana Machine
|
d8611f1b13 | skip failing test suite (#187478) | ||
Tiago Costa
|
82e45362dd
|
skip flaky suite (#179307) | ||
|
Kibana Machine
|
dfcd9b8c4e
|
[8.15] [Obs AI Assistant] hide ai assistant menu item when in a disabled space (#188017) (#188161)
# Backport This will backport the following commits from `main` to `8.15`: - [[Obs AI Assistant] hide ai assistant menu item when in a disabled space (#188017)](https://github.com/elastic/kibana/pull/188017) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sandra G","email":"neptunian@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-11T21:06:24Z","message":"[Obs AI Assistant] hide ai assistant menu item when in a disabled space (#188017)\n\nHides AI Assistant button when in a space where the AI Assistant is\r\ndisabled","sha":"81b1705ea61ae69990a284ac7de808c7cd9eec22","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Obs AI Assistant","ci:project-deploy-observability","v8.15.0","v8.16.0"],"title":"[Obs AI Assistant] hide ai assistant menu item when in a disabled space","number":188017,"url":"https://github.com/elastic/kibana/pull/188017","mergeCommit":{"message":"[Obs AI Assistant] hide ai assistant menu item when in a disabled space (#188017)\n\nHides AI Assistant button when in a space where the AI Assistant is\r\ndisabled","sha":"81b1705ea61ae69990a284ac7de808c7cd9eec22"}},"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/188017","number":188017,"mergeCommit":{"message":"[Obs AI Assistant] hide ai assistant menu item when in a disabled space (#188017)\n\nHides AI Assistant button when in a space where the AI Assistant is\r\ndisabled","sha":"81b1705ea61ae69990a284ac7de808c7cd9eec22"}}]}] BACKPORT--> Co-authored-by: Sandra G <neptunian@users.noreply.github.com> |
||
|
Kibana Machine
|
7504c3844e
|
[8.15] [Discover] Unskip search alert serverless tests on MKI (#187771) (#188159)
# Backport This will backport the following commits from `main` to `8.15`: - [[Discover] Unskip search alert serverless tests on MKI (#187771)](https://github.com/elastic/kibana/pull/187771) <!--- 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-11T20:57:46Z","message":"[Discover] Unskip search alert serverless tests on MKI (#187771)\n\n- Closes https://github.com/elastic/kibana/issues/187069\r\n- Closes https://github.com/elastic/kibana/issues/180101\r\n- Closes https://github.com/elastic/kibana/issues/180100\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee3543990b68df1c7c7cf797ae0bda9bdc3af07d","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] Unskip search alert serverless tests on MKI","number":187771,"url":"https://github.com/elastic/kibana/pull/187771","mergeCommit":{"message":"[Discover] Unskip search alert serverless tests on MKI (#187771)\n\n- Closes https://github.com/elastic/kibana/issues/187069\r\n- Closes https://github.com/elastic/kibana/issues/180101\r\n- Closes https://github.com/elastic/kibana/issues/180100\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee3543990b68df1c7c7cf797ae0bda9bdc3af07d"}},"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/187771","number":187771,"mergeCommit":{"message":"[Discover] Unskip search alert serverless tests on MKI (#187771)\n\n- Closes https://github.com/elastic/kibana/issues/187069\r\n- Closes https://github.com/elastic/kibana/issues/180101\r\n- Closes https://github.com/elastic/kibana/issues/180100\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ee3543990b68df1c7c7cf797ae0bda9bdc3af07d"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
16da13489b
|
[8.15] [Discover] Fix chart getting stuck on loading when switching from ES|QL (#188034) (#188147)
# Backport This will backport the following commits from `main` to `8.15`: - [[Discover] Fix chart getting stuck on loading when switching from ES|QL (#188034)](https://github.com/elastic/kibana/pull/188034) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T18:32:35Z","message":"[Discover] Fix chart getting stuck on loading when switching from ES|QL (#188034)\n\n## Summary\r\n\r\nThis PR fixes an issue I noticed where the Discover chart can get stuck\r\non loading when switching from ES|QL to data view mode due to a race\r\ncondition:\r\n\r\n\r\n |
||
|
Kibana Machine
|
54efb7c080
|
[8.15] [SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed (#188106) (#188148)
# Backport This will backport the following commits from `main` to `8.15`: - [[SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed (#188106)](https://github.com/elastic/kibana/pull/188106) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T18:45:04Z","message":"[SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed (#188106)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/security-team/issues/9646\r\n\r\nThe embedded discover's `update` mechanism has changed and the `grid`\r\nand `hideChart` properties keep changing on initial sync, causing the\r\ntimeline show as `changed` when it actually didn't. These two properties\r\nare not important to actually determine the changed state of timeline\r\nand we can therefore ignore them.","sha":"b97f309926e240902787cc011df8ebaca64fffa7","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","backport:prev-minor","v8.16.0"],"title":"[SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed","number":188106,"url":"https://github.com/elastic/kibana/pull/188106","mergeCommit":{"message":"[SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed (#188106)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/security-team/issues/9646\r\n\r\nThe embedded discover's `update` mechanism has changed and the `grid`\r\nand `hideChart` properties keep changing on initial sync, causing the\r\ntimeline show as `changed` when it actually didn't. These two properties\r\nare not important to actually determine the changed state of timeline\r\nand we can therefore ignore them.","sha":"b97f309926e240902787cc011df8ebaca64fffa7"}},"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/188106","number":188106,"mergeCommit":{"message":"[SecuritySolution][Threat Hunting Investigation] Fix timeline showing as changed when it wasn't actually changed (#188106)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/security-team/issues/9646\r\n\r\nThe embedded discover's `update` mechanism has changed and the `grid`\r\nand `hideChart` properties keep changing on initial sync, causing the\r\ntimeline show as `changed` when it actually didn't. These two properties\r\nare not important to actually determine the changed state of timeline\r\nand we can therefore ignore them.","sha":"b97f309926e240902787cc011df8ebaca64fffa7"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co> |
||
|
Kibana Machine
|
f106c1620e
|
[8.15] [Index management] Clean up and remove comments from FTR tests (#188130) (#188143)
# Backport This will backport the following commits from `main` to `8.15`: - [[Index management] Clean up and remove comments from FTR tests (#188130)](https://github.com/elastic/kibana/pull/188130) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Saarika Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-11T18:06:59Z","message":"[Index management] Clean up and remove comments from FTR tests (#188130)\n\nRemove irrelevant comment, raised in\r\n[comment](https://github.com/elastic/kibana/pull/188045#discussion_r1674255549)","sha":"40a65306416f7b97a03ab2001e725eaef2075bda","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.15.0","v8.16.0"],"title":"[Index management] Clean up and remove comments from FTR tests","number":188130,"url":"https://github.com/elastic/kibana/pull/188130","mergeCommit":{"message":"[Index management] Clean up and remove comments from FTR tests (#188130)\n\nRemove irrelevant comment, raised in\r\n[comment](https://github.com/elastic/kibana/pull/188045#discussion_r1674255549)","sha":"40a65306416f7b97a03ab2001e725eaef2075bda"}},"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/188130","number":188130,"mergeCommit":{"message":"[Index management] Clean up and remove comments from FTR tests (#188130)\n\nRemove irrelevant comment, raised in\r\n[comment](https://github.com/elastic/kibana/pull/188045#discussion_r1674255549)","sha":"40a65306416f7b97a03ab2001e725eaef2075bda"}}]}] BACKPORT--> Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com> |
||
|
Kibana Machine
|
97033fac4c
|
[8.15] [Discover] Increase the comparison field limit to 250 (#188028) (#188146)
# Backport This will backport the following commits from `main` to `8.15`: - [[Discover] Increase the comparison field limit to 250 (#188028)](https://github.com/elastic/kibana/pull/188028) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T18:30:48Z","message":"[Discover] Increase the comparison field limit to 250 (#188028)\n\n## Summary\r\n\r\nThis PR increases the Discover comparison field limit to 250:\r\n\r\n (#188142)
# Backport This will backport the following commits from `main` to `8.15`: - [[Security Solution] Document flyout investigation guide and response action updates (#187920)](https://github.com/elastic/kibana/pull/187920) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-07-11T18:02:11Z","message":"[Security Solution] Document flyout investigation guide and response action updates (#187920)\n\n## Summary\r\n\r\nThis PR updates the UI for investigation guide and response actions per\r\nupdated [Figma\r\nmock](https://www.figma.com/design/882AiMJMr1GMKnXN5G6WDa/Component-library?node-id=2500-131607&t=JBKKkcwOOMjURFWu-0).\r\n\r\n### Investigation guide\r\n\r\nAlerts with investigation guide\r\n\r\n (#188141)
# Backport This will backport the following commits from `main` to `8.15`: - [[Maps] Update ems-client@8.5.3 (#188099)](https://github.com/elastic/kibana/pull/188099) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jorge Sanz","email":"jorge.sanz@elastic.co"},"sourceCommit":{"committedDate":"2024-07-11T17:43:13Z","message":"[Maps] Update ems-client@8.5.3 (#188099)\n\nReplaces #187679\n\nUpdates `@elastic/ems-client` to\n[8.5.3](https://github.com/elastic/ems-client/releases/tag/v8.5.3) which\nis an update in the library dependencies without any new features.","sha":"8670e59daeafde421d3ed6fe6b57577d662bb8fc","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Feature:Maps","v8.16.0"],"title":"[Maps] Update ems-client@8.5.3","number":188099,"url":"https://github.com/elastic/kibana/pull/188099","mergeCommit":{"message":"[Maps] Update ems-client@8.5.3 (#188099)\n\nReplaces #187679\n\nUpdates `@elastic/ems-client` to\n[8.5.3](https://github.com/elastic/ems-client/releases/tag/v8.5.3) which\nis an update in the library dependencies without any new features.","sha":"8670e59daeafde421d3ed6fe6b57577d662bb8fc"}},"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/188099","number":188099,"mergeCommit":{"message":"[Maps] Update ems-client@8.5.3 (#188099)\n\nReplaces #187679\n\nUpdates `@elastic/ems-client` to\n[8.5.3](https://github.com/elastic/ems-client/releases/tag/v8.5.3) which\nis an update in the library dependencies without any new features.","sha":"8670e59daeafde421d3ed6fe6b57577d662bb8fc"}}]}] BACKPORT--> Co-authored-by: Jorge Sanz <jorge.sanz@elastic.co> |