---
title: Datadog
description: Export agent traces to Datadog APM alongside the rest of your stack.
type: instrumentation
keywords:
  - otel
  - opentelemetry
  - tracing
  - observability
  - apm
  - otlp
---

# Datadog

Instrumentation integration for eve. Export agent traces to Datadog APM alongside the rest of your stack.

## Install

Add Datadog instrumentation from eve's registry:

```bash
eve add instrumentation/datadog
```

## Quick start

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

```ts
// agent/instrumentation.ts
import { 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](/docs/guides/instrumentation) for the trace hierarchy and the `recordInputs`/`recordOutputs` controls.

[Read the full instrumentation documentation](/docs/guides/instrumentation)

---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)