[RADIATOR] "Wellness" metric

[Jose Borges Ferreira]

Hi!
On a high level, you can do something like this:

On a PreClientHook ( one of the first hooks to be called ) or on
PreProcessingHook ( to keep things under the same Handler section ) you can
add something like this:

     $p->{RecvMicroTime} = &Time::HiRes::time();

And access it on the way out on the PostProcessingHook:

    my $proc_time = &Time::HiRes::time() - $op->{RecvMicroTime};
   &main::log($main::LOG_NOTICE, sprintf("this request took :%.6f secs
",$proc_time));

You can also access this value on any other Hook using the $op hash. This
can be useful to profile all your Auth clauses.

I almost forgot, you must include Time::HiRes somewhere, probably under
StartupHook.

Let me know if you need extra help


José Borges Ferreira

Ted Turner <http://www.brainyquote.com/quotes/authors/t/ted_turner.html>  -
"Sports is like a war without the killing."

On Mon, Sep 21, 2009 at 8:34 PM, Dominic J. Eidson <deidson at seton.org>wrote:

> While troubleshooting some Wireless issues, the vendor in question is
> trying to blame Radiator for being too slow in responding to radius
> requests, and claiming this is causing issues with roaming.
>
> Is there an easy way (using Hooks?) to include the amount of time it's
> taking to process a RADIUS request, or some other "wellness" metric we
> can use to compare times without problems to times with problems?
>
>
>  - d.
>
>
> --
> Dominic J. Eidson
> Sr. Network Engineer
> Seton Family of Hospitals
> 512-324-1000 x18711
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20090921/bf63e151/attachment.html