Skip to content

Disk buffering span exporter to avoid data loss (existing Java feature) #3299

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

Open
mfarzami opened this issue Feb 25, 2025 · 2 comments
Open

Comments

@mfarzami
Copy link

What problem do you want to solve?

The current span exporter offerings may drop spans under high traffic if the buffer overflows.

Describe the solution you'd like

I am looking for a Python version of the disk buffering span exporters that were released in Java (https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/disk-buffering). These exporters store telemetry data in files which can be sent later on demand. There is a thread buffering the spans to a disk and a thread reading the spans from the disk.

Describe alternatives you've considered

Writing a custom span exporter that uses queueing/local storage to avoid overload, which would be complicated.

Additional Context

No response

Would you like to implement a fix?

None

@aabmass
Copy link
Member

aabmass commented Feb 25, 2025

Describe alternatives you've considered

Writing a custom span exporter that uses queueing/local storage to avoid overload, which would be complicated.

Isn't that the feature request here?

@mfarzami
Copy link
Author

mfarzami commented Feb 26, 2025

Thanks for your quick response! Yes it is, I meant that the alternative to an OpenTelemetry feature would be to write a custom exporter myself for my use case, but I believe the exporter would be a feature that benefits other users as well (as illustrated by the decision to create a Java version). Let me know your thoughts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants