Remove ActivityPropagationHandler breaking change #1316
-
We have been using the activity handler with the IHttpForwarder. Could you elaborate how to deal with this in RC.1 for both .NET 6 and earlier? thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi, We originally added the handler to YARP as a workaround to bridge the gap in As such, the scenario is expected to "just work" in YARP on .NET 6.0 and newer by default, there is no need to use workarounds like the For versions before 6.0, YARP will work as a silent pass-through for distributed tracing by default - the trace will not be broken, but the proxy will not participate in it either. Can you also describe how you are currently using the handler (just setting the config flag, wrapping the handler manually, using vendor-specific distributed tracing packages ...)? |
Beta Was this translation helpful? Give feedback.
Hi,
We originally added the handler to YARP as a workaround to bridge the gap in
SocketsHttpHandler
, where it couldn't make use of distributed tracing out of the box.The good news is that we made a lot of improvements in the area for the 6.0 release with the introduction of the
DistributedContextPropagator
class. As part of the change, we enabled distributed tracing onSocketsHttpHandler
by default as well, including the option to configure it via theActivityHeadersPropagator
property.As such, the scenario is expected to "just work" in YARP on .NET 6.0 and newer by default, there is no need to use workarounds like the
ActivityPropagationHandler
.For versions before 6.0, YARP will work …