Collect OpenTelemetry messages over HTTP or gRPC. Supports standard Export Service Request messages for logs, metrics, and traces. Implements OpenTelemetry OTLP Specification 1.0.0 with OTLP/gRPC and OTLP/HTTP. Provides protocol detection using the HTTP Content-Type header.


OpenTelemetry, OTel, OTLP, telemetry, metrics, traces, logs


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.

Display NameAPI NameDefault ValueAllowable ValuesDescription
AddressAddress0.0.0.0Internet Protocol Address on which to listen for OTLP Export Service Requests. The default value enables listening on all addresses.
PortPort4317TCP port number on which to listen for OTLP Export Service Requests over HTTP and gRPC
SSL Context ServiceSSL Context ServiceController Service API:
Implementations: StandardRestrictedSSLContextService
SSL Context Service enables TLS communication for HTTPS
Client AuthenticationClient AuthenticationWANT
  • WANT
  • NONE
Client authentication policy for TLS communication with HTTPS
Worker ThreadsWorker Threads2Number of threads responsible for decoding and queuing incoming OTLP Export Service Requests
Queue CapacityQueue Capacity1000Maximum number of OTLP request resource elements that can be received and queued
Batch SizeBatch Size100Maximum number of OTLP request resource elements included in each FlowFile produced


successExport Service Requests containing OTLP Telemetry

Reads Attributes:

None specified.

Writes Attributes:

mime.typeContent-Type set to application/json
resource.typeOpenTelemetry Resource Type: LOGS, METRICS, or TRACES
resource.countCount of resource elements included in messages

State management:

This component does not store state.


This component is not restricted.

Input requirement:

This component does not allow an incoming relationship.

System Resource Considerations:

None specified.