New announcements for Serverless, Network, RUM, and more from Dash! New announcements from Dash!

Agent proxy for logs

Log collection requires the Datadog Agent v6.0+. Older versions of the Agent do not include the log collection interface.

Logs make use of a different set of proxy settings than other data types forwarded by the Datadog Agent. This is because logs are transported over TCP/SSL, while other features submit data with HTTPS.

If you use a proxy for TCP transmission, configure the Datadog Agent to send logs to your proxy through TCP using the following parameters in the datadog.yaml configuration file:

  logs_dd_url: <PROXY_ENDPOINT>:<PROXY_PORT>
  logs_no_ssl: true

The parameters above can also be set with the following environment variables:


Note: The parameter logs_no_ssl is required to make the Agent ignore the discrepancy between the hostname on the SSL certificate ( or and your proxy hostname. It is recommended to use a SSL encrypted connection between your proxy and Datadog intake endpoint.

  • Then configure your proxy to listen on <PROXY_PORT> and forward the received logs to:

    • For on port 10516 and activate SSL encryption.
    • For on port 443 and activate SSL encryption.
  • Use the public key for TLS encryption for the SSL encryption:

    On some systems, the full certificate chain may be required. If so, use this public key instead:

To send your logs to your Datadog account with a SOCKS5 proxy server use the following settings in your datadog.yaml configuration file:

  socks5_proxy_address: <MY_SOCKS5_PROXY_URL>:<MY_SOCKS5_PROXY_PORT>

The parameter above can also be set with the following environment variable:


Port 443

The parameter use_port_443 does not affect logs sent through a proxy. You need to configure the proxy itself to forward logs to

Further Reading

Table of Contents