Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Compression and encoding
Tempo can compress traces that it pushes to backend storage. This requires extra
memory and CPU, but it reduces the quantity of stored data.
Anecdotal tests suggest that
zstd will cut your storage costs to ~15% of the uncompressed amount.
It is highly recommended to use the default
Compression is configured under storage like so:
storage: trace: block: v2_encoding: zstd
The following options are supported:
Although all of these compression formats are supported in Tempo, at Grafana
zstd. It’s possible/probable that the other compression algorithms may have issue at scale.
File an issue if you have any problems.
The WAL also supports compression. By default, this is configured to use
snappy. This comes with a small performance
penalty but reduces disk I/O and and adds checksums to the WAL. All of the above configuration options are supported
snappy has been tested at scale.
storage: trace: wal: v2_encoding: snappy