Skip to content

[9.4] [Security Solution] fix wrong banner shown in Discover document flyout because of missing services (#268249)#268749

Merged
PhilippeOberti merged 1 commit into
elastic:9.4from
PhilippeOberti:backport/9.4/pr-268249
May 12, 2026
Merged

[9.4] [Security Solution] fix wrong banner shown in Discover document flyout because of missing services (#268249)#268749
PhilippeOberti merged 1 commit into
elastic:9.4from
PhilippeOberti:backport/9.4/pr-268249

Conversation

@PhilippeOberti
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.4:

Questions ?

Please refer to the Backport tool documentation

…t because of missing services (elastic#268249)

## Summary

This PR makes a super small couple of changes:

#### Fix wrong banner message

Move the `RemoteDocumentCallout` inside the `flyoutProviders` to ensure
that the `services` are setup correctly. There was an inconsistency when
opening the flyout in Discover (which was showing `This attack
originates from a linked project. Some features may not be available.`)
and opening the same flyout in a Dashboard where Discover is embedded
(which was showing `This attack originates from a remote cluster. Some
features may not be available.`).

#### Remove the `metadataCallout`

Remove the `EuiCallOut` for missing metadata when the `services` or
`store` aren't defined. This is for better consistency with the header
and footer sections of the flyout, which are currently both returning
`null`.

### 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
- [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 e465723)

# Conflicts:
#	x-pack/solutions/security/plugins/security_solution/public/one_discover/alert_flyout_header_component/index.tsx
@kibanamachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #33 / cases security and spaces enabled: basic Cases telemetry should return the correct total number of alerts attached to cases

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 12.0MB 12.0MB +10.0B

@PhilippeOberti PhilippeOberti merged commit 1c51138 into elastic:9.4 May 12, 2026
34 of 35 checks passed
@PhilippeOberti PhilippeOberti deleted the backport/9.4/pr-268249 branch May 12, 2026 21:38
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