docs(observability-proxy): state what the metrics limits bound

The comment claimed the limits bound everything a request makes
vmselect do, but windows and offsets inside the expression pass
through unchecked: they are bounded by the store's retention and by
vmselect's own series and sample limits, not by the proxy. A reader
taking the comment at its word would rely on a cost cap that does not
exist.

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 6f5b0b666e
commit eaadba4add
1 file changed
+4 -1
+4 -1
View File
@@ -26,7 +26,10 @@ import (
"time"
)
// MetricsLimits bound what one metrics request may make vmselect do.
// 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.
type MetricsLimits struct {
MaxRange time.Duration
MaxPoints int