-
|
Is it possible to use the traces that the otel collector exported to a custom index in elasticsearch without having to make the traces go through the jaeger collector or the ingester (when coming from kafka)? If so, I would like to know how to do it. Today my structure is like this: App sends to the otel collector, the otel collector exports to elasticsearch with a dynamic index (traces-appName.otel-environment) and I would like to deploy the jaeger ui to read this specific index, probably having 1 jaeger ui per deployed app. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @Kaua3045! I'm Dosu and I’m helping the jaeger team. Based on the available information, it is not currently possible to use Jaeger UI to read traces exported by the OpenTelemetry (otel) collector directly to a custom index in Elasticsearch unless those traces are stored in the format and indices expected by Jaeger’s backend (query-service). The Jaeger UI does not connect directly to Elasticsearch; it relies on the Jaeger query-service, which is responsible for querying trace data from the storage backend. All configuration related to which indices are read is handled by the backend, not the UI itself. The Jaeger backend allows you to customize Elasticsearch index names using options like If you want to have one Jaeger UI per app, each showing only traces for that app, you would need to ensure that the traces are ingested and indexed by Jaeger using its expected conventions, and then use the No documentation or issues were found that describe a supported way to achieve this setup without routing traces through Jaeger components. If you have a strong requirement for this architecture, it may require custom development or a different approach to trace visualization. To reply, just mention my name @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Hi @Kaua3045! I'm Dosu and I’m helping the jaeger team.
Based on the available information, it is not currently possible to use Jaeger UI to read traces exported by the OpenTelemetry (otel) collector directly to a custom index in Elasticsearch unless those traces are stored in the format and indices expected by Jaeger’s backend (query-service). The Jaeger UI does not connect directly to Elasticsearch; it relies on the Jaeger query-service, which is responsible for querying trace data from the storage backend. All configuration related to which indices are read is handled by the backend, not the UI itself.
The Jaeger backend allows you to customize Elasticsearch index names using options …