Skip to main content

Datadog Logs Sink Node

Quick Reference​

Connection Profile Select a Datadog connection profile. It carries the Datadog site (region) and the Datadog API key used to authenticate against the logs intake API.

Source Default ddsource applied to each log when the record does not already carry one. ex: fleak

Service Default service applied to each log when the record does not already carry one. ex: my-service

Tags Default comma-separated ddtags applied to each log when the record does not already carry them. ex: env:prod,team:data

Batch Size Number of records sent per intake request. Default: 500.

Overview​

The Datadog Logs Sink node forwards records from your workflow to Datadog Logs through the Datadog HTTP logs intake API. Records are buffered and sent in batches, and you can attach a default ddsource, service, and ddtags to every record. Authentication and region are supplied by a Datadog connection profile, which holds the Datadog site and API key.

Configuration​

Datadog Logs Sink node configuration

FieldDescriptionRequiredDefault
Connection ProfileSelect or create a Datadog connection profile. It supplies the Datadog site (region, e.g. datadoghq.com), which derives the intake endpoint, and the API key, sent in the DD-API-KEY header.Yes—
SourceDefault ddsource injected into each log. Applied only when the record does not already carry a ddsource.No—
ServiceDefault service injected into each log. Applied only when the record does not already carry a service.No—
TagsDefault ddtags (comma-separated) injected into each log. Applied only when the record does not already carry ddtags.No—
Batch SizeNumber of records sent in a single intake request. Minimum: 1.No500

Connection Profile​

The connection profile determines both where and how logs are delivered. Its site selects the Datadog region and derives the intake endpoint https://http-intake.logs.<site>/api/v2/logs — common values are datadoghq.com (US1, default), datadoghq.eu (EU1), us3.datadoghq.com, us5.datadoghq.com, and ap1.datadoghq.com. Its API key is sent in the DD-API-KEY header on every request.

Source, Service, and Tags​

Source, Service, and Tags set defaults for the Datadog reserved attributes ddsource, service, and ddtags. Each default is injected only when the incoming record does not already contain that attribute, so per-record values coming from upstream nodes are preserved. Leave a field blank to send whatever the record already carries (or nothing).

Batch Size​

Records accumulate in memory until the batch reaches this size, at which point the node serializes the batch as a single JSON array and POSTs it to the logs intake endpoint. Larger batches reduce request overhead; smaller batches lower memory usage and keep latency tighter.

Examples​

Example: Ship Workflow Logs to Datadog​

Use this node when you want every record produced by the workflow to land in Datadog Logs.

  • Select the Datadog connection profile for the target region and account.
  • Set Source to identify the origin of the logs — for example fleak.
  • Set Service to the service name the logs should be grouped under — for example my-service.
  • Add Tags such as env:prod,team:data to make the logs easy to filter in Datadog.

Example: Preserve Per-Record Metadata​

Because Source, Service, and Tags are applied only when the record does not already carry them, upstream nodes can set ddsource, service, or ddtags on individual records and those values win. Use the node fields to supply a fallback for records that do not set their own.

Error Handling​

Each batch is sent as a single POST to the Datadog logs intake API. A non-success HTTP response fails the entire batch, which is then routed to the configured error handling.