[RADIATOR] logging (radiator and authlog) and accounting to ElasticSearch

[Hartmaier Alexander]

On 2014-04-02 20:57, Heikki Vatiainen wrote:
> On 04/01/2014 02:59 PM, Hartmaier Alexander wrote:
>
>> I think extending LogFormat is the right way to go because one might
>> want to log to a file or database in json or yaml as well.
>> What I still haven't figured out is a config format.
>> Enabling to pass a Perl sub to LogFormat would be the most flexible
>> option but not the most user friendly.
>>
>> Ideas?
> Wouldn't subclassing Log FILE work. Or maybe subclassing LogGeneric
> directly? I'd think keeping Log FILE as simple and straight forward
> would be a good goal since sometimes (Trace 4) a lot of traffic will
> pass through it.
I just checked, LogFormat is indeed defined in LogFILE.pm, I thought it
is shared by different logging classes and defined in a base class.
I don't care so much where it is defined but how.
Do you think configuring a Perl sub that returns a serialized string is
the way to go for structured logging?
I was thinking about writing a Log module that uses Log::Any, Log4perl
or Log::Dispatch so that you can do everything these modules support.
My only concern is that the logging module affects Radiator and if e.g.
RabbitMQ is down and logs can't be stored Radiator stops working.
This might be intended if logging is an absolute requirement, but others
might prefer availability over logging. Ideally this should be configurable.

What happens for the LogSQL class if the database goes down?

Is there some documentation how to write a Log class? I looks like It
only has to have the ConfigKeywords hash, subclass from
Radius::LogGeneric and an initialize and log sub.

Is there anything special I need to do to allow a ConfigKeyword to hold
a Perl sub?

BR Alex

>
>
> Thanks,
> Heikki
>



*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
Handelsgericht Wien, FN 79340b
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then
delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*