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

Extend vulture to generate long-running traces #791

Closed
kvrhdn opened this issue Jun 24, 2021 · 0 comments · Fixed by #951
Closed

Extend vulture to generate long-running traces #791

kvrhdn opened this issue Jun 24, 2021 · 0 comments · Fixed by #951
Assignees

Comments

@kvrhdn
Copy link
Member

kvrhdn commented Jun 24, 2021

Is your feature request related to a problem? Please describe.
Vulture currently generates random traces and sends them in a single batch to Tempo. To improve our test coverage we'd also like to send long-running traces, i.e. traces that will span multiple blocks in Tempo.

The ingester considers a trace complete after a configurable idle period (by default 30s). If vulture can send spans with a longer delay between them they should end up in different blocks and Tempo will have to do additional work to combine all spans into a single trace when requested.

Describe the solution you'd like
Vulture is currently stateless and ideally it stays stateless.

The following should probably be configurable:

  • a setting to enable/disable long-running traces
  • the delay between send requests

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants