Stream syslog via Fluentd if you already collect logs with it or if a specific use case requires an additional component, for example, forwarding logs to different targets. If you want to benefit from a secure, trusted edge component with enterprise support and life-cycle management, see Syslog ingestion with ActiveGate.
In the case where Linux system syslog observability is the main focus, we recommend deploying OneAgent, which autodiscovers host syslog data, preserves topology context, and requires minimal configuration and maintenance.
You can send Syslog to Dynatrace using Fluentd. Configure Fluentd to send Syslog to Dynatrace generic ingest API.
Set up the flow from Syslog producer over Fluentd to Dynatrace with the following steps:
logs.ingest
(Ingest Logs) scope.In the examples below, you can send syslogs to a remote endpoint, which is Fluentd.
Configure Rsyslog on Linux Ubuntu to forward syslogs to a remote server, Fluentd.
You need to add the following line to the syslog daemon configuration file /etc/rsyslog.conf
(UDP protocol):
*.* @<fluentd host IP>:5140
*.*
instructs the daemon to forward all messages to the specified Fluentd instance listening on port 5140. <fluentd host IP>
needs to point to the IP address of Fluentd.@
symbols, ( @@
), as follows:*.* @@<fluentd host IP>:5140
Configure the F5 BIG-IP system to log to a remote syslog server (11.x - 17.x). Refer to the F5 BIG-IP documentation for procedures regarding remote Syslog configuration.
The Dynatrace software intelligence platform and the Davis AI engine depend on context-rich, quality data. You can provide the context for your data ingested via Generic log ingest API that supports a set of keys and semantic attributes. You can also provide custom attributes that don't require indexing in the Dynatrace Grail database.
Add the log.source
attribute based on the source of syslogs in Fluentd.
The syslog message often needs additional context to differentiate sources during analysis. In this example, there are two separate syslog endpoints exposed in Fluentd: one for the Linux syslogs, and the other one for F5 syslogs. This helps decorate log streams with meaningful log.source attribute
. The Fluentd configuration file needs to look like this:
<source>@type syslogport 5140bind 0.0.0.0tag system-linux</source><source>@type syslogport 5141bind 0.0.0.0tag system-f5</source>
You need to add log.source
attribute based on the fluentd tag.
<filter system-linux.**>@type record_transformer<record>log.source "linux syslogs"</record></filter><filter system-f5.**>@type record_transformer<record>log.source "f5 syslogs"</record></filter>
Refer to the Fluentd record_transformer filter plugin documentation for more details.