Is your feature request related to a problem? Please describe.
Exceptions are currently not handled as per OpenTelemetry specifications.
Describe the solution you'd like
This feature would require changes in the SDK (for instance self.tracing.add_event() and self.tracing.record_exception(), at least, if the solution uses Events as per OTel specs), as well as changes in the UI to handle events (again, if the solution uses Events). Also, Exceptions would not be part of the trace outputsanymore.
Describe alternatives you've considered
Implementing Events (proper solution but with more moving parts)
Adding exceptions as another span attribute (non-standard solution but with fewer moving parts)
Is your feature request related to a problem? Please describe. Exceptions are currently not handled as per OpenTelemetry specifications.
Describe the solution you'd like This feature would require changes in the SDK (for instance
self.tracing.add_event()
andself.tracing.record_exception()
, at least, if the solution usesEvents
as per OTel specs), as well as changes in the UI to handle events (again, if the solution usesEvents
). Also, Exceptions would not be part of the traceoutputs
anymore.Describe alternatives you've considered
Events
(proper solution but with more moving parts)Additional context https://github.com/open-telemetry/opentelemetry-specification/blob/v1.33.0/specification/trace/api.md https://github.com/open-telemetry/opentelemetry-specification/blob/v1.33.0/specification/trace/exceptions.md https://opentelemetry.io/docs/specs/semconv/exceptions/exceptions-spans/ https://opentelemetry.io/docs/concepts/signals/traces/