p202 system metrics

Server metrics: sync counters, the sync job queue (queued, running, lag), recent spans and active alerts

New in 1.9.77
All commands

p202 CLI reference

Back to the docs

01Run it

Straight from the command's own help.

p202 system metrics --json

02What you get

Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.

p202 system metrics
$ p202 system metrics
alerts:      {"active":[],"thresholds":{"failure_spike":20,"queue_lag_seconds":300}}
counters:    []
queue:       {"queue_lag_seconds":0,"queued_jobs":0,"running_jobs":0}
tracing:     {"recent_spans":[]}
updated_at:
Real output · p202 1.9.77 · demo dataexit 0

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 system metrics

Set flags below; the command updates as you type.

04How it works

GET /system/metrics. alerts.active lists a failure spike or a queue lag past its threshold (P202_ALERT_FAILURE_SPIKE, P202_ALERT_QUEUE_LAG_SECONDS on the server).

Needs an Admin or Super user key with system:read.

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands system metrics --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
p202 commands system metrics --json
{
  "path": "p202 system metrics",
  "use": "metrics",
  "short": "Server metrics: sync counters, the sync job queue (queued, running, lag), recent spans and active alerts",
  "long": "GET /system/metrics. alerts.active lists a failure spike or a queue lag past its threshold\n(P202_ALERT_FAILURE_SPIKE, P202_ALERT_QUEUE_LAG_SECONDS on the server).\n\nNeeds an Admin or Super user key with system:read.",
  "runnable": true,
  "example": "p202 system metrics --json"
}