Complete operational monitoring summary

This commit is contained in:
2026-08-03 00:21:06 +02:00
parent b464d016b2
commit 1426fd96b1
6 changed files with 153 additions and 15 deletions
+8
View File
@@ -76,6 +76,14 @@ Promote from local development to a production-like profile when a feature
depends on PostgreSQL, Redis, Celery, module package lifecycle, or durable file
storage.
The Operations page is the canonical monitoring surface. Its summary reports
worker and queue coverage, queue depth, active tasks, local filesystem capacity
when observable, backup/restore evidence, runtime-node skew, and recovery-ledger
operations split into active, failed, recovery-required, and outcome-unknown
states. S3 capacity remains provider-owned unless a configured module check
supplies bounded usage metrics; Ops must not enumerate an object store merely to
render a dashboard.
Promote from a single-process profile to a split-worker profile when queued
work becomes part of normal operation: