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 Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Address | Address | 0.0.0.0 | Internet Protocol Address on which to listen for OTLP Export Service Requests. The default value enables listening on all addresses. | |
| Port | Port | 4317 | TCP port number on which to listen for OTLP Export Service Requests over HTTP and gRPC | |
| SSL Context Service | SSL Context Service | Controller Service API: SSLContextService Implementations: StandardSSLContextService StandardRestrictedSSLContextService | SSL Context Service enables TLS communication for HTTPS | |
| Client Authentication | Client Authentication | WANT |
| Client authentication policy for TLS communication with HTTPS |
| Worker Threads | Worker Threads | 2 | Number of threads responsible for decoding and queuing incoming OTLP Export Service Requests | |
| Queue Capacity | Queue Capacity | 1000 | Maximum number of OTLP request resource elements that can be received and queued | |
| Batch Size | Batch Size | 100 | Maximum number of OTLP request resource elements included in each FlowFile produced |
| Name | Description |
|---|---|
| success | Export Service Requests containing OTLP Telemetry |
| Name | Description |
|---|---|
| mime.type | Content-Type set to application/json |
| resource.type | OpenTelemetry Resource Type: LOGS, METRICS, or TRACES |
| resource.count | Count of resource elements included in messages |