I tried using this with emojivoto, but I'm having trouble with context propagation.
Tracing a single service works fine but the traffic across some services is traced as different trace id.
Expected Behavior
Trace ID is propagated across multiple services
Actual Behavior
A series of events across multiple services are traced as different traces
Hi, thanks for such a nice project!
I tried using this with emojivoto, but I'm having trouble with context propagation. Tracing a single service works fine but the traffic across some services is traced as different trace id.
Expected Behavior
Trace ID is propagated across multiple services
Actual Behavior
A series of events across multiple services are traced as different traces
Steps to Reproduce the Problem
curl "http://your-node-ip:30084/api/list"
http://your-node-ip:30081
and check the traced dataAdditional Info
Kubernetes version:
Output of
kubectl version
:operation-system/kernel version:
Output of
awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release
: Output ofuname -r
: