capturing radius performance metrics

[Munroe Sollog]

For those of you using radsniff for stats collection, has anyone had any
luck using the telgraf collectd plugin?  radsniff seems to work fine to
collectd but when I plumb it to telegraf, telegraf complains about invalid
packet length.  I have a bug open for telegraf, but I was wondering if
anyone else has the same issue.

https://github.com/influxdata/telegraf/tree/master/plugins/parsers/collectd


On Fri, Jan 3, 2020 at 6:05 PM Nathan Ward <lists+freeradius at daork.net>
wrote:

>
> > On 4/01/2020, at 10:15 AM, Munroe Sollog <mus3 at lehigh.edu> wrote:
> >
> > I would like to monitor the ongoing real-world performance of my
> freeradius
> > server.  In this case, I'm defining performance as time between receiving
> > request and sending answer.  I have used radsniff and radclient to do
> some
> > benchmarking, but neither really seem like a sustainable or appropriate
> > solution for long-term data collection in a production environment.
>
> You can have radsniff write to a collectd socket. I have this in many many
> production servers, it works very well.
>
> Collectd can write out many formats, including to other collection
> services over a network.
>
> Of course, it shows packet rate etc. stats rather than radius process
> internal stats, but it gets you most of the way there.
>
> --
> Nathan Ward
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html



-- 
Munroe Sollog
Senior Network Engineer
munroe at lehigh.edu