-
Notifications
You must be signed in to change notification settings - Fork 494
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
[Feature]: OTLP File Exporter #2602
Comments
Happy to host it in the contrib repo. (Or even this repo.) |
@joshwlewis hi, are you actively working on this? |
@berkus, no I'm not working on it at the moment. I have aspirations to do it, but haven't found the bandwidth just yet. Feel free to tackle it if you want. If it's of interest or help, I did roll my own (for traces only): https://github.com/heroku/libcnb.rs/blob/108faf180d8368011eae62c0fc5acc28b8d8119a/libcnb/src/tracing.rs#L126-L176 |
@joshwlewis got it, thank you for the update! |
Related Problems?
Prior to #2040, the
opentelemetry-stdout
crate was able to export in a format compatible with the OTLP File Exporter specification here. Passing in a file as the writer allowed the exporter to export to a file, and the default JSON serializer was compatible with the spec (example setup here). Since #2040, a writer can no longer be passed in, and the format is not JSON.Describe the solution you'd like:
I'd love to see a
FileExporter
that complies with https://opentelemetry.io/docs/specs/otel/protocol/file-exporter.Considered Alternatives
No response
Additional Context
There is some discussion here about whether this functionality is strictly required for SDKs.
I may have to roll my own OTLP File Exporter soon. I could potentially contribute it back to this library if desired.
The text was updated successfully, but these errors were encountered: