## Summary
Closes#218143
Reverts #39292
This PR parallelizes the artifact outputs and archive creation tasks to
reduce build runtime by about 49% (104min down to 53min). It required
buffering the logs as they were all interweaved from each task and were
not easily parsed by a human. So, the PR also cleans up the logging a
little bit by utilizing the dropdowns available in Buildkite.
### Testing
https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6253
I also tried bumping the machine to `c2-standard-30` which increases
vCPU from 16 to 30 and Memory from 64GB to 120GB:
https://buildkite.com/elastic/kibana-artifacts-snapshot/builds/6254
This results in a 13% reduction in run time for the parallel builds but
is about twice the cost, which isn't worth it.
This PR moves the migration-on-read logic into the storage adapter so
it's not possible to accidentally read unmigrated `_source` objects and
adds tests for this for asset links (dashboards and queries). While
there is no migration on read currently ongoing for dashboards and
queries, this test will highlight problems in this area, avoiding an
issue like the one we had with streams definitions themselves.
## Summary
This PR is a follow up of [this previous
one](https://github.com/elastic/kibana/pull/220590) that removed the
advanced setting allowing users to switch between the Session View
component rendered in the expandable flyout and as an overlay to the
alerts table.
This PR focuses on removing all code related to the Session View
component when displayed as an overlay of the Alerts page alerts table
and in Timeline.
**_As the previous PR had removed the ability to switch back to this
overlay mode, this PR does not introduces any visible changes in the UI.
If anything looks different or behaves differently, then there is an
issue and this PR should not be merged._**
Session View in expandable flyout remains unchanged:
https://github.com/user-attachments/assets/54107185-ff9b-4090-ac0d-7c4f3f1a421f
### Checklist
- [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
## Summary
### Fleet changes
- Update type of `packagePolicy.listIds()`
### Security Solution
- The logic that is triggered on plugin start as well as when fleet
policies (integration + agent) are updated and ensures that internal DOT
indices associated with endpoint data streams are created was updated to
ensure it supports spaces
### Checklist
- [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
# Summary
Clarified in the Entity Analytics dashboard that Entity Risk scoring is
for entity types other than just "users"
# How to test
Open the Entity Analytics dashboard, click "Enable", and notice that the
text is updated.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary
This PR is only moving files and update file paths. No code changes are
implemented whatsoever.
The PR focuses on moving a bunch of folders and files that lived under
the `detections` folder but were actually only used within the
`detection_engine` folder.
- if the files/folders were used within a single `detection_engine`
folder (like for example `rule_actions_overflow` is only used within
`rule_details_ui`) then things were moved closest to where it was used)
- if the files/folders were used within multiple `detection_engine`
folders, then things were moved into a `components` folder under the
existing `common` folder at the root of `detection_engine`
**_If there are any folders or files that you feel should live in a
specific folder, let me know. I'm happy to move things around some
more!_**
### Checklist
- [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
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[@launchdarkly/node-server-sdk](https://redirect.github.com/launchdarkly/js-core/tree/main/packages/sdk/server-node)
([source](https://redirect.github.com/launchdarkly/js-core)) |
dependencies | patch | [`^9.9.1` ->
`^9.9.2`](https://renovatebot.com/diffs/npm/@launchdarkly%2fnode-server-sdk/9.9.1/9.9.2)
|
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOkNvcmUiLCJUZWFtOlNlY3VyaXR5IiwiYmFja3BvcnQ6cHJldi1tYWpvciIsImJhY2twb3J0OnByZXYtbWlub3IiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->
Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>
## Summary
Close https://github.com/elastic/kibana/issues/219601
An invisible item appeared in the side nav for Serverless Observability
(within the "Infrastructure" secondary panel). I tracked it down to the
inclusion of a `'metrics:assetDetails'` deepLink.
Removing the deepLink solves the problem, however I'm unsure if
including the deepLink is the correct configuration of the code. If it
is, then the `'metrics:assetDetails'` deepLink definition needs to be
adjusted. I'm unsure where that definition lives in the codebase.
### Identify risks
- [x] Need someone from Observability UX Mgmt to double-check the
requirements.
## Summary
Closes https://github.com/elastic/kibana/issues/205805
This PR extracts the share export functionality into a standalone
triggered UI action, and builds mostly off of the work that's been done
in https://github.com/elastic/kibana/pull/211665 as such any share
integration type that's registered under the groupId `export` will show
up within the afore mentioned standalone export type.
Registering a new export type would happen like so;
```js
share.registerShareIntegration({
groupId: 'export',
...
config: () => ({
...
}),
prerequisiteCheck({ license, capabilities, objectType }) {
// The prerequisiteCheck callback will get passed the license, app capabilities and the objectType
// of the current caller, this can then be used to determine if this integration should be available,
// returning false in here disables the integration,
}
})
```
*P.S.* This registration can also be scoped to a particular object type
(i.e. lens, dashboard etc.) if said integration is intended to only be
available for only a particular object type.
## Visuals for new export experience
#### _visualize_
##### (_lens_)
<img width="768" alt="Screenshot 2025-04-24 at 10 53 25"
src="https://github.com/user-attachments/assets/31966ded-b1f7-417e-840e-4596b310d6bc"
/>
##### (_others_)
<img width="1720" alt="Screenshot 2025-04-25 at 09 04 50"
src="https://github.com/user-attachments/assets/8b675974-9a4b-4dcc-9aca-77cea5a25654"
/>
#### _dashboard_
##### _(user with all reporting permissions)_
<img width="640" alt="Screenshot 2025-04-24 at 10 53 40"
src="https://github.com/user-attachments/assets/d16da148-3c25-4a58-a847-d4d5a3736106"
/>
##### _(user with no pdf, png, csv privileges doesn't have the export
button visible)_
<img width="1728" alt="Screenshot 2025-05-02 at 13 11 21"
src="https://github.com/user-attachments/assets/e47426fb-db5b-4c2a-bee5-557fefbb40ec"
/>
#### _discover_
<img width="626" alt="Screenshot 2025-04-04 at 20 18 50"
src="https://github.com/user-attachments/assets/f4bdd2a3-2527-4334-b253-7686e4131d87"
/>
<img width="1728" alt="Screenshot 2025-05-02 at 13 11 43"
src="https://github.com/user-attachments/assets/9a6e7fa2-260d-4b68-a1ae-61c499849fb8"
/>
### Test scenarios
- Pull this PR and run it locally, or test in the provision environment
linked to this PR.
- Navigate to the dashboard, discover, and visualize app. The nav menu
should display icon buttons for sharing and export.
- Clicking the "Share" icon (up arrow) opens the familiar share modal
without export. The "Export" icon (down arrow) opens a new popover with
available options.
- Export Functionality Test;
- Single Export Option: When there's only one export option, the flyout
opens automatically.
- Disabled Reporting Features: Create a new role with reporting
subPrivileges and test it by creating a user assigned to that role. Log
in as the user, and the export popover should reflect the limited
reporting features.
- In the case where the current user has no registered integrations
available to them, the export functionality will not be displayed
<!--
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
### Identify risks
Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
-->
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary
- API test that verifies whether fields are correctly inherited
- update an assertion that fails on Cloud because a cluster may have
existing streams in place
The handling of `.kibana_streams` documents in the execution plan wasn't
optimal because it would update the definition docs of ancestors and
descendants of all changed streams as well, even if no change actually
happened.
This PR fixes this problem by checking whether a stream got actually
changed or not.
It also switches the bulk operation for changed definitions from the
implicit `"wait_for"` refresh param to `true`. Since concurrent access
is anyways not supported by the streams API (there are plans to
introduce an explicit lock), this won't change make things less
efficient in practice but return the request faster to the user.
Closes#82154
## Summary
This PR fixes the error count navigation reload issue in the APM
waterfall. To fix that, it combines the prevent default action needed
because of the flyout opening and the navigation using the
`navigateToUrl` action to create a SPA-like experience:
https://github.com/user-attachments/assets/43faf3b9-2038-40d0-89c9-62c37087386d
Testing ⬆️
- The navigation to the errors tab should not cause a full page refresh
- The flyout should open without issues on click
+ Now the errors link supports keyboard navigation (fixed that part
here, it was skipped before)
https://github.com/user-attachments/assets/82c2d0b7-caef-4c24-8af9-d6b1d7f75eef
This PR updates the ES|QL grammars (lexer and parser) to match the
latest version in Elasticsearch.
---------
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary
Fixes the inference endpoint assignment to the trained model object. The
`elser` service was replaced with `elasticsearch`, so the check for
assigning endpoints wasn’t working.
It fixes the check for the Stop deployment action on the Trained Models
page, preventing the user from stopping an inference endpoint.
<img width="771" alt="image"
src="https://github.com/user-attachments/assets/1c76a716-971f-410a-a82a-141dc3d9b9fc"
/>
### Checklist
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## Summary
Closes: https://github.com/elastic/kibana/issues/205589https://github.com/user-attachments/assets/762a3a01-90f8-4741-8ddd-b5b9a7fe65cc
Changes:
**Removed closing logic from `onChange`**
Deleted the `closePopover()` invocation in the radio-group’s `onChange`
Now selecting a radio option leaves the popover open as expected.
**Preserved Escape behavior**
The popover still closes when pressing Escape, per standard overlay
patterns.
**Accessibility alignment**
Followed the ARIA radio-group
[pattern](https://www.w3.org/WAI/ARIA/apg/patterns/radio/):
`Space/Enter` should select without closing, arrow keys move focus &
selection.
This matches both screen-reader usage and standard keyboard navigation.
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This PR updates the function definitions and inline docs based on the
latest metadata from Elasticsearch.
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
## Summary
Remove run soon for sync private location task !!
It's not needed since it's a scheduled task running every 10 minutes .
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
