On Feb 6, 2019, at 9:44 AM, R3DNano <r3dnano@gmail.com> wrote:
I'm trying to manage the global freeradius status from a remote location. The files under /var/log/radius/radacct are pretty detailed and have a lot of information about what is going on with the freeradius server. However, searching the old mailing list archives, I see there's a particular thread of someone asking how to send the radacct logs to a remote syslog being not a recommended practice.
Why not? It's fine.
What's a practical way of having this information for further analysis outside of the freeradius server? Send it to an SQL database somehow perhaps?
Also, about the logs sent to syslog (for further forwarding to a remote syslog server) - is there a way to customize what's being sent on those messages?
No. The server messages can't be customized. There are literally hundreds of different messages. If you need *additional* custom messages, see the "linelog" module. It can do custom log messages to syslog. You can then use "linelog" any place you want additional logging. Alan DeKok.