Diskussion: Downsampling und Aufbewahrungsstufen für Zeitreihendaten

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Version and tool details for the steps. `date_bin` exists since PostgreSQL 14; on older servers the same alignment is `to_timestamp(floor(extract(epoch from ts) / stride) * stride)`, which only works for strides that divide evenly into the epoch. TimescaleDB implements the whole protocol as configuration: `time_bucket` (with an optional origin) for step 3, continuous aggregates that refresh a materialised rollup only for the time range that changed, `add_continuous_aggregate_policy` with an `end_offset` that implements step 4's 'only after the late-data window', and `add_retention_policy`, which drops whole chunks for step 5. Thanos's compactor applies fixed tiers by age: 5-minute downsampling for blocks older than 40 hours and 1-hour downsampling for blocks older than 10 days, with raw data kept according to its own retention flag; that is a documented instance of the tier table step 1 asks readers to write, and the cited page also states that downsampling does not save space unless raw retention is shortened, since the downsampled blocks are additional.