Add ISAC system metrics
This commit is contained in:
@@ -113,3 +113,20 @@ Unsupported destructive identity operations, account deletion, incomplete
|
||||
snapshots, stale targets, and events whose dependencies no longer exist are
|
||||
marked non-reversible or rejected. Recovery for those cases requires a
|
||||
specialized workflow rather than inferred database writes.
|
||||
|
||||
# System metrics
|
||||
|
||||
The read-only `/admin/metrics` route requires `metrics.view` and collects a
|
||||
point-in-time process-local health snapshot. Node and operating-system APIs
|
||||
provide process CPU and memory, event-loop utilization and delay, host memory,
|
||||
load average, core count, platform, and uptime. Embedded Turso pragmas provide
|
||||
page allocation, page size, and free-page information; aggregate SQL queries
|
||||
provide application record volumes.
|
||||
|
||||
The interface refreshes on demand and may poll every ten seconds while the
|
||||
operator keeps auto-refresh enabled. CPU and event-loop values are deltas from
|
||||
the previous server-side sample, so the first or infrequently requested sample
|
||||
is directional rather than a monitoring-grade time series. Production alerting
|
||||
and historical analysis should eventually use a dedicated external telemetry
|
||||
system. This surface deliberately omits secrets, environment-variable values,
|
||||
and full database paths.
|
||||
|
||||
Reference in New Issue
Block a user