Dear Alan,

I have an idea, please suggest and correct me if I am wrong or right and this will work or not.

Suppose for auth requests I want the statistics of authorize module. So in listen.c I have seen a function call ret_code=process_authorize();. So whatever is the ret_code of this module according to that a server replies to NAS.

Under this there is a switch statement which deals with ret_code(). So I will take a global structure which consists of module return codes and will update here each return code variable for auth module.

Now for auth requests the moment auth_socket_recv() method is hit I will update my auth request counter so that it keeps track of the no. of auth requests anytime.
       
If you find this OK, the same thing I will follow for Accounting and Authentication requests as well.


Regards,
Himanshu Pandey



From: Alan DeKok <aland@deployingradius.com>
Sent: Thu, 25 Sep 2014 18:35:47
To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Subject: Re: Module Statistics in freeradius
Himanshu Pandey wrote:
> Adding something more to it. Like How many auth or accounting request
> received? How many of them failed? How
> many of them were OK,noop,reject etc.

 That information isn't tracked.

 If you want to modify the source, see src/main/modcall.c.  All of the
module handling is done there.

 Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Get your own FREE website, FREE domain & FREE mobile app with Company email.  
Know More >