An input plugin to ingest OTLP Logs, Metrics, and Traces
The OpenTelemetry input plugin allows you to receive data as per the OTLP specification, from various OpenTelemetry exporters, the OpenTelemetry Collector, or Fluent Bit's OpenTelemetry output plugin.
Our compliant implementation fully supports OTLP/HTTP and OTLP/GRPC. Note that the single port
configured which defaults to 4318 supports both transports.
Key | Description | default |
---|---|---|
Important note: Raw traces means that any data forwarded to the traces endpoint (/v1/traces
) will be packed and forwarded as a log message, and will NOT be processed by Fluent Bit. The traces endpoint by default expects a valid protobuf encoded payload, but you can set the raw_traces
option in case you want to get trace telemetry data to any of Fluent Bit's supported outputs.
Fluent Bit based on the OTLP desired protocol exposes the following endpoints for data ingestion:
OTLP/HTTP
Logs
/v1/logs
Metrics
/v1/metrics
Traces
/v1/traces
OTLP/GRPC
Logs
/opentelemetry.proto.collector.log.v1.LogService/Export
/opentelemetry.proto.collector.log.v1.LogService/Export
Metrics
/opentelemetry.proto.collector.metric.v1.MetricService/Export
/opentelemetry.proto.collector.metrics.v1.MetricsService/Export
Traces
/opentelemetry.proto.collector.trace.v1.TraceService/Export
/opentelemetry.proto.collector.traces.v1.TracesService/Export
The OpenTelemetry plugin currently supports the following telemetry data types:
A sample config file to get started will look something like the following:
With the above configuration, Fluent Bit will listen on port 4318
for data. You can now send telemetry data to the endpoints /v1/metrics
, /v1/traces
, and /v1/logs
for metrics, traces, and logs respectively.
A sample curl request to POST json encoded log data would be:
Type | HTTP/JSON | HTTP/Protobuf |
---|---|---|
listen
The network address to listen.
0.0.0.0
port
The port for Fluent Bit to listen for incoming connections. Note that as of Fluent Bit v3.0.2 this port is used for both transport OTLP/HTTP and OTLP/GRPC.
4318
tag_key
Specify the key name to overwrite a tag. If set, the tag will be overwritten by a value of the
raw_traces
Route trace data as a log
false
buffer_max_size
Specify the maximum buffer size in KB/MB/GB to the HTTP payload.
4M
buffer_chunk_size
Initial size and allocation strategy to store the payload (advanced users only)
512K
successful_response_code
It allows to set successful response code. 200
, 201
and 204
are supported.
201
tag_from_uri
If true, tag will be created from uri. e.g. v1_metrics from /v1/metrics .
true
Logs
Stable
Stable
Metrics
Unimplemented
Stable
Traces
Unimplemented
Stable