[Security Solution][Alert KPI] Fix white space bug in alert KPIs#260803
Merged
kelvtanv merged 13 commits intoelastic:mainfrom Apr 14, 2026
Merged
[Security Solution][Alert KPI] Fix white space bug in alert KPIs#260803kelvtanv merged 13 commits intoelastic:mainfrom
kelvtanv merged 13 commits intoelastic:mainfrom
Conversation
kelvtanv
added
backport:all-open
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
PhilippeOberti
requested changes
Apr 1, 2026
Contributor
PhilippeOberti
left a comment
PhilippeOberti
left a comment
There was a problem hiding this comment.
While this fixes the empty space issue, it introduces an unwanted behavior on smaller screens.
This is the current behavior on main
Screen.Recording.2026-04-01.at.4.42.57.PM.mov
And this is the behavior on this branch
Screen.Recording.2026-04-01.at.4.40.43.PM.mov
Contributor
Author
Are you referring to how the kpi rows turn into cards? If so, I think that is how its supposed to function based on this EuiMemoryTable attribute, and in fact happens on I can change the responsiveBreakpoint for each of the kpis to be Screen.Recording.2026-04-01.at.9.24.06.PM.mov |
Contributor
No I meant on |
PhilippeOberti
approved these changes
Apr 13, 2026
Contributor
PhilippeOberti
left a comment
PhilippeOberti
left a comment
There was a problem hiding this comment.
Now the behavior seems correct, thanks for fixing this!
I would change the release_note:skip label into release_note:fix for docs to pick this up.
PhilippeOberti
added
the
Team:Threat Hunting:Investigations
Contributor
|
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
kelvtanv
added
release_note:fix
and removed
release_note:skip
Contributor
|
Starting backport for target branches: 8.19, 9.2, 9.3, 9.4 https://github.com/elastic/kibana/actions/runs/24400582568 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Apr 14, 2026
…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)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Apr 14, 2026
#260803) (#263070) # Backport This will backport the following commits from `main` to `9.4`: - [[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)](#260803) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kelvin Tan","email":"141756464+kelvtanv@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-04-14T13:05:29Z","message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.4.0","v9.5.0"],"title":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs","number":260803,"url":"https://github.com/elastic/kibana/pull/260803","mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/260803","number":260803,"mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}}]}] BACKPORT--> Co-authored-by: Kelvin Tan <141756464+kelvtanv@users.noreply.github.com>
mbondyra
added a commit
to mbondyra/kibana
that referenced
this pull request
Apr 14, 2026
* commit '11ed3645c5ededae2a6e29f2a79b31f52208b441': (157 commits) remove sync register uiAction methods (elastic#254590) [performance] Apply minimal auth to the search route (elastic#257497) [ES|QL] Reports correctly the controls server side errors (elastic#263020) [SecuritySolution][Navigation] Enable classic nav updates (elastic#262358) [Inference] Use pretty name and logo on feature settings page (elastic#262531) [Security Solution] fix AT-AB cypress test (elastic#262991) [SigEvents] Seed sigevents env script (elastic#261172) Adjust conditions for validating no refetch for expanded row (elastic#262978) [Agent Builder] update copy for the announcement modal (elastic#263034) [Search] Hide index management links for users without privileges (elastic#262627) Simplify OAS schema for GET `/api/spaces/space` query params (elastic#260831) Fix fleet output OAS regressions: SSL type explosion and Kafka union wrappers (elastic#260842) [Dashboards in chat] fix agent confusing the axes in a horizontal chat (elastic#263064) [One Workflow] Add alert state checkbox UI for workflow connector (elastic#259770) [One Workflow] Deprecate legacy Cases step types in workflow authoring (elastic#262070) skip failing test suite (elastic#248090) fix flaky test: MonitorDetails filter apply button not enabled (elastic#260788) fix: propagate AbortSignal to executeAsReasoningAgent for task cancellation (elastic#262811) [Security Solution][Alert KPI] Fix white space bug in alert KPIs (elastic#260803) [Streams] Move helpers and format_size_unit to utils folder (elastic#262550) ... # Conflicts: # x-pack/platform/plugins/shared/dashboard_agent/public/attachment_types/canvas_integration/dashboard_canvas_content.test.tsx # x-pack/platform/plugins/shared/dashboard_agent/public/attachment_types/canvas_integration/dashboard_canvas_content.tsx # x-pack/platform/plugins/shared/dashboard_agent/public/attachment_types/canvas_integration/use_register_canvas_action_buttons.ts # x-pack/platform/plugins/shared/dashboard_agent/public/attachment_types/index.test.tsx # x-pack/platform/plugins/shared/dashboard_agent/public/attachment_types/index.tsx
This was referenced Apr 14, 2026
kelvtanv
added a commit
to kelvtanv/kibana
that referenced
this pull request
Apr 14, 2026
…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
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kelvtanv
added a commit
to kelvtanv/kibana
that referenced
this pull request
Apr 14, 2026
…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
kelvtanv
added a commit
to kelvtanv/kibana
that referenced
this pull request
Apr 14, 2026
…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
kelvtanv
added a commit
that referenced
this pull request
Apr 14, 2026
#260803) (#263149) # Backport This will backport the following commits from `main` to `9.3`: - [[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)](#260803) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kelvin Tan","email":"141756464+kelvtanv@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-04-14T13:05:29Z","message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.4.0","v9.5.0"],"title":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs","number":260803,"url":"https://github.com/elastic/kibana/pull/260803","mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/263070","number":263070,"state":"MERGED","mergeCommit":{"sha":"421b14f38b985ea8cec5ede61aebcbb71abd22dd","message":"[9.4] [Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803) (#263070)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.4`:\n- [[Security Solution][Alert KPI] Fix white space bug in alert KPIs\n(#260803)](https://github.com/elastic/kibana/pull/260803)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Kelvin Tan <141756464+kelvtanv@users.noreply.github.com>"}},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/260803","number":260803,"mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}}]}] BACKPORT-->
kelvtanv
added a commit
that referenced
this pull request
Apr 14, 2026
#260803) (#263150) # Backport This will backport the following commits from `main` to `9.2`: - [[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)](#260803) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kelvin Tan","email":"141756464+kelvtanv@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-04-14T13:05:29Z","message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.4.0","v9.5.0"],"title":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs","number":260803,"url":"https://github.com/elastic/kibana/pull/260803","mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/263070","number":263070,"state":"MERGED","mergeCommit":{"sha":"421b14f38b985ea8cec5ede61aebcbb71abd22dd","message":"[9.4] [Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803) (#263070)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.4`:\n- [[Security Solution][Alert KPI] Fix white space bug in alert KPIs\n(#260803)](https://github.com/elastic/kibana/pull/260803)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Kelvin Tan <141756464+kelvtanv@users.noreply.github.com>"}},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/260803","number":260803,"mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}}]}] BACKPORT-->
kelvtanv
added a commit
that referenced
this pull request
Apr 14, 2026
…Is (#260803) (#263152) # Backport Sanity check: https://github.com/user-attachments/assets/cc21ed7d-5e32-45b3-8b6d-677be0e0a23a This will backport the following commits from `main` to `8.19`: - [[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)](#260803) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kelvin Tan","email":"141756464+kelvtanv@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-04-14T13:05:29Z","message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Threat Hunting:Investigations","backport:all-open","v9.4.0","v9.5.0"],"title":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs","number":260803,"url":"https://github.com/elastic/kibana/pull/260803","mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/263070","number":263070,"state":"MERGED","mergeCommit":{"sha":"421b14f38b985ea8cec5ede61aebcbb71abd22dd","message":"[9.4] [Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803) (#263070)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.4`:\n- [[Security Solution][Alert KPI] Fix white space bug in alert KPIs\n(#260803)](https://github.com/elastic/kibana/pull/260803)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Kelvin Tan <141756464+kelvtanv@users.noreply.github.com>"}},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/260803","number":260803,"mergeCommit":{"message":"[Security Solution][Alert KPI] Fix white space bug in alert KPIs (#260803)\n\n## Summary\n\n[See issue](https://github.com/elastic/kibana/issues/225838)\n\n- Happens on both the new attacks page and alerts page for any kpi that\nhas an arbitrary list of items\n- Caused by content overflowing parent container \n- For example within the `Alerts by name` kpi, if there are many rows,\nthe content is hidden and scrollable but still (invisibly) takes up\nspace within the parent container\n- Fix the tree map kpi to be bounded within the parent container (so\nborder does not overlap with content) and only make the graph portion\nscrollable\n\n### To test\n1. Setup lots of rules (enough to overflow the kpi)\n2. Generate a bunch of alerts from those rules\n3. Alternatively, generate a bunch of alerts with unique hostnames to\noverflow the `Top alerts by` kpi when sorting by `host.name`\n4. Go to the summary section in alerts kpi and notice the large\nscrollable white space\n5. Go to the tree map and make sure the graph is large, notice the graph\noverlaps the border of the bounding container and scrolling scrolls the\nentire bounding container\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/be6683c7-8590-495f-bc89-fce7182af135\n\nAfter:\n\n\n\nhttps://github.com/user-attachments/assets/7b4d53c7-cfd4-406f-8955-80217b5dd09e\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"58479ea7a8c04967d6805239f5f7e192f1d9b584"}}]}] BACKPORT-->
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
5 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.
Summary
See issue
Alerts by namekpi, if there are many rows, the content is hidden and scrollable but still (invisibly) takes up space within the parent containerTo test
Top alerts bykpi when sorting byhost.nameBefore:
prev.mov
After:
whitespace.bug.fix.mov
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelinesbackport:*labels.