docs(observability-proxy): name the timeout as the bound on rollup work

vmselect's sample limit counts raw samples read, not the work of a
rollup that revisits each sample across overlapping windows, so for
that work the forwarded timeout is the limit that applies.

Assisted-by: LLM
Signed-off-by: ZverGuy <maximbel2003@gmail.com>
This commit is contained in:
ZverGuy committed 2026-11-10 03:56:18 +07:00
1 parent eaadba4add
commit b4ddb93b6f
1 file changed
+3 -2
+3 -2
View File
@@ -28,8 +28,9 @@ import (
// MetricsLimits bound the window, resolution and timeout a metrics request
// asks vmselect for. Windows and offsets inside the expression are not
// limited here: they cannot read past the store's retention, and vmselect
// caps the series and samples one query may touch.
// limited here: they cannot read past the store's retention, vmselect caps
// the series and samples one query may touch, and MaxTimeout bounds the
// work of rollups over long overlapping windows.
type MetricsLimits struct {
MaxRange time.Duration
MaxPoints int