acceptable-rose-47165
03/16/2022, 1:21 PMtracing:
service_name: "kratos"
providers:
jaeger:
propagation: w3c
sampling:
type: const
value: 1
server_url: <http://localhost:14250/sampling>
local_agent_address: localhost:6831
provider: jaeger
So the problems I’m seeing are:
1. The Traceparent
header received from the request isn’t being propagated, so a new trace is started when it reaches Kratos. (Logs show that this header is present).
2. Kratos itself isn’t propagating the trace ID’s correctly. What should be multiple spans within a single trace are actually creating multiple traces with a single span in each.
Has anyone run into this problem, know how to solve it, or have a working configuration?acceptable-rose-47165
03/16/2022, 2:25 PMmigration-status
trace works how I’d expect, with all the database transactions included in the same trace. However, for /sessions/whoami
, an new trace is created for the top level request and for each resulting database transaction. And it doesn’t pick up the existing trace that was started by the proxy before it.magnificent-energy-493