Enable OTLP ingest on the Datadog Agent by setting otlp_config.receiver.protocols.grpc.endpoint in datadog.yaml
Configure the OTel SDK OTLP exporter in the application to point at the Agent's OTLP port (default 4317 for gRPC)
Set service.name, deployment.environment, and service.version resource attributes in the SDK to map to Datadog's DD_SERVICE, DD_ENV, and DD_VERSION
Verify trace ingestion in the Datadog APM Services list and confirm that the service appears with the correct env and version tags
Use Datadog's APM to Infrastructure correlation by clicking a trace and navigating to the correlated host metrics panel
Known gotchas
OTel resource attributes are mapped to Datadog reserved tags using a fixed mapping table; custom resource attributes outside this mapping appear as span tags but not as infrastructure tags
OTLP ingest via the Agent does not support all Datadog APM features such as App Analytics or live tail filtering; some features require the Datadog native tracer
The Agent OTLP receiver listens on 4317 by default but this port may conflict with an existing OTel Collector running on the same host; configure a distinct port if both run concurrently
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp