Nauris Sadovskis

hey folks, any update on this?

I have not, but it seems it also does not support overriding incoming headers to construct new ones ?

@kpratyus exactly - Google Load Balancers do not use `traceparent` header and in our chain the conversion needs to happen in NGINX so we also can instrument the entire flow....

I should note that Google's format is compatible with W3C (if this was not immediately clear). Namely: ``` # Google: X-Cloud-Trace-Context 05d7c045f9cd3c474f9e6b733823fb44/14127515246394157611;o=1 ^ ^ | | trace id (32 chars)...

Hi @kpratyus, just to update this thread - we have found a temporary workaround by using and modifying [headers-more](https://www.nginx.com/resources/wiki/modules/headers_more/) module (see below) to run at an earlier stage and build...

We're having the issues when using V2 API too, so this is definitely still a problem which DataDog V2 API has not solved: ``` │ received non 2xx response code:...

cc: @meeech and @zachaller since both of you seem to be involved in getting DataDog API v2 functionality out :)

@zachaller @meeech - yes, this is ready for final review!