sase telemetry¶
Inspect locally persisted telemetry (defaults to list)
Reference for sase telemetry. Run sase telemetry --help for the exact output on this checkout.
usage: sase telemetry [-h] {cleanup-test-data,health,list,snapshot,status} ...
Inspect locally persisted telemetry. Running 'sase telemetry' without a subcommand delegates to 'sase telemetry list'.
Bare sase telemetry defaults to sase telemetry list.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
Subcommands:
| Subcommand | Summary |
|---|---|
sase telemetry cleanup-test-data |
Preview or remove telemetry with known test labels |
sase telemetry health |
Traffic-light health assessment |
sase telemetry list |
Show the metric catalog from internal definitions |
sase telemetry snapshot |
Display current values from the local store |
sase telemetry status |
Quick health check and config display |
sase telemetry cleanup-test-data¶
usage: sase telemetry cleanup-test-data [-h] [-n] [-y]
Preview or remove telemetry rows whose exact labels identify test data. Deletion requires the explicit -y/--yes flag.
Options:
| Option | Description | Default |
|---|---|---|
-n, --dry-run |
Preview exact matches without deleting rows | false |
-h, --help |
show this help message and exit | — |
-y, --yes |
Confirm deletion after the preview | false |
sase telemetry health¶
usage: sase telemetry health [-h] [-j]
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Machine-readable JSON output | false |
sase telemetry list¶
usage: sase telemetry list [-h] [-s SUBSYSTEM] [-t {counter,gauge,histogram}]
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-s SUBSYSTEM, --subsystem SUBSYSTEM |
Filter to a specific subsystem (e.g., 'Agent Lifecycle') | — |
-t TYPE, --type TYPE |
Filter by metric type (choices: counter, gauge, histogram) |
— |
sase telemetry snapshot¶
usage: sase telemetry snapshot [-h] [-f {json,rich}] [-s SUBSYSTEM]
Options:
| Option | Description | Default |
|---|---|---|
-f FORMAT, --format FORMAT |
Output format (default: rich) (choices: json, rich) |
rich |
-h, --help |
show this help message and exit | — |
-s SUBSYSTEM, --subsystem SUBSYSTEM |
Filter by subsystem | — |
sase telemetry status¶
usage: sase telemetry status [-h]
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
Related: CLI command groups.
_[project]: A sase project is a named unit of work registered with SASE. _[workspace]: A sase workspace is a numbered clone of a project's primary repo, managed by the workspace store and tracked in that project's registry.json. _[agent]: A sase agent is an agent session or a single agent that does not belong to a session. _[prompt]: A prompt is the text SASE hands to a provider to start an agent turn. _[macro]: A macro is a reusable prompt triggered with #name in agent prompts. _[Patch]: A Patch is SASE's local unit of change. _[bead]: A bead is one tracked work item in SASE's git-native issue tracker. _[plan]: A plan is a persisted, approved artifact recording the intent behind agent work. _[TUI]: The TUI is SASE's terminal interface for running agents and reviewing results. _[epic]: An epic is an executable multi-phase plan run with sase bead work. _[gate]: A sase gate is a durable, command-backed request for one user decision, created when work must pause for the user. _[monitor]: A sase monitor is a monitor turn that runs one long command under a detached supervisor, so the command outlives the agent that started it. *[stitch]: A stitch is the lightweight ordered change record inside a Patch's STITCHES: section.