Skip to content

OTLP Protocol Receiver

An OTLP Protocol Receiver is a component in an OpenTelemetry Collector configured to accept telemetry data via the OpenTelemetry Protocol (OTLP).^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]

Configuration

In an OpenTelemetry configuration file, the receiver is defined under the receivers section.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md] The standard identifier for this receiver type is otlp.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]

Supported Protocols

The otlp receiver supports multiple transport protocols for data ingestion.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md] These include:

  • gRPC: A high-performance RPC framework.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]
  • HTTP: Standard web protocol for transmission.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]

Example Configuration

The following YAML snippet demonstrates a basic configuration that enables both gRPC and HTTP protocols:^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]

receivers:
  otlp:
    protocols:
      grpc:
      http:

When deployed in a sample environment (such as within Kubernetes), this receiver setup typically listens on port 4317 for gRPC connections.^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]

  • [[OpenTelemetry]]
  • [[Observability]]
  • [[Telemetry Pipeline]]

Sources

^[400-devops-07-monitoring-and-observability-k8s-istio-samples-open-telemetry-readme.md]