Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Correlate service calls through ContextPropagationToken

See original GitHub issue

We need to explore the API required to trace service call by propagating the ContextPropagationToken. The goal is to be able to trace an entire call chain, regardless of implementation.

Issue Analytics

State:
Created 5 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

2reactions

abe545commented, Aug 3, 2020

@JamesNK can you help me understand why this is not needed? At Namely, we have grpc services written in go, python & c# - we currently propagate deadline + cancellation between all 3 (we haven’t migrated off Grpc.Core). Are we mistaken that this actually works from the c# and python services to go? If it does currently work, why do you think it isn’t valuable to have this propagation work with grpc-dotnet (or are those 2 supported, but not the tracing)? We wrote client + server interceptors to support the zipkin traces we currently use - but if we could use built-in support for propagating tracing, that would be ideal.

0reactions

JamesNKcommented, Jun 24, 2020

I don’t think this is needed. I don’t think correlating calls between an app that is using both Grpc.Core and grpc-dotnet is that valuable, and in .NET Core we have Activity to propagate telemetry.

Can reopen if a use case for ContextPropagationToken is identified.