-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Improve alert with mininimal interval/duration and retention configuration keys #2558
Comments
Hi @ajgringo619 in the develop branch, i just added a feature to be able to tweek the alert plugin from the Glances configuration file:
This is just a first step. I also want to open the discussion regarding another enhancement by making the minimum time between two alerts configurable ? For example: First alert starts at 01:00:00 with a duration of 1 minutes. Actualy Glances will display 3 alerts. If we set the min_delay_between_events to 60 seconds, the future Glances version will display only one alerts. What do you think @ajgringo619 ? |
This looks great. As an additional setting, allow each type of alert to be configurable separately, so that a user can decide how long to show a critical alert over a warning. |
@ajgringo619 something like that:
|
This looks great - thank you! |
Done in the develop branch for the duration and interval configuration key. Configuration file example:
TODO: add retention for warning and critical. |
I would like to see
glances
to have the ability to remove warning/critical issue messages that are no longer relevant, either by time-out or by only displaying a set amount of messages. As you can see from the posted screenshot, my screen gets filled up pretty fast when there's a lot of stuff going on:Now, since these messages can still be relevant, I'm not suggesting automatically removing them; just give use the option to limit their number to something a little more reasonable.
The text was updated successfully, but these errors were encountered: