joe-elliott
commented
8 months ago We do not currently have any plans at the moment to provide this functionality. There's not a lot of great ways to do this now, but you've identified one: downloading the trace json and keeping it in some kind off shared storage that multiple team members have access to.
You could also create a second tenant with a longer retention and write a script that pulled a trace by id from tenant A and then write it to tenant B (with the longer retenion).
I would support the creation of an API that did this reading/writing automatically, but it would need to be behind a feature flag. Supporting this feature "correctly" would likely require some kind of verification or authorization process before copying traces between tenants.
github-actions[bot]
sam-mcbr
Is your feature request related to a problem? Please describe. We are trying to move from Jaeger to Tempo. One really helpful feature of Jaeger is the ability to archive spans and keep them around longer than regular spans. Are there plans to add this functionality to Tempo?
Describe the solution you'd like Would love to see a button in the Grafana Tempo UI (on the Explore tab) for archiving a trace, which maybe replicates it to a secondary blocks-storage location with a different retention than the single block storage, or prevents the compactor from removing the blocks in a single blocks-storage instance.
Describe alternatives you've considered Download the trance JSON and reupload when wanting to view it in the UI, or rolling a custom solution to mark traces with a tag that replicates them to a long-term storage location.