Datadog
CertifiedEnterprise EditionTasks that ship Kestra workflow logs to Datadog via the HTTP intake API for centralized monitoring.
Use the LogExporter with a Datadog basePath and apiKey to push run logs to the correct regional endpoint. Configure source, service, and chunk size to match your Datadog log attribution and throughput needs, and pair it with a LogShipper to automate log exports.
Datadog
Tasks that ship Kestra workflow logs to Datadog via the HTTP intake API for centralized monitoring.
Use the LogExporter with a Datadog basePath and apiKey to push run logs to the correct regional endpoint. Configure source, service, and chunk size to match your Datadog log attribution and throughput needs, and pair it with a LogShipper to automate log exports.
How to use the Datadog plugin
Ship Kestra execution logs to Datadog Logs from Kestra flows.
Authentication
Set basePath (required, the region-specific Datadog intake URL, e.g. https://http-intake.logs.datadoghq.com for US or https://http-intake.logs.datadoghq.eu for EU) and apiKey (required). Store secrets in secrets and set connection properties on each task.
Log exporters
LogExporter ships execution logs to Datadog Logs in batches — set basePath and apiKey (both required). Optionally set source (the ddsource field, default Kestra), service (the Datadog service tag, default LogExporter), and chunk (logs per request, default 1000).
HTTP options
options carries over to the Datadog client: connect and read timeouts, an HTTP proxy (with credentials), redirects, and ssl.insecureTrustAllCertificates. A SOCKS proxy.type is rejected rather than silently downgraded. auth, enabledTcpExtendedKeepAlive, logs, allowFailed and allowedResponseCodes have no equivalent and are ignored, and a non-2xx response always fails the task.
