Update storage.md to provide right-sizing advice on retention

Signed-off-by: Sean Killeen <SeanKilleen@gmail.com>
This commit is contained in:
Sean Killeen 2024-07-15 12:30:16 -04:00 committed by GitHub
parent d7d06b40d4
commit f031fe1fa3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -137,6 +137,18 @@ will be used.
Expired block cleanup happens in the background. It may take up to two hours Expired block cleanup happens in the background. It may take up to two hours
to remove expired blocks. Blocks must be fully expired before they are removed. to remove expired blocks. Blocks must be fully expired before they are removed.
## Right-Sizing Retention Size
If you are utilizing `storage.tsdb.retention.size` to set a size limit, you
will want to consider the right size for this value relative to the storage you
have allocated for Prometheus. It is wise to reduce the retention size to provide
a buffer, ensuring that older entries will be removed before the allocated storage
for Prometheus becomes full.
At present, we recommend setting the retention size to, at most, 80-85% of your
allocated Prometheus disk space. This increases the likelihood that older entires
will be removed prior to hitting any disk limitations.
## Remote storage integrations ## Remote storage integrations
Prometheus's local storage is limited to a single node's scalability and durability. Prometheus's local storage is limited to a single node's scalability and durability.