Jaeger 2.6.0 - write to an existing elasticsearch index

[MarkusOvervad]

Is it correctly understood, that it is not possible to write to an already existing index in elasticsearch?

[dosubot[bot]]

It is possible for Jaeger to write to an existing Elasticsearch index, but there are some important requirements and configuration steps:

• Jaeger can use read and write aliases for Elasticsearch indices. This setup requires you to create and manage the aliases externally before starting Jaeger. Jaeger itself does not create or manage these aliases automatically. This approach is often used with the Elasticsearch rollover API or Index Lifecycle Management (ILM) features. You can enable this with the es.use-aliases option, but you must ensure the aliases already exist and are managed outside of Jaeger.
  Reference

• You can disable Jaeger's automatic creation of index templates by setting es.create-index-templates to false. This allows you to manually create and manage your own index templates and indices before deploying Jaeger, which can include pointing Jaeger to existing indices or aliases.
  Reference

• If you want to use ILM, you must also manage the ILM policies and aliases externally, and this is only supported for Elasticsearch version 7 and above.
  Reference

In summary: Jaeger does not prevent you from writing to an existing Elasticsearch index, but you must configure it to use aliases and/or disable template creation, and you are responsible for preparing the indices and aliases in Elasticsearch before Jaeger starts. There are no known issues or discussions indicating that this is not possible in Jaeger 2.6.0.

To continue talking to Dosu, mention @dosu-bot.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}