Skip to content

docs: document prometheus.interval cache disable #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
platinummonkey merged 1 commit into from
Sep 11, 2026
Merged

docs: document prometheus.interval cache disable #59

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions documentation/docs/install/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,7 @@ If you don't use Prometheus, set `disable` to `true`.
|UP_PROMETHEUS_HTTP_LISTEN |prometheus.http_listen |`0.0.0.0:9130`
|UP_PROMETHEUS_REPORT_ERRORS | prometheus.report_errors | `false`
|UP_PROMETHEUS_BUFFER | prometheus.buffer |`50`
|UP_PROMETHEUS_INTERVAL | prometheus.interval |`60s` cache refresh. `0` / `0s` disables the cache so `/metrics` fetches live. Values below 15s warn but are not clamped.

:::tip
The [Prometheus](../dependencies/prometheus) page has a full explanation of how to configure Poller.
Expand Down
4 changes: 3 additions & 1 deletion documentation/docs/poller/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,9 @@ available to display the data.
points only refresh roughly once a minute (or slower), regardless of how often UniFi
Poller is scraped or how often Prometheus scrapes UniFi Poller. Setting a Prometheus
`scrape_interval` shorter than the controller's own update rate will not increase the
resolution of the underlying data.
resolution of the underlying data. Poller's own `prometheus.interval` is the cache
refresh period (`0` fetches live on each `/metrics` scrape) and is distinct from
Prometheus's `scrape_interval`, which only controls how often Prometheus hits `/metrics`.
- This matters most for rate-based panels. Prometheus's `rate()` function needs at least
two real data points inside the range vector you give it; if the range is shorter than
the controller's update interval, `rate()` can return `0` even though traffic didn't
Expand Down