Tracking packet/s in the server

[Alan Buxey]

Hi,

>   The issue there is WHEN do you send traps?
> 
> - when the queue of delayed packets gets more than half full?
> - when the PPS IN-OUT > ... ?
> - how to rate limit the traps so that you don't get spammed by them?
> 
>   What criteria should be used?

perhaps another threshold/counter - eg no more than X per hour??  one advantage
of the trigger.conf is that it can be used to bootstrap an external process...so, for
example if the one RADIUS server is getting a little 'hot', I can instruct my S3/cloud/VM
system to spin up another VM and send a message to the load-balancer to say theres another
box it can use...and when things go quiet the server farm can be dynamically shrunk again.

alan