-
Notifications
You must be signed in to change notification settings - Fork 773
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
Comments
Does this mean when using |
|
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 ? |
The changelog shows the version Exception was removed. So if you use the version prior to it, you'll get exceptions.
The above is misleading statement.. Not sure what it is supposed to mean? @vishweshbankwar could you clarify? |
Following up on this: The ability to export these attributes are available on https://www.nuget.org/packages/OpenTelemetry/1.7.0-alpha.1 |
open-telemetry/semantic-conventions#619 Once this is done, we can make the exception part as default without experimental feature. |
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. |
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
The text was updated successfully, but these errors were encountered: