Datadog
- Configuration Parameters
  - Configuration File
- Troubleshooting
  - 403 Forbidden

Datadog

The Datadog output plugin allows to ingest your logs into Datadog.

Before you begin, you need a Datadog account, a Datadog API key, and you need to activate Datadog Logs Management.

Configuration Parameters

Key	Description	Default
Host	Required - The Datadog server where you are sending your logs.	`http-intake.logs.datadoghq.com`
TLS	Required - End-to-end security communications security protocol. Datadog recommends setting this to `on`.	`off`
compress	Recommended - compresses the payload in GZIP format, Datadog supports and recommends setting this to `gzip`.
apikey	Required - Your Datadog API key.
dd_service	Recommended - The human readable name for your service generating the logs - the name of your application or database.
dd_source	Recommended - A human readable name for the underlying technology of your service. For example, `postgres` or `nginx`.
dd_tags	Optional - The tags you want to assign to your logs in Datadog.

Configuration File

Get started quickly with this configuration file:

[OUTPUT]
    Name        datadog
    Match       *
    Host        http-intake.logs.datadoghq.com
    TLS         on
    compress    gzip
    apikey      <my-datadog-api-key>
    dd_service  <my-app-service>
    dd_source   <my-app-source>
    dd_tags     team:logs,foo:bar

Troubleshooting

403 Forbidden

If you get a 403 Forbidden error response, double check that you have a valid Datadog API key and that you have activated Datadog Logs Management.