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

Distributed query tracing #1312

Closed
MichaelScofield opened this issue Apr 3, 2023 · 3 comments
Closed

Distributed query tracing #1312

MichaelScofield opened this issue Apr 3, 2023 · 3 comments
Labels
C-feature Category Features

Comments

@MichaelScofield
Copy link
Collaborator

What problem does the new feature solve?

Can't see the status of distributed query, hard to debug.

What does the feature do?

Add distributed query tracing, and visualize it.

Implementation challenges

No response

@MichaelScofield MichaelScofield added the C-feature Category Features label Apr 3, 2023
@waynexia
Copy link
Member

waynexia commented Apr 3, 2023

can #1023 + jaeger solve this?

@MichaelScofield
Copy link
Collaborator Author

Part of it, #1023 is too broad, we need more domain specific tracing.

@waynexia
Copy link
Member

A rough plan:

  1. request first comes to frontend in any protocol
  2. frontend assigns a trace id (a random u64 for now) to the context
  3. pass the trace id all around
  4. record the trace id in trace span (from minitrace)
  5. feed minitrace records to jaeger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category Features
Projects
None yet
Development

No branches or pull requests

4 participants