How does one set up flow-control throttling for events? I am using SEC to de-duplicate/debounce, and mostly use it to create tickets that document network availability. I would rather throttle or delay a ticket rather than ignoring it.
Periodically, I may get power events on campus. It would be normal for SEC to write 3-5 tickets an hour, but not out of the question to see 100-200 tickets for power events. Unfortunately, the resulting 'flood' tends to crash the SMTP ticket gateway. Has anyone created a queueing mechanism within the rules for SEC, or will this action need to happen outside of SEC? I suspect that it would need to be the latter, but I would not mind examples. Regards, Tim -- Tim Peiffer Network Support Engineer Office of Information Technology University of Minnesota/NorthernLights GigaPOP +1 612 626-7884 (desk) ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
