We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When there is an unhandled exception coming from the user function, we could mark the span as Error and attach the error. E.g.
case NonFatal(ex) => span.setStatus(trace.StatusCode.ERROR, ex.getMessage)
This will make it easier later on the UI. E.g. in jaeger (note the red mark and the otel.status_descriptor):
otel.status_descriptor
The text was updated successfully, but these errors were encountered:
Now, after reading this I'm not so sure anymore if this is one case that warrants the error setting.
Sorry, something went wrong.
I would have a look at https://opentelemetry.io/docs/specs/semconv/general/trace/. Maybe better than opentracing semantic conventions?
It looks great by the way. I definitely like the idea.
No branches or pull requests
When there is an unhandled exception coming from the user function, we could mark the span as Error and attach the error. E.g.
This will make it easier later on the UI. E.g. in jaeger (note the red mark and the
otel.status_descriptor
):The text was updated successfully, but these errors were encountered: