Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security Solution] Closing all alerts on the last page of alerts table shows an empty list #169540

Open
damianpfister opened this issue Oct 23, 2023 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team

Comments

@damianpfister
Copy link

Describe the bug: Closing all alerts on the second page of alerts shows an empty list

Kibana/Elasticsearch Stack version: 8.10.2

Server OS version: ESS

Browser and Browser OS versions: Chrome Latest

Elastic Endpoint version: N/A

Original install method (e.g. download page, yum, from source, etc.): N/A

Functional Area (e.g. Endpoint management, timelines, resolver, etc.): Alert Management

Steps to reproduce:
When this customer closes a full list of alerts in the Security UI, that page remains empty until clicking back to the previous page, yet the page number drops suggesting no alerts exist at all.
The customer provided a video recording of this to show what they mean, along with a HAR file.
The workaround is a page refresh or clicking on "page 1" again.

Current behavior: When this customer closes a full list of alerts in the Security UI, that page remains empty until clicking back to the previous page, yet the page number drops suggesting no alerts exist at all.

Expected behavior: The page should not be empty

Screenshots (if relevant):
See https://github.com/elastic/sdh-security-team/issues/738

Errors in browser console (if relevant): N/A

Provide logs and/or server output (if relevant): N/A

Any additional context (logs, chat logs, magical formulas, etc.): N/A

@damianpfister damianpfister added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Oct 23, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@MadameSheema MadameSheema added Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Investigations Security Solution Investigations Team labels Oct 23, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@damianpfister
Copy link
Author

Any thoughts on what might be happening here @michaelolo24 @PhilippeOberti ?

@PhilippeOberti
Copy link
Contributor

Haven't looked at why this is happening yet, but I can easily reproduce the issue locally.

Screen.Recording.2023-11-27.at.3.32.11.PM.mov

This seems like a pretty low priority to me as there are many workarounds:

  • clicking on any other page in the pagination at the bottom of the table
  • refresh the page

But we should look into it at some point!

@PhilippeOberti PhilippeOberti changed the title [Security Solution] Closing all alerts on the second page of alerts shows an empty list [Security Solution] Closing all alerts on the last page of alerts table shows an empty list Nov 27, 2023
@PhilippeOberti PhilippeOberti added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed triage_needed labels Nov 27, 2023
@111andre111
Copy link

Probably related?
#171059

@michaelolo24 michaelolo24 added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Feb 20, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@michaelolo24
Copy link
Contributor

Guessing the table fails to reset the current page to the new last page after closing the alerts. Guessing some state setting may neeed to be updated on close, like if pageX has no more data, go to pageX - 1 on alert status change...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

No branches or pull requests

7 participants