Users often ask for this feature. The trace retention period is usually short, and often people would put a link to the trace into some issue tracker to improve service performance, but by the time someone starts working on the ticket the trace has already expired.
— https://github.com/jaegertracing/jaeger-ui/issues/7
First use case I have for this is writing some user documentation for reading a trace :)
- on jaeger-query, set --es-archive.enabled=true & check if we need to change any of the other related --es-archive. values
- on jaeger-ui, set "archiveEnabled": true in the json config