How to change span store ttl for Jaeger V2?

[norin-dlkh]

Hi everyone,
I tried to change span store ttl in jaeger:2.5.0 but it doesn't seem like it's working.

In version 1, we can use --badger.span-store-ttl param to adjust to expire of the span. But, for V2, I have follow the migration guide on google doc but it doesn't seem like it's working.

Here is my config.yml

...
     jaeger_query:
        storage:
          traces: primary_store
          traces_archive: archive_store
          metrics: metrics_storage
        ui:
          config_file: /jaeger/config-ui.json


      jaeger_storage:
        backends:
          primary_store:
            badger:
              ttl:
                span_store: 720h

              directories:
                keys: "/app/data"
                values: "/app/data"
              ephemeral: false

            memory:
              max_traces: 100000
...

I got some error when running with the above configuration;

Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

error decoding 'extensions': error reading configuration for "jaeger_storage": decoding failed due to the following error(s):

error decoding 'backends[primary_store]': decoding failed due to the following error(s):

'badger.ttl' has invalid keys: span_store
2025/05/09 07:16:24 failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

error decoding 'extensions': error reading configuration for "jaeger_storage": decoding failed due to the following error(s):

error decoding 'backends[primary_store]': decoding failed due to the following error(s):

'badger.ttl' has invalid keys: span_store

Anyone know how to fix this?

[norin-dlkh]

Wait, just a random input value, when I use ttl.spans, it seems like it is no longer crash. Not sure if it's the correct value. Will see if it's working as I expect.

[Sawn-CG]

did it work?

[norin-dlkh]

Nope, it doesn't. I can only retrieve data in the last few day only. Further than that, no data is response

[Sawn-CG]

have you tried setting env var BADGER_SPAN_STORE_TTL=120h as said in https://github.com/orgs/jaegertracing/discussions/6250.
I tried, now the querier service does not start in jaeger v2

[yurishkuro]

badger:
  directories:
    ...
  ttl:
    spans: 720h

[norin-dlkh]

  service:
  extensions: [jaeger_storage, jaeger_query, healthcheckv2]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [jaeger_storage_exporter, spanmetrics]
    metrics/spanmetrics:
      receivers: [spanmetrics]
      exporters: [prometheus]
  telemetry:
    resource:
      service.name: jaeger
    metrics:
      level: detailed
      readers:
        - pull:
            exporter:
              prometheus:
                host: 0.0.0.0
                port: 14269
    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:
      endpoint: 0.0.0.0:14133
      status:
        enabled: true
        path: "/status"

  jaeger_query:
    storage:
      traces: primary_store
      traces_archive: archive_store
      metrics: metrics_storage
    ui:
      config_file: /jaeger/config-ui.json


  jaeger_storage:
    backends:
      primary_store:
        badger:
          directories:
            keys: "/app/data"
            values: "/app/data"
          ephemeral: false
          ttl:
            spans: 720h
        memory:
          max_traces: 100000
      archive_store:
        badger:
          directories:
            keys: "/app/jaeger_archive/"
            values: "/app/jaeger_archive/"
          ephemeral: false
          ttl:
            spans: 720h
        memory:
          max_traces: 100000
    metric_backends:
      metrics_storage:
        prometheus:
          endpoint: http://prometheus:9090
          normalize_calls: true
          normalize_duration: true

connectors:
  spanmetrics:

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "0.0.0.0:4317"
      http:
        endpoint: "0.0.0.0:4318"


processors:
  batch:



exporters:
  jaeger_storage_exporter:
    trace_storage: primary_store
    queue:
      num_consumers: 50
      queue_size: 1000
  prometheus:
    endpoint: "0.0.0.0:14270"

Here is my full config, but it doesn't seem working. It doesn't crash but when I tried query back date for more than 2 days, no data is response.