From 23c7193ca491409d1090daf9d0dcba4d0e24d9b7 Mon Sep 17 00:00:00 2001 From: Andrii Chubatiuk Date: Fri, 17 May 2024 15:33:22 +0300 Subject: [PATCH] docs: added information about difference between default_rollup and last_over_time (#6282) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6279 (cherry picked from commit ce3cfd720e81affe2222df57b0b24e537c8a2ae5) --- docs/MetricsQL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/MetricsQL.md b/docs/MetricsQL.md index fec10e5dc..3c6e82da3 100644 --- a/docs/MetricsQL.md +++ b/docs/MetricsQL.md @@ -328,6 +328,7 @@ See also [increases_over_time](#increases_over_time). `default_rollup(series_selector[d])` is a [rollup function](#rollup-functions), which returns the last [raw sample](https://docs.victoriametrics.com/keyconcepts/#raw-samples) value on the given lookbehind window `d` per each time series returned from the given [series_selector](https://docs.victoriametrics.com/keyconcepts/#filtering). +Compared to [last_over_time](last_over_time) it accounts for [staleness markers](https://docs.victoriametrics.com/vmagent/#prometheus-staleness-markers) to detect stale series. If the lookbehind window is skipped in square brackets, then it is automatically calculated as `max(step, scrape_interval)`, where `step` is the query arg value passed to [/api/v1/query_range](https://docs.victoriametrics.com/keyconcepts/#range-query) or [/api/v1/query](https://docs.victoriametrics.com/keyconcepts/#instant-query),