-
Notifications
You must be signed in to change notification settings - Fork 338
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
feat: add jaeger rest endpoints for grafana tracing support #4197
feat: add jaeger rest endpoints for grafana tracing support #4197
Conversation
.map(|result| make_jaeger_api_response(result, BodyFormat::default())) | ||
} | ||
|
||
/// GET otel-traces-v0_6/traces/{trace-id-base-64} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would avoid putting the "otel-traces-v0_6/traces/{trace-id-base-64}" in comment, if we do correctly the openapi stuff it should be sufficient.
Just say "Get trace by ID", it's singular.
.into_inner(); | ||
|
||
Ok(JaegerSearchBody { | ||
data: Some(get_operations_response.operation_names), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
operation names is empty, it's a bit strange. if you take get_operations_response.operations.into_iter().map(|op| op.name).collect_vec()
instead, it will work in grafana
@guilload did you see this weird empty operation name list?
Refactor parse duration for jaeger.
😅🎉 |
Description
Add jaeger rest endpoints for grafana tracing support
TODO:
go_parse_duration
dependencyutil.rs
intomodels.rs
(can we get rid of some of them?)Related issues:
quickwit-oss/quickwit-datasource#5