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
Currently, when a message of type EXCEPTION is returned by a thrift service, the server-side span is tagged as an error. However, no details of the exception are logged to the span. When the SpanProcessor catches an exception, it creates error logs and adds them to the span. Can the library do the same when the exception is returned by thrift? Just the type of the exception being returned would be useful.
The text was updated successfully, but these errors were encountered:
I see. That is a pain. So there's basically no way of getting the details of that exception without extending the ProcessFunction class, and that class is referenced directly by code generated by the thrift compiler. You would need a change to thrift itself to be able to add the details of the exception to the span.
Currently, when a message of type EXCEPTION is returned by a thrift service, the server-side span is tagged as an error. However, no details of the exception are logged to the span. When the SpanProcessor catches an exception, it creates error logs and adds them to the span. Can the library do the same when the exception is returned by thrift? Just the type of the exception being returned would be useful.
The text was updated successfully, but these errors were encountered: