Attributes fields inside .jsonl file

[BaptisteMeynier]

Hello everybody,

I use Fluentbit to parse a .jsonl file which follow the Opentelemetry datamodel convention.
With SpanId,TraceId,Body... and Attributes

I use tail input plugin to read it and as output I send to Opentelemetry plugin.

Field logs_attributes_metadata_key fetch data from metadata but not inside message. So to manage to send Attributes as Otel I should move these fields as root record_message field and use logs_body_key_attributes. So It's involve to perform some operations on FluentBit side almost all root field are duplicated like like SpanId, TraceId.

Is it possible to add on Opentelemetry output plugin a new field which will find field inside message like logs_span_id_message_key for example call logs_attributes_message_key ?

[hamedrabah]

At the moment the OpenTelemetry output treats these as two different sources. logs_attributes_metadata_key reads the record's OTLP metadata, while the documented message-key options cover fields such as trace ID, span ID and severity. There is no equivalent logs_attributes_message_key option for a nested Attributes map.

So with a Tail/JSONL input you need a transform before the output: use a Lua filter (or another record-processing filter) to build the structure the OTLP output expects, or promote the relevant fields and use logs_body_key_attributes true so the remaining record fields become log attributes. The latter flattens the record rather than preserving an arbitrary nested OTLP Attributes object.

Adding logs_attributes_message_key would therefore be a reasonable feature request; it is not currently a configuration knob you are overlooking.

[BaptisteMeynier]

Thx a lot @hamedrabah for your anwser. With a lua script it's work well indeed.

How can I submit a ticket in order to evaluate my request about logs_attributes_message_key ?