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

Support Jaeger query APIs #5401

Open
zyy17 opened this issue Jan 20, 2025 · 0 comments
Open

Support Jaeger query APIs #5401

zyy17 opened this issue Jan 20, 2025 · 0 comments
Assignees
Labels
C-feature Category Features

Comments

@zyy17
Copy link
Collaborator

zyy17 commented Jan 20, 2025

What problem does the new feature solve?

The current GreptimeDB supports ingesting trace data by OTel; however, we don't provide a better way to render the data. To use Grafana or Jaeger UI, we should support Jaeger query APIs.

What does the feature do?

Implement Jaeger query APIs.

Implementation challenges

Although the Jaeger has v2 and v3 APIs, the v2 APIs are more compatible. We can implement v2 APIs at first.

The following APIs are used in Grafana Jaeger datasource:

  • /api/services/;
  • /api/traces;
  • /api/dependencies: Actually, get dependencies can be a flow task in GreptimeDB;
@zyy17 zyy17 added the C-feature Category Features label Jan 20, 2025
@zyy17 zyy17 self-assigned this Jan 20, 2025
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

1 participant