Jaeger query other jaeger? #7944
Replies: 1 comment
-
|
Jaeger v2 can't be configured to query a generic Jaeger-compatible HTTP endpoint like the one VictoriaTraces exposes. Jaeger only supports specific storage backends: memory, badger, cassandra, elasticsearch, opensearch, clickhouse, and a gRPC-based "remote storage" API. There is no option to point Jaeger directly at an HTTP endpoint for querying traces (source). If VictoriaTraces implements Jaeger's gRPC Remote Storage API, you could use that as a backend by configuring Jaeger with the There isn't any official documentation or plugin for this scenario. If you need a Jaeger UI for VictoriaTraces, check if VictoriaTraces offers a gRPC remote storage endpoint, or consider building/requesting a bridge. Alternatively, you might want to look at UIs that natively support VictoriaTraces' HTTP API. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to set up jaeger v2, but only as a read-only UI. I'm running on kubernetes with various otel-collector objects already. I have a pre-existing jaegerless system and I'm ingesting data through otel-collectors into VictoriaTraces.
VictoriaTraces exposes a http jaeger endpoint for querying (
http://<vtselect-service>.<namespace>.svc.cluster.local:10471/select/jaeger), but I can't seem to find how a standalone jaeger instance would query a jaeger-compatible endpoint.Beta Was this translation helpful? Give feedback.
All reactions