Support Grafana tracing view(s)

[fmassot]

To support the Jaeger grafana plugin without the jaeger-query layer, we need to implement the following REST endpoints:

• GET api/services
• GET api/services/{service}/operations
• GET api/traces?service={service}&start={start_in_ns}&end={end_in_ns}&lookback=custom
• GET api/traces/{trace-id-base-64}

The handlers of those endpoints should use the jaeger gRPC service.

[macthestack]

This would be great if possible!

In https://quickwit.io/blog/observing-rust-app-with-quickwit-jaeger-grafana it sure looks like someone's got it working.

[fmassot]

@macthestack I wrote this blog post :)

We could make Quickwit compatible with the Jaeger grafana plugin. From the plugin code, a Jaeger internal API is used api/traces instead of the gRPC API. We could either expose this API in Quickwit or just copy the frontend code of the Jaeger plugin and do the gRPC calls on the Quickwit backend plugin.

Note that tempo offers richer views (Service Graph and Service Graph view) and it could be nice to add that too in the plugin.

[etolbakov]

@fmassot I believe we can close this one right?

[fmassot]

Yes indeed!