docs: drop stale delta-query caveat now that deltatocumulative is live

This commit is contained in:
damocles 2026-08-30 20:04:06 +02:00
commit b699ca8857

View file

@ -380,8 +380,8 @@ delta-to-cumulative processor.
**`hive-metric` counters are the one exception**, reporting delta by default **`hive-metric` counters are the one exception**, reporting delta by default
(see above) — programmatically set on the exporter, which overrides this (see above) — programmatically set on the exporter, which overrides this
container-wide env var for that tool specifically. `--type gauge` is container-wide env var for that tool specifically. `--type gauge` is
unaffected either way; gauges have no temporality. The collector pipeline unaffected either way; gauges have no temporality. The hive-tier collector
here has no `deltatocumulative` processor, so a delta `hive-metric` counter's runs a `deltatocumulative` processor ahead of export, so a delta
raw values land in VictoriaMetrics as-is — query it with `sum_over_time()` / `hive-metric` counter still lands in VictoriaMetrics as a cumulative
`rate_over_sum()`, not the standard `rate()`/`increase()` (those re-diff an series — the standard `rate()`/`increase()` idioms work on it exactly like
already-delta series and produce wrong numbers). any other counter in this system, no special query needed.