jaeger 2.6.0 compability with Elasticsearch 8.X

[VolodymyrVolodymyrovych]

Hello!

I have the issue with compability with Jaeger 2.6.0 with Elastic 8.X. It's my config:

service:
  extensions: [jaeger_storage, jaeger_query, healthcheckv2]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [jaeger_storage_exporter]
  telemetry:
    resource:
      service.name: jaeger
    metrics:
      level: detailed
      readers:
        - pull:
            exporter:
              prometheus:
                host: 0.0.0.0
                port: 8888
    logs:
      level: debug
    # TODO Initialize telemetry tracer once OTEL released new feature.
    # https://github.com/open-telemetry/opentelemetry-collector/issues/10663

extensions:
  healthcheckv2:
    use_v2: true
    http:

  jaeger_query:
    storage:
      traces: elastic_storage
      #traces_archive: another_elastic_storage
    ui:
      config_file: ./config-ui.json

  jaeger_storage:
    backends:
      elastic_storage:
        elasticsearch:
          server_urls:
            - https://elastic.com
          indices:
            index_prefix: "jaeger-main"
            spans:
              date_layout: "2006-01-02"
              rollover_frequency: "day"
              shards: 5
              replicas: 1
            services:
              date_layout: "2006-01-02"
              rollover_frequency: "day"
              shards: 5
              replicas: 1
            dependencies:
              date_layout: "2006-01-02"
              rollover_frequency: "day"
              shards: 5
              replicas: 1
            sampling:
              date_layout: "2006-01-02"
              rollover_frequency: "day"
              shards: 5
              replicas: 1
      #another_elastic_storage:
      #  elasticsearch:
      #    server_urls:
      #      - http://localhost:9200
      #    indices:
      #      index_prefix: "jaeger-archive"

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:

exporters:
  jaeger_storage_exporter:
    trace_storage: elastic_storage

After running the command I have an error:

./jaeger --config=config-elastic.yaml (I used binary)

Error: cannot start pipelines: failed to start "jaeger_storage_exporter" exporter: cannot create trace writer: failed to create template "jaeger-main-jaeger-span": error creating index template jaeger-main-jaeger-span: [400 Bad Request] {"error":{"root_cause":[{"type":"parse_exception","reason":"request body is required"}],"type":"parse_exception","reason":"request body is required"},"status":400}
2025/05/23 10:48:48 cannot start pipelines: failed to start "jaeger_storage_exporter" exporter: cannot create trace writer: failed to create template "jaeger-main-jaeger-span": error creating index template jaeger-main-jaeger-span: [400 Bad Request] {"error":{"root_cause":[{"type":"parse_exception","reason":"request body is required"}],"type":"parse_exception","reason":"request body is required"},"status":400}

Is it Jaeger 2.6.0 compatible with Elastic 8.X ? Give me please some suggestions :) Maybe I need to use an older version?
Thanks!

[yurishkuro]

All releases are tested against ES v8, e.g. the recent run, which has a config similar to yours.

My guess is this is related to your setup.

The error {"type":"parse_exception","reason":"request body is required"} is odd. Do you have some kind of proxy between jaeger and ES?

[VolodymyrVolodymyrovych]

Sorry for inaccurate information, I have the elastic 9, and jaeger see it:

info    config/config.go:302    Elasticsearch detected  {"otelcol.component.id": "jaeger_storage", "otelcol.component.kind": "extension", "version": 9}

yes, I have ... it's nginx which is configured to use instead http://elastic.com:9200 to https://elastic.com

[yurishkuro]

V9 is not supported atm.

[VolodymyrVolodymyrovych]

ok, thanks a lot

[dosubot[bot]]

Jaeger 2.6.0 is compatible with Elasticsearch 8.X—this is confirmed in the official documentation, which states that Jaeger supports Elasticsearch versions 7.x and 8.x, and will automatically detect and use the correct API and index mappings for your Elasticsearch version (source).

The error you are seeing:

error creating index template jaeger-main-jaeger-span: [400 Bad Request] {"error":{"root_cause":[{"type":"parse_exception","reason":"request body is required"}],"type":"parse_exception","reason":"request body is required"},"status":400}

means that Jaeger is sending a request to Elasticsearch to create an index template, but the request body is empty when Elasticsearch expects data. This can happen due to a misconfiguration or a missing part of the configuration that results in Jaeger not sending the required template definition (source).

Suggestions:

1. Check your Elasticsearch endpoint:
   The server_urls field in your config is set to https://elastic.com, which is not a valid Elasticsearch server endpoint. It should point to your actual Elasticsearch instance, e.g., http://localhost:9200 or your cluster's address.

2. Explicitly set the Elasticsearch version:
   If auto-detection fails, you can explicitly set the version in your config under the elasticsearch section:

   elasticsearch:
     version: 8
     server_urls:
       - http://your-elasticsearch-host:9200
     ...

3. Review your index template configuration:
   Make sure there are no missing or misconfigured fields in your indices section. Compare your config with the official sample config to ensure all required fields are present.

4. Elasticsearch authentication:
   If your Elasticsearch instance requires authentication (username/password or API key), ensure those credentials are included in your config.

Summary:
Jaeger 2.6.0 should work with Elasticsearch 8.X. The error is likely due to an invalid Elasticsearch endpoint or a misconfiguration in your Jaeger config, resulting in an empty request body when creating index templates. Double-check your server_urls and other config fields, and try explicitly setting the Elasticsearch version if needed.

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}