You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if there is a CPU spike, it will send an alert, then a recovery alert, and then another alert if there is an intermittent spike.
I think there should probably be something like a delay between an alert and a recovery check to see if a recovery is really warranted.
Another possible way around this issue is to only send an alert after a certain amount of consecutive checks showed an alert is really necessary. That would cut down the amount of times that an alert would be sent for a short spike
The text was updated successfully, but these errors were encountered:
Currently if there is a CPU spike, it will send an alert, then a recovery alert, and then another alert if there is an intermittent spike.
I think there should probably be something like a delay between an alert and a recovery check to see if a recovery is really warranted.
Another possible way around this issue is to only send an alert after a certain amount of consecutive checks showed an alert is really necessary. That would cut down the amount of times that an alert would be sent for a short spike
The text was updated successfully, but these errors were encountered: