Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opentelemetry: add Logs metadata support for JSON payload #9724

Merged
merged 5 commits into from
Dec 16, 2024

Conversation

edsiper
Copy link
Member

@edsiper edsiper commented Dec 14, 2024

When the data ingestion in in_opentelemetry comes as JSON payload, the metadata is not registered. This PR adds the group record with the proper schema to solve this problem. Also it registers spanId, traceId and observedTimeUnixNano

In addition in out_opentelemetry, it removes the strict string value check of severityText and allows the value set originally.

The unit test for in_opentelemetry has been extended to validate the group metadata and group body.


Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

This change adds support to parse and register the resources and scope metadata
coming from Logs which are ingested from a JSON payload.

Signed-off-by: Eduardo Silva <[email protected]>
the new configuration option 'data_mode' allows to control what type
of data the plugin pass to the callback set by the caller. By default
it was always passing one log record at a time in the configured 'format'; now
with 'data_mode' the user can set 'single_record' (default) or 'chunk'.

When the option 'chunk' is passed, the whole binary chunk is passed to the callback
as a reference (it's up to the caller to unpack and validate the content)

Signed-off-by: Eduardo Silva <[email protected]>
@edsiper edsiper deleted the otel-logs-json-metadata branch December 16, 2024 04:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant