On 24.3.2016 0.28, Hugh Irvine wrote: > Otherwise you can add your own custom time attributes in the current > request packet and post-process the logs to derive the deltas.
Maybe this recent addition to 4.16 patches would be helpful too? Added a new global configuration parameter: ResponseTimeThreshold 10 The value is a millisecond threshold for Radiator's response time. If the respose time is exceeded, a warning will be loggged. Here's an example of what it logs: Tue Mar 15 16:47:41 2016 577739: WARNING: Response time 16.804 ms for Access-Request id 236 exceeded 3 ms. (User: 'mikem', Client: 'DEFAULT' (default-client), Handler: '' (handler-identifier), Last AuthBy: 'FILE' (authby-identifier)) Currently this is a global setting that's not turned on by default. Alex, you mentioned about logging each request with the processing time. Which logfile this should go into? There's work underway to log just the messages Radiator sends and receives. This is separate from the current logging and is more like what AuthLog does. What AuthLog logs are the successful and failed authentications. The message log will log all messages. The log format is configurable. At least text (similar to like trace 5 packet dump), pcapng and JSON will be supported. Thanks, Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
