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.

Sign up for GitHub

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

Jump to bottom

Span duplication on tracing ingestion #1230

Closed
2 tasks
inancgumus opened this issue Mar 4, 2024 · 2 comments
Closed
2 tasks

Span duplication on tracing ingestion #1230

inancgumus opened this issue Mar 4, 2024 · 2 comments
Labels
bug Something isn't working next Might be eligible for the next planning (not guaranteed!)

Comments

@inancgumus
Copy link
Member

inancgumus commented Mar 4, 2024 •
edited
Loading

What?

@DefCon-007:

The http endpoints directly proxy tempo, so I guess duplication may happen at ingestion time in the browser itself.

  • TraceID: 1f104d305b61f1ef3b5f91511a089b13

  • Test Run ID (staging): 166704

See @w1kman's internal message for details.

Version: k6 0.49

Why?

No response

How?

No response

Tasks

Tasks
Preview Give feedback

Related PR(s)/Issue(s)

No response
@inancgumus inancgumus added the bug Something isn't working label Mar 4, 2024
@inancgumus inancgumus changed the title Keep the title concise. Use the common language we can use to identify the issue. Span duplication on tracing ingestion Mar 4, 2024
@inancgumus inancgumus added the next Might be eligible for the next planning (not guaranteed!) label Mar 4, 2024
@w1kman
Copy link

w1kman commented Mar 5, 2024

Seems to be an issue only when I have more than one browser VU.

  • 100% of the time, it works with 1 VU
  • 100% of the time, it DOESNT work with 2 VUs

@ankur22
Copy link
Collaborator

ankur22 commented Mar 7, 2024

This was fixed thanks to #1219 🎉

@ankur22 ankur22 closed this as completed Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working next Might be eligible for the next planning (not guaranteed!)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@inancgumus @ankur22 @w1kman