Archive Storage in Jaeger

[Shin-Thant]

Hi! I'm using Jaeger all-in-one, and use YAML config. I enabled archive storage and set up a store for archive storage. However, although I clicked the Archive button, it doesn't store and expires after one minute. I checked if there is a directory for archive storage, and there is.

This is config.yaml 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: "${env:JAEGER_LISTEN_HOST:-localhost}"
                port: 8888
    logs:
      level: info

extensions:
  healthcheckv2:
    use_v2: true
    http:
      endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:13133"
    grpc:

  jaeger_query:
    storage:
      traces: main_storage
      traces_archive: archive_storage
    ui:
      config_file: /my-config/config-ui.json

  jaeger_storage:
    backends:
      main_storage:
        badger:
          directories:
            keys: "/tmp/jaeger/"
            values: "/tmp/jaeger/"
          ephemeral: false
          ttl:
            spans: 1m # 2 days
      archive_storage:
        badger:
          directories:
            keys: "/tmp/jaeger_archive/"
            values: "/tmp/jaeger_archive/"
          ephemeral: false
          ttl:
            spans: 1h # 30 days

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:4317"
      http:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:4318"

  jaeger:
    protocols:
      grpc:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:14250"
      thrift_http:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:14268"
      thrift_binary:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:6832"
      thrift_compact:
        endpoint: "${env:JAEGER_LISTEN_HOST:-localhost}:6831"

processors:
  batch:

exporters:
  jaeger_storage_exporter:
    trace_storage: main_storage

This is config-ui.json file.

{
  "archiveEnabled": true
}

[dosubot[bot]]

Jaeger’s Badger backend supports separate TTL and directories for main and archive storage, and your YAML config looks correct in that regard. The archive feature in the UI only triggers the backend to move traces; actual retention is controlled by the backend config and TTL settings. If traces in archive storage are still expiring after one minute, double-check that the archive storage directory is not overlapping with the main storage, and that the TTL for archive storage is set as intended (in your config, it’s 1 hour). Also, make sure ephemeral mode is set to false for both stores, as ephemeral storage will not persist data.

If the issue persists, check Jaeger’s logs for errors related to storage or permissions, and confirm that the backend is actually writing to the archive directory. The code expects clean separation between main and archive backends, including directories and TTLs, for correct operation. Most issues with traces expiring too quickly are due to TTL misconfiguration, ephemeral storage, or directory overlap between main and archive stores. There are no recent code-level limitations or bugs documented that would prevent Badger from being used for archive storage if configured properly¹².

To reply, just mention @dosu.

---

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

Footnotes

1. Badger backend factory and TTL handling ↩

2. Badger backend config options ↩