Starting with syslog-ng OSE
To embed multiple objects into a configuration object, use the following syntax. Note that you must enclose the configuration block between braces instead of parenthesis.
<type-of-top-level-object> <name-of-top-level-object> { channel { <configuration-objects> }; };
For example, to process a log file in a specific way, you can define the required processing rules (parsers and rewrite expressions) and combine them in a single object:
source s_apache { channel { source { file("/var/log/apache/error.log"); }; parser(p_apache_parser); }; }; log { source(s_apache); ... };
The s_apache source uses a file source (the error log of an Apache webserver) and references a specific parser to process the messages of the error log. The log statement references only the s_apache source, and any other object in the log statement can already use the results of the p_apache_parserparser.
NOTE: You must start the object definition with a channel even if you will use a junction, for example:
parser demo-parser() { channel { junction { channel { ... }; channel { ... }; }; }; };
If you want to embed configuration objects into sources or destinations, always use channels, otherwise the source or destination will not behave as expected. For example, the following configuration is good:
source s_filtered_hosts { channel{ source { pipe("/dev/pipe"); syslog(ip(192.168.0.1) transport("tcp")); syslog(ip(127.0.0.1) transport("tcp")); }; filter { netmask(10.0.0.0/16); }; }; };
You can define global variables in the configuration file. Global variables are actually name-value pairs. When syslog-ng processes the configuration file during startup, it automatically replaces `name` with value. To define a global variable, use the following syntax:
@define name "value"
The value can be any string, but special characters must be escaped (for details, see Regular expressions). To use the variable, insert the name of the variable enclosed between backticks (`, similarly to using variables in Linux or UNIX shells) anywhere in the configuration file. If backticks are meant literally, repeat the backticks to escape them. For example, ``not-substituted-value``.
The value of the global variable can be also specified using the following methods:
Without any quotes, as long as the value does not contain any spaces or special characters. In other word, it contains only the following characters: a-zA-Z0-9_..
Between apostrophes, in case the value does not contain apostrophes.
Between double quotes, in which case special characters must be escaped using backslashes (\).
TIP: The environmental variables of the host are automatically imported and can be used as global variables.
In syslog-ng OSE
For example, if an application is creating multiple log files in a directory, you can store the path in a global variable, and use it in your source definitions.
@define mypath "/opt/myapp/logs" source s_myapp_1 { file("`mypath`/access.log" follow-freq(1)); }; source s_myapp_2 { file("`mypath`/error.log" follow-freq(1)); }; source s_myapp_3 { file("`mypath`/debug.log" follow-freq(1)); };
The syslog-ng OSE application will interpret this as:
@define mypath "/opt/myapp/logs" source s_myapp_1 { file("/opt/myapp/logs/access.log" follow-freq(1)); }; source s_myapp_2 { file("/opt/myapp/logs/error.log" follow-freq(1)); }; source s_myapp_3 { file("/opt/myapp/logs/debug.log" follow-freq(1)); };
To increase its flexibility and simplify the development of additional modules, the syslog-ng OSE application is modular. The majority of syslog-ng OSE's functionality is in separate modules. As a result, it is also possible to fine-tune the resource requirements of syslog-ng OSE (for example, by loading only the modules that are actually used in the configuration, or simply omitting modules that are not used but require large amount of memory).
Each module contains one or more plugins that add some functionality to syslog-ng OSE (for example, a destination or a source driver).
To display the list of available modules, run the syslog-ng --version command.
To display the description of the available modules, run the syslog-ng --module-registry command.
To customize which modules syslog-ng OSE automatically loads when syslog-ng OSE starts, use the --default-modules command-line option of syslog-ng OSE.
To request loading a module from the syslog-ng OSE configuration file, see Loading modules.
For details on the command-line parameters of syslog-ng OSE mentioned in the previous list, see the syslog-ng OSE man page at The syslog-ng manual page.
The syslog-ng Open Source Edition application loads every available module during startup.
To load a module that is not loaded automatically, include the following statement in the syslog-ng OSE configuration file:
@module <module-name>
Note the following points about the @module statement:
The @module statement is a top-level statement, that is, it cannot be nested into any other statement. It is usually used immediately after the @version statement.
Every @module statement loads a single module: loading multiple modules requires a separate @module statement for every module.
In the configuration file, the @module statement of a module must be earlier than the module is used.
NOTE: To disable loading every module automatically, set the autoload-compiled-modules global variable to 0 in your configuration file:
@define autoload-compiled-modules 0
Note that in this case you have to explicitly load the modules you want to use.
To ensure that a module is loaded, include the following statement in the syslog-ng OSE configuration file or the external files included in the configuration file:
@requires <module-name>
NOTE: If you include the @requires statement in the:
Note that this is not true for modules marked as mandatory. You can make a dependency module mandatory by defining an error message after the @requires <module-name> statement, for example:
@requires http "The http() driver is required for elasticsearch-http(). Install syslog-ng-mod-http to continue."
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center