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.

Update to latest tracer is breaking - cannot exempt downstream service from header propagation.

See original GitHub issue

Describe the bug There was a change in how header propagation makes its way to downstream services as of the latest tracer versions. (Propagate trace tags to downstream services (horizontal propagation) (https://github.com/DataDog/dd-trace-dotnet/pull/2897)) I do not see a way to exempt certain downstream services from this feature. We have certain external services (think massive banks) that are throwing errors at the presence of unexpected headers. This same complaint was made on the JS side and implemented there. https://github.com/DataDog/dd-trace-js/issues/1601

Calling this as a bug in that we were functional until updating to the latest tracer version (2.12). Just installed 2.12 to a bunch of servers that I need to go manually downgrade as I need to inventory what external services are now rejecting our requests. Took a pretty big time investment to diagnose this across a few team members.

Added clarifications: servers were at various versions, all bumped to latest agent version of 7.37.1.1 and tracer version of 2.12.0 - errors were observed - situation was resolved by only downgrading tracer to version 2.11.0

outbound http call is executing in a netstandard2.0 class library that’s running in a full framework 4.7.2 webapi app

Issue Analytics

State:
Created a year ago
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

pierotiboucommented, Jul 25, 2022

Hello, Regarding the Feature request part of the issue, we’re discussing internally if we could add this feature across the board with the same behaviour/configuration for each tracer. But indeed, it makes sense to us to add the feature. I’ll update on this when we have more visibility on when we would schedule this work.

0reactions

andrewlockcommented, Aug 3, 2022

@mrtristan we have just released version 2.13.0 of the tracer, which should fix this issue. I’ll close this now, but feel free to re-open if you run into any problems, thanks.

Top Results From Across the Web

Unable to use the Golang otel http client to propagate B3 ...

My expectations are that all incoming headers (passed in by cURL command) are propagated to the downstream service, by using the otel http ......

Spring Cloud Sleuth

The most common propagation approach is to copy a trace context from a client by sending an RPC request to a server receiving...

A Strange Header Propagation Issue | by Ahmet Geymen

The first comment that can be made is that the Accept-Language header information was not transmitted during “from client to service b” propagation....

Java Agent version 1.x

Potentially breaking changesedit. The list of instrumentation groups for log-related features have been simplified to logging , log-reformatting , log ...

Changelog — Finagle 22.4.0 documentation

RetryPolicy will accept the new c.t.finagle.service. ... only one endpoint, since the client cannot do anything meaningful by breaking the circuit early.