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
How do you perceive a feature, especially useful for SSDs, where in Alerts would be definable an Alert that would show when certain Bytes per Time are writen, i.e. 10 GB written in last minute?
I am requesting this feature because I saw a scenario where an app that was profiling the SSD in background, what was unwanted and also not triggered by the user, wrote 500 GB to it without a knowledge of a user. If there would be an early enough alert that something had written 50 GB in last, let's say minute, or maybe an earlier alert after 30 sec that there were 25 GB written in last 30 sec, the unwanted process could be stopped before wasting the rest of valuable GBs up to 500GB.
Thank you very much for considering this, best regards, God bless you, Kamil+
The text was updated successfully, but these errors were encountered:
skajp2018
changed the title
feature req: alert when bytes per time is writen
feature req: alert when specified bytes per time period were writen
Sep 5, 2019
Hi Guys,
Thanks for all of your good work.
How do you perceive a feature, especially useful for SSDs, where in Alerts would be definable an Alert that would show when certain Bytes per Time are writen, i.e. 10 GB written in last minute?
I am requesting this feature because I saw a scenario where an app that was profiling the SSD in background, what was unwanted and also not triggered by the user, wrote 500 GB to it without a knowledge of a user. If there would be an early enough alert that something had written 50 GB in last, let's say minute, or maybe an earlier alert after 30 sec that there were 25 GB written in last 30 sec, the unwanted process could be stopped before wasting the rest of valuable GBs up to 500GB.
Thank you very much for considering this, best regards, God bless you, Kamil+
The text was updated successfully, but these errors were encountered: