Referencing earlier messages of the context
When creating the aggregated message, or in the various parameters of the grouping-by() parser, you can also refer to fields and values of earlier messages of the context by adding the @<distance-of-referenced-message-from-the-current> suffix to the macro. For example, if there are three log messages in a context, the ${HOST}@1 expression refers to the host field of the current (third) message in the context, the ${HOST}@2 expression refers to the host field of the previous (second) message in the context, ${PID}@3 to the PID of the first message, and so on. For example, the following message can be created from SSH login/logout messages: An SSH session for ${SSH_USERNAME}@1 from ${SSH_CLIENT_ADDRESS}@2 closed. Session lasted from ${DATE}@2 to ${DATE}.
|
|
Caution:
When referencing an earlier message of the context, always enclose the field name between braces, for example, ${PID}@3. The reference will not work if you omit the braces. |
|
|
NOTE:
To use a literal @ character in a template, use @@. |
Example: Referencing values from an earlier message
The following action can be used to log the length of an SSH session (the time difference between a login and a logout message in the context):
aggregate(
value('value name="MESSAGE" An SSH session for ${SSH_USERNAME}@1 from ${SSH_CLIENT_ADDRESS}@2 closed. Session lasted from ${DATE}@2 to ${DATE}')
)
For another example, see The grouping-by() parser in syslog-ng blog post
If you do not know in which message of the context contains the information you need, you can use the grep template function. For details, see grep.
Example: Using the grep template function
The following example selects the message of the context that has a username name-value pair with the root value, and returns the value of the auth_method name-value pair.
$(grep ("${username}" == "root") ${auth_method})To perform calculations on fields that have numerical values, see Numerical operations.
Options of grouping-by parsers
The grouping-by has the following options.
aggregate()
| Synopsis: | aggregate() |
Description: Specifies the message that syslog-ng OSE generates when the context is closed. This option is mandatory.
Note that the aggregate() option has access to every message of the context, and has the following options:
-
inherit-mode: This attribute controls which name-value pairs and tags are propagated to the newly generated message.
-
context: syslog-ng OSE collects every name-value pair from each message stored in the context, and includes them in the generated message. If a name-value pair appears in multiple messages of the context, the value in the latest message will be used. Note that tags are not merged, the generated message will inherit the tags assigned to the last message of the context.
-
last-message: Only the name-value pairs appearing in the last message are copied. If the context contains only a single message, then it is the message that triggered the action.
-
none: An empty message is created, without inheriting any tags or name-value pairs.
The default value of inherit-mode() is context.
For details on the message context, see Correlating messages using the grouping-by() parser.
-
-
tags: Adds the specified tag to the list of tags.
-
value: Adds a name-value pair to the generated message. You can include text, macros, template functions, and you can also reference every message of the context. For details on accessing other messages of the context, see Referencing earlier messages of the context.
having()
| Synopsis: | having() |
Description: Specifies a filter: syslog-ng OSE generates the aggregate message only if the result of the filter expression is true. Note that the having() filter has access to every message of the context. For details on accessing other messages of the context, see Referencing earlier messages of the context.
inject-mode()
| Synopsis: | inject-mode() |
Description: By default, the aggregated message that syslog-ng OSE generates is injected into the same place where the grouping-by() statement is referenced in the log path. To post the generated message into the internal() source instead, use the inject-mode() option in the definition of the parser.
Example: Sending triggered messages to the internal() source
To send the generated messages to the internal source, use the inject-mode("internal") option:
parser p_grouping-by {grouping-by(
...
inject-mode("internal")
);};
To inject the generated messages where the parser is referenced, use the inject-mode("pass-through") option:
parser p_grouping-by {grouping-by(
...
inject-mode("pass-through")
);};You can configure the generated message in the aggregate() option (see aggregate()). You can create an entire message, use macros and values extracted from the original message, and so on.
key()
| Synopsis: | key() |
Description: Specifies the key as a template (that is, the name of a name-value pair) that every message must have to be added to the context. The value of the key must be the same for every message of the context. For example, this can be a session-id parsed from firewall messages, and so on.
This is a mandatory option.
|
|
NOTE:
Messages that do not have a key will all belong to the same context. |
|
|
NOTE:
If the value of the key is static (for example, key("PROGRAM") instead of key("$PROGRAM")), all messages will belong to the same context. |
scope()
| Synopsis: | scope() |
Description: Specifies which messages belong to the same context. The following values are available:
-
process: Only messages that are generated by the same process of a client belong to the same context, that is, messages that have identical ${HOST}, ${PROGRAM} and ${PID} values.
-
program: Messages that are generated by the same application of a client belong to the same context, that is, messages that have identical ${HOST} and ${PROGRAM} values.
-
host: Every message generated by a client belongs to the same context, only the ${HOST} value of the messages must be identical.
-
global: Every message belongs to the same context. This is the default value.
timeout()
| Synopsis: | timeout([seconds]) |
Description: Specifies the maximum time to wait for all messages of the context to arrive. If no new message is added to the context during this period, the context is assumed to be complete and syslog-ng OSE generates and sends the triggered message (specified in the aggregate() option), and clears the context. If a new message is added to the context, the timeout period is restarted.
This option is mandatory, and its value must be equal to or greater than 1.
trigger()
| Synopsis: | trigger() |
Description: A filter that specifies the final message of the context. If the filter matches the incoming message, syslog-ng OSE generates and sends the triggered message (specified in the aggregate() option), and clears the context.
where()
| Synopsis: | where() |
Description: Specifies a filter condition. Messages not matching the filter will not be added to the context. Note that the where() filter has access only to the current message.
Enriching log messages with external data
To properly interpret the events that the log messages describe, you must be able to handle log messages as part of a system of events, instead of individual information chunks. The syslog-ng OSE application allows you to import data from external sources to include in the log messages, thus extending, enriching, and complementing the data found in the log message.
The syslog-ng OSE application currently provides the following possibilities to enrich log messages.
-
You can add name-value pairs from an external CSV file. For details, see Adding metadata from an external file.
-
You can resolve the IP addresses from log messages to include GeoIP information in the log messages. For details, see Looking up GeoIP data from IP addresses (DEPRECATED).
-
You can write custom Python modules to process the messages and add data from external files or databases. For details, see The Python Parser.
Adding metadata from an external file
In syslog-ng OSE version
The database file is a simple text file in comma-separated value (CSV) format, where each line contains the following information:
-
A selector or ID that appears in the log messages, or the name of a filter that matches the messages, for example, the hostname.
-
The name of the name-value pair that syslog-ng OSE adds to matching log messages.
-
The value of the name-value pairs.
For example, the following csv-file contains three lines identified with the IP address, and adds the host-role field to the log message.
192.168.1.1,host-role,webserver 192.168.2.1,host-role,firewall 192.168.3.1,host-role,mailserver
The database file:
The database file must comply with the RFC4180 CSV format, with the following exceptions and limitations:
-
The values of the CSV-file cannot contain line-breaks
To add multiple name-value pairs to a message, include a separate line in the database for each name-value pair, for example:
192.168.1.1,host-role,webserver 192.168.1.1,contact-person,"John Doe" 192.168.1.1,contact-email,johndoe@example.com
Technically, add-contextual-data() is a parser in syslog-ng OSE so you have to define it as a parser object.
Declaration:
parser p_add_context_data {
add-contextual-data(
selector("$HOST"),
database("context-info-db.csv"),
);
};
You can also add data to messages that do not have a matching selector entry in the database using the default-selector() option.
If you modify the database file, you have to reload syslog-ng OSE for the changes to take effect. If reloading syslog-ng OSE or the database file fails for some reason, syslog-ng OSE will keep using the last working database file.
Example: Adding metadata from a CSV file
The following example defines uses a CSV database to add the role of the host based on its IP address, and prefixes the added name-value pairs with .metadata. The destination includes a template that simply appends the added name-value pairs to the end of the log message.
@include "scl.conf"
source s_network {
network(port(5555));
};
destination d_local {
file("/tmp/test-msgs.log"
template("$MSG Additional metadata:[${.metadata.host-role}]")};
parser p_add_context_data {
add-contextual-data(selector("$SOURCEIP"), database("context-info-db.csv"), default-selector("unknown"), prefix(".metadata."));
};
log {
source(s_network);
parser(p_add_context_data);
destination(d_local);
};192.168.1.1,host-role,webserver 192.168.2.1,host-role,firewall 192.168.3.1,host-role,mailserver unknown,host-role,unknown