You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a feature request for the spec. After all error-chaining is common for many languages. I also registered open-telemetry/semantic-conventions#941 for the spec.
Is your feature request related to a problem? Please describe.
The Error.cause, when present, is just as important (and often more important) then the wrapping exception. Currently recordException() loses this information completely.
Describe the solution you'd like
Two possible solutions:
Introduce exception.cause attribute.
Use existing attributes, but combine their values. E.g. message = error.message + '; cause:' + error.chain.message, and the same for stack.
(1) is more preferred, however, it'd be hard to make the exception.cause recursive, since the Attributes type doesn't allow sub-objects.
Describe alternatives you've considered
Do the (2) above manually in call sites.
The text was updated successfully, but these errors were encountered:
This might be a feature request for the spec. After all error-chaining is common for many languages. I also registered open-telemetry/semantic-conventions#941 for the spec.
Is your feature request related to a problem? Please describe.
The
Error.cause
, when present, is just as important (and often more important) then the wrapping exception. CurrentlyrecordException()
loses this information completely.Describe the solution you'd like
Two possible solutions:
exception.cause
attribute.message = error.message + '; cause:' + error.chain.message
, and the same for stack.(1) is more preferred, however, it'd be hard to make the
exception.cause
recursive, since theAttributes
type doesn't allow sub-objects.Describe alternatives you've considered
Do the (2) above manually in call sites.
The text was updated successfully, but these errors were encountered: