Log paths determine what happens with the incoming log messages. Messages coming from the sources listed in the log statement and matching all the filters are sent to the listed destinations.
To define a log path, add a log statement to the syslog-ng configuration file using the following syntax:
log {
source(s1); source(s2); ...
filter(f1); filter(f2); ...
destination(d1); destination(d2); ...
flags(flag1[, flag2...]);
};
![]() |
Warning |
|---|---|
Log statements are processed in the order they appear in the configuration file. |
All matching log statements are processed by default, so a single log message might be sent to the same destination several times, provided the destination is listed in several log statements.
This default behavior can be changed using the flags()
parameter. Flags apply to individual log paths; they are not global options. The
following flags available in syslog-ng:
final: Do not send the message to any further destination.
fallback: Process messages that were not processed by other log paths.
catchall: Process every message, regardless of its source.
flow-control: Stop reading messages from the source if the destination cannot accept them. See Section 8.3, “Managing incoming and outgoing messages with flow-control”.
For details on the individual flags, see Section 9.3, “Log path flags”. The
effect and use of the flow-control flag is detailed in Section 8.3, “Managing incoming and outgoing messages with flow-control”.
![]() |
Note |
|---|---|
Note that a message goes to every matching destination by
default. To change this behavior, use the |
© 2007 BalaBit IT Security
Please send your comments or documentation bugs to: documentation@balabit.com