---
title: Datadog OTLP Intake Endpoint
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > OpenTelemetry in Datadog > Send OpenTelemetry Data to Datadog > Datadog
  OTLP Intake Endpoint
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Datadog OTLP Intake Endpoint

## Overview{% #overview %}

For production workloads, Datadog recommends sending OpenTelemetry data through a [Datadog Agent](https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent.md) or [OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter.md). These components provide metadata enrichment, signal processing, and centralized sampling. The recommended Collector setup exports telemetry to Datadog over OTLP.

Use the direct OTLP intake endpoints on this page when deploying a Collector or Agent is not feasible. Examples include serverless functions, managed platforms that export telemetry on your behalf, and environments with strict resource constraints.

{% image
   source="https://docs.dd-static.net/images/opentelemetry/setup/direct-ingest.675dcfafdeeca4017efe7eb10ad44571.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/opentelemetry/setup/direct-ingest.675dcfafdeeca4017efe7eb10ad44571.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Diagram: OpenTelemetry SDK sends data directly to Datadog through the intake endpoint." /%}

Your setup depends on where your telemetry is coming from. Check the [Managed platforms](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/managed_platforms.md) list first; if your platform has a dedicated endpoint, use it. Otherwise, use the serverless or signal-specific pages.

| If your telemetry comes from…                                                                                                                                  | Start here                                                                                                                                                                                                                                      |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A managed platform (Cloudflare, Vercel, Heroku, Netlify, Modal, and [others](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/managed_platforms.md)) | [Managed platforms](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/managed_platforms.md)                                                                                                                                            |
| A serverless environment sending traces (Lambda, ECS Fargate, Azure Functions, Cloud Run, GKE Autopilot)                                                       | [Serverless](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/serverless.md)                                                                                                                                                          |
| Your own app, host, or container                                                                                                                               | [Logs](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/logs.md), [Metrics](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/metrics.md), or [Traces](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/traces.md) |

See also: [Instrumenting for Agent Observability](https://docs.datadoghq.com/llm_observability/instrument/otel_instrumentation.md?tab=python#setup).

## Intake limits{% #intake-limits %}

Datadog enforces a maximum payload size per request on each OTLP intake endpoint. Requests that exceed the limit are rejected with an `HTTP 413 Request Entity Too Large` response. If you receive a 413, reduce the export batch size or flush more frequently so each request stays under the limit.

| Signal  | Endpoint path | Maximum payload size   |
| ------- | ------------- | ---------------------- |
| Metrics | `/v1/metrics` | 512 KiB (compressed)   |
| Logs    | `/v1/logs`    | 5.1 MiB (uncompressed) |
| Traces  | `/v1/traces`  | 15 MiB (uncompressed)  |

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Send Data to Datadog](https://docs.datadoghq.com/opentelemetry/setup.md)
- [Use OpenTelemetry-native observability with Datadog from ingestion to investigation](https://www.datadoghq.com/blog/native-otel-with-datadog/)