Module subject 

Constants

COMMANDS_ALL

EVENTS_STARTED_FILTER

Wildcard the backend events projector consumes on STREAM_EVENTS. Narrow (events.started.>) rather than the whole events.> so future event types can carry their own filters without rerouting the started subset.

INVENTORY_HW

INVENTORY_NET

INVENTORY_SW

OBS_FILTER

obs.> — filter the backend projector subscribes to so a new PC starts flowing into the timeline without any per-PC SUB registration. Pairs with obs for publish.

Functions

commands_group

commands_pc

events_started

events.started.<exec_id>.<pc_id> — v0.30 / PR α’ lifecycle event published by the agent just before spawning a script’s child process. Lets the backend project an in-flight row into execution_results (with finished_at = NULL) so the SPA Activity table can show running rows alongside finished ones. Backend subscribes via EVENTS_STARTED_FILTER.

heartbeat

host_perf

host_perf.<pc_id> — Phase 1 of the perf telemetry pipeline. The agent publishes a whole-host CPU / Memory / Disk I/O / Network snapshot here on the cadence set by host_perf_interval in agent_config (default 60 s). Distinct subject from heartbeat.<pc_id> so the periodic heartbeat publisher stays untouched and pre-host_perf backends that don’t subscribe simply ignore the new traffic.

inventory

kill

kill.<exec_id> — Spec §2.6 Layer 3 abort signal. The exec_id is the deployment / scheduler-fire UUID (formerly named job_id pre-v0.29; renamed for accuracy — every Command.exec_id is a per-deploy UUID, not a job-catalog id).

logs_fetch

logs.fetch.<pc_id> — request/reply: operator (or backend) sends a LogsRequest; the addressed agent replies with the tail of its local log file. On-demand only, no stream.

obs

obs.<pc_id> — per-PC observability event stream (Issue #246). The agent publishes one crate::wire::ObsEvent per timeline event (sign-in / out, power on / off, sleep / resume, agent milestones, diagnostic bundle pointers). Distinct from events.started.* (in-flight script lifecycle) and host_perf.<pc_id> (numeric telemetry) — obs.* is the semantic-event stream the SPA Timeline page consumes.

ping

agents.<pc_id>.ping — v0.38 / #133 request/reply for the active “ping” round-trip. The agent answers with a fresh Heartbeat on demand instead of the backend waiting up to ~30 s for the next periodic heartbeat tick to land. Distinct subject from heartbeat.<pc_id> so the periodic publisher is unaffected and old agents that don’t subscribe simply time the request out.

process_perf

process_perf.<pc_id> — Phase 2: top-N per-process snapshot published only while process_perf_enabled is true AND the process_perf_expires_at deadline is in the future. Separate subject from host_perf.<pc_id> because process-perf is an opt-in investigation mode — having its own subject lets the projector skip the heavy table entirely for hosts that never turn it on.

results