The iptables parser can parse the log messages of the iptables command. Available in version 3.16 and later.

Declaration

@version: 3.38
@include "scl.conf"
log {
    <a href="/syslog-ng.github.io/admin-guide/200_About/002_Glossary#source" class="nav-link content-tooltip">source</a> { system(); };
    <a href="/syslog-ng.github.io/admin-guide/200_About/002_Glossary#parser" class="nav-link content-tooltip">parser</a> { iptables-parser(); };
    <a href="/syslog-ng.github.io/admin-guide/200_About/002_Glossary#destination" class="nav-link content-tooltip">destination</a> { ... };
};

The iptables-parser() is actually a reusable configuration snippet configured to parse iptables messages. For details on using or writing such configuration snippets, see Reusing configuration blocks. You can find the source of the iptables configuration snippet on GitHub.

prefix()

Synopsis: prefix()

Description: Insert a prefix before the name part of the parsed name-value pairs to help further processing. For example:

  • To insert the my-parsed-data. prefix, use the prefix(my-parsed-data.) option.

  • To refer to a particular data that has a prefix, use the prefix in the name of the macro, for example, ${my-parsed-data.name}.

  • If you forward the parsed messages using the IETF-syslog protocol, you can insert all the parsed data into the SDATA part of the message using the prefix(.SDATA.my-parsed-data.) option.

Names starting with a dot (for example, .example) are reserved for use by syslog-ng OSE. If you use such a macro name as the name of a parsed value, it will attempt to replace the original value of the macro (note that only soft macros can be overwritten, see Hard versus soft macros. To avoid such problems, use a prefix when naming the parsed values, for example, prefix(my-parsed-data.)

By default, iptables-parser() uses the .iptables. prefix. To modify it, use the following format:

parser {
    iptables-parser(prefix("myprefix."));
};

Updated: