rsyslog

(Optional) Activate Rsyslog file monitoring module. If you want to watch/monitor specific log files, then you have to activate the imfile module by adding this to your rsyslog.conf:

module(load="imfile" PollingInterval="10") #needs to be done just once

Create a /etc/rsyslog.d/datadog.conf file.

Set the log files to monitor and configure the destination endpoint. Add the following in /etc/rsyslog.d/datadog.conf.

## For each file to send
input(type="imfile" ruleset="infiles" Tag="<APP_NAME_OF_FILE1>" File="<PATH_TO_FILE1>")

## Set the Datadog Format to send the logs
$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - - %msg%\n"

## Define the destination for the logs
ruleset(name="infiles") {
    action(type="omfwd" target="intake.logs.datadoghq.com" protocol="tcp" port="10514" template="DatadogFormat")
}

(Optional) TLS Encryption: While sending your logs directly from Rsyslog to your Datadog account, if you want to add TLS encryption, take the following steps.

• Install rsyslog-gnutls:

  sudo apt-get install rsyslog-gnutls ca-certificates
  

• Modify your /etc/rsyslog.d/datadog.conf to end with the following content:

  ## Define the destination for the logs
  $DefaultNetstreamDriverCAFile /etc/ssl/certs/ca-certificates.crt
  ruleset(name="infiles") {
    action(type="omfwd" protocol="tcp" target="intake.logs.datadoghq.com" port="10516" template="DatadogFormat" StreamDriver="gtls" StreamDriverMode="1" StreamDriverAuthMode="x509/name" StreamDriverPermittedPeers="*.logs.datadoghq.com" )
  }
  

Restart Rsyslog and your new logs are forwarded directly to your Datadog account.

sudo service rsyslog restart

Associate those logs with the host metrics and tags. To make sure that these logs are associated with the metrics and tags from the same host in your Datadog account, set the HOSTNAME in your rsyslog.conf to match the hostname of your Datadog metrics. If you did not specify any hostname in your configuration file for the metrics using datadog.conf or datadog.yaml, then you do not need to change anything. If you did specify a custom hostname for your metric, replace the %HOSTNAME% value in the format to match the same custom name.

Use Datadog integrations. To get the best use out of your logs in Datadog, set the source on your logs. The source can be set directly in the Agent if you forward your logs to the Datadog Agent.

Otherwise you need a specific format per log source, which means you need a specific configuration file per source in /etc/rsyslog.d/.

To set the source, use the following format (if you have several sources, change the name of the format in each file):

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\"] %msg%\n"

You can also add custom tags with the ddtags attribute:

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\" ddtags=\"env:dev,<KEY:VALUE>\"] %msg%\n"

(Optional) Datadog cuts inactive connections after a period of inactivity. Some Rsyslog versions are not able to reconnect properly when necessary. To mitigate this issue, use time markers so the connection never stops. To achieve this, add the following line in your Rsyslog configuration:

module(load="immark" interval="20")

And don’t forget to restart:

sudo service rsyslog restart

(Optional) Activate Rsyslog file monitoring module. If you want to watch or monitor specific log files, activate the imfile module by adding this to your rsyslog.conf:

module(load="imfile" PollingInterval="10") #needs to be done just once

Create a /etc/rsyslog.d/datadog.conf file.

Set the log files to monitor and configure the destination endpoint. Add the following in /etc/rsyslog.d/datadog.conf.

## For each file to send
input(type="imfile" ruleset="infiles" Tag="<APP_NAME_OF_FILE1>" File="<PATH_TO_FILE1>" StateFile="<UNIQUE_FILE_ID>")

## Set the Datadog Format to send the logs
$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - - %msg%\n"

## Define the destination for the logs
ruleset(name="infiles") {
     action(type="omfwd" target="tcp-intake.logs.datadoghq.eu" protocol="tcp" port="1883" template="DatadogFormat")
}

(Optional) TLS Encryption: While sending your logs directly from Rsyslog to your Datadog account, if you want to add TLS encryption, take the following steps.

• Install rsyslog-gnutls:

  sudo apt-get install rsyslog-gnutls ca-certificates
  

• Modify your /etc/rsyslog.d/datadog.conf to end with the following content:

  ## Define the destination for the logs
  $DefaultNetstreamDriverCAFile /etc/ssl/certs/ca-certificates.crt
  ruleset(name="infiles") {
    action(type="omfwd" protocol="tcp" target="tcp-intake.logs.datadoghq.eu" port="443" template="DatadogFormat"           StreamDriver="gtls" StreamDriverMode="1" StreamDriverAuthMode="x509/name" StreamDriverPermittedPeers="*.logs.datadoghq.eu" )
  }
  

Restart Rsyslog, and your new logs are forwarded directly to your Datadog account.

sudo service rsyslog restart

Associate those logs with the host metrics and tags. To make sure these logs are associated with the metrics and tags from the same host in your Datadog account, set the same HOSTNAME in your rsyslog.conf so that its value matches the hostname of your Datadog metrics. Note: If you did not specify any hostname in your configuration file for the metrics using datadog.conf or datadog.yaml, you do not need to change anything. If you did specify a custom hostname for your metric, make sure to replace the %HOSTNAME% value in the format to match the same custom name.

Use Datadog integrations. To get the best use out of your logs in Datadog, set the source on your logs. The source can be set directly in the Agent if you forward your logs to the Datadog Agent.

Otherwise you need a specific format per log source which means you need a specific configuration file per source in /etc/rsyslog.d/.

To set the source, use the following format (if you have several sources, change the name of the format in each file):

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\"] %msg%\n"

You can also add custom tags with the ddtags attribute:

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\" ddtags=\"env:dev,<KEY:VALUE>\"] %msg%\n"

(Optional) Datadog cuts inactive connections after a period of inactivity. Some Rsyslog versions are not able to reconnect properly when necessary. To mitigate this issue, use time markers so the connection never stops. To achieve this, add the following line in your Rsyslog configuration:

module(load="immark" interval="20")

And don’t forget to restart:

sudo service rsyslog restart

(Optional) Activate Rsyslog file monitoring module. If you want to watch or monitor specific log files, activate the imfile module by adding this to your rsyslog.conf:

$ModLoad imfile
$InputFilePollInterval 10
$PrivDropToGroup adm
$WorkDirectory /var/spool/rsyslog

Create a /etc/rsyslog.d/datadog.conf file.

Set the log files to monitor and configure the destination endpoint. Add the following in /etc/rsyslog.d/datadog.conf.

## Input for FILE1
$InputFileName /<PATH_TO_FILE1>
$InputFileTag <APP_NAME_OF_FILE1>
$InputFileStateFile <UNIQUE_FILE_ID>
$InputFileSeverity info
$InputRunFileMonitor

## Set the Datadog Format to send the logs
$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - - %msg%\n"

## Define the destination for the logs
*.* @@intake.logs.datadoghq.com:10514;DatadogFormat

(Optional) TLS Encryption: While sending your logs directly from Rsyslog to your Datadog account, if you want to add TLS encryption, take the following steps.

• Install rsyslog-gnutls:

  sudo apt-get install rsyslog-gnutls ca-certificates
  

• Modify your /etc/rsyslog.d/datadog.conf to end with the following content:

  #Define the destination for the logs
  
  $DefaultNetstreamDriverCAFile /etc/ssl/certs/ca-certificates.crt
  $ActionSendStreamDriver gtls
  $ActionSendStreamDriverMode 1
  $ActionSendStreamDriverAuthMode x509/name
  $ActionSendStreamDriverPermittedPeer *.logs.datadoghq.com
  *.* @@intake.logs.datadoghq.com:10516;DatadogFormat
  

Restart Rsyslog and your new logs are forwarded directly to your Datadog account.

sudo service rsyslog restart

Associate those logs with the host metrics and tags. To make sure these logs are associated with the metrics and tags from the same host in your Datadog account, set the same HOSTNAME in your rsyslog.conf so that its value matches the hostname of your Datadog metrics. Note: If you did not specify any hostname in your configuration file for the metrics using datadog.conf or datadog.yaml, you do not need to change anything. If you did specify a custom hostname for your metric, make sure to replace the %HOSTNAME% value in the format to match the same custom name.

Use Datadog integrations. To get the best use out of your logs in Datadog, set the source on your logs. The source can be set directly in the Agent if you forward your logs to the Datadog Agent.

Otherwise you need a specific format per log source which means you need a specific configuration file per source in /etc/rsyslog.d/.

To set the source, use the following format (if you have several sources, change the name of the format in each file):

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\"] %msg%\n"

You can also add custom tags with the ddtags attribute:

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\" ddtags=\"env:dev,<KEY:VALUE>\"] %msg%\n"

(Optional) Datadog cuts inactive connections after a period of inactivity. Some Rsyslog versions are not able to reconnect properly when necessary. To mitigate this issue, use time markers so the connection never stops. To achieve this, add the following 2 lines in your Rsyslog configuration:

$ModLoad immark
$MarkMessagePeriod 20

And don’t forget to restart:

sudo service rsyslog restart

(Optional) Activate Rsyslog file monitoring module. If you want to watch or monitor specific log files, activate the imfile module by adding this to your rsyslog.conf:

$ModLoad imfile
$InputFilePollInterval 10
$PrivDropToGroup adm
$WorkDirectory /var/spool/rsyslog

Create a /etc/rsyslog.d/datadog.conf file.

Set the log files to monitor and configure the destination endpoint. Add the following in /etc/rsyslog.d/datadog.conf.

## Input for FILE1
$InputFileName /<PATH_TO_FILE1>
$InputFileTag <APP_NAME_OF_FILE1>
$InputFileStateFile <UNIQUE_FILE_ID>
$InputFileSeverity info
$InputRunFileMonitor

## Set the Datadog Format to send the logs
$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - - %msg%\n"

## Define the destination for the logs
*.* @@tcp-intake.logs.datadoghq.eu:1883;DatadogFormat

(Optional) TLS Encryption: While sending your logs directly from Rsyslog to your Datadog account, if you want to add TLS encryption, take the following steps.

• Install rsyslog-gnutls:

  sudo apt-get install rsyslog-gnutls ca-certificates
  

• Modify your /etc/rsyslog.d/datadog.conf to end with the following content:

  #Define the destination for the logs
  
  $DefaultNetstreamDriverCAFile /etc/ssl/certs/ca-certificates.crt
  $ActionSendStreamDriver gtls
  $ActionSendStreamDriverMode 1
  $ActionSendStreamDriverAuthMode x509/name
  $ActionSendStreamDriverPermittedPeer *.logs.datadoghq.eu
  *.* @@tcp-intake.logs.datadoghq.eu:443;DatadogFormat
  

Restart Rsyslog and your new logs are forwarded directly to your Datadog account.

sudo service rsyslog restart

Associate those logs with the host metrics and tags. To make sure these logs are associated with the metrics and tags from the same host in your Datadog account, set the same HOSTNAME in your rsyslog.conf so that its value matches the hostname of your Datadog metrics. Note: If you did not specify any hostname in your configuration file for the metrics using datadog.conf or datadog.yaml, you do not need to change anything. If you did specify a custom hostname for your metric, make sure to replace the %HOSTNAME% value in the format to match the same custom name.

Use Datadog integrations. To get the best use out of your logs in Datadog, set the source on your logs. The source can be set directly in the Agent if you forward your logs to the Datadog Agent.

Otherwise you need a specific format per log source which means you need a specific configuration file per source in /etc/rsyslog.d/.

To set the source, use the following format (if you have several sources, change the name of the format in each file):

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\"] %msg%\n"

You can also add custom tags with the ddtags attribute:

$template DatadogFormat,"<DATADOG_API_KEY> <%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% - - [metas ddsource=\"<MY_SOURCE_NAME>\" ddtags=\"env:dev,<KEY:VALUE>\"] %msg%\n"

(Optional) Datadog cuts inactive connections after a period of inactivity. Some Rsyslog versions are not able to reconnect properly when necessary. To mitigate this issue, use time markers so the connection never stops. To achieve this, add the following 2 lines in your Rsyslog configuration:

$ModLoad immark
$MarkMessagePeriod 20

And don’t forget to restart:

sudo service rsyslog restart