Skip to content

[9.2] [Security Solution] update the name of the Security solution default and Security solution alerts data views when needed (#238354)#238525

Merged
kibanamachine merged 1 commit intoelastic:9.2from
kibanamachine:backport/9.2/pr-238354
Oct 10, 2025
Merged

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

…and Security solution alerts data views when needed (elastic#238354)

## Summary

This PR aims at fixing a UI issue related to the data view picker
changes we made recently in Security Solution. After enabling the
`dataViewPickerEnabled` feature flag (see [this
PR](elastic#234101)) we realized that the
`Security solution default` and `Security solution alerts` aren't
displayed properly.
This is only visible within an environment that had those data view
existing before turning on the feature flag.

Instead of showing `Security solution default` we show this
<img width="562" height="366" alt="Screenshot 2025-10-09 at 4 10 40 PM"
src="https://github.com/user-attachments/assets/3b59501e-f1ae-460d-b26c-b46f876ea772"
/>

And instead of showing `Security solution alerts` we show this
<img width="558" height="404" alt="Screenshot 2025-10-09 at 4 10 18 PM"
src="https://github.com/user-attachments/assets/f50a0eb7-a5f2-41e0-8018-28d9ddf92ee6"
/>

Looking at the Data Views screen under Stack Management, we indeed see
that the names are matching what we see in the data view picker
<img width="734" height="655" alt="Screenshot 2025-10-09 at 4 11 46 PM"
src="https://github.com/user-attachments/assets/ebc743e8-91d9-4ac1-8992-85290db59f10"
/>

For the `Security solution default` data view, we added the name in
[this PR](elastic#224333).
For the `Security solution alerts` data view, we created the alert index
and the corresponding data view in [this
PR](elastic#224144).
But we changed both names in [this
PR](elastic#231374) (from `Default
security data view` to `Security solution default` and from `Security
alert data view` to `Security solution alerts` respectively).

This means that if one of these data views was created either without a
name or with an old name, that name would persist and be visible within
the new data view picker.

## The fix

This PR makes a simple fix: if the names of the saved object differ from
what we expect (only for the `default` and `alerts` data views), we
update the saved object.

Here's en example of the data view being updated after a refresh

https://github.com/user-attachments/assets/4ef8c623-3e45-4a57-93bb-0464c3189f67

### Checklist

- [x] 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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

(cherry picked from commit 4f30b77)
@kibanamachine kibanamachine merged commit 38ad5f0 into elastic:9.2 Oct 10, 2025
16 checks passed
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #27 / discover/group1 discover test nested query should support querying on nested fields
  • [job] [logs] FTR Configs #93 / Endpoint plugin @ess @serverless @skipInServerlessMKI When attempting to call an endpoint api "after all" hook in "@ess @serverless @skipInServerlessMKI When attempting to call an endpoint api"

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 11.1MB 11.1MB +138.0B

cc @PhilippeOberti

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants