Metrics and timings

[Alan DeKok]

On Sep 15, 2016, at 1:45 PM, Louis Munro <lmunro at inverse.ca> wrote:
> I am curious to know what people use, if anything, to collect metrics about the various database calls that FreeRADIUS does.
> E.g. How fast is that LDAP server, or that SQL database?

  Not much.  The problem is that until recently, collecting lots of timing metrics was expensive.  i.e. it noticeably slowed systems down.

  Now.. it's 2016.  You can always buy more CPU power for small amounts of money.

> Sure you can measure some of that from the database side itself, and radsniff can give you some idea of the latency for your requests, but what do you do if you make multiple calls to a series of servers, some of which you may not have access to (cough.. AD server )?

  For 4.0, we'll be adding tons of metrics to the server.  They'll likely be an optional part of the build, but they will definitely be available.

> Short of adding metrics to each module I want them from (something I have played with using a statsd client library) is there a recommended way of getting that information?
> Especially if I want historical data to be able to compare against for anomaly detection or capacity planning?

  We'll be adding metrics to each individual module, along with a way to export them.

  Alan DeKok.