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

[Serverless][Security Solution] Alerts page is not refreshed after changing the status of the alert #167809

Closed
MadameSheema opened this issue Oct 2, 2023 · 5 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience consider-next fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Serverless Work as part of the Serverless project for its initial release Team:Detection Engine Security Solution Detection Engine Area 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

@MadameSheema
Copy link
Member

Describe the bug:

  • Alerts page is not refreshed after changing the status of the alert

Kibana/Elasticsearch Stack version:

Initial setup:

  • To have alerts generated by a detection rule

Steps to reproduce:

  1. Navigate to the alerts page
  2. Change the status of one of the alerts listed

Current behavior:

  • The page is not refreshed
Alerts.-.Kibana.8.webm

Expected behavior:

  • The page should be refreshed
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience triage_needed Team:Threat Hunting Security Solution Threat Hunting Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Serverless labels Oct 2, 2023
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@yctercero
Copy link
Contributor

PR with fix and tests - #168426

Trying to get merged in today, just waiting on CI.

@yctercero yctercero added Team:Detection Engine Security Solution Detection Engine Area consider-next fixed and removed triage_needed labels Oct 13, 2023
@crowens
Copy link

crowens commented Oct 24, 2023

There was a fix merged 2 weeks ago. Can this be closed @yctercero

@yctercero
Copy link
Contributor

Confirmed fix in Charlie's prod environment. Note in video it's a bit confusing as 200 new alerts were also generated in that moment, but there is a decrease of 10.

alerts_refresh.mov

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 consider-next fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Project:Serverless Work as part of the Serverless project for its initial release Team:Detection Engine Security Solution Detection Engine Area 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

8 participants