Datadog

Community-contributed integration

This integration is community-maintained. Reference: ory/integrates/monitoring-observability/datadog.

Monitor self-hosted Ory in Datadog over OpenTelemetry. Ory's tracer emits OTLP, which Datadog ingests either through the Datadog Agent's OTLP receiver or through Datadog's agentless OTLP intake.

See the self-hosted distributed tracing and self-hosted observability docs.

There is no `datadog` tracing provider

TRACING_PROVIDER accepts otel, jaeger, or zipkin only. Reach Datadog over OTLP with TRACING_PROVIDER=otel, not through a native Datadog tracer. Ory's span helper does set Datadog-convention error attributes (error.message, error.stack, error.type), so traces arriving over OTLP render correctly in Datadog APM.

Self-hosted only

Ory Network does not export telemetry to customer-owned collectors — managed project configuration excludes operational settings such as tracing and logging.

Ingestion paths

1. Datadog Agent OTLP receiver (recommended). Run the agent with otlp_config.receiver.protocols.{grpc,http} enabled (ports 4317 / 4318) and point Ory's OTLP exporter at it.
2. Datadog OTLP intake (agentless). Ship straight to Datadog with the DD-API-KEY header. Endpoints per region:

Region	OTLP gRPC	OTLP HTTP
US1	otlp.datadoghq.com:4317	otlp.datadoghq.com:4318
US3	otlp.us3.datadoghq.com:4317	otlp.us3.datadoghq.com:4318
US5	otlp.us5.datadoghq.com:4317	otlp.us5.datadoghq.com:4318
EU	otlp.datadoghq.eu:4317	otlp.datadoghq.eu:4318

For Prometheus metrics, the Datadog Agent's OpenMetrics check can scrape /metrics/prometheus on each Ory service.

Resources

• Datadog
• Ory tracing
• Ory observability
• Reference: ory/integrates/monitoring-observability/datadog