Dean Meehan
09/18/2025, 11:34 AM{event:{},fields:{}} so that all of the fields are now part of the opentelemetry attributes/resources envelope within Fluentbit?Dean Meehan
09/18/2025, 1:05 PM{ "event": { "Hello": "meta?", "level": "INFO", }, "host": "localhost", "fields": { "field_1": "value_1", } }
...but we'd love to be able to natively send these to an OTEL platform with the correct fields as part of the OTEL atributes/resources correctly scope into the right format
{
"body": "{\"Hello\":\"meta?\",\"level\":\"INFO\"}",
"id": "0hySMFcuBVPIYVOE4CNuWFbKqC8",
"timestamp": "2025-09-18T11:32:13.249668633Z",
"attributes": {
"record_meta": "ok"
},
"resources": {},
"scope": {},
"severity_text": "",
"severity_number": 0,
"scope_name": "",
"scope_version": "",
"span_id": "",
"trace_flags": 0,
"trace_id": ""
}Anurag Gupta
09/22/2025, 3:35 AMAnurag Gupta
09/22/2025, 3:36 AMAnurag Gupta
09/22/2025, 3:36 AMAnurag Gupta
09/22/2025, 3:36 AMRobert McElhinney
10/01/2025, 2:20 PMRobert McElhinney
10/01/2025, 2:21 PM- name: content_modifier
context: otel_resource_attributes
action: upsert
key: service.name
value: my-service
looks like it only works for static values - we can't use $fields['field_1']Robert McElhinney
10/01/2025, 2:48 PMlogs_body_key_attributes but that's actually missing from the official logs: https://docs.fluentbit.io/manual/data-pipeline/outputs/opentelemetry