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][Threat Hunting Investigations] browser page crashes when trying to change Stack by in Alerts Trend #175295

Closed
vitaliidm opened this issue Jan 23, 2024 · 6 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team triage_needed

Comments

@vitaliidm
Copy link
Contributor

Describe the bug:
browser page becomes unresponsible and crashes when trying to change Stack by in Alerts Trend

Kibana/Elasticsearch Stack version:
Tested in 8.13 only (main)

Steps to reproduce:

  1. Open rule details page with generated alerts
  2. Got to alerts tab
  3. Try to change Stack by filed in trend(histogram)
  4. Page becomes unresponsive and crashes

Screenshots (if relevant):

alerts.trend.crash.mov
@vitaliidm vitaliidm 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. Team:Threat Hunting:Investigations Security Solution Investigations Team labels Jan 23, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@angorayc angorayc self-assigned this Jan 24, 2024
@michaelolo24
Copy link
Contributor

@angorayc I tried testing this on siem dev and it doesn't seem to be happening anymore, but I'm not sure if there are some conditions involved in @vitaliidm's environment that may have caused this

@semd
Copy link
Contributor

semd commented Mar 13, 2024

@michaelolo24 I also tested this in main and 8.13 branches, and siem dev as well, and can not reproduce it either. @vitaliidm Can you still reproduce the error in your environment?

@vitaliidm
Copy link
Contributor Author

@michaelolo24 , @semd
Looks like it was fixed - I tried main and current 8.13, could not reproduce.

But when I switched my local env to January 23rd commits(date of creation of this ticket) I could easily reproduce it.

@semd
Copy link
Contributor

semd commented Mar 14, 2024

Okay, it might have been caused by a temporarily inconsistent state, if it's currently fixed in 8.13 branch we can close it.
Thanks for taking the time to report it @vitaliidm

@semd semd closed this as completed Mar 14, 2024
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 Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team triage_needed
Projects
None yet
Development

No branches or pull requests

5 participants