bhatti admin metrics
bhatti admin metrics server only
Section titled “bhatti admin metrics ”Query metrics snapshots over time.
Synopsis
Section titled “Synopsis”sudo bhatti admin metrics [—since <range>]
Description
Section titled “Description”The server takes a metrics snapshot roughly every minute and persists it to the database (in metrics_snapshots). This command reads them back and prints a compact table — request rates, error counts, proxy traffic, cold wakes, sandbox state distribution, host load, available memory.
The output is bucketed automatically based on the time range:
| Range | Bucket size |
|---|---|
| < 2 hours | 1 minute |
| 2–24 hours | 15 minutes |
| > 24 hours | 1 hour |
Each row aggregates the snapshots in its bucket (sums for counters like req/min, last-value for gauges like LOAD).
--since accepts the same formats as admin events --since — relative durations or absolute dates. The default is 1 hour.
Examples
Section titled “Examples”# Last hour at 1-minute resolution (default)sudo bhatti admin metricsTIME REQ/min ERR PROXY/min WAKES HOT WARM COLD LOAD MEM_AVAIL14:21 47 0 8 0 4 6 7 0.4 19421 MB14:20 52 1 9 1 4 5 8 0.5 19388 MB14:19 44 0 7 0 4 4 9 0.5 19412 MB...# Last 12 hours, auto-bucketed to 15-minute intervalssudo bhatti admin metrics --since 12h# Last week, auto-bucketed to 1-hour intervalssudo bhatti admin metrics --since 7d# Machine-readable, raw 1-min snapshots for the last 30 minutessudo bhatti admin metrics --since 30m --json | jq '.[] | .api_requests'Options
Section titled “Options”| Flag | Default | Description |
|---|---|---|
--since <range> | 1h | Earliest snapshot to include. |
See Global flags for --url, --token, --json, --timing, --data-dir.
See also
Section titled “See also”bhatti admin status— current totalsbhatti admin events— what happened, when