-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
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
should client otel span be parent of server span #105
Comments
Do you mean you expect one trace? You are seeing multiple traces? |
Sorry, yes I expected one trace, and I am seeing two. |
Ah ok. Yes, then that is a bug. |
I am using grpcbox 0.16.0 and opentelemetry_grpcbox 0.2.0, correct versions? |
Yea, those are the latest. |
Just an FYI. I switched to use the opencensus interceptor included with grpcbox and the behavior is exactly the same, I get two traces, one for the client and one for the server. |
Using the opentelemetry grpcbox instrumentation library and I am seeing both the client and server spans in Zipkin. However, I expected to see one span, with the client span being the parent of the server span. Or perhaps the client span with the server span a sub-span of the client. Both my client and server are Erlang.
The text was updated successfully, but these errors were encountered: