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

Export LogRecord.Exception data when using otlp exporter #4831

Closed
vishweshbankwar opened this issue Sep 6, 2023 · 7 comments · Fixed by #5258
Closed

Export LogRecord.Exception data when using otlp exporter #4831

vishweshbankwar opened this issue Sep 6, 2023 · 7 comments · Fixed by #5258
Labels
enhancement New feature or request logs Logging signal related pkg:OpenTelemetry.Exporter.OpenTelemetryProtocol Issues related to OpenTelemetry.Exporter.OpenTelemetryProtocol NuGet package
Milestone

Comments

@vishweshbankwar
Copy link
Member

Opening this issue to track progress on exporting attributes corresponding to LogRecord.Exception in OTLP exporter. The semantic conventions for these attributes are not yet stable and hence the attributes are not part of stable OTLP log exporter. The attributes will be available in only the pre-release versions of the exporter.

https://github.com/open-telemetry/semantic-conventions/blob/main/docs/exceptions/exceptions-logs.md#attributes

@vishweshbankwar vishweshbankwar added the enhancement New feature or request label Sep 6, 2023
@cijothomas cijothomas added pkg:OpenTelemetry.Exporter.OpenTelemetryProtocol Issues related to OpenTelemetry.Exporter.OpenTelemetryProtocol NuGet package logs Logging signal related labels Sep 6, 2023
@davesmits
Copy link

Does this mean when using LogError the exception that is passed as parameter its stacktrace is currently not send?

@cijothomas
Copy link
Member

Does this mean when using LogError the exception that is passed as parameter its stacktrace is currently not send?

Correct : https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/CHANGELOG.md#160-rc1

@davesmits
Copy link

Thanks for the details; just curious; does it mean there is a non stable version around that is up to date but just still contains this information ?

@cijothomas
Copy link
Member

The changelog shows the version Exception was removed. So if you use the version prior to it, you'll get exceptions.

The attributes will be available in only the pre-release versions of the exporter.

The above is misleading statement.. Not sure what it is supposed to mean? @vishweshbankwar could you clarify?

@vishweshbankwar
Copy link
Member Author

Following up on this: The ability to export these attributes are available on https://www.nuget.org/packages/OpenTelemetry/1.7.0-alpha.1

#4955

@cijothomas
Copy link
Member

open-telemetry/semantic-conventions#619 Once this is done, we can make the exception part as default without experimental feature.

@cijothomas
Copy link
Member

https://github.com/open-telemetry/semantic-conventions/blob/main/docs/exceptions/exceptions-logs.md#semantic-conventions-for-exceptions-in-logs is stable now., and OTLP Logexporter can bring back this functionality now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request logs Logging signal related pkg:OpenTelemetry.Exporter.OpenTelemetryProtocol Issues related to OpenTelemetry.Exporter.OpenTelemetryProtocol NuGet package
Projects
None yet
3 participants