Getting metrics with Opensearch with 2.14.1 or 2.15.

[erlicthemad]

I am trying to get the traces working with Jaeger and OpenSearch. I did attempt to follow the examples in the Git Repo, and after following some of the other threads, I have come up with this configuration. But when I go to look at Jaeger, it tells me there is no data. To test this, I am using otelgen to generate my traces.

All of my certificates are generated by Certbot and Let's Encrypt, making all the certs valid.

This is the screen that I see.

This is my configuration file.

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
      http:
        endpoint: "0.0.0.0:4318"
        tls:
          enabled: true
          cert_file: /etc/jaeger/ssl/fullchain.pem
          key_file: /etc/jaeger/ssl/privkey.pem

processors:
  batch:

exporters:
  jaeger_storage_exporter:
    trace_storage: some_storage

I am seeing the following in my logs as I try to accomplish this. I have also tried to add the ca_file for the OTLP receivers. This made no change.

These are the logs that I am getting from my journalctl. I have seen in other posts that Jeager is very picky about IPv4 and IPv6, while using IPv6 vs IPv4 at times. I did try to do this by disabling V6 on my Ubuntu server, which Jeager really does not like at all.

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}
Feb 15 13:38:11 prometheus jaeger[4005624]: 2026/02/15 13:38:11 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:38:13 prometheus jaeger[4005624]: 2026-02-15T13:38:13.477Z        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:38:28 prometheus jaeger[4005624]: 2026-02-15T13:38:28.108Z        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:38:59 prometheus jaeger[4005624]: 2026-02-15T13:38:59.708Z        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:39:35 prometheus jaeger[4005624]: 2026-02-15T13:39:35.385Z        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:40:49 prometheus jaeger[4005624]: 2026-02-15T13:40:49.871Z        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:42:29 prometheus jaeger[4005624]: 2026-02-15T13:42:29.740Z        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:43:46 prometheus jaeger[4005624]: 2026/02/15 13:43:46 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:43:56 prometheus jaeger[4005624]: 2026/02/15 13:43:56 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:44:06 prometheus jaeger[4005624]: 2026/02/15 13:44:06 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:44:22 prometheus jaeger[4005624]: 2026-02-15T13:44:22.565Z        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:44:51 prometheus jaeger[4005624]: 2026/02/15 13:44:51 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:45:06 prometheus jaeger[4005624]: 2026/02/15 13:45:06 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:45:31 prometheus jaeger[4005624]: 2026/02/15 13:45:31 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"
Feb 15 13:46:41 prometheus jaeger[4005624]: 2026-02-15T13:46:41.272Z        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:34986->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:48:48 prometheus jaeger[4005624]: 2026-02-15T13:48:48.788Z        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]]

The "error reading server preface: EOF" errors you're seeing are a known issue in Jaeger v2 when TLS is enabled on the OTLP receiver. These errors are from Jaeger's internal self-telemetry trying to export its own traces to 127.0.0.1:4317, but without matching TLS configuration—so it's attempting plain gRPC against your TLS-enabled endpoint.

The fix: Disable Jaeger's internal self-tracing by setting these environment variables before starting Jaeger:

OTEL_TRACES_SAMPLER=always_off
OTEL_TRACES_EXPORTER=none
OTEL_SDK_DISABLED=true

This is safe—it only disables Jaeger tracing itself, not your actual trace collection functionality.

Why this happens: Jaeger v2 doesn't yet support configuring TLS for internal telemetry exports (there's a TODO in the config noting this is pending an upstream OpenTelemetry Collector feature).

Good news: These errors are non-fatal and don't prevent your traces from being stored—they're just noisy retry attempts. Once you set those environment variables, the errors should stop.

For the "no data" issue in the Monitor tab specifically, make sure your otelgen traces are actually reaching Jaeger by checking if they appear in the Search tab first.

To reply, just mention @dosu.

---

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

   

[erlicthemad]

Thanks,
But it does not solve my initial question of getting metrics from my traces. I still get the message that there is no data yet. I have sent several traces to Jaeger from otelgen to try and generate some metrics.

[dosubot[bot]]

The Monitor tab metrics require more than just the metric_backends configuration—you need the spanmetrics connector in your pipeline to actually generate RED metrics from traces. Your current config stores traces but doesn't compute metrics from them.

There are two approaches for metrics with OpenSearch:

Option 1: Use OpenSearch for direct metrics querying
OpenSearch can compute metrics directly from stored trace data, but this requires that your traces are actually being stored. First verify traces appear in the Search tab.

Option 2: Add the spanmetrics connector + Prometheus
Add a spanmetrics connector to your pipeline that generates metrics, then export to Prometheus:

connectors:
  spanmetrics:

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [jaeger_storage_exporter, spanmetrics]
    metrics:
      receivers: [spanmetrics]
      exporters: [prometheus]

Important: If you're on v2.15.1, there's a known SPM regression causing the Monitor tab to show "no data" even with correct configuration. Consider using v2.15.0 or v2.14.1 until that's fixed.

Can you confirm whether traces are showing up in the Search tab?

To reply, just mention @dosu.

---

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

   

[erlicthemad]

I am trying to use OpenSearch for direct metrics querying. When I search in the Search tab, I see 6 traces that match the 6 I sent using otelgen. But when I go to the Metrics tab, it still says there is no data yet.

This same issue was observed in both v2.14.1 and v2.15.0.