-
Notifications
You must be signed in to change notification settings - Fork 306
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.Exporter.Geneva: Compatibility with Fluent Bit #2574
base: main
Are you sure you want to change the base?
Conversation
What is the name and version of this "latest Fluent Bit's forward input plugin"? Can you give a link? If the existing exporter and fluentd has been working and this new version is breaking. Would it be more appropriate to apply a fix in this new version? |
@xiang17 I have updated the post to include the fluent bit version I have tried i.e. fluent-bit v3.0.6. Before making this change, I also looked at fluent bit code base as well and the code on the fluent bit is the same since it was first written, hence feel it is not a regression and existing exporter never worked with fluent bit. |
Can you sign the EasyCLA? |
@xiang17 EasyCLA done. |
@xiang17 wondering whom all I need to get this PR approved? |
Design discussion issue #
Currently, Traces and Logs emitted by OpenTelemetry.Exporter.Geneva package in Forward protocol format are not compatible with Fluent Bit's forward input plugin (tried with fluent-bit v3.0.6) and it fails to process those events with the following error:
where -8 error code means FLB_EVENT_DECODER_ERROR_WRONG_TIMESTAMP_TYPE

Changes
To make it compatible, as part of this PR, I applied the same strategy which Fluent Bit uses as part of forward output plugin where it has capability to send timestamp in the form of integer.

After applying the change, I was able to validate both Traces and Logs working e2e with Fluent Bit.
Please provide a brief description of the changes here.
Merge requirement checklist
CHANGELOG.md
files updated for non-trivial changes