[9.3] [Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)#263149
Merged
kelvtanv merged 1 commit intoelastic:9.3from Apr 14, 2026
Merged
[9.3] [Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)#263149kelvtanv merged 1 commit intoelastic:9.3from
kelvtanv merged 1 commit intoelastic:9.3from
Conversation
…stic#260803) ## Summary [See issue](elastic#225838) - Happens on both the new attacks page and alerts page for any kpi that has an arbitrary list of items - Caused by content overflowing parent container - For example within the `Alerts by name` kpi, if there are many rows, the content is hidden and scrollable but still (invisibly) takes up space within the parent container - Fix the tree map kpi to be bounded within the parent container (so border does not overlap with content) and only make the graph portion scrollable ### To test 1. Setup lots of rules (enough to overflow the kpi) 2. Generate a bunch of alerts from those rules 3. Alternatively, generate a bunch of alerts with unique hostnames to overflow the `Top alerts by` kpi when sorting by `host.name` 4. Go to the summary section in alerts kpi and notice the large scrollable white space 5. Go to the tree map and make sure the graph is large, notice the graph overlaps the border of the bounding container and scrolling scrolls the entire bounding container Before: https://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135 After: https://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit 58479ea) # Conflicts: # x-pack/solutions/security/plugins/security_solution/public/detections/components/attacks/kpis/attacks_summary_panel.tsx
2 tasks
PhilippeOberti
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto9.3:Questions ?
Please refer to the Backport tool documentation