[Kea-users] kea-dhcp remote syslog

Geist, Dan (CCI-Atlanta) Dan.Geist at cox.com
Tue Oct 24 13:51:03 UTC 2023


It depends on how you want to manage your systems, but my preference is to let software do the things it’s best at. Kea can send to multiple logging targets, but you’ll probably get better flexibility to store/mangle/redirect messages if you use a service designed for that. Syslog-ng (or rsyslog, logstash,  etc.) have a lot more capabilities there.

Also, using the native syslog target kea (as opposed to the file mode) will likely yield performance increase on heavily loaded system as file handles are fairly expensive. Systemd’s logging facility is often incorporated at the core with outputs that are used by userspace apps like syslog-ng

Dan

From: Kea-users <kea-users-bounces at lists.isc.org> on behalf of DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
Date: Tuesday, October 24, 2023 at 9:39 AM
To: kea-users at lists.isc.org <kea-users at lists.isc.org>
Subject: [EXTERNAL] [Kea-users] kea-dhcp remote syslog
Hi all,

I have read in the documentation that multiple loggers can be setup.

But I don't quit understand how to setup remote logging.

thus far we have setup our logging locally using this config:
"loggers": [
    {
        "name": "kea-dhcp4",
        "output_options": [
            {
                "output": "/var/log/kea/kea-dhcp4.log"
            }
        ],
        "severity": "INFO",

        "debuglevel": 0
    }

So how can we setup additional logging to be forwarded to our syslog server?
(we are using syslog-ng locally)
Should we configure an additional logger to syslog, filter out the message locally and sent them to the remote logger ?

Any help is appreciated

Regards,

Ronald

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20231024/b75f6bc8/attachment-0001.htm>


More information about the Kea-users mailing list