Re^4: Email Thresholding

Good thought. The email notification only needs to be rate limited for each event:

Event A happens, send email.
Event B happens 5 minutes later, send email on Event B.
Five minutes later there are 10 more Event A's, do not send email out for these repeated events.
Event C happens 30 minutes, send email.
Etc.

Comment on Re^4: Email Thresholding

Replies are listed 'Best First'.
Re^5: Email Thresholding by aaron_baugher (Curate) on Apr 06, 2015 at 21:33 UTC
In that case, I'd probably have a config file that saves each event type along with a timestamp of the last email sent for that type. That could be done with any module that can save key/value pairs in a file. Then, in pseudo-code: `when there is an event, get the type (A) if there is a timestamp saved for A and if the timestamp is less than 1 hour old do nothing otherwise send an email about A and update the timestamp for A with the current time` [download] Do it like that, and you can run your script as often as you like without getting extra emails. Aaron B. Available for small or large Perl jobs and *nix system administration; see my home node.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Email Thresholding
by aaron_baugher (Curate) on Apr 06, 2015 at 21:33 UTC

In that case, I'd probably have a config file that saves each event type along with a timestamp of the last email sent for that type. That could be done with any module that can save key/value pairs in a file. Then, in pseudo-code:

when there is an event, get the type (A)
if there is a timestamp saved for A
  and if the timestamp is less than 1 hour old
    do nothing
otherwise send an email about A
  and update the timestamp for A with the current time
[download]

Do it like that, and you can run your script as often as you like without getting extra emails.

Aaron B.
Available for small or large Perl jobs and *nix system administration; see my home node.

[reply]
[d/l]