Observability
The observability section is the cabinet’s window into work that happens elsewhere. Every panel is read-only by design — interactive driving lives in the desktop app and the CLI.
If you need to drive a session, hand off to desktop or CLI. The cabinet keeps the transcript so you can review it later.
What “observability” means here
Observability in CMDOP is the ability to see what your agents, members, and bots have been doing — never to drive them. The cabinet shows:
- Machine inventory and live health.
- Session transcripts (after the fact, and live in read-only mode).
- Schedule run history.
- Per-request audit trail.
The four panels
Inventory, status, metrics. Admin-only actions: rename, retag, deregister.
Sessions inspectorRead-only session transcripts and metadata.
Schedules & runsRead-only inventory of scheduled tasks and their run history.
Audit logEvery authenticated request, filterable and exportable.
What is not here
- Interactive command execution — desktop / CLI.
- Schedule authoring — skills + agent (
../../cli/trigger). - Agent-to-agent ask debugging — desktop Activity tab.
- Live chat — desktop Chat tab or
../../cli/chat.
Refresh model
Observability data updates live, with no manual refresh. Expectations:
- Health and status — sub-second latency.
- Session transcripts — seconds; recent output is buffered.
- Schedule runs — seconds; eventually consistent with the schedule executor.
- Audit log — near real-time; rotated and immutable on disk.
Permissions
Observability respects fleet roles and per-machine access overrides:
- View-Only members see the same panels but no admin actions.
- Per-machine access can hide individual machines from a member’s inventory.
- Audit log entries are visible to Members and above; export is Owner / Admin.
Cmdop