[Kea-users] Configuring LFC logger ?

[Marcin Siodelski]

Nicolas,

Yes, can you please open a ticket?

Thanks,
Marcin

On 12.04.2016 17:57, Chaigneau, Nicolas wrote:
>
> Hello Marcin,
>
>
> Thanks for your reply, which confirms what I suspected.
>
> I agree that this is not a major issue, and it can wait for a later
> release.
>
> Should I open a ticket for this ?
>
>
>
> Regards,
> Nicolas.
>
>
> > Hello Nicolas,
> >
> > Sorry for the delayed response to your post.
> >
> > No, there is currently no way to configure the logging for LFC from
> the Kea configuration file. The reason being that LFC is running in a
> separate process and this process has no built-in capability to
> read/understand Kea configuration file. At the time of writing LFC we
> envisaged the need for a dedicated LFC logger, but we did not
> implement it due to time constraints. There is a command line
> parameter exposed by the kea-lfc application which receives a
> name/location of the Kea configuration file, but it utterly ignores
> this parameter.
> >
> > I think it is a reasonable request to finally implement
> configuration parsing in the kea-lfc app, but this is not in scope for
> the upcoming release, so we can probably think about it for the 1.2
> release. In a mean time we'd need to stick with syslog.
> >
> > Marcin
> >
> > On 31.03.2016 15:28, Chaigneau, Nicolas wrote:
> >> Hello Kea friends,
> >>
> >>
> >> I have a question about LFC and logging:
> >>
> >> By default, the LFC process logs through syslog with facility "local0".
> >> I'm trying to make it log into a file. I've added the following in
> kea configuration file:
> >>
> >>
> >>                 {
> >>                         "name": "DhcpLFC",
> >>                         "output_options": [
> >>                                 {
> >>                                         "destination": "file",
> >>                                         "output":
> "/path-to-logs/kea1-open-lfc.log"
> >>                                 }
> >>                         ],
> >>                         "severity": "INFO"
> >>                 },
> >>
> >>
> >>
> >>
> >> But this does not work.
> >> The "name" (DhcpLFC) I've retrieved from the code, but it is
> probably wrong, since it is not listed in the available defined
> loggers (kea guide 17.1.1.1 "defined loggers").
> >>
> >> I'm not really sure this is feasible, since kea guide also states
> the following (about lfc command line process):
> >>
> >> "The -c argument specifies the configuration file. This is
> required, but not currently used by the process."
> >>
> >>
> >>
> >> So... is there a way (besides configuring syslog itself) to
> configure the LFC logs ?
> >>
> >>
> >>
> >>
> >> Thanks for your help.
>
> This message contains information that may be privileged or
> confidential and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not
> the intended recipient, you are not authorized to read, print, retain,
> copy, disseminate, distribute, or use this message or any part
> thereof. If you receive this message in error, please notify the
> sender immediately and delete all copies of this message.
>