upstream/prometheus
1
0
Fork 0
mirror of https://github.com/prometheus/prometheus.git synced 2026-02-19 02:29:16 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

explain how to ignore WAL files and cleanup resulting grafs

Browse source 
We don't want do backup WAL files, so we should show how to actually
ignore those files.

Also explain what happens every 2 hours a little more clearly.

Move things around so the paragraphs flow more easily.

Followup for #14297.

Signed-off-by: Antoine Beaupré <anarcat@debian.org>
Co-authored-by: Bryan Boreham <bjboreham@gmail.com>
This commit is contained in:
Antoine Beaupré 2024-06-19 14:07:09 -04:00
parent 93bbf4bc90
commit 54847efd17
No known key found for this signature in database
GPG key ID: 02293A6FA4E53473
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/storage.md
View file

@ -59,12 +59,16 @@ A Prometheus server's data directory looks something like this:
Note that a limitation of local storage is that it is not clustered or
replicated. Thus, it is not arbitrarily scalable or durable in the face of
drive or node outages and should be managed like any other single node
database.
database. With proper architecture, it is possible to retain years of
data in local storage.
[Snapshots](querying/api.md#snapshot) are recommended for backups. Backups
made without snapshots run the risk of losing data that was recorded since
the last WAL sync, which typically happens every two hours. With proper
architecture, it is possible to retain years of data in local storage.
the last TSDB block was created, which typically happens every two hours,
covering the last three hours of samples. Excluding the WAL files (the
`chunks_head/`, `wal/`, and `wbl/` directories in `storage.tsdb.path`)
on backup or restore will ensure a coherent backup, in any case, at the
cost of losing the time range covered by the WAL files.
Alternatively, external storage may be used via the
[remote read/write APIs](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage).