Open efgpinto opened 8 months ago
Now, after reading this I'm not so sure anymore if this is one case that warrants the error setting.
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.
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
):