-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
cli: include active trace spans in debug.zip #58608
Comments
Hi @tbg, I've guessed the C-ategory of your issue and suitably labeled it. Please re-label if inaccurate. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
Note that this motivates #58610 |
Just noticed this issue: have already included a select into debug.zip for the long-running trace spans vtable in #59492 but we can leave this open if we want the Jaeger-compatible output. |
To close this issue, we should also include the payloads for all of the long-running trace spans via #60922. |
Is your feature request related to a problem? Please describe.
Now that we have a way to observe long-running trace spans, we should also include them in debug.zip:
#55592
Describe the solution you'd like
Either dump (a suitably filtered) select on #55733 or add and hit an API endpoint straight into the registry.
The latter might be preferrable if we want Jaeger-compatible output.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: