I'm trying to get Hydra (self-hosted in docker com...
# talk-hydrae
echoing-summer-66259
10/17/2022, 8:52 PMI'm trying to get Hydra (self-hosted in docker compose) traces parented to traces propagated from my backend service (service is calling admin/clients as a test). Is there some extra configuration that is required for this to work?
echoing-summer-66259
10/17/2022, 8:54 PMI've tried b3, b3multi and W3C Trace context, all with no result.
echoing-summer-66259
10/17/2022, 9:01 PMFWIW, this is with the Otel provider.
m
magnificent-energy-493
10/18/2022, 1:11 PM
Hello Christopher, did you see the tracing docs:
https://www.ory.sh/docs/hydra/self-hosted/tracing
https://www.ory.sh/docs/ecosystem/logging
Maybe those can be helpful figuring this out.
e
echoing-summer-66259
10/18/2022, 3:02 PMThat documentation is what lead me to believe that Hydra supported this: "Following existing traces: If you have deployed Hydra behind a proxy that has initiated a trace, Hydra will attempt to join that trace by examining the request headers for tracing context." However, that is not what I'm experiencing.
echoing-summer-66259
10/18/2022, 3:04 PMAs you can see, I have Hydra successfully reporting traces. I also have our backend service reporting traces. I've verified that the trace propagation works with "ExampleService" and I'm sending the same headers to Hydra.
echoing-summer-66259
10/18/2022, 3:06 PMFrom the logs:
Copy code
time=2022-10-18T15:00:10Z level=info msg=started handling request http_request=map[headers:map[accept:*/* accept-encoding:gzip, deflate, br b3:6f916dc508e869cb2cb71a976b80589f-0fddd5fa829e1b33-1 connection:close traceparent:00-6f916dc508e869cb2cb71a976b80589f-0fddd5fa829e1b33-01 user-agent:node-fetch x-b3-sampled:1 x-b3-spanid:0fddd5fa829e1b33 x-b3-traceid:6f916dc508e869cb2cb71a976b80589f] host:localhost:4445 method:GET path:/clients query:Value is sensitive and has been redacted. To see the value set config key "log.leak_sensitive_values = true" or environment variable "LOG_LEAK_SENSITIVE_VALUES=true". remote:172.22.0.1:45230 scheme:http] otel=map[span_id:0fddd5fa829e1b33 trace_id:6f916dc508e869cb2cb71a976b80589f]4 Views