Careful evaluation is required for these systems as they vary greatly in durability, performance, and efficiency.įor further details on file format, see TSDB format. The use of RAID is suggested for storage availability, and snapshotsĪrchitecture, it is possible to retain years of data in local storage.Īlternatively, external storage may be used via the remote read/write APIs. Thus, it is not arbitrarily scalable or durable in the face ofĭrive or node outages and should be managed like any other single nodeĭatabase. Note that a limitation of local storage is that it is not clustered or High-traffic servers may retain more than three WAL files in order to keep atĪ Prometheus server's data directory looks something like this. Prometheus will retain a minimum of three write-ahead log files. Has not yet been compacted thus they are significantly larger than regular blockįiles.
Replayed when the Prometheus server restarts. It is secured against crashes by a write-ahead log (WAL) that can be The current block for incoming samples is kept in memory and is not fully Of deleting the data immediately from the chunk segments). When series areĭeleted via the API, deletion records are stored in separate tombstone files (instead The samples in the chunks directoryĪre grouped together into one or more segment files of up to 512MB each by default. Of a directory containing a chunks subdirectory containing all the time series samplesįor that window of time, a metadata file, and an index file (which indexes metric namesĪnd labels to time series in the chunks directory). Ingested samples are grouped into blocks of two hours.
Prometheus's local time series database stores data in a custom, highly efficient format on local storage. Prometheus includes a local on-disk time series database, but also optionally integrates with remote storage systems.
0 kommentar(er)
