mirror of
https://github.com/elastic/kibana.git
synced 2025-04-21 00:13:52 -04:00
70331 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
f5bd489c5f
|
[8.12] [Bug][Investigations] - Fix slow timeline queries (#176838) (#176956)
# Backport This will backport the following commits from `main` to `8.12`: - [[Bug][Investigations] - Fix slow timeline queries (#176838)](https://github.com/elastic/kibana/pull/176838) <!--- Backport version: 9.4.3 --> ### 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-02-14T21:02:20Z","message":"[Bug][Investigations] - Fix slow timeline queries (#176838)\n\n## Summary\r\n\r\n**Version Affected: 8.11.x, 8.12.0, 8.12.1**\r\n\r\n### Background\r\n\r\nThe ID field necessary to track long running timeline search strategy\r\nqueries was no longer being passed to ES search after work in 8.11. This\r\nled to what looked like long running timeline queries, but in reality\r\nwere queries being repeated due to the ID not being tracked. This pr\r\nre-introduces the ID field necessary for long running timeline search\r\nstrategies in security solution\r\n\r\n**Views Affected:**\r\n - Timeline tabs (query, correlation, pinned)\r\n - Explore events tables (hosts, users, network)\r\n - Rule preview table\r\n \r\n\r\nPre-fix:\r\n\r\nObserver the changing ID's for the `timelineSearchStrategy` `eventsAll`\r\nqueries.\r\n\r\n\r\n |
||
|
Kibana Machine
|
e446672754
|
[8.12] [Discover][Alerts] Fix Discover results when alert excludes matches from previous runs (#176690) (#176931)
# Backport This will backport the following commits from `main` to `8.12`: - [[Discover][Alerts] Fix Discover results when alert excludes matches from previous runs (#176690)](https://github.com/elastic/kibana/pull/176690) <!--- 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-02-14T16:44:40Z","message":"[Discover][Alerts] Fix Discover results when alert excludes matches from previous runs (#176690)\n\n- Closes https://github.com/elastic/kibana/issues/148282\r\n\r\n## Summary\r\n\r\nIn case if user creates a rule and enables \"Exclude matches from\r\nprevious runs\", Discover link will now include a time filter to filter\r\nprevious results out.\r\n\r\n<img width=\"500\" alt=\"Screenshot 2024-02-12 at 14 02 18\"\r\nsrc=\" |
||
|
Kibana Machine
|
4884e48e60
|
[8.12] [Security Solution] Fix broken Rule Filters components when content is extremely long and when alias is present (#176590) (#176928)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Fix broken Rule Filters components when content is extremely long and when alias is present (#176590)](https://github.com/elastic/kibana/pull/176590) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Juan Pablo Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2024-02-14T15:13:07Z","message":"[Security Solution] Fix broken Rule Filters components when content is extremely long and when alias is present (#176590)\n\nFixes: https://github.com/elastic/kibana/issues/145076\r\nFixes: https://github.com/elastic/kibana/issues/162543\r\n\r\n## Summary\r\n\r\nThis PR solves two separate issues in the Filters component, used in the\r\nRule Details page.\r\n\r\n1. **when rule filter is extremely long, the component would break the\r\nlayout of the whole page**: fixed by adding a styled wrapper component\r\nto our About, Definition and Schedule section, [that allows wrapping of\r\nextremely long text\r\n`anywhere`](https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap).\r\nThis was precisely the issue that was breaking our layout when the\r\nfilters were extremely long, with the aggravating factor that the\r\nfilters were async loaded, and populated the component after the css was\r\nloaded.\r\n2. **when a rule filter had a name (alias) that should have been\r\ndisplayed as a label instead of the actual filter**. This was like this\r\nbefore 8.8, but was apparently lost during some refactoring. This PR\r\nreintroduces that logic.\r\n\r\n## Screenshots\r\n\r\n### Broken page with long filters\r\n\r\n#### Before\r\n\r\n
Maxim Palenov
|
78cb16c595
|
[8.12] [Security Solution] Fix importing rules referencing preconfigured connectors (#176284) (#176887)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Fix importing rules referencing preconfigured connectors (#176284)](https://github.com/elastic/kibana/pull/176284) <!--- Backport version: 8.9.8 --> ### 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-02-13T15:30:25Z","message":"[Security Solution] Fix importing rules referencing preconfigured connectors (#176284)\n\n**Fixes:** https://github.com/elastic/kibana/issues/157253\r\n\r\n## Summary\r\n\r\nThis PR fixes rules import with `overwrite_action_connectors` set to true when ndjson contains rules with actions referencing preconfigured action connectors.\r\n\r\n## Details\r\n\r\nA user can preconfigure action connectors as described [here](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html). At the same time Elastic Could instances have Elastic-cloud-SMTP connector preconfigured. In particular import doesn't work as expected in Elastic Cloud for rules having actions referencing the preconfigured Elastic-cloud-SMTP connector.\r\n\r\nThis is fixed by filtering out preconfigured connector ids so importing logic only handles custom action connectors.\r\n\r\nOn top of this functional tests have been added to make sure the problem won't come back.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios\r\n- [x] [Ran](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5139) in Flaky test runner for ESS and Serverless and no flakiness has been revealed","sha":"934a06ccf7c599685e04469ff0801e461ee9c2d5","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:medium","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Actions","Team:Detection Rule Management","Feature:Rule Import/Export","v8.13.0","v8.12.2"],"number":176284,"url":"https://github.com/elastic/kibana/pull/176284","mergeCommit":{"message":"[Security Solution] Fix importing rules referencing preconfigured connectors (#176284)\n\n**Fixes:** https://github.com/elastic/kibana/issues/157253\r\n\r\n## Summary\r\n\r\nThis PR fixes rules import with `overwrite_action_connectors` set to true when ndjson contains rules with actions referencing preconfigured action connectors.\r\n\r\n## Details\r\n\r\nA user can preconfigure action connectors as described [here](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html). At the same time Elastic Could instances have Elastic-cloud-SMTP connector preconfigured. In particular import doesn't work as expected in Elastic Cloud for rules having actions referencing the preconfigured Elastic-cloud-SMTP connector.\r\n\r\nThis is fixed by filtering out preconfigured connector ids so importing logic only handles custom action connectors.\r\n\r\nOn top of this functional tests have been added to make sure the problem won't come back.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios\r\n- [x] [Ran](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5139) in Flaky test runner for ESS and Serverless and no flakiness has been revealed","sha":"934a06ccf7c599685e04469ff0801e461ee9c2d5"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176284","number":176284,"mergeCommit":{"message":"[Security Solution] Fix importing rules referencing preconfigured connectors (#176284)\n\n**Fixes:** https://github.com/elastic/kibana/issues/157253\r\n\r\n## Summary\r\n\r\nThis PR fixes rules import with `overwrite_action_connectors` set to true when ndjson contains rules with actions referencing preconfigured action connectors.\r\n\r\n## Details\r\n\r\nA user can preconfigure action connectors as described [here](https://www.elastic.co/guide/en/kibana/current/pre-configured-connectors.html). At the same time Elastic Could instances have Elastic-cloud-SMTP connector preconfigured. In particular import doesn't work as expected in Elastic Cloud for rules having actions referencing the preconfigured Elastic-cloud-SMTP connector.\r\n\r\nThis is fixed by filtering out preconfigured connector ids so importing logic only handles custom action connectors.\r\n\r\nOn top of this functional tests have been added to make sure the problem won't come back.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios\r\n- [x] [Ran](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5139) in Flaky test runner for ESS and Serverless and no flakiness has been revealed","sha":"934a06ccf7c599685e04469ff0801e461ee9c2d5"}},{"branch":"8.12","label":"v8.12.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Maxim Palenov
|
fd2f4ee908
|
[8.12] [Security Solution] Fix losing data upon prebuilt rule upgrade to a new version in which the rule's type is different (#176421) (#176811)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Fix losing data upon prebuilt rule upgrade to a new version in which the rule's type is different (#176421)](https://github.com/elastic/kibana/pull/176421) <!--- Backport version: 8.9.8 --> ### 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-02-12T13:09:23Z","message":"[Security Solution] Fix losing data upon prebuilt rule upgrade to a new version in which the rule's type is different (#176421)\n\n**Fixes:** https://github.com/elastic/kibana/issues/169480\r\n\r\n## Summary\r\n\r\nThis PR fixes losing the following rule data upon prebuilt rule upgrade to a new version in which the rule's type is different\r\n\r\n- Saved Object id\r\n- exceptions list (default and shared)\r\n- Timeline id\r\n- Timeline title\r\n\r\n## Details\r\n\r\nThe problem occurs when user upgrades a prebuilt rule to a newer version which has a different rule type.\r\n\r\nChecking the code it's not so hard to find [`upgradeRule()`](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/rule_objects/upgrade_prebuilt_rules.ts#L49) function which performs prebuilt rule upgrade. It has the following comment\r\n\r\n> If we're trying to change the type of a prepackaged rule, we need to delete the old one and replace it with the new rule, keeping the enabled setting, actions, throttle, id, and exception lists from the old rule.\r\n\r\nLooking below in the code it's clear that only enabled state and actions get restored upon rule upgrade. Missing to restore `exceptions lists` leads to disappearing exceptions upon rule upgrade.\r\n\r\nOn top of this `execution results` and `execution events` also get lost due to missing to restore saved object `id`. Execution log isn't gone anywhere but can't be bound to a new id. Direct links to rule details page won't work neither after upgrade.\r\n\r\nThis PR fixes the problem by restoring rule bound data after upgrade.\r\n\r\nFTR tests were restructured to accommodate extra tests to cover this bug fix. \r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"ffdcc34d0d4f05aad8ad979775e8b0f503af313d","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:high","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","v8.13.0","v8.12.2"],"number":176421,"url":"https://github.com/elastic/kibana/pull/176421","mergeCommit":{"message":"[Security Solution] Fix losing data upon prebuilt rule upgrade to a new version in which the rule's type is different (#176421)\n\n**Fixes:** https://github.com/elastic/kibana/issues/169480\r\n\r\n## Summary\r\n\r\nThis PR fixes losing the following rule data upon prebuilt rule upgrade to a new version in which the rule's type is different\r\n\r\n- Saved Object id\r\n- exceptions list (default and shared)\r\n- Timeline id\r\n- Timeline title\r\n\r\n## Details\r\n\r\nThe problem occurs when user upgrades a prebuilt rule to a newer version which has a different rule type.\r\n\r\nChecking the code it's not so hard to find [`upgradeRule()`](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/rule_objects/upgrade_prebuilt_rules.ts#L49) function which performs prebuilt rule upgrade. It has the following comment\r\n\r\n> If we're trying to change the type of a prepackaged rule, we need to delete the old one and replace it with the new rule, keeping the enabled setting, actions, throttle, id, and exception lists from the old rule.\r\n\r\nLooking below in the code it's clear that only enabled state and actions get restored upon rule upgrade. Missing to restore `exceptions lists` leads to disappearing exceptions upon rule upgrade.\r\n\r\nOn top of this `execution results` and `execution events` also get lost due to missing to restore saved object `id`. Execution log isn't gone anywhere but can't be bound to a new id. Direct links to rule details page won't work neither after upgrade.\r\n\r\nThis PR fixes the problem by restoring rule bound data after upgrade.\r\n\r\nFTR tests were restructured to accommodate extra tests to cover this bug fix. \r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"ffdcc34d0d4f05aad8ad979775e8b0f503af313d"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176421","number":176421,"mergeCommit":{"message":"[Security Solution] Fix losing data upon prebuilt rule upgrade to a new version in which the rule's type is different (#176421)\n\n**Fixes:** https://github.com/elastic/kibana/issues/169480\r\n\r\n## Summary\r\n\r\nThis PR fixes losing the following rule data upon prebuilt rule upgrade to a new version in which the rule's type is different\r\n\r\n- Saved Object id\r\n- exceptions list (default and shared)\r\n- Timeline id\r\n- Timeline title\r\n\r\n## Details\r\n\r\nThe problem occurs when user upgrades a prebuilt rule to a newer version which has a different rule type.\r\n\r\nChecking the code it's not so hard to find [`upgradeRule()`](https://github.com/elastic/kibana/blob/main/x-pack/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/rule_objects/upgrade_prebuilt_rules.ts#L49) function which performs prebuilt rule upgrade. It has the following comment\r\n\r\n> If we're trying to change the type of a prepackaged rule, we need to delete the old one and replace it with the new rule, keeping the enabled setting, actions, throttle, id, and exception lists from the old rule.\r\n\r\nLooking below in the code it's clear that only enabled state and actions get restored upon rule upgrade. Missing to restore `exceptions lists` leads to disappearing exceptions upon rule upgrade.\r\n\r\nOn top of this `execution results` and `execution events` also get lost due to missing to restore saved object `id`. Execution log isn't gone anywhere but can't be bound to a new id. Direct links to rule details page won't work neither after upgrade.\r\n\r\nThis PR fixes the problem by restoring rule bound data after upgrade.\r\n\r\nFTR tests were restructured to accommodate extra tests to cover this bug fix. \r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"ffdcc34d0d4f05aad8ad979775e8b0f503af313d"}},{"branch":"8.12","label":"v8.12.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
625fb5df67
|
[8.12] [Search] Fix multiple radio buttons conflicting in connector config (#176795) (#176809)
# Backport This will backport the following commits from `main` to `8.12`: - [[Search] Fix multiple radio buttons conflicting in connector config (#176795)](https://github.com/elastic/kibana/pull/176795) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-13T10:57:32Z","message":"[Search] Fix multiple radio buttons conflicting in connector config (#176795)\n\n## Summary\r\n\r\nThis fixes an issue where multiple radio groups in a single connector\r\nconfig would conflict leading to UI glitches.","sha":"8477b6b8bc0f9a2b32e6650a8064d7b3cd461e9b","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.13.0","v8.12.2","v8.14.0"],"title":"[Search] Fix multiple radio buttons conflicting in connector config","number":176795,"url":"https://github.com/elastic/kibana/pull/176795","mergeCommit":{"message":"[Search] Fix multiple radio buttons conflicting in connector config (#176795)\n\n## Summary\r\n\r\nThis fixes an issue where multiple radio groups in a single connector\r\nconfig would conflict leading to UI glitches.","sha":"8477b6b8bc0f9a2b32e6650a8064d7b3cd461e9b"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","8.14"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176795","number":176795,"mergeCommit":{"message":"[Search] Fix multiple radio buttons conflicting in connector config (#176795)\n\n## Summary\r\n\r\nThis fixes an issue where multiple radio groups in a single connector\r\nconfig would conflict leading to UI glitches.","sha":"8477b6b8bc0f9a2b32e6650a8064d7b3cd461e9b"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
111062883f
|
[8.12] [Fleet] Fix wrong policy_id in dev tools flyout request (#176729) (#176800)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Fix wrong policy_id in dev tools flyout request (#176729)](https://github.com/elastic/kibana/pull/176729) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-13T10:02:20Z","message":"[Fleet] Fix wrong policy_id in dev tools flyout request (#176729)\n\nFixes https://github.com/elastic/kibana/issues/172798\r\n\r\n## Summary\r\nSmall bug fix: when adding a new integration, the `policy_id` in dev\r\ntools flyout request was not correct\r\n\r\nSteps to reproduce:\r\n\r\n- Add one agent policy to the stack\r\n- Go to any integration and navigate to `add integration` page\r\n- Switch to `Existing hosts` and select an existing policy. \r\n- Open `Preview API request`. The policy id in the preview should be the\r\none from the selected policy\r\n- Switch back to `New hosts`\r\n- Open `Preview API request`. The policy id should be\r\n`<agent_policy_id>` again (not the one from the previously selected\r\npolicy)\r\n\r\n
Tomasz Ciecierski
|
81529e2870
|
[EDR Workflows] Add technical preview badge to S1 flyout (#176581) | ||
|
Kibana Machine
|
b3354bcd11
|
[8.12] [Discover] Unskip update data view test (#176508) (#176740)
# Backport This will backport the following commits from `main` to `8.12`: - [[Discover] Unskip update data view test (#176508)](https://github.com/elastic/kibana/pull/176508) <!--- 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-02-12T18:21:00Z","message":"[Discover] Unskip update data view test (#176508)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n95x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5099\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"0f31c0bff36a375f47aefc41d604551e56fac181","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","v8.13.0"],"title":"[Discover] Unskip update data view test","number":176508,"url":"https://github.com/elastic/kibana/pull/176508","mergeCommit":{"message":"[Discover] Unskip update data view test (#176508)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n95x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5099\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"0f31c0bff36a375f47aefc41d604551e56fac181"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176508","number":176508,"mergeCommit":{"message":"[Discover] Unskip update data view test (#176508)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n95x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5099\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"0f31c0bff36a375f47aefc41d604551e56fac181"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
bea3819ebe
|
[8.12] Fix PIT issue (#176699) (#176747)
# Backport This will backport the following commits from `main` to `8.12`: - [Fix PIT issue (#176699)](https://github.com/elastic/kibana/pull/176699) <!--- 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-02-12T19:09:40Z","message":"Fix PIT issue (#176699)","sha":"e17f2f1b766fc727b9d972a7808b01a10a478782","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Telemetry","release_note:skip","Team: SecuritySolution","backport:prev-minor","v8.13.0","v8.12.2"],"title":"Fix PIT issue","number":176699,"url":"https://github.com/elastic/kibana/pull/176699","mergeCommit":{"message":"Fix PIT issue (#176699)","sha":"e17f2f1b766fc727b9d972a7808b01a10a478782"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176699","number":176699,"mergeCommit":{"message":"Fix PIT issue (#176699)","sha":"e17f2f1b766fc727b9d972a7808b01a10a478782"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sebastián Zaffarano <sebastian.zaffarano@elastic.co> |
||
Aleh Zasypkin
|
c7faa67815
|
[8.12] chore: bump socks transitive dependency from 2.7.1 to 2.7.3 (#176693) (#176721)
# Backport This will backport the following commits from `main` to `8.12`: - [chore: bump `socks` transitive dependency from `2.7.1` to `2.7.3` (#176693)](https://github.com/elastic/kibana/pull/176693) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2024-02-12T15:24:31Z","message":"chore: bump `socks` transitive dependency from `2.7.1` to `2.7.3` (#176693)\n\n## Summary\r\n\r\nBump `socks` transitive dependency from `2.7.1` to `2.7.3` to reduce a\r\nnumber of packages that depend on outdated `ip` package.","sha":"f69c7496c49f1f117ed732280e9bf2e281a9ba0e","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","backport:all-open","v8.13.0"],"number":176693,"url":"https://github.com/elastic/kibana/pull/176693","mergeCommit":{"message":"chore: bump `socks` transitive dependency from `2.7.1` to `2.7.3` (#176693)\n\n## Summary\r\n\r\nBump `socks` transitive dependency from `2.7.1` to `2.7.3` to reduce a\r\nnumber of packages that depend on outdated `ip` package.","sha":"f69c7496c49f1f117ed732280e9bf2e281a9ba0e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176693","number":176693,"mergeCommit":{"message":"chore: bump `socks` transitive dependency from `2.7.1` to `2.7.3` (#176693)\n\n## Summary\r\n\r\nBump `socks` transitive dependency from `2.7.1` to `2.7.3` to reduce a\r\nnumber of packages that depend on outdated `ip` package.","sha":"f69c7496c49f1f117ed732280e9bf2e281a9ba0e"}}]}] BACKPORT--> |
||
Dzmitry Lemechko
|
109659785e
|
[8.12] [chore] update chromedriver to 121 (#176190) (#176232)
# Backport This will backport the following commits from `main` to `8.12`: - [[chore] update chromedriver to 121 (#176190)](https://github.com/elastic/kibana/pull/176190) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2024-02-05T09:26:31Z","message":"[chore] update chromedriver to 121 (#176190)\n\nBumping chromedriver to the latest version","sha":"ff3c1af8ee5c2cc16c7a4452557d448f88f05c0b","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","v8.12.1","v8.13.0","v7.17.18"],"number":176190,"url":"https://github.com/elastic/kibana/pull/176190","mergeCommit":{"message":"[chore] update chromedriver to 121 (#176190)\n\nBumping chromedriver to the latest version","sha":"ff3c1af8ee5c2cc16c7a4452557d448f88f05c0b"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","7.17"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176190","number":176190,"mergeCommit":{"message":"[chore] update chromedriver to 121 (#176190)\n\nBumping chromedriver to the latest version","sha":"ff3c1af8ee5c2cc16c7a4452557d448f88f05c0b"}},{"branch":"7.17","label":"v7.17.18","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
867e4b54b5
|
[8.12] [Fleet] Add documentation about transforms/authorize endpoint in openapi (#176610) (#176688)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Add documentation about transforms/authorize endpoint in openapi (#176610)](https://github.com/elastic/kibana/pull/176610) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-12T11:56:06Z","message":"[Fleet] Add documentation about transforms/authorize endpoint in openapi (#176610)\n\n## Summary\r\n\r\nPR to address missing openapi docs about thie following endpoint - it\r\nwas added a while ago but we forgot to update the docs.\r\n\r\n```\r\napi/fleet/epm/packages/{pkgName}/{pkgVersion}/transforms/authorize\r\n{\r\n \"transforms\": [\r\n {\r\n \"transformId\": <transform_id>\r\n }\r\n ]\r\n}\r\n```\r\n\r\n\r\n### Checklist\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87de70fd581fa5a0916d43854a2366eb85e3460a","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.13.0"],"title":"[Fleet] Add documentation about transforms/authorize endpoint in openapi","number":176610,"url":"https://github.com/elastic/kibana/pull/176610","mergeCommit":{"message":"[Fleet] Add documentation about transforms/authorize endpoint in openapi (#176610)\n\n## Summary\r\n\r\nPR to address missing openapi docs about thie following endpoint - it\r\nwas added a while ago but we forgot to update the docs.\r\n\r\n```\r\napi/fleet/epm/packages/{pkgName}/{pkgVersion}/transforms/authorize\r\n{\r\n \"transforms\": [\r\n {\r\n \"transformId\": <transform_id>\r\n }\r\n ]\r\n}\r\n```\r\n\r\n\r\n### Checklist\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87de70fd581fa5a0916d43854a2366eb85e3460a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176610","number":176610,"mergeCommit":{"message":"[Fleet] Add documentation about transforms/authorize endpoint in openapi (#176610)\n\n## Summary\r\n\r\nPR to address missing openapi docs about thie following endpoint - it\r\nwas added a while ago but we forgot to update the docs.\r\n\r\n```\r\napi/fleet/epm/packages/{pkgName}/{pkgVersion}/transforms/authorize\r\n{\r\n \"transforms\": [\r\n {\r\n \"transformId\": <transform_id>\r\n }\r\n ]\r\n}\r\n```\r\n\r\n\r\n### Checklist\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\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"87de70fd581fa5a0916d43854a2366eb85e3460a"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com> |
||
|
Kibana Machine
|
bf9b01ddc4
|
[8.12] [EDR Workflows] [Osquery] Change query ID regex pattern (#176507) (#176677)
# Backport This will backport the following commits from `main` to `8.12`: - [[EDR Workflows] [Osquery] Change query ID regex pattern (#176507)](https://github.com/elastic/kibana/pull/176507) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tomasz Ciecierski","email":"tomasz.ciecierski@elastic.co"},"sourceCommit":{"committedDate":"2024-02-12T10:56:35Z","message":"[EDR Workflows] [Osquery] Change query ID regex pattern (#176507)","sha":"45f554d734f3ee973c3b20a9bbdf24b7bf602f6a","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Defend Workflows","Feature:Osquery","v8.13.0","v8.12.2"],"title":"[EDR Workflows] [Osquery] Change query ID regex pattern","number":176507,"url":"https://github.com/elastic/kibana/pull/176507","mergeCommit":{"message":"[EDR Workflows] [Osquery] Change query ID regex pattern (#176507)","sha":"45f554d734f3ee973c3b20a9bbdf24b7bf602f6a"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176507","number":176507,"mergeCommit":{"message":"[EDR Workflows] [Osquery] Change query ID regex pattern (#176507)","sha":"45f554d734f3ee973c3b20a9bbdf24b7bf602f6a"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tomasz Ciecierski <tomasz.ciecierski@elastic.co> |
||
Ash
|
3bc819083b
|
[8.12] [SentinelOne] Fix Agent status on Timeline Alert details (#176210) (#176663)
# Backport This will backport the following commits from `main` to `8.12`: - [[SentinelOne] Fix Agent status on Timeline Alert details (#176210)](https://github.com/elastic/kibana/pull/176210) <!--- Backport version: 8.9.8 --> ### 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-02-10T12:28:32Z","message":"[SentinelOne] Fix Agent status on Timeline Alert details (#176210)\n\n## Summary\r\n \r\nFixes https://github.com/elastic/kibana/issues/174235 \r\n\r\n<img width=\"1906\" alt=\"Zrzut ekranu 2024-02-5 o 11 54 15\"\r\nsrc=\" |
||
|
Kibana Machine
|
916aaf6c31
|
[8.12] [Security Solution] Disable installation button for users with Security:Read privileges (#176598) (#176616)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Disable installation button for users with Security:Read privileges (#176598)](https://github.com/elastic/kibana/pull/176598) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Juan Pablo Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2024-02-09T16:47:13Z","message":"[Security Solution] Disable installation button for users with Security:Read privileges (#176598)\n\nFixes: https://github.com/elastic/kibana/issues/161543\r\n\r\n## Summary\r\n\r\nOriginal bug issue reported an infinite loading state in the **Add\r\nElastic rules** page when user doesn't have write privileges, i.e. has\r\n`Security: Read`.\r\n\r\nHowever, that seems to have been fixed already, as the list of rules to\r\ninstall is shown, but no individual \"Install button\" for each row is\r\nshowed. **This is expected behaviour**.\r\n\r\n\r\n
Alex Szabo
|
b6e9d62ecd
|
[Ops] Pin axios@1.6.3 in 8.12 (#176601)
## Summary Backports #174794 There is a known issue (https://github.com/axios/axios/issues/6179) with `axios@>=1.6.4` and `follow-redirects@>=1.15.4` which results in auth errors on our side. This PR backports the pinning (by setting a `resolutions` entry) axios / follow-redirects. |
||
Dario Gieselaar
|
eebc33007e
|
[8.12] [Obs AI Assistant] Improve recall speed (#176428) (#176561)
# Backport This will backport the following commits from `main` to `8.12`: - [[Obs AI Assistant] Improve recall speed (#176428)](https://github.com/elastic/kibana/pull/176428) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2024-02-08T16:27:24Z","message":"[Obs AI Assistant] Improve recall speed (#176428)\n\nImproves recall speed by outputting as CSV with zero-indexed document\r\n\"ids\". Previously, it was a JSON object, with the real document ids.\r\nThis causes the LLM to \"think\" for longer, for whatever reason. I didn't\r\nactually see a difference in completion speed, but emitting the first\r\nvalue took significantly less time when using the CSV output. I also\r\ntried sending a single document per request using the old format, and\r\nwhile that certainly improves things, the slowest request becomes the\r\nbottleneck. These are results from about 10 tries per strategy (I'd love\r\nto see others reproduce at least the `batch` vs `csv` strategy results):\r\n\r\n`batch`: 24.7s\r\n`chunk`: 10s\r\n`csv`: 4.9s\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc58a0d3a71dd946fb24a75050930030c002d2a4","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v8.13.0","v8.12.2"],"number":176428,"url":"https://github.com/elastic/kibana/pull/176428","mergeCommit":{"message":"[Obs AI Assistant] Improve recall speed (#176428)\n\nImproves recall speed by outputting as CSV with zero-indexed document\r\n\"ids\". Previously, it was a JSON object, with the real document ids.\r\nThis causes the LLM to \"think\" for longer, for whatever reason. I didn't\r\nactually see a difference in completion speed, but emitting the first\r\nvalue took significantly less time when using the CSV output. I also\r\ntried sending a single document per request using the old format, and\r\nwhile that certainly improves things, the slowest request becomes the\r\nbottleneck. These are results from about 10 tries per strategy (I'd love\r\nto see others reproduce at least the `batch` vs `csv` strategy results):\r\n\r\n`batch`: 24.7s\r\n`chunk`: 10s\r\n`csv`: 4.9s\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc58a0d3a71dd946fb24a75050930030c002d2a4"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176428","number":176428,"mergeCommit":{"message":"[Obs AI Assistant] Improve recall speed (#176428)\n\nImproves recall speed by outputting as CSV with zero-indexed document\r\n\"ids\". Previously, it was a JSON object, with the real document ids.\r\nThis causes the LLM to \"think\" for longer, for whatever reason. I didn't\r\nactually see a difference in completion speed, but emitting the first\r\nvalue took significantly less time when using the CSV output. I also\r\ntried sending a single document per request using the old format, and\r\nwhile that certainly improves things, the slowest request becomes the\r\nbottleneck. These are results from about 10 tries per strategy (I'd love\r\nto see others reproduce at least the `batch` vs `csv` strategy results):\r\n\r\n`batch`: 24.7s\r\n`chunk`: 10s\r\n`csv`: 4.9s\r\n\r\n---------\r\n\r\nCo-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc58a0d3a71dd946fb24a75050930030c002d2a4"}},{"branch":"8.12","label":"v8.12.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
1ba3eee76b
|
[8.12] [FTR] Fix URL checks in navigateToApp (#176546) (#176563)
# Backport This will backport the following commits from `main` to `8.12`: - [[FTR] Fix URL checks in navigateToApp (#176546)](https://github.com/elastic/kibana/pull/176546) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2024-02-09T08:15:18Z","message":"[FTR] Fix URL checks in navigateToApp (#176546)\n\n## Summary\r\n\r\nThis PR fixes the URL check for successful navigation in the `common`\r\nPageObject `navigateToApp` method.","sha":"736af7b0e07512b7797e3759d076dbcebbb55b64","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.13.0","v8.12.2"],"title":"[FTR] Fix URL checks in navigateToApp","number":176546,"url":"https://github.com/elastic/kibana/pull/176546","mergeCommit":{"message":"[FTR] Fix URL checks in navigateToApp (#176546)\n\n## Summary\r\n\r\nThis PR fixes the URL check for successful navigation in the `common`\r\nPageObject `navigateToApp` method.","sha":"736af7b0e07512b7797e3759d076dbcebbb55b64"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176546","number":176546,"mergeCommit":{"message":"[FTR] Fix URL checks in navigateToApp (#176546)\n\n## Summary\r\n\r\nThis PR fixes the URL check for successful navigation in the `common`\r\nPageObject `navigateToApp` method.","sha":"736af7b0e07512b7797e3759d076dbcebbb55b64"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co> |
||
Paul Tavares
|
20f8b18501
|
[8.12] [Security Solution][Endpoint] Fix Manifest Manger so that it works with large (>10k) (#174411) (#176531)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution][Endpoint] Fix Manifest Manger so that it works with large (>10k) (#174411)](https://github.com/elastic/kibana/pull/174411) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-06T21:48:12Z","message":"[Security Solution][Endpoint] Fix Manifest Manger so that it works with large (>10k) (#174411)\n\n## Summary\r\n\r\n### Fleet Changes:\r\n\r\n- Two new utilities that return `AsyncIterator`'s:\r\n - one for working with ElasticSearch `.search()` method\r\n - one for working with SavedObjects `.find()` method\r\n- NOTE: although the `SavedObjects` client already supports getting back\r\nan `find` interface that returns an `AysncIterable`, I was not\r\nconvenient to use in our use cases where we are returning the data from\r\nthe SO back to an external consumer (services exposed by Fleet). We need\r\nto be able to first process the data out of the SO before returning it\r\nto the consumer, thus having this utility facilitates that.\r\n- both handle looping through ALL data in a given query (even if >10k)\r\n- new `fetchAllArtifacts()` method in `ArtifactsClient`: Returns an\r\n`AsyncIterator` enabling one to loop through all artifacts (even if\r\n>10k)\r\n- new `fetchAllItemIds()` method in `PackagePolicyService`: return an\r\n`AsyncIterator` enabling one to loop through all item IDs (even if >10k)\r\n- new `fetchAllItems()` method in `PackagePolicyService`: returns an\r\n`AsyncIterator` enabling one to loop through all package policies (even\r\nif >10k)\r\n\r\n\r\n### Endpoint Changes:\r\n\r\n- Retrieval of existing artifacts as well as list of all policies and\r\npolicy IDs now use new methods introduced into fleet services (above)\r\n- Added new config property -\r\n`xpack.securitySolution.packagerTaskTimeout` - to enable customer to\r\nadjust the timeout value for how long the artifact packager task can\r\nrun. Default has been set to `20m`\r\n- Efficiencies around batch processing of updates to Policies and\r\nartifact creation\r\n- improved logging\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9150f9fa2f110bcd54f90f21554bad5e6d92fd0f","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","Team:Defend Workflows","ci:cloud-deploy","v8.13.0","v8.12.2"],"number":174411,"url":"https://github.com/elastic/kibana/pull/174411","mergeCommit":{"message":"[Security Solution][Endpoint] Fix Manifest Manger so that it works with large (>10k) (#174411)\n\n## Summary\r\n\r\n### Fleet Changes:\r\n\r\n- Two new utilities that return `AsyncIterator`'s:\r\n - one for working with ElasticSearch `.search()` method\r\n - one for working with SavedObjects `.find()` method\r\n- NOTE: although the `SavedObjects` client already supports getting back\r\nan `find` interface that returns an `AysncIterable`, I was not\r\nconvenient to use in our use cases where we are returning the data from\r\nthe SO back to an external consumer (services exposed by Fleet). We need\r\nto be able to first process the data out of the SO before returning it\r\nto the consumer, thus having this utility facilitates that.\r\n- both handle looping through ALL data in a given query (even if >10k)\r\n- new `fetchAllArtifacts()` method in `ArtifactsClient`: Returns an\r\n`AsyncIterator` enabling one to loop through all artifacts (even if\r\n>10k)\r\n- new `fetchAllItemIds()` method in `PackagePolicyService`: return an\r\n`AsyncIterator` enabling one to loop through all item IDs (even if >10k)\r\n- new `fetchAllItems()` method in `PackagePolicyService`: returns an\r\n`AsyncIterator` enabling one to loop through all package policies (even\r\nif >10k)\r\n\r\n\r\n### Endpoint Changes:\r\n\r\n- Retrieval of existing artifacts as well as list of all policies and\r\npolicy IDs now use new methods introduced into fleet services (above)\r\n- Added new config property -\r\n`xpack.securitySolution.packagerTaskTimeout` - to enable customer to\r\nadjust the timeout value for how long the artifact packager task can\r\nrun. Default has been set to `20m`\r\n- Efficiencies around batch processing of updates to Policies and\r\nartifact creation\r\n- improved logging\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9150f9fa2f110bcd54f90f21554bad5e6d92fd0f"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/174411","number":174411,"mergeCommit":{"message":"[Security Solution][Endpoint] Fix Manifest Manger so that it works with large (>10k) (#174411)\n\n## Summary\r\n\r\n### Fleet Changes:\r\n\r\n- Two new utilities that return `AsyncIterator`'s:\r\n - one for working with ElasticSearch `.search()` method\r\n - one for working with SavedObjects `.find()` method\r\n- NOTE: although the `SavedObjects` client already supports getting back\r\nan `find` interface that returns an `AysncIterable`, I was not\r\nconvenient to use in our use cases where we are returning the data from\r\nthe SO back to an external consumer (services exposed by Fleet). We need\r\nto be able to first process the data out of the SO before returning it\r\nto the consumer, thus having this utility facilitates that.\r\n- both handle looping through ALL data in a given query (even if >10k)\r\n- new `fetchAllArtifacts()` method in `ArtifactsClient`: Returns an\r\n`AsyncIterator` enabling one to loop through all artifacts (even if\r\n>10k)\r\n- new `fetchAllItemIds()` method in `PackagePolicyService`: return an\r\n`AsyncIterator` enabling one to loop through all item IDs (even if >10k)\r\n- new `fetchAllItems()` method in `PackagePolicyService`: returns an\r\n`AsyncIterator` enabling one to loop through all package policies (even\r\nif >10k)\r\n\r\n\r\n### Endpoint Changes:\r\n\r\n- Retrieval of existing artifacts as well as list of all policies and\r\npolicy IDs now use new methods introduced into fleet services (above)\r\n- Added new config property -\r\n`xpack.securitySolution.packagerTaskTimeout` - to enable customer to\r\nadjust the timeout value for how long the artifact packager task can\r\nrun. Default has been set to `20m`\r\n- Efficiencies around batch processing of updates to Policies and\r\nartifact creation\r\n- improved logging\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9150f9fa2f110bcd54f90f21554bad5e6d92fd0f"}},{"branch":"8.12","label":"v8.12.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
e49980a4f7
|
[8.12] [ML][Field Statistics] Fix Zero for items in Top Values # (#176328) (#176441)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML][Field Statistics] Fix Zero for items in Top Values # (#176328)](https://github.com/elastic/kibana/pull/176328) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-07T20:22:01Z","message":"[ML][Field Statistics] Fix Zero for items in Top Values # (#176328)\n\n## Summary\r\n\r\nThis PR fixes https://github.com/elastic/kibana/issues/174084.\r\nPreviously, we calculated the doc count based on the sampled count from\r\nthe random sampler in order to accurately estimate the right percentage\r\nof docs sampled in the Field Stats. However, this should only apply to\r\nwhen random sampler was actually used (where sampler probability < 1).\r\nThis PR fixes that.\r\n\r\nBefore\r\n\r\n (#176517)
# Backport This will backport the following commits from `main` to `8.12`: - [Update docs-preview link (#176468)](https://github.com/elastic/kibana/pull/176468) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nassim Kammah","email":"nkammah@gmail.com"},"sourceCommit":{"committedDate":"2024-02-08T07:42:35Z","message":"Update docs-preview link (#176468)\n\n## Summary\r\n\r\nFollowing the migration from Jenkins to Buildkite, docs previews are now\r\navailable at <repo>_bk_<PR>.\r\nMore context in https://github.com/elastic/docs/pull/2898\r\n\r\n### Checklist\r\n\r\n\r\n### Risk Matrix\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":"096bf5515a34f1158a3bd1c0a259388b337f1f68","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.13.0"],"title":"Update docs-preview link","number":176468,"url":"https://github.com/elastic/kibana/pull/176468","mergeCommit":{"message":"Update docs-preview link (#176468)\n\n## Summary\r\n\r\nFollowing the migration from Jenkins to Buildkite, docs previews are now\r\navailable at <repo>_bk_<PR>.\r\nMore context in https://github.com/elastic/docs/pull/2898\r\n\r\n### Checklist\r\n\r\n\r\n### Risk Matrix\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":"096bf5515a34f1158a3bd1c0a259388b337f1f68"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176468","number":176468,"mergeCommit":{"message":"Update docs-preview link (#176468)\n\n## Summary\r\n\r\nFollowing the migration from Jenkins to Buildkite, docs previews are now\r\navailable at <repo>_bk_<PR>.\r\nMore context in https://github.com/elastic/docs/pull/2898\r\n\r\n### Checklist\r\n\r\n\r\n### Risk Matrix\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":"096bf5515a34f1158a3bd1c0a259388b337f1f68"}}]}] BACKPORT--> Co-authored-by: Nassim Kammah <nkammah@gmail.com> |
||
|
Kibana Machine
|
014ef995ae
|
[8.12] [Fleet] Allow back previously disabled bulk actions (#176485) (#176512)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Allow back previously disabled bulk actions (#176485)](https://github.com/elastic/kibana/pull/176485) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-08T14:59:23Z","message":"[Fleet] Allow back previously disabled bulk actions (#176485)\n\nPatch for https://github.com/elastic/kibana/issues/171914\r\n\r\n## Summary\r\nIn https://github.com/elastic/kibana/pull/175318 I had disabled the bulk\r\nactions when the count was incorrect (negative). This was not a good\r\nidea, since some of those actions could still be applied (like\r\nunenrolling) even if the shown count is not correct. Here I'm removing\r\nthat check.\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b62011026850bf968a90c403cae11c453c4e9130","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.13.0"],"title":"[Fleet] Allow back previously disabled bulk actions","number":176485,"url":"https://github.com/elastic/kibana/pull/176485","mergeCommit":{"message":"[Fleet] Allow back previously disabled bulk actions (#176485)\n\nPatch for https://github.com/elastic/kibana/issues/171914\r\n\r\n## Summary\r\nIn https://github.com/elastic/kibana/pull/175318 I had disabled the bulk\r\nactions when the count was incorrect (negative). This was not a good\r\nidea, since some of those actions could still be applied (like\r\nunenrolling) even if the shown count is not correct. Here I'm removing\r\nthat check.\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b62011026850bf968a90c403cae11c453c4e9130"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176485","number":176485,"mergeCommit":{"message":"[Fleet] Allow back previously disabled bulk actions (#176485)\n\nPatch for https://github.com/elastic/kibana/issues/171914\r\n\r\n## Summary\r\nIn https://github.com/elastic/kibana/pull/175318 I had disabled the bulk\r\nactions when the count was incorrect (negative). This was not a good\r\nidea, since some of those actions could still be applied (like\r\nunenrolling) even if the shown count is not correct. Here I'm removing\r\nthat check.\r\n\r\n\r\n\r\n### Checklist\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"b62011026850bf968a90c403cae11c453c4e9130"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <criamico@users.noreply.github.com> |
||
Elastic Machine
|
9167e3cc7e
|
[8.12] Sync bundled packages with Package Storage (#176509)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/337 |
||
|
Kibana Machine
|
c5a102b02b
|
[8.12] [Security Solution] Improve logging for FTR test `retry` function (#176316) (#176497)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Improve logging for FTR test `retry` function (#176316)](https://github.com/elastic/kibana/pull/176316) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Juan Pablo Djeredjian","email":"jpdjeredjian@gmail.com"},"sourceCommit":{"committedDate":"2024-02-08T12:35:54Z","message":"[Security Solution] Improve logging for FTR test `retry` function (#176316)\n\n## Summary\r\n\r\n**Fixes:** \r\n- https://github.com/elastic/kibana/issues/175481\r\n- https://github.com/elastic/kibana/issues/175250\r\n\r\n\r\n### Description\r\n\r\nImproves logging for the `retry` FTR integration testing utility that is\r\nused to wrap helpers that make endpoint calls or direct Elasticsearch\r\noperations.\r\n\r\nThe previous logging would only explain that the maximum amount of\r\nretries had been reached, with the actual error caused in the test being\r\nlost, which proved hard to debug.\r\n\r\nThese changes catches the error and log it, allowing us to understand\r\nwhy a retried test failed.\r\n\r\nError now reported as:\r\n\r\n```\r\n[00:00:19] │ERROR Retrying installPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal Server Error\", got 200 \"OK\"\r\n[00:00:19] │ debg --- retry.tryForTime failed again with the same message...\r\n[00:00:19] │ERROR Reached maximum number of retries for test: 2/2\r\n[00:00:19] └- ✖ fail: Rules Management - Prebuilt Rules - Update Prebuilt Rules Package @ess @serverless @skipInQA update_prebuilt_rules_package should allow user to install prebuilt rules from scratch, then install new rules and upgrade existing rules from the new package\r\n[00:00:19] │ Error: \"Reached maximum number of retries for test: 2/2\"\r\n[00:00:19] │ at block (retry.ts:72:16)\r\n[00:00:19] │ at runAttempt (retry_for_success.ts:29:21)\r\n[00:00:19] │ at retryForSuccess (retry_for_success.ts:79:27)\r\n[00:00:19] │ at RetryService.tryForTime (retry.ts:23:12)\r\n[00:00:19] │ at retry (retry.ts:62:20)\r\n[00:00:19] │ at installPrebuiltRulesPackageByVersion (install_fleet_package_by_url.ts:77:25)\r\n[00:00:19] │ at Context.<anonymous> (update_prebuilt_rules_package.ts:106:46)\r\n[00:00:19] │ at Object.apply (wrap_function.js:73:16)\r\n```\r\nMain error is still `\"Reached maximum number of retries for test: 2/2\"`,\r\nbut now additional logging of exactly **what failed in the test** is\r\nerror-logged as seen above: `ERROR Retrying\r\ninstallPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal\r\nServer Error\", got 200 \"OK\"`\r\n\r\n**Flaky test run:** \r\n- Shared 50 and 50:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5068\r\n- Ess 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5091\r\n- Serverless 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5092\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":"479a022bd3a8ae79ca9af1eb12a90a26cb53efdf","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","v8.13.0","v8.12.2"],"title":"[Security Solution] Improve logging for FTR test `retry` function","number":176316,"url":"https://github.com/elastic/kibana/pull/176316","mergeCommit":{"message":"[Security Solution] Improve logging for FTR test `retry` function (#176316)\n\n## Summary\r\n\r\n**Fixes:** \r\n- https://github.com/elastic/kibana/issues/175481\r\n- https://github.com/elastic/kibana/issues/175250\r\n\r\n\r\n### Description\r\n\r\nImproves logging for the `retry` FTR integration testing utility that is\r\nused to wrap helpers that make endpoint calls or direct Elasticsearch\r\noperations.\r\n\r\nThe previous logging would only explain that the maximum amount of\r\nretries had been reached, with the actual error caused in the test being\r\nlost, which proved hard to debug.\r\n\r\nThese changes catches the error and log it, allowing us to understand\r\nwhy a retried test failed.\r\n\r\nError now reported as:\r\n\r\n```\r\n[00:00:19] │ERROR Retrying installPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal Server Error\", got 200 \"OK\"\r\n[00:00:19] │ debg --- retry.tryForTime failed again with the same message...\r\n[00:00:19] │ERROR Reached maximum number of retries for test: 2/2\r\n[00:00:19] └- ✖ fail: Rules Management - Prebuilt Rules - Update Prebuilt Rules Package @ess @serverless @skipInQA update_prebuilt_rules_package should allow user to install prebuilt rules from scratch, then install new rules and upgrade existing rules from the new package\r\n[00:00:19] │ Error: \"Reached maximum number of retries for test: 2/2\"\r\n[00:00:19] │ at block (retry.ts:72:16)\r\n[00:00:19] │ at runAttempt (retry_for_success.ts:29:21)\r\n[00:00:19] │ at retryForSuccess (retry_for_success.ts:79:27)\r\n[00:00:19] │ at RetryService.tryForTime (retry.ts:23:12)\r\n[00:00:19] │ at retry (retry.ts:62:20)\r\n[00:00:19] │ at installPrebuiltRulesPackageByVersion (install_fleet_package_by_url.ts:77:25)\r\n[00:00:19] │ at Context.<anonymous> (update_prebuilt_rules_package.ts:106:46)\r\n[00:00:19] │ at Object.apply (wrap_function.js:73:16)\r\n```\r\nMain error is still `\"Reached maximum number of retries for test: 2/2\"`,\r\nbut now additional logging of exactly **what failed in the test** is\r\nerror-logged as seen above: `ERROR Retrying\r\ninstallPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal\r\nServer Error\", got 200 \"OK\"`\r\n\r\n**Flaky test run:** \r\n- Shared 50 and 50:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5068\r\n- Ess 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5091\r\n- Serverless 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5092\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":"479a022bd3a8ae79ca9af1eb12a90a26cb53efdf"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176316","number":176316,"mergeCommit":{"message":"[Security Solution] Improve logging for FTR test `retry` function (#176316)\n\n## Summary\r\n\r\n**Fixes:** \r\n- https://github.com/elastic/kibana/issues/175481\r\n- https://github.com/elastic/kibana/issues/175250\r\n\r\n\r\n### Description\r\n\r\nImproves logging for the `retry` FTR integration testing utility that is\r\nused to wrap helpers that make endpoint calls or direct Elasticsearch\r\noperations.\r\n\r\nThe previous logging would only explain that the maximum amount of\r\nretries had been reached, with the actual error caused in the test being\r\nlost, which proved hard to debug.\r\n\r\nThese changes catches the error and log it, allowing us to understand\r\nwhy a retried test failed.\r\n\r\nError now reported as:\r\n\r\n```\r\n[00:00:19] │ERROR Retrying installPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal Server Error\", got 200 \"OK\"\r\n[00:00:19] │ debg --- retry.tryForTime failed again with the same message...\r\n[00:00:19] │ERROR Reached maximum number of retries for test: 2/2\r\n[00:00:19] └- ✖ fail: Rules Management - Prebuilt Rules - Update Prebuilt Rules Package @ess @serverless @skipInQA update_prebuilt_rules_package should allow user to install prebuilt rules from scratch, then install new rules and upgrade existing rules from the new package\r\n[00:00:19] │ Error: \"Reached maximum number of retries for test: 2/2\"\r\n[00:00:19] │ at block (retry.ts:72:16)\r\n[00:00:19] │ at runAttempt (retry_for_success.ts:29:21)\r\n[00:00:19] │ at retryForSuccess (retry_for_success.ts:79:27)\r\n[00:00:19] │ at RetryService.tryForTime (retry.ts:23:12)\r\n[00:00:19] │ at retry (retry.ts:62:20)\r\n[00:00:19] │ at installPrebuiltRulesPackageByVersion (install_fleet_package_by_url.ts:77:25)\r\n[00:00:19] │ at Context.<anonymous> (update_prebuilt_rules_package.ts:106:46)\r\n[00:00:19] │ at Object.apply (wrap_function.js:73:16)\r\n```\r\nMain error is still `\"Reached maximum number of retries for test: 2/2\"`,\r\nbut now additional logging of exactly **what failed in the test** is\r\nerror-logged as seen above: `ERROR Retrying\r\ninstallPrebuiltRulesPackageByVersion: Error: expected 500 \"Internal\r\nServer Error\", got 200 \"OK\"`\r\n\r\n**Flaky test run:** \r\n- Shared 50 and 50:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5068\r\n- Ess 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5091\r\n- Serverless 100 runs:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5092\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":"479a022bd3a8ae79ca9af1eb12a90a26cb53efdf"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Juan Pablo Djeredjian <jpdjeredjian@gmail.com> |
||
|
Elastic Machine
|
45bf1be40a
|
[8.12] Sync bundled packages with Package Storage (#176447)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/332 |
||
christineweng
|
6cfaf54ea8
|
[8.12] [Security Solution][Flyout] - fix analyzer preview loading and update hover actions in rule preview (#175282) (#176243)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution][Flyout] - fix analyzer preview loading and update hover actions in rule preview (#175282)](https://github.com/elastic/kibana/pull/175282) <!--- Backport version: 8.9.8 --> ### 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-01-29T23:16:30Z","message":"[Security Solution][Flyout] - fix analyzer preview loading and update hover actions in rule preview (#175282)\n\n## Summary\r\n\r\n- Fixed a bug introduced by\r\nhttps://github.com/elastic/kibana/pull/174651: analyzer preview is stuck\r\nin loading state because `_id` is not in the index for a preview alert.\r\nAdded back `kibana.alert.ancestor.id` when flyout is open in alert\r\npreview.\r\n\r\n- Refactor the use of security hover actions in flyout. The hover action\r\nwrapper checks the type of document/scope (whether it is an alert, or in\r\na preview) to determine what actions to show on hover. Most hover\r\nactions should behave consistently when flyout is in rule preview (do\r\nnot show filter options)\r\n - Related: https://github.com/elastic/kibana/issues/173608 \r\n- Not included in this pr: 1) hover actions in alert reason preview, 2)\r\nhover actions in left panel entity details as the component is owned by\r\na different team and required greater refactor effort\r\n\r\n- Fixed a UI bug on assignees breaking into multiple lines\r\n\r\n (#176435)
# Backport This will backport the following commits from `main` to `8.12`: - [[Discover] Unskip custom time range test (#176132)](https://github.com/elastic/kibana/pull/176132) <!--- 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-02-07T17:57:50Z","message":"[Discover] Unskip custom time range test (#176132)\n\n- Closes https://github.com/elastic/kibana/issues/104578\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5021\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5062\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5076\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9999f3674bd03f2cf1b01888ac328020933b2088","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","v8.13.0"],"title":"[Discover] Unskip custom time range test","number":176132,"url":"https://github.com/elastic/kibana/pull/176132","mergeCommit":{"message":"[Discover] Unskip custom time range test (#176132)\n\n- Closes https://github.com/elastic/kibana/issues/104578\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5021\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5062\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5076\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9999f3674bd03f2cf1b01888ac328020933b2088"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176132","number":176132,"mergeCommit":{"message":"[Discover] Unskip custom time range test (#176132)\n\n- Closes https://github.com/elastic/kibana/issues/104578\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5021\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5062\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5076\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"9999f3674bd03f2cf1b01888ac328020933b2088"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
7e6bb7d9e6
|
[8.12] [RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner (#176268) (#176438)
# Backport This will backport the following commits from `main` to `8.12`: - [[RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner (#176268)](https://github.com/elastic/kibana/pull/176268) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jiawei Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-07T18:59:35Z","message":"[RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner (#176268)\n\n## Summary\r\n\r\nResolves: https://github.com/elastic/kibana/issues/176267\r\n\r\nFixes a bug where we were not removing untracked alerts from the task\r\nrunner. This is because the `es.client.search` query we used was not\r\ncorrect.\r\n\r\n\r\n### Checklist\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":"fb30f37afca46b4abbd8ce12174c1e46c0272500","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.12.0","v8.13.0"],"title":"[RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner","number":176268,"url":"https://github.com/elastic/kibana/pull/176268","mergeCommit":{"message":"[RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner (#176268)\n\n## Summary\r\n\r\nResolves: https://github.com/elastic/kibana/issues/176267\r\n\r\nFixes a bug where we were not removing untracked alerts from the task\r\nrunner. This is because the `es.client.search` query we used was not\r\ncorrect.\r\n\r\n\r\n### Checklist\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":"fb30f37afca46b4abbd8ce12174c1e46c0272500"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176268","number":176268,"mergeCommit":{"message":"[RAM][BUG] Fix bug where bulk untrack wasn't removing alerts from task runner (#176268)\n\n## Summary\r\n\r\nResolves: https://github.com/elastic/kibana/issues/176267\r\n\r\nFixes a bug where we were not removing untracked alerts from the task\r\nrunner. This is because the `es.client.search` query we used was not\r\ncorrect.\r\n\r\n\r\n### Checklist\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":"fb30f37afca46b4abbd8ce12174c1e46c0272500"}}]}] BACKPORT--> Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com> |
||
Mykola Harmash
|
aa102263c2
|
[8.12] [Profiling,Infra,APM] Disable Profiling integration by default (#175201) (#176406)
# Backport This will backport the following commits from `main` to `8.12`: - [[Profiling,Infra,APM] Disable Profiling integration by default (#175201)](https://github.com/elastic/kibana/pull/175201) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-01-24T11:44:26Z","message":"[Profiling,Infra,APM] Disable Profiling integration by default (#175201)\n\nCloses https://github.com/elastic/kibana/issues/175016\r\n\r\n## Summary\r\n\r\nThis PR disables the Profiling integration in Infra and APM by default\r\non the plugin configuration level because this integration require users\r\nto first configure the main `profiling` plugin. On-prem users will have\r\nto manually enable both integrations once they enabled the Universal\r\nProfiling for their hosts. Cloud users will have Infra and APM\r\nintegrations enabled by default because on Cloud instances Universal\r\nProfiling is already configured. A PR for the default Cloud settings\r\nwill follow after this one is merged.\r\n\r\nChanges I've made:\r\n* Disabled the Infra integration be default\r\n* Introduced a new APM feature flag for the Profiling integration\r\n* Made sure all the places in APM that rely on Profiling integration\r\nrespect the new feature flag\r\n* Fixed a bug in APM when Universal Profiling was shown even though the\r\nintegration was disabled in UI settings\r\n\r\n\r\n |
||
Pablo Machado
|
5a4ad2651f
|
[8.12] [Security Solution] Only query security alerts with the current user (#175903) (#176395)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Only query security alerts with the current user (#175903)](https://github.com/elastic/kibana/pull/175903) <!--- 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-02-02T11:24:34Z","message":"[Security Solution] Only query security alerts with the current user (#175903)\n\n## Summary\r\n\r\nFix risk score query to only search security alerts with the current\r\nuser.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b5df2e58b6dc0a6e3e734688b8c2591f42312c4","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:low","backport missing","Team: SecuritySolution","v8.12.1","Team:Entity Analytics","v8.13.0"],"number":175903,"url":"https://github.com/elastic/kibana/pull/175903","mergeCommit":{"message":"[Security Solution] Only query security alerts with the current user (#175903)\n\n## Summary\r\n\r\nFix risk score query to only search security alerts with the current\r\nuser.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b5df2e58b6dc0a6e3e734688b8c2591f42312c4"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/175903","number":175903,"mergeCommit":{"message":"[Security Solution] Only query security alerts with the current user (#175903)\n\n## Summary\r\n\r\nFix risk score query to only search security alerts with the current\r\nuser.\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"5b5df2e58b6dc0a6e3e734688b8c2591f42312c4"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
0be4e96091
|
[8.12] [Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507) (#176074) (#176375)
# Backport This will backport the following commits from `main` to `8.12`: - [[Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507) (#176074)](https://github.com/elastic/kibana/pull/176074) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2024-02-07T09:22:19Z","message":"[Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507) (#176074)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/security-team/issues/8507\r\n\r\nWith these changes we address the issue where users can upload any file\r\nto be imported as a value list.\r\n\r\nThe restrictions are:\r\n* Users should be limited to uploading .txt or .csv. All other file\r\ntypes should return a 415.\r\n* Users should be limited to uploading files of 9K bytes size. Files\r\nlarger than that should return a 413.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ESS 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5019)\r\n- [Serverless 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5020)","sha":"c38410affe0bccd61884b58a41b7bda48c78d86f","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","Team:Detection Engine","8.13 candidate","v8.13.0","v8.12.2","v7.17.19"],"title":"[Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507)","number":176074,"url":"https://github.com/elastic/kibana/pull/176074","mergeCommit":{"message":"[Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507) (#176074)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/security-team/issues/8507\r\n\r\nWith these changes we address the issue where users can upload any file\r\nto be imported as a value list.\r\n\r\nThe restrictions are:\r\n* Users should be limited to uploading .txt or .csv. All other file\r\ntypes should return a 415.\r\n* Users should be limited to uploading files of 9K bytes size. Files\r\nlarger than that should return a 413.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ESS 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5019)\r\n- [Serverless 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5020)","sha":"c38410affe0bccd61884b58a41b7bda48c78d86f"}},"sourceBranch":"main","suggestedTargetBranches":["8.12","7.17"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176074","number":176074,"mergeCommit":{"message":"[Exceptions][Value Lists] Add file type and size constraints to value list uploads (#8507) (#176074)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/security-team/issues/8507\r\n\r\nWith these changes we address the issue where users can upload any file\r\nto be imported as a value list.\r\n\r\nThe restrictions are:\r\n* Users should be limited to uploading .txt or .csv. All other file\r\ntypes should return a 415.\r\n* Users should be limited to uploading files of 9K bytes size. Files\r\nlarger than that should return a 413.\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ESS 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5019)\r\n- [Serverless 97\r\ntimes](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5020)","sha":"c38410affe0bccd61884b58a41b7bda48c78d86f"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.19","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
Tiago Costa
|
d80cfe145c
|
chore(NA): bump version to 8.12.2 (#176315)
Usually bump from 8.12.1 to 8.12.2 Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
faa93cbb60
|
[8.12] [Ent Search] Connector client copy cleanup (#176290) (#176331)
# Backport This will backport the following commits from `main` to `8.12`: - [[Ent Search] Connector client copy cleanup (#176290)](https://github.com/elastic/kibana/pull/176290) <!--- 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-02-06T17:31:55Z","message":"[Ent Search] Connector client copy cleanup (#176290)\n\nAdditional fixes missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The deployment first paragraph was outdated and irrelevant to the user\r\nworkflow\r\n- Some of step headings were vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.13.0","v8.12.2"],"title":"[Ent Search] Connector client copy cleanup","number":176290,"url":"https://github.com/elastic/kibana/pull/176290","mergeCommit":{"message":"[Ent Search] Connector client copy cleanup (#176290)\n\nAdditional fixes missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The deployment first paragraph was outdated and irrelevant to the user\r\nworkflow\r\n- Some of step headings were vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176290","number":176290,"mergeCommit":{"message":"[Ent Search] Connector client copy cleanup (#176290)\n\nAdditional fixes missed in https://github.com/elastic/kibana/pull/173366\r\n\r\n- The deployment first paragraph was outdated and irrelevant to the user\r\nworkflow\r\n- Some of step headings were vague","sha":"87a66f24898d9d0ad20b357f62cdc9ea407ad27b"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> |
||
|
Kibana Machine
|
ea7b6c4247
|
[8.12] [Fleet] Logstash Output - being compliant to RFC-952 (#176298) (#176323)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Logstash Output - being compliant to RFC-952 (#176298)](https://github.com/elastic/kibana/pull/176298) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex S","email":"Terilia@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-06T16:33:56Z","message":"[Fleet] Logstash Output - being compliant to RFC-952 (#176298)\n\n## Summary\r\n\r\nThe logstash output in fleet was not following the\r\n[RFC-952](https://www.rfc-editor.org/rfc/rfc952) correctly, only\r\naccepting lowercase url's for the hostname, even though according to the\r\nstandard, this should be irrelevant.\r\n\r\nAdditionally added two new unit tests, to check that this behaviour is\r\ncompliant in the future as well.\r\n\r\n\r\n## Fix explanation\r\n\r\nThe issue was in the past that the URL Type in nodejs is automatically\r\nlowercase, and then the value of the form is or the string provided is\r\nchecked against this url type. The types behaviour is explained here:\r\nhttps://nodejs.org/api/url.html#the-whatwg-url-api\r\n\r\nAs we would like to be case insensitive, in the check, the value is also\r\nlowerecased with: val.toLowerCase() to pass the check\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":"55429179ba30ca3a922f6daf44ce17f8d5f19507","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.13.0"],"title":"[Fleet] Logstash Output - being compliant to RFC-952","number":176298,"url":"https://github.com/elastic/kibana/pull/176298","mergeCommit":{"message":"[Fleet] Logstash Output - being compliant to RFC-952 (#176298)\n\n## Summary\r\n\r\nThe logstash output in fleet was not following the\r\n[RFC-952](https://www.rfc-editor.org/rfc/rfc952) correctly, only\r\naccepting lowercase url's for the hostname, even though according to the\r\nstandard, this should be irrelevant.\r\n\r\nAdditionally added two new unit tests, to check that this behaviour is\r\ncompliant in the future as well.\r\n\r\n\r\n## Fix explanation\r\n\r\nThe issue was in the past that the URL Type in nodejs is automatically\r\nlowercase, and then the value of the form is or the string provided is\r\nchecked against this url type. The types behaviour is explained here:\r\nhttps://nodejs.org/api/url.html#the-whatwg-url-api\r\n\r\nAs we would like to be case insensitive, in the check, the value is also\r\nlowerecased with: val.toLowerCase() to pass the check\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":"55429179ba30ca3a922f6daf44ce17f8d5f19507"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176298","number":176298,"mergeCommit":{"message":"[Fleet] Logstash Output - being compliant to RFC-952 (#176298)\n\n## Summary\r\n\r\nThe logstash output in fleet was not following the\r\n[RFC-952](https://www.rfc-editor.org/rfc/rfc952) correctly, only\r\naccepting lowercase url's for the hostname, even though according to the\r\nstandard, this should be irrelevant.\r\n\r\nAdditionally added two new unit tests, to check that this behaviour is\r\ncompliant in the future as well.\r\n\r\n\r\n## Fix explanation\r\n\r\nThe issue was in the past that the URL Type in nodejs is automatically\r\nlowercase, and then the value of the form is or the string provided is\r\nchecked against this url type. The types behaviour is explained here:\r\nhttps://nodejs.org/api/url.html#the-whatwg-url-api\r\n\r\nAs we would like to be case insensitive, in the check, the value is also\r\nlowerecased with: val.toLowerCase() to pass the check\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":"55429179ba30ca3a922f6daf44ce17f8d5f19507"}}]}] BACKPORT--> Co-authored-by: Alex S <Terilia@users.noreply.github.com> |
||
|
Kibana Machine
|
9c1c90b350
|
[8.12] [ML] Anomaly Detection: Fix `values-dots` colors (#176303) (#176326)
# Backport This will backport the following commits from `main` to `8.12`: - [[ML] Anomaly Detection: Fix `values-dots` colors (#176303)](https://github.com/elastic/kibana/pull/176303) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2024-02-06T16:45:19Z","message":"[ML] Anomaly Detection: Fix `values-dots` colors (#176303)\n\n## Summary\r\n\r\nFixes the colors of \"value dots\", the dots that are shown in the Single\r\nMetric Viewer when theres sparse data and not a continuous line.\r\n\r\nBefore:\r\n\r\n<img width=\"1112\" alt=\"image\"\r\nsrc=\" |
||
|
Elastic Machine
|
4e40e1d926
|
[8.12] Sync bundled packages with Package Storage (#176319)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/315 |
||
|
Kibana Machine
|
341e9e6122
|
[8.12] [Search] Fix connector config resetting without changes (#176235) (#176297)
# Backport This will backport the following commits from `main` to `8.12`: - [[Search] Fix connector config resetting without changes (#176235)](https://github.com/elastic/kibana/pull/176235) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-06T14:08:19Z","message":"[Search] Fix connector config resetting without changes (#176235)\n\n## Summary\r\n\r\nThis fixes an issue in the connector configuration where the config\r\nwould keep resetting without config changes.","sha":"9ccd7cc5713cf893c8f22fc52f3f8d5d71635e7e","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.13.0","v8.12.2"],"title":"[Search] Fix connector config resetting without changes","number":176235,"url":"https://github.com/elastic/kibana/pull/176235","mergeCommit":{"message":"[Search] Fix connector config resetting without changes (#176235)\n\n## Summary\r\n\r\nThis fixes an issue in the connector configuration where the config\r\nwould keep resetting without config changes.","sha":"9ccd7cc5713cf893c8f22fc52f3f8d5d71635e7e"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176235","number":176235,"mergeCommit":{"message":"[Search] Fix connector config resetting without changes (#176235)\n\n## Summary\r\n\r\nThis fixes an issue in the connector configuration where the config\r\nwould keep resetting without config changes.","sha":"9ccd7cc5713cf893c8f22fc52f3f8d5d71635e7e"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
02ddd20b41
|
[8.12] [Discover] Unskip edit data view test (#176134) (#176275)
# Backport This will backport the following commits from `main` to `8.12`: - [[Discover] Unskip edit data view test (#176134)](https://github.com/elastic/kibana/pull/176134) <!--- 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-02-06T08:07:34Z","message":"[Discover] Unskip edit data view test (#176134)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5022\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"f019b531a020c934ad67a4cd997b9a4508cbde49","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:DataDiscovery","backport:prev-minor","v8.13.0"],"title":"[Discover] Unskip edit data view test","number":176134,"url":"https://github.com/elastic/kibana/pull/176134","mergeCommit":{"message":"[Discover] Unskip edit data view test (#176134)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5022\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"f019b531a020c934ad67a4cd997b9a4508cbde49"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176134","number":176134,"mergeCommit":{"message":"[Discover] Unskip edit data view test (#176134)\n\n- Closes https://github.com/elastic/kibana/issues/174066\r\n\r\n## Summary\r\n\r\n50x\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5022\r\n\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed","sha":"f019b531a020c934ad67a4cd997b9a4508cbde49"}}]}] BACKPORT--> Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
|
Kibana Machine
|
a94310fc91
|
[8.12] [Fleet] Fix assets being unintentionally moved to the default space during Fleet setup (#176173) (#176250)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Fix assets being unintentionally moved to the default space during Fleet setup (#176173)](https://github.com/elastic/kibana/pull/176173) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2024-02-05T18:55:49Z","message":"[Fleet] Fix assets being unintentionally moved to the default space during Fleet setup (#176173)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/175173\r\n\r\nUse a scoped SO client when importing assets to prevent always importing\r\nassets into the default space during Fleet setup.\r\n\r\n## To do\r\n\r\nAdd tests?\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c07ee4ad0f9ca0912d88d4cccf85474f1811e8dc","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.13.0"],"title":"[Fleet] Fix assets being unintentionally moved to the default space during Fleet setup","number":176173,"url":"https://github.com/elastic/kibana/pull/176173","mergeCommit":{"message":"[Fleet] Fix assets being unintentionally moved to the default space during Fleet setup (#176173)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/175173\r\n\r\nUse a scoped SO client when importing assets to prevent always importing\r\nassets into the default space during Fleet setup.\r\n\r\n## To do\r\n\r\nAdd tests?\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c07ee4ad0f9ca0912d88d4cccf85474f1811e8dc"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176173","number":176173,"mergeCommit":{"message":"[Fleet] Fix assets being unintentionally moved to the default space during Fleet setup (#176173)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/175173\r\n\r\nUse a scoped SO client when importing assets to prevent always importing\r\nassets into the default space during Fleet setup.\r\n\r\n## To do\r\n\r\nAdd tests?\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"c07ee4ad0f9ca0912d88d4cccf85474f1811e8dc"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co> |
||
|
Kibana Machine
|
6d3559f465
|
[8.12] [DOCS] Add link to on-prem install tutorial (#176096) (#176234)
# Backport This will backport the following commits from `main` to `8.12`: - [[DOCS] Add link to on-prem install tutorial (#176096)](https://github.com/elastic/kibana/pull/176096) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"David Kilfoyle","email":"41695641+kilfoyle@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-05T15:22:15Z","message":"[DOCS] Add link to on-prem install tutorial (#176096)\n\nThis adds a link on the [Install\r\nKibana](https://www.elastic.co/guide/en/kibana/current/install.html)\r\npage pointing to a new example walkthrough of the on-prem install steps.\r\n\r\n\r\n (#176217)
# Backport This will backport the following commits from `main` to `8.12`: - [[DOCS] Adds the release notes for 8.12.1 (#176214)](https://github.com/elastic/kibana/pull/176214) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-05T13:06:54Z","message":"[DOCS] Adds the release notes for 8.12.1 (#176214)\n\nAdds the release notes for 8.12.1","sha":"3b88a0c1eb0451b98cd505861c638310729d3e08","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.12.0","v8.12.1","v8.13.0"],"title":"[DOCS] Adds the release notes for 8.12.1","number":176214,"url":"https://github.com/elastic/kibana/pull/176214","mergeCommit":{"message":"[DOCS] Adds the release notes for 8.12.1 (#176214)\n\nAdds the release notes for 8.12.1","sha":"3b88a0c1eb0451b98cd505861c638310729d3e08"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176214","number":176214,"mergeCommit":{"message":"[DOCS] Adds the release notes for 8.12.1 (#176214)\n\nAdds the release notes for 8.12.1","sha":"3b88a0c1eb0451b98cd505861c638310729d3e08"}}]}] BACKPORT--> Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com> |
||
|
Kibana Machine
|
43a6eb645d
|
[8.12] [Security Solution] Fix rule export for a large number of rules (#175979) (#176211)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security Solution] Fix rule export for a large number of rules (#175979)](https://github.com/elastic/kibana/pull/175979) <!--- 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-02-05T11:33:16Z","message":"[Security Solution] Fix rule export for a large number of rules (#175979)\n\n**Fixes:** https://github.com/elastic/kibana/issues/170015\r\n\r\n## Summary\r\n\r\nThis PR fixes inability to export a large number of rules.\r\n\r\n## Details\r\n\r\nThe problem appears as 500 server error shown by UI in attempt to export a large number of rules (1K or more). In fact it boils down to `too_many_clauses` ES error. Server side fetches rules by passing each `ruleId` in ES query. When the number of `ruleIds` exceeds the limit `too_many_clauses` error is returned. The limit is set via `indices.query.bool.max_clause_count` and the value is [calculated dynamically](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-settings.html) with the minimum value `1024`.\r\n\r\nThe fix makes sure rules are processed in chunks by 1024 to prevent `too_many_clauses` error and guarantee it works in different environment.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"576fe37b16db4fb6e1224387d5485ddb8fed6787","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","impact:high","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Rule Import/Export","v8.13.0","v8.12.2"],"title":"[Security Solution] Fix rule export for a large number of rules","number":175979,"url":"https://github.com/elastic/kibana/pull/175979","mergeCommit":{"message":"[Security Solution] Fix rule export for a large number of rules (#175979)\n\n**Fixes:** https://github.com/elastic/kibana/issues/170015\r\n\r\n## Summary\r\n\r\nThis PR fixes inability to export a large number of rules.\r\n\r\n## Details\r\n\r\nThe problem appears as 500 server error shown by UI in attempt to export a large number of rules (1K or more). In fact it boils down to `too_many_clauses` ES error. Server side fetches rules by passing each `ruleId` in ES query. When the number of `ruleIds` exceeds the limit `too_many_clauses` error is returned. The limit is set via `indices.query.bool.max_clause_count` and the value is [calculated dynamically](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-settings.html) with the minimum value `1024`.\r\n\r\nThe fix makes sure rules are processed in chunks by 1024 to prevent `too_many_clauses` error and guarantee it works in different environment.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"576fe37b16db4fb6e1224387d5485ddb8fed6787"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/175979","number":175979,"mergeCommit":{"message":"[Security Solution] Fix rule export for a large number of rules (#175979)\n\n**Fixes:** https://github.com/elastic/kibana/issues/170015\r\n\r\n## Summary\r\n\r\nThis PR fixes inability to export a large number of rules.\r\n\r\n## Details\r\n\r\nThe problem appears as 500 server error shown by UI in attempt to export a large number of rules (1K or more). In fact it boils down to `too_many_clauses` ES error. Server side fetches rules by passing each `ruleId` in ES query. When the number of `ruleIds` exceeds the limit `too_many_clauses` error is returned. The limit is set via `indices.query.bool.max_clause_count` and the value is [calculated dynamically](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-settings.html) with the minimum value `1024`.\r\n\r\nThe fix makes sure rules are processed in chunks by 1024 to prevent `too_many_clauses` error and guarantee it works in different environment.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios","sha":"576fe37b16db4fb6e1224387d5485ddb8fed6787"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
c97a4a4c01
|
[8.12] [Security solution] Update default Bedrock api url (#176090) (#176176)
# Backport This will backport the following commits from `main` to `8.12`: - [[Security solution] Update default Bedrock api url (#176090)](https://github.com/elastic/kibana/pull/176090) <!--- 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-02-02T17:43:33Z","message":"[Security solution] Update default Bedrock api url (#176090)","sha":"3a4ad7725a28429f25acd3ce630fb43f45ecde1e","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team: SecuritySolution","ci:cloud-deploy","ci:cloud-redeploy","v8.13.0","Team:Security Generative AI","v8.12.2"],"title":"[Security solution] Update default Bedrock api url","number":176090,"url":"https://github.com/elastic/kibana/pull/176090","mergeCommit":{"message":"[Security solution] Update default Bedrock api url (#176090)","sha":"3a4ad7725a28429f25acd3ce630fb43f45ecde1e"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176090","number":176090,"mergeCommit":{"message":"[Security solution] Update default Bedrock api url (#176090)","sha":"3a4ad7725a28429f25acd3ce630fb43f45ecde1e"}},{"branch":"8.12","label":"v8.12.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
|
Kibana Machine
|
0e7f0277d8
|
[8.12] Updates test file wrapper to deterministically detect file write completion (#176115) (#176161)
# Backport This will backport the following commits from `main` to `8.12`: - [Updates test file wrapper to deterministically detect file write completion (#176115)](https://github.com/elastic/kibana/pull/176115) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2024-02-02T14:57:37Z","message":"Updates test file wrapper to deterministically detect file write completion (#176115)\n\nCloses #119267\r\n\r\n## Summary\r\n\r\nAttempts to deterministically detect when a file is written in entirety\r\nin order to resolve flaky test issues where parsed JSON is incomplete.\r\n\r\nFlaky Test Runner:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5015","sha":"f9125ba079aeaa31fcd07e442cf6789c344452ec","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:all-open","v8.13.0"],"title":"Updates test file wrapper to deterministically detect file write completion","number":176115,"url":"https://github.com/elastic/kibana/pull/176115","mergeCommit":{"message":"Updates test file wrapper to deterministically detect file write completion (#176115)\n\nCloses #119267\r\n\r\n## Summary\r\n\r\nAttempts to deterministically detect when a file is written in entirety\r\nin order to resolve flaky test issues where parsed JSON is incomplete.\r\n\r\nFlaky Test Runner:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5015","sha":"f9125ba079aeaa31fcd07e442cf6789c344452ec"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176115","number":176115,"mergeCommit":{"message":"Updates test file wrapper to deterministically detect file write completion (#176115)\n\nCloses #119267\r\n\r\n## Summary\r\n\r\nAttempts to deterministically detect when a file is written in entirety\r\nin order to resolve flaky test issues where parsed JSON is incomplete.\r\n\r\nFlaky Test Runner:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5015","sha":"f9125ba079aeaa31fcd07e442cf6789c344452ec"}}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> |
||
|
Kibana Machine
|
8bff5996f2
|
[8.12] [Fleet] Fix categories labels in integration overview (#176141) (#176157)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Fix categories labels in integration overview (#176141)](https://github.com/elastic/kibana/pull/176141) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-02T14:19:39Z","message":"[Fleet] Fix categories labels in integration overview (#176141)\n\nCloses https://github.com/elastic/kibana/issues/176031\r\n\r\n## Summary\r\n\r\nFixing missing category label in Integration overwiew page for\r\nsubintegrations. The category label was just showing the parent\r\nIntegration label but not the own category. To fix it, I'm adding the\r\ncategories in `integrationInfo` as well.\r\n\r\n### Before\r\n
Cristina Amico
|
ad6180df31
|
[8.12] [Fleet] Prevent deletion of agent policies with inactive agents from UI (#175815) (#176131)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Prevent deletion of agent policies with inactive agents from UI (#175815)](https://github.com/elastic/kibana/pull/175815) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-02-01T20:25:45Z","message":"[Fleet] Prevent deletion of agent policies with inactive agents from UI (#175815)\n\nFixes https://github.com/elastic/kibana/issues/155925\r\n\r\n## Summary\r\nPrevent deleting an agent policy that has inactive agents assigned. The\r\nworkaround to fix existing \"orphaned\" agents is outlined\r\n[here](https://github.com/elastic/kibana/issues/155925#issuecomment-1919250162).\r\n\r\n### API\r\nAdding check for inactive agents to the agent policy \"delete\" endpoint -\r\nIt will now fail if the policy has either active or inactive agents:\r\n\r\n```\r\n POST /api/fleet/agent_policies/delete\r\n {\r\n agentPolicyId: 1234534,\r\n }\r\n```\r\n\r\n### UI \r\nWarning added to the \"delete\" action in the UI when trying to delete a\r\npolicy that has active or inactive agents.\r\n\r\n## Testing\r\n- Have a policy with many inactive agents assigned to it\r\n- Try to delete it from the agent policy list or settings\r\n- The deletion is prevented and a warning is raised:\r\n\r\n
David Sánchez
|
d6bbcfc7e8
|
[EDR Workflows] Unskip e2e tests due vagrant up error (#175780)
## Summary Re-enable skipped e2e tests due vagrant up error. This pr depends on this change: https://github.com/elastic/kibana/pull/175755 Originally merged at main here: https://github.com/elastic/kibana/pull/175754 fixes: https://github.com/elastic/kibana/issues/170811 fixes: https://github.com/elastic/kibana/issues/170674 fixes: https://github.com/elastic/kibana/issues/169343 fixes: https://github.com/elastic/kibana/issues/170601 fixes: https://github.com/elastic/kibana/issues/173464 fixes: https://github.com/elastic/kibana/issues/170667 fixes: https://github.com/elastic/kibana/issues/170812 fixes: https://github.com/elastic/kibana/issues/170604 fixes: https://github.com/elastic/kibana/issues/170373 fixes: https://github.com/elastic/kibana/issues/169958 fixes: https://github.com/elastic/kibana/issues/170814 fixes: https://github.com/elastic/kibana/issues/170424 fixes: https://github.com/elastic/kibana/issues/170706 fixes: https://github.com/elastic/kibana/issues/170563 fixes: https://github.com/elastic/kibana/issues/169689 fixes: https://github.com/elastic/kibana/issues/170817 fixes: https://github.com/elastic/kibana/issues/169821 fixes: https://github.com/elastic/kibana/issues/170816 fixes: https://github.com/elastic/kibana/issues/170794 ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3066656a16
|
[8.12] [Fleet] Fix max agent for agent activity (#176081) (#176092)
# Backport This will backport the following commits from `main` to `8.12`: - [[Fleet] Fix max agent for agent activity (#176081)](https://github.com/elastic/kibana/pull/176081) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2024-02-01T18:59:34Z","message":"[Fleet] Fix max agent for agent activity (#176081)","sha":"9872b70a84f61d75243064e81abea42afdf9a58f","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Fleet","backport:prev-minor","v8.13.0"],"title":"[Fleet] Fix max agent for agent activity","number":176081,"url":"https://github.com/elastic/kibana/pull/176081","mergeCommit":{"message":"[Fleet] Fix max agent for agent activity (#176081)","sha":"9872b70a84f61d75243064e81abea42afdf9a58f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","branchLabelMappingKey":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/176081","number":176081,"mergeCommit":{"message":"[Fleet] Fix max agent for agent activity (#176081)","sha":"9872b70a84f61d75243064e81abea42afdf9a58f"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
Jon
|
279160094b
|
[8.12] Upgrade selenium-webdriver to 4.17.0 (#175746) (#176058)
#175746 |