> We already have 'queue' and 'deny' hooks - we can just plug in to that. > I've been using the attached plugin to do stats capturing to a dbm > database - I'd probably change the backend now (given some weirdness I've > been seeing with Berkeley DB under load), but the general concept has > worked well. Happy to have it generalised further too.
The only catch is this means you can't get statistics from queue plugins. I.e. I have two queue plugins that fire. The first one DECLINES unless there's something specific in the transaction notes. Once the final queue plugin run, we're out of luck. Actually, it looks like the reset_transaction hook will run after the queue hook. There's also the disconnect hook. Lots of hooks! -R
