Jaeger 2.15 has issues with Operation dropdown.

[erlicthemad]

When working with Jaeger after upgrading to 2.15, the Operation dropdown starts showing an error.

Under 2.14.1

After upgrading to 2.15

The backend is set for OpenSearch and appears to work.

This is the Jaeger OpenSearch config. Based on the examples in the Git Repo referenced in the docs.

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: info
    # TODO Initialize telemetry tracer once OTEL released new feature.
    # https://github.com/open-telemetry/opentelemetry-collector/issues/10663

extensions:
  healthcheckv2:
    use_v2: true
    component_health:
      include_permanent_errors: false
      include_recoverable_errors: true
      recovery_duration: 5m
    http:
      endpoint: "127.0.0.1:13133"
      status:
        enabled: true
        path: "/health/status"
      config:
        enabled: true
        path: "/health/config"
    grpc:
      endpoint: "127.0.0.1:13132"
      transport: "tcp"
      tls:
        enabled: true
        cert_file: /etc/jaeger/ssl/fullchain.pem
        key_file: /etc/jaeger/ssl/privkey.pem
        ca_file: /etc/jaeger/ssl/fullchain.pem

  jaeger_query:
    storage:
      traces: some_storage
      metrics: some_storage
      traces_archive: another_storage
    ui:
      config_file: /etc/jaeger/ui-config.json
      log_access: false
    http:
      endpoint: "0.0.0.0:16686"
      tls:
        enabled: true
        cert_file: /etc/jaeger/ssl/fullchain.pem
        key_file: /etc/jaeger/ssl/privkey.pem
        ca_file: /etc/jaeger/ssl/fullchain.pem

  jaeger_storage:
    backends:
      some_storage: &opensearch_config
        opensearch:
          server_urls:
            - "https://prometheus.wizardsunlimited.com:9200"
          # custom_headers:
          #   Host: "my-opensearch-domain.us-east-1.es.amazonaws.com"
          #   X-Custom-Header: "custom-value"
          tls:
            insecure: false
            ca_file: /etc/jaeger/ssl/fullchain.pem
          auth:
            basic:
              username: "admin"
              password: ""
          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_storage:
        opensearch:
          server_urls:
            - "https://prometheus.wizardsunlimited.com:9200"
          tls:
            insecure: false
            ca_file: /etc/jaeger/ssl/fullchain.pem
          auth:
            basic:
              username: "admin"
              password: ""
          indices:
            index_prefix: "jaeger-archive"
    # Optional, enable metrics backend to use Monitor tab
    metric_backends:
      some_storage: *opensearch_config
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "0.0.0.0:4317"
        tls:
          enabled: true
          cert_file: /etc/jaeger/ssl/fullchain.pem
          key_file: /etc/jaeger/ssl/privkey.pem
          ca_file: /etc/jaeger/ssl/fullchain.pem
      http:
        endpoint: "0.0.0.0:4318"
        tls:
          enabled: true
          cert_file: /etc/jaeger/ssl/fullchain.pem
          key_file: /etc/jaeger/ssl/privkey.pem
          ca_file: /etc/jaeger/ssl/fullchain.pem
processors:
  batch:

exporters:
  jaeger_storage_exporter:
    trace_storage: some_storage

These are some of the errors I am seeing. They do not appear to be related to this issue specifically.

`
Feb 15 13:37:46 prometheus jaeger[4005624]: 2026-02-15T13:37:46.392Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: read tcp 127.0.0.1:59212->127.0.0.1:4317: read: connection reset by peer" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}
Feb 15 13:37:47 prometheus jaeger[4005624]: 2026-02-15T13:37:47.394Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: read tcp 127.0.0.1:59216->127.0.0.1:4317: read: connection reset by peer" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}
Feb 15 13:37:49 prometheus jaeger[4005624]: 2026-02-15T13:37:49.120Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: EOF" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}
Feb 15 13:37:51 prometheus jaeger[4005624]: 2026-02-15T13:37:51.480Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: EOF" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}
Feb 15 13:37:55 prometheus jaeger[4005624]: 2026-02-15T13:37:55.116Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: read tcp 127.0.0.1:34574->127.0.0.1:4317: read: connection reset by peer" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}
Feb 15 13:37:56 prometheus jaeger[4005624]: 2026/02/15 13:37:56 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:38:01 prometheus jaeger[4005624]: 2026-02-15T13:38:01.912Z warn grpc@v1.78.0/clientconn.go:1526 [core] [Channel #3 SubChannel #8] grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "error reading server preface: EOF" {"resource": {"service.instance.id": "e499f30b-6b4b-4d65-95d6-9bf68d87933b", "service.name": "jaeger", "service.version": "v2.15.0"}, "grpc_log": true}

`

[dosubot[bot]]

Hi @erlicthemad! I'm Dosu and I’m helping the jaeger team.

This is a known bug in Jaeger v2.15.0 that was reported and fixed. The issue occurs because the OpenSearch/Elasticsearch backends don't store or return the spanKind field for operations, but the UI in 2.15.0 started requiring it via schema validation.

Solution: Upgrade to Jaeger v2.15.1 which was released specifically to fix this. The fix defaults empty spanKind values to "internal" on the backend side.

The gRPC connection errors you're seeing (127.0.0.1:4317) are a separate issue - those appear to be Jaeger's internal telemetry trying to export traces to itself. This is unrelated to the Operation dropdown problem.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[erlicthemad]

Thanks, I will get the 2.15.1 and give it a try.