-
For example, imagine using local disk as the storage backend. Can I limit the data by time (e.g. store data for a month only) or limit data by storage (e.g. store only 1 TB of data and delete oldest entries if the limit is reached)? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi! Yes, the compactor is the component tasked with handling data retention. Retention in Tempo is defined based on time. To configure it, use the |
Beta Was this translation helpful? Give feedback.
-
I would also recommend setting a lifecycle policy on your object storage that deletes objects a day or two after your Tempo retention. If a compactor or ingester OOMs while creating a block it can orphan objects and Tempo will lose track of them. This should be rare, but a lifecycle policy will prevent these objects from existing forever. |
Beta Was this translation helpful? Give feedback.
Hi! Yes, the compactor is the component tasked with handling data retention. Retention in Tempo is defined based on time. To configure it, use the
compactor.block_retention
config option. It defaults to 14 days. Once that a block is older than the configured retention period, the compactor will delete it.