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] Succeeded status filter is not working correctly under execution logs #137935

Open
ghost opened this issue Aug 3, 2022 · 4 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Rule Monitoring Security Solution Detection Rule Monitoring area impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@ghost
Copy link

ghost commented Aug 3, 2022

Related to: #136138, #139889

Describe the bug
Succeeded status filter is not working correctly under execution logs

Build info

VERSION : 8.4.0 BC1
Build: 54999
COMMIT: 58f7eaf0f8dc3c43cbfcd393e587f155e97b3d0d

Preconditions

  1. Kibana should be running
  2. Rule should created
  3. Execution logs Warning, Fail, success should be exist

Steps to Reproduce

  1. Navigate to security > Rule page
  2. Click on above created rule
  3. Navigate to execution tab
  4. From status drop down select the succeeded only
  5. Observe that warning and succeeded logs are displayed

Actual Result
succeeded status filter is not working correctly under execution logs

Expected Result
succeeded status filter should be work correctly under execution logs

Screen-cast

execution.logs.mp4

image

What's Working

  • This issue is not occurring for failed and warning
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.4.0 labels Aug 3, 2022
@ghost ghost self-assigned this Aug 3, 2022
@elasticmachine
Copy link
Contributor

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

@ghost ghost assigned MadameSheema and unassigned ghost Aug 3, 2022
@MadameSheema MadameSheema removed their assignment Aug 3, 2022
@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Detection Rule Management Security Detection Rule Management Team labels Aug 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@peluja1012 peluja1012 added the Feature:Rule Monitoring Security Solution Detection Rule Monitoring area label Aug 3, 2022
@banderror banderror removed their assignment Aug 4, 2022
@banderror
Copy link
Contributor

Could be caused by the same reasons as this one: #136138

@pborgonovi
Copy link
Contributor

Validated latest 8.15 BC and issue still exists:

Screen.Recording.2024-07-24.at.2.13.49.PM.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 Feature:Rule Monitoring Security Solution Detection Rule Monitoring area impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

No branches or pull requests

5 participants