Jaeger - Distributed Tracing Platform
Jaeger V2 and Elasticsearch mapping data problem #8184
-
|
Hi all, Jaeger started and running , but get some errors in logs At Jaeger UI , I get error "Error loading services: Failed to fetch services: 500" as screenshot There are 2 index templates created : jaeger-primary-jaeger-service , jaeger-primary-jaeger-span in Elasticsearch automatically There are 2 indices created : jaeger-primary-jaeger-span-2026-03-17 , jaeger-primary-jaeger-service-2026-03-17 in Elasticsearch automatically How can I fix this problem ? Please give me some advice, thank you very much. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Hi @jackchuong! I'm Dosu and I’m helping the jaeger team. The issue you're experiencing is a race condition between Jaeger's index template creation and Elasticsearch's auto-index creation. When spans arrive before templates are fully applied, Elasticsearch creates indices with its default dynamic mappings (fields as To fix this:
For a more robust setup, consider using ILM (Index Lifecycle Management) with the jaeger_storage:
backends:
primary_store:
elasticsearch:
use_aliases: true
use_ilm: true
create_mappings: false # Must be false when ILM is enabledBefore starting Jaeger with ILM:
The es-rollover init action explicitly creates templates before indices, eliminating the race condition. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
@dosu
As soon as Jaeger write spans to Elasticsearch , I get index mappings again , it is still wrong So index templates are not applied to new indices. |
Beta Was this translation helpful? Give feedback.
-
|
The key clue here is that when you pre-created the indices with This confirms your templates are not matching or not properly registered in Elasticsearch. Please verify your templates are actually visible to Elasticsearch: If these return the templates with mappings, also check:
If templates look correct but still aren't applying, the recommended approach for ES 8.x is to use ILM with the docker run --rm -e ES_SERVER_URLS=https://IP-of-ES:9200 \
-e ES_USERNAME=elastic -e ES_PASSWORD=****** \
-e ES_INDEX_PREFIX=jaeger-primary \
-e ES_USE_ILM=false \
jaegertracing/jaeger-es-rollover:latest initThis will create the proper templates and initial indices with correct mappings. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
@dosu I suspect that the template automatically generated by Jaeger is problematic, so the newly created indexes have no mappings. To resolve the requirement to keep the Jaeger indexes for 7 days, I tried the following two solutions:
Update index templates Delete , recreate indices , create alias --> new indices Let's wait and see if it works. |
Beta Was this translation helpful? Give feedback.
-
|
Great progress! Your manual template setup is the right approach given the issues with Jaeger's automatic template creation. Important for your ILM setup to work: Make sure your Jaeger configuration includes these settings: jaeger_storage:
backends:
primary_store:
elasticsearch:
use_aliases: true
use_ilm: true
create_mappings: false
# ... rest of your configWithout Also note from the ILM configuration discussion: when using ILM, you should not use date-based index naming in your template patterns. ILM manages index naming with a numeric suffix pattern (e.g., Your ILM policy looks good with the 1d/50gb rollover and 7d retention. Let us know if the ILM approach works or if you run into any issues! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
@dosu |
Beta Was this translation helpful? Give feedback.
-
|
Glad to hear you got it working! 🎉 For anyone else hitting this issue: the root cause was that Jaeger V2's automatic index template creation wasn't applying mappings correctly in Elasticsearch 8.x, resulting in fields being mapped as Thanks for following up with the solution! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
Great progress! Your manual template setup is the right approach given the issues with Jaeger's automatic template creation.
Important for your ILM setup to work: Make sure your Jaeger configuration includes these settings:
Without
use_aliases: true, Jaeger will continue writing to date-based indices directly (likejaeger-primary-jaeger-span-2026-03-19) instead of your write aliases (jaeger-primary-jaeger-span-write). This would bypass your ILM rollover configuration.Also note from the ILM configuration discu…