-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add support for Exceptions in Threshold rules #76631
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
woops - I thought Luke had created this issue, so directed the question at him, re-posted the question back to the creator. |
@Bananenbrei - which alert was this for? We now have many alerts available, I'm guessing this was the log threshold alert, or perhaps as part of the security solution. |
@pmuellr - this was in regards to the newly added Threshold rules in the Security Application (Security -> Detection). Exceptions (lists) are supported for the custom query rules but not for the threshold ones. |
Pinging @elastic/siem (Team:SIEM) |
This would be a great addition. |
This is indeed something that is missing in the current version. |
This PR adds exceptions support to Threshold rules #85103. |
Describe the feature:
Threshold rules currently do not seem to support Exceptions
Describe a specific use case for the feature:
I want to alert after a total of 10/20/50 unique ports have been queried but not if the IP Address belongs to a vulnerability scanner.
I want to alert after a total of 5 failed logon events happened but not for some specific users
The text was updated successfully, but these errors were encountered: