Documentation Index
Fetch the complete documentation index at: https://sysg.dev/llms.txt
Use this file to discover all available pages before exploring further.
status
Check the health of running services with an interactive table interface.sysg status reads the supervisor’s cached
snapshot instead of rebuilding live process state for every invocation. The
cache refresh interval and detail level are controlled by the top-level
status configuration block. Use --live when you need systemg to recompute a
fresh snapshot for that request.
Interactive Mode
By default,sysg status displays an interactive table where you can:
- Tab or ↓ (Down arrow) - Move to the next service
- Shift+Tab or ↑ (Up arrow) - Move to the previous service
- Enter - Open the inspect view for the selected service
- q or ESC - Exit the status view
Options
| Short | Long | Description |
|---|---|---|
-c | --config | Path to configuration file |
-s | --service | Show specific service details |
- | --all | Show all services including orphaned state (services not in current config) |
- | --sys | Opt into privileged system mode. Requires running as root |
- | --json | Emit machine-readable JSON output instead of a table (disables interactive mode) |
- | --no-color | Disable ANSI colors in output |
- | --live | Force a fresh supervisor snapshot instead of reading the cached snapshot |
- | --stream | Continuously refresh status at the provided interval (e.g., 5, 1s, 2m) (disables interactive mode) |
- | --log-level | Set verbosity (debug, info, warn, error) |
Examples
View all services
View specific service
Stream status updates
status.snapshot_interval_secs.
Force a fresh snapshot
--live bypasses the cached read for this invocation and updates the cache with
the fresh result. With status.snapshot_mode: summary, the fresh snapshot still
uses the cheaper summary detail level; with detailed, it recomputes full
process and spawn-tree details.
Performance
The defaultstatus.snapshot_mode: summary keeps status inexpensive for larger
systems by skipping process tree expansion, runtime command lookups, and per-pid
user/uptime lookups. Use status.snapshot_mode: detailed when you want richer
process and spawn-tree detail in status/inspect views.
Output fields
- SERVICE - Service name from configuration
- STATUS -
running,stopped, orfailed - PID - Process ID
- UPTIME - Time since service started
- CPU% - Current CPU usage
- MEM% - Current memory usage
