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

[feature request] Official file exporter #5920

Open
DrEsteban opened this issue Oct 23, 2024 · 2 comments
Open

[feature request] Official file exporter #5920

DrEsteban opened this issue Oct 23, 2024 · 2 comments
Labels
enhancement New feature or request needs-spec-change Issues which require the OpenTelemetry Specification to clarify or define behavior

Comments

@DrEsteban
Copy link

DrEsteban commented Oct 23, 2024

Package

None

Is your feature request related to a problem?

No response

What is the expected behavior?

It would be nice if there were an "official" filesystem exporter for traces/logs/metrics in .NET. I find it useful for local debugging, as well as job-based workloads where the logs could be exported or further processed.

Which alternative solutions or features have you considered?

I've copy/pasted the implementation of the ConsoleExporter(s) and simply updated the WriteLine() method in the base class to write to a FileStream instead of the console.

This is fine for most cases, (aside from the annoyance of having to copy/paste/adapt), but it's obviously in a very human-readable format. It'd be nice if there were perhaps 2 official implementations or modes: One to output in a similar human-readable format, and one that's serialized for a more machine-readable format.

Additional context

#5231

@DrEsteban DrEsteban added enhancement New feature or request needs-triage New issues which have not been classified or triaged by a community member labels Oct 23, 2024
@DrEsteban DrEsteban changed the title [feature request] Official File exporter [feature request] Official file exporter Oct 23, 2024
@cijothomas
Copy link
Member

Once open-telemetry/opentelemetry-specification#4183 lands, this is doable.

@cijothomas cijothomas added needs-spec-change Issues which require the OpenTelemetry Specification to clarify or define behavior and removed needs-triage New issues which have not been classified or triaged by a community member labels Oct 23, 2024
@martinjt
Copy link
Member

The relevant one is this: open-telemetry/opentelemetry-specification#3817

Whether that will become a thing is a different question. From stdout you should be able to pipe the data though, and in all other scenarios, a collector with the file exporter would likely be the more efficient way to do this.

I suppose we'll see whether this becomes a requirement, but until then, there are other ways this can be achieved and therefore I don't think we should leave this open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-spec-change Issues which require the OpenTelemetry Specification to clarify or define behavior
Projects
None yet
Development

No branches or pull requests

3 participants