Where Does Jaeger Store Traces and Config?
Jaeger trace storage backend paths and config file spots on Linux for self-hosted tracing. Covers defaults.
Last updated
Jaeger keeps trace config in launch flags with sampling and storage backend. Spans themselves live in Cassandra or Elasticsearch per those flags. The flags decide retention.
All in one binaries default to memory storage for tests. Production installs point at persistent backends with separate dumps. Back up the backend database with launch configs. Memory spans vanish on every restart. Sampling trims trace volume. Dependencies map service calls. Tags filter slow spans. Retention drops old traces first.
Where Jaeger stores this, by platform
/etc/jaeger/sampling.json
Sampling strategies file referenced by collectors when used. Version in git for team review. Reload collectors after edits.
/var/lib/jaeger/badger
Badger local backend directory when selected over Cassandra or ES. Defaults under /tmp for all-in-one tests. Copy with Jaeger stopped.
Frequently asked questions
what do i back up for a Jaeger move
Back up the backend database for the chosen span storage. Traces live in Cassandra or Elasticsearch per flags. Config files hold sampling. Both restore history.
where are Jaeger spans stored
Open the launch flags or docker env to read SPAN_STORAGE_TYPE. Binaries default to memory, packages use Cassandra or ES. The flag decides where spans land.
Notice an outdated path? Let us know.