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

Alert suppression/aggregation - feature request #2

Open
ewilded opened this issue May 13, 2019 · 0 comments
Open

Alert suppression/aggregation - feature request #2

ewilded opened this issue May 13, 2019 · 0 comments

Comments

@ewilded
Copy link

ewilded commented May 13, 2019

It would be nice to have some sort of customiseable (so it can be adjusted/disabled in config at user's will) alert suppression mechanism.

For example, if there was more than 3 alerts within the last 20-seconds, just display another one with a message like 'More alerts suppressed, please see the C:\Program Files\Attack Monitor\logs\2019-05-13.txt log file for more details'. And add an option for how long to ignore alerts from being displayed after such threshold is reached. This could help prevent situations when (I experience this especially after wakeup from sleep) bunch of alerts queue up and it takes several minutes to get rid of them by clicking one after another, which at the same time can impede GUI usage of other active windows (e.g. web browser, that's exactly the spot where my 'full screen' option is on youtube/netflix :P).

I do understand this is a part and parcel of the early stage of learning so should gradually be less of a problem once proper learning rules are added in learning mode, however I do realize every system is unique and therefore everyone needs to adjust their own normalcy rules individually, so more users will face this issue regardless to the maturity of the pre-defined exceptions.json file coming with the installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant