OTLP ingestion is off by default, and you can turn it on by updating your datadog.yaml file configuration or by setting environment variables. The following datadog.yaml configurations enable endpoints on the default ports.

For gRPC, default port 4317:

otlp_config:
  receiver:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

For HTTP, default port 4318:

otlp_config:
  receiver:
    protocols:
      http:
        endpoint: 0.0.0.0:4318

Alternatively, configure the endpoints by providing the port through the environment variables:

• For gRPC (localhost:4317): DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_GRPC_ENDPOINT
• For HTTP (localhost:4318): DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT

These must be passed to both the core Agent and trace Agent processes. If running in a containerized environment, use 0.0.0.0 instead of localhost to ensure the server is available on non-local interfaces.

Configure either gRPC or HTTP for this feature. Here is an example application that shows configuration for both.

OTLP logs ingestion on the Datadog Agent is disabled by default so that you don’t have unexpected logs product usage that may impact billing. To enable OTLP logs ingestion:

1. Explicitly enable log collection as a whole by following Host Agent Log collection setup:

   logs_enabled: true
   

2. Set otlp_config.logs.enabled to true:

   otlp_config:
     logs:
       enabled: true
   

1. Follow the Datadog Docker Agent setup.

2. For the Datadog Agent container, set the following endpoint environment variables and expose the corresponding port:

   • For gRPC: Set DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_GRPC_ENDPOINT to 0.0.0.0:4317 and expose port 4317.
   • For HTTP: Set DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT to 0.0.0.0:4318 and expose port 4318.

3. If you want to enable OTLP logs ingestion, set the following endpoint environment variables in the Datadog Agent container:

   • Set DD_LOGS_ENABLED to true.
   • Set DD_OTLP_CONFIG_LOGS_ENABLED to true.

1. Follow the Kubernetes Agent setup.

2. Configure the following environment variables in both the trace Agent container and the core Agent container:

   For gRPC:

   name: DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_GRPC_ENDPOINT # enables gRPC receiver on port 4317
   value: "0.0.0.0:4317"
   

   For HTTP:

   name: DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT # enables HTTP receiver on port 4318
   value: "0.0.0.0:4318"
   

3. Map the container ports 4317 or 4318 to the host port for the core Agent container:

   For gRPC:

   ports:
     - containerPort: 4317
       hostPort: 4317
       name: traceportgrpc
       protocol: TCP
   

   For HTTP

   ports:
     - containerPort: 4318
       hostPort: 4318
       name: traceporthttp
       protocol: TCP
   

4. If you want to enable OTLP logs ingestion, set the following endpoint environment variables in the core Agent container:

   Enable log collection with your DaemonSet:

   name: DD_LOGS_ENABLED
   value: "true"
   

   And enable OTLP logs ingestion:

   name: DD_OTLP_CONFIG_LOGS_ENABLED
   value: "true"
   

1. Follow the Kubernetes Agent setup.

2. Enable the OTLP endpoints in the Agent by editing the datadog.otlp section of the values.yaml file:

   For gRPC:

   otlp:
    receiver:
      protocols:
        grpc:
          endpoint: 0.0.0.0:4317
          enabled: true
   

   For HTTP:

   otlp:
    receiver:
      protocols:
        http:
          endpoint: 0.0.0.0:4318
          enabled: true
   

This enables each protocol in the default port (4317 for OTLP/gRPC and 4318 for OTLP/HTTP).

1. Follow the Kubernetes Agent setup.

2. Enable the preferred protocol:

   For gRPC:

   --set "datadog.otlp.receiver.protocols.grpc.enabled=true"
   

   For HTTP:

   --set "datadog.otlp.receiver.protocols.http.enabled=true"
   

This enables each protocol in the default port (4317 for OTLP/gRPC and 4318 for OTLP/HTTP).

For detailed instructions on using OpenTelemetry with AWS Lambda and Datadog, including:

• Instrumenting your Lambda functions with OpenTelemetry
• Using OpenTelemetry API support within Datadog tracers
• Sending OpenTelemetry traces to the Datadog Lambda Extension

See the Serverless documentation for AWS Lambda and OpenTelemetry.

1. For the application container, set OTEL_EXPORTER_OTLP_ENDPOINT environment variable to point to the Datadog Agent container. For example:

   OTEL_EXPORTER_OTLP_ENDPOINT=http://<datadog-agent>:4318
   

2. Both containers must be defined in the same bridge network, which is handled automatically if you use Docker Compose. Otherwise, follow the Docker example in Tracing Docker Applications to set up a bridge network with the correct ports.

In the application deployment file, configure the endpoint that the OpenTelemetry client sends traces to with the OTEL_EXPORTER_OTLP_ENDPOINT environment variable.

For gRPC:

env:
 - name: HOST_IP
   valueFrom:
     fieldRef:
       fieldPath: status.hostIP
 - name: OTEL_EXPORTER_OTLP_ENDPOINT
   value: "http://$(HOST_IP):4317" # sends to gRPC receiver on port 4317

For HTTP:

env:
 - name: HOST_IP
   valueFrom:
     fieldRef:
       fieldPath: status.hostIP
 - name: OTEL_EXPORTER_OTLP_ENDPOINT
   value: "http://$(HOST_IP):4318" # sends to HTTP receiver on port 4318

Note: To enrich container tags for custom metrics, set the appropriate resource attributes in the application code where your OTLP metrics are generated. For example, set the container.id resource attribute to the pod’s UID.