syslog-ng Open Source Edition 3.16 - Administration Guide

Install the syslog-ng application on the host. For details installing syslog-ng on specific operating systems, see Installing syslog-ng.

Configure the local sources to collect the log messages of the host. Starting with version 3.2, syslog-ng OSE automatically collects the log messages that use the native system logging method of the platform, for example, messages from /dev/log on Linux, or /dev/klog on FreeBSD. For a complete list of messages that are collected automatically, see system: Collecting the system-specific log messages of a platform.

To configure syslog-ng OSE, edit the syslog-ng.conf file with any regular text editor application. The location of the configuration file depends on how you installed syslog-ng OSE. Native packages of a platform (like the ones downloaded from Linux repositories) typically place the configuration file under the /etc/syslog-ng/ directory.

Add sources to collect the messages from your log files. File sources look like this:

source s_myfilesource {
    file("/var/log/myapplication.log" follow-freq(1));
};

Name every source uniquely. For details on configuring file sources, see file: Collecting messages from text files.

source s_local {
    system();
    internal();
};

Create a network destination that points directly to the syslog-ng server, or to a local relay. The network destination greatly depends on the protocol that your log server or relay accepts messages. Many systems still use the legacy BSD-syslog protocol (RFC3162) over the unreliable UDP transport:

destination d_network { network("10.1.2.3" transport("udp")); };

However, if possible, use the much more reliable IETF-syslog protocol over TCP transport:

destination d_network {
    syslog("10.1.2.3" transport("tcp"));
};

Create a log statement connecting the local sources to the syslog-ng server or relay. For example:

log {
    source(s_local); destination(d_network);
};

If the logs will also be stored locally on the host, create local file destinations.

destination d_local {
    file("/var/log/messages");
};

Create a log statement connecting the local sources to the file destination.

log {
    source(s_local); destination(d_local);
};

Set filters, macros and other features and options (for example TLS encryption) as necessary.

@version: 3.16
@include "scl.conf"
source s_local {
    system(); internal();
};
destination d_local {
    file("/var/log/messages");
};
log {
    source(s_local); destination(d_local);
};

@version: 3.16
@include "scl.conf"
source s_local {
    system(); internal();
};
destination d_syslog_tcp {
    syslog("192.168.1.1" transport("tcp") port(2010));
};
log {
    source(s_local);destination(d_syslog_tcp);
};

Install the syslog-ng application on the host. For details installing syslog-ng on specific operating systems, see Installing syslog-ng.

Starting with version 3.2, syslog-ng OSE automatically collects the log messages that use the native system logging method of the platform, for example, messages from /dev/log on Linux, or /dev/klog on FreeBSD. For a complete list of messages that are collected automatically, see system: Collecting the system-specific log messages of a platform.

To configure syslog-ng OSE, edit the syslog-ng.conf file with any regular text editor application. The location of the configuration file depends on how you installed syslog-ng OSE. Native packages of a platform (like the ones downloaded from Linux repositories) typically place the configuration file under the /etc/syslog-ng/ directory.

Configure the network sources that collect the log messages sent by the clients and relays. How the network sources should be configured depends also on the capabilities of your client hosts: many older networking devices support only the legacy BSD-syslog protocol (RFC3164) using UDP transport:

source s_network {
    syslog(ip(10.1.2.3) transport("udp"));
};

However, if possible, use the much more reliable TCP transport:

source s_network {
    syslog(ip(10.1.2.3) transport("tcp"));
};

For other options, see syslog: Collecting messages using the IETF syslog protocol (syslog() driver) and tcp, tcp6, udp, udp6: Collecting messages from remote hosts using the BSD syslog protocol— OBSOLETE.

Create local destinations that will store the log messages, for example file- or program destinations. The default configuration of syslog-ng OSE places the collected messages into the /var/log/messages file:

destination d_local {
    file("/var/log/messages");
};

If you want to create separate logfiles for every client host, use the ${HOST} macro when specifying the filename, for example:

destination d_local {
    file("/var/log/messages_${HOST}");
};

For details on further macros and how to use them, see template and rewrite: Format, modify, and manipulate log messages.

Create a log statement connecting the sources to the local destinations.

log {
    source(s_local); source(s_network); destination(d_local);
};

Set filters, options (for example TLS encryption) and other advanced features as necessary.

@version: 3.16
@include "scl.conf"
options {
    time-reap(30);
    mark-freq(10);
    keep-hostname(yes);
};
source s_local {
    system(); internal();
};
source s_network {
    syslog(transport(tcp));
};
destination d_logs {
    file(
        "/var/log/syslog-ng/logs.txt"
        owner("root")
        group("root")
        perm(0777)
        );
    };
log {
    source(s_local); source(s_network); destination(d_logs);
};

Install the syslog-ng application on the host. For details installing syslog-ng on specific operating systems, see Installing syslog-ng.

Configure the network sources that collect the log messages sent by the clients.

Create a network destination that points to the syslog-ng server.

Create a log statement connecting the network sources to the syslog-ng server.

Configure the local sources that collect the log messages of the relay host.

Create a log statement connecting the local sources to the syslog-ng server.

Enable the keep-hostname() and disable the chain-hostnames() options. (For details on how these options work, see chain-hostnames().)

Set filters and options (for example TLS encryption) as necessary.

@version: 3.16
@include "scl.conf"
options {
    time-reap(30);
    mark-freq(10);
    keep-hostname(yes);
    chain-hostnames(no);
};
source s_local {
    system(); internal();
};
source s_network {
    syslog(transport(tcp));
};
destination d_syslog_tcp {
    syslog("192.168.1.5" transport("tcp") port(2010));
};
log {
    source(s_local); source(s_network);
    destination(d_syslog_tcp);
};