Datadog

Instrumentation

Export agent traces to Datadog APM alongside the rest of your stack.

Install

Add Datadog instrumentation from eve's registry:

Quick start

Create agent/instrumentation.ts and point the OTLP exporter at Datadog's intake for your site, authenticated with your API key:

// agent/instrumentation.tsimport { defineInstrumentation } from "eve/instrumentation";import { OTLPHttpProtoTraceExporter, registerOTel } from "@vercel/otel";
export default defineInstrumentation({  setup: ({ agentName }) =>    registerOTel({      serviceName: agentName,      traceExporter: new OTLPHttpProtoTraceExporter({        url: process.env.DATADOG_OTLP_TRACES_ENDPOINT!,        headers: { "dd-api-key": process.env.DD_API_KEY! },      }),    }),});

// agent/instrumentation.tsimport { defineInstrumentation } from "eve/instrumentation";import { OTLPHttpProtoTraceExporter, registerOTel } from "@vercel/otel";
export default defineInstrumentation({  setup: ({ agentName }) =>    registerOTel({      serviceName: agentName,      traceExporter: new OTLPHttpProtoTraceExporter({        url: process.env.DATADOG_OTLP_TRACES_ENDPOINT!,        headers: { "dd-api-key": process.env.DD_API_KEY! },      }),    }),});

Configure

Datadog's direct OTLP trace intake is site-specific (for example datadoghq.com vs datadoghq.eu) and currently in Preview; look up the endpoint for your site in Datadog's OTLP intake docs. For production, Datadog recommends routing through an OpenTelemetry Collector with the Datadog exporter instead. See the instrumentation guide for the trace hierarchy and the recordInputs/recordOutputs controls.