-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing traces #2517
Comments
Hey @BartNetJS ! Thanks for opening this issue. |
I see the issue. Tracetest doesn't know how to handle multiple trace roots at once. I'll work on a fix for that. |
After the PR gets merged, I'll release version 0.11.8 with that patch. Thanks again for reporting your issues! That's really helpful for us. |
Hey @BartNetJS. I worked on a fix for your problem and I'm releasing 0.18.8 right now. You can either:
If you have any problems, let me know. |
Great @mathnogueira! , A small issue. |
Seems a problem with the websocket updates. I'll check it tomorrow and I'll let you know when that's fixed. Thanks for being active and reporting the issues you are seeing and suggesting features. I speak for the whole team when I say this is one of the most valuable things for an open-source project. |
I'm missing traces after my test runs.
I can see the traces in jaeger:
But in tracetest i see only one trace
The max wait time is set to 5 minutes, but it doesn't wait that long.
In the documentation https://docs.tracetest.io/configuration/trace-polling/ is see "Has the span # changed"
What does that mean?
And what could be my issue?
This is the full jaeger trace file:
trace.txt
The text was updated successfully, but these errors were encountered: