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
{{ message }}
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.
I'm having a problem where traces sent by version 72eb374947a2ef5291457d86d00eb689d9a23fa4 latest commit, aren't picked up by our services, instead a gateway service generates own trace_id which is carried over to other backends. I started reviewing code and notice the spanName isn't used, but passed with values like HTTP OPTIONS. Should users be able to configure it in Http constructor?
The text was updated successfully, but these errors were encountered:
Is this intentional?
xk6-distributed-tracing/client/client.go
Line 83 in 72eb374
I'm having a problem where traces sent by version
72eb374947a2ef5291457d86d00eb689d9a23fa4
latest commit, aren't picked up by our services, instead a gateway service generates own trace_id which is carried over to other backends. I started reviewing code and notice the spanName isn't used, but passed with values likeHTTP OPTIONS
. Should users be able to configure it in Http constructor?The text was updated successfully, but these errors were encountered: