Bohan Jiang 46f7ac6bac docs(self-host): document task_usage_hourly rollup requirement (MUL-2682) (#3280) ...

The Usage / Runtime dashboards read from `task_usage_hourly`, but the
default self-host stack does not schedule `rollup_task_usage_hourly()`
anywhere — the bundled pgvector/pgvector:pg17 image ships without
pg_cron, and the backend does not run the rollup in-process. Fresh
installs see the dashboard stay at zero forever (#3244), and upgrades
from v0.3.4 → v0.3.5+ are blocked by migration 103's fail-closed guard
(#3015).

Document the three supported paths (external cron / systemd-timer /
CronJob, Postgres with pg_cron, or backfill_task_usage_hourly for
upgrades) across SELF_HOSTING.md, SELF_HOSTING_ADVANCED.md, the
quickstart pages on the docs site, and add troubleshooting entries
for both the silent-zero and the migration-guard failure modes.

Co-authored-by: multica-agent <github@multica.ai>

2026-05-26 16:03:14 +08:00

..

cloud-quickstart.zh.mdx

…

meta.zh.json

…

self-hosting.zh.mdx

docs(self-host): document task_usage_hourly rollup requirement (MUL-2682) (#3280)

2026-05-26 16:03:14 +08:00