You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Apologies if this feels less like a GH Issue and more like a GH Discussion).
I have a project that is using Hasura as a GraphQL federation layer as well as for inter-process communication.
The flow is as follows:
First, an external GraphQL client calls Hasura. Then...
Hasura forwards the request to an internal Go server, sending along B3 headers
The Go service runs on Gin HTTP and is instrumented with this NR Go Agent. This is the part I haven't figured out yet — Gin middleware needs to be able to extract the B3 headers to ascertain the trace ID and parent span.
The Go service makes a B3 instrumented request to Hasura using the nrb3 module.
Summary
Hello 👋🏼
(Apologies if this feels less like a GH Issue and more like a GH Discussion).
I have a project that is using Hasura as a GraphQL federation layer as well as for inter-process communication.
The flow is as follows:
First, an external GraphQL client calls Hasura. Then...
nrb3
module.Hasura only supports B3 headers for propagation, whereas New Relic (from what I gather) only supports W3C headers.
Desired Behaviour
The desired behavior would be to see hierarchical spans all under one trace.
Possible Solution
Unsure. I'm exploring a resolution on the Hasura side where we simply alias the b3 headers as w3c headers.
Additional context
The text was updated successfully, but these errors were encountered: