Skip to content
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

Open
BartNetJS opened this issue May 10, 2023 · 6 comments
Open

Missing traces #2517

BartNetJS opened this issue May 10, 2023 · 6 comments
Assignees
Labels
bug Something isn't working triage requires triage user-request

Comments

@BartNetJS
Copy link

BartNetJS commented May 10, 2023

I'm missing traces after my test runs.
I can see the traces in jaeger:

image

But in tracetest i see only one trace

image

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

@BartNetJS BartNetJS added bug Something isn't working triage requires triage labels May 10, 2023
@adnanrahic
Copy link
Contributor

Hey @BartNetJS ! Thanks for opening this issue.
We'll have a look and get back to you ASAP.

@mathnogueira
Copy link
Contributor

I see the issue. Tracetest doesn't know how to handle multiple trace roots at once. I'll work on a fix for that.

@mathnogueira
Copy link
Contributor

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.

@mathnogueira
Copy link
Contributor

Hey @BartNetJS. I worked on a fix for your problem and I'm releasing 0.18.8 right now. You can either:

  1. Update your tracetest CLI to 0.18.8 in a few minutes and reinstall the server
  2. Update the docker tag you are running to use the tag v0.18.8

If you have any problems, let me know.

@BartNetJS
Copy link
Author

Great @mathnogueira! ,
Thanks for the quick fix.
I've installed the new version, and it looks already great!

A small issue.
When I run the test I see the followind result:
image
And if i click the 'timeline view' i got the error
image

When i refresh the page, it is rendered as expected:
image

@mathnogueira
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage requires triage user-request
Projects
None yet
Development

No branches or pull requests

3 participants