shc / arch / event-river ← lab docs

The cluster narrates itself

$shc events -T event,audit live
in-process bus event 4131 peers ×2

- = node-local, never replicated

Every line is a real code. Grep it.

No daemon, no docker. The lines are generated in JavaScript, but every code, message string and payload key is lifted from the repo. Two fates, one stream. The docker module registers its 15 raw container/exec/health codes with Ephemeral: true (internal/modules/docker/eventtypes.go:77-93), and Service.Publish gates on that: an ephemeral event skips the event insert and the peer broadcast, and still fans out to the in-process bus so the recorder and this stream see it (internal/modules/events/service.go:304-314). That is why the sequence column has holes: sequence is the event row id, stamped only on the durable path, and the JSON envelope omits it when zero (internal/modules/events/types.go:80-84). The split exists for a reason: exec probe churn was ~72% of bus traffic and each replicated row became a fat raft entry that blew a wiped node's replay budget (events/classification.go:14-31, docker/eventtypes.go:65-76). The codes. Container verbs map at internal/modules/docker/events.go:38-52; health_status maps at :56-65 and returns nothing for anything but healthy/unhealthy, so health_status: starting has no code and this page emits none. Docker lines are published with Message: type + " " + action and payload actor_id, action, type, time_nano, attributes (internal/subsystems/impl/docker_events.go:225-238). Deployment and node transitions come from the health pollers (internal/modules/health/events.go:15-35, emitted at internal/daemon/services_seams.go:222-240,263-303); reconcile fires V200500RCNATT / V200501RCNHEAL / V200502RCNFAIL with no message at all, payload only (internal/modules/health/reconcile/reconcile.go:263-301), and the reason strings are built at reconcile/service.go:66-73,89-93. A200100STKINS and A200400BKPCRT are audit-grade (app/events.go:14,61, backup/events.go:19,232). V200320 is two different events: EXCCRT (ephemeral exec probe) and STKRUN (durable stack transition), which is exactly why durability is a per-code set and not a numeric-prefix test. The command. shc events streams SSE from /api/method/shc.events.stream (internal/modules/events/commands/main.go:142). Its -T/--type whitelist is matched against classifyEventType, which returns "docker" only for a D-prefixed code, and no production publisher emits one, so the shipped default -T docker,audit keeps the audit lines and drops this whole container river. -T event,audit is the flag pair that actually streams what you see here (main.go:163, router.go:424-478). For the same reason -q/--quiet, whose exec-noise filter keys on eventType == "docker", cannot fire in production today (main.go:42-46,296-312): it is a real flag on shc events, and not on shc logs, but it does not currently thin this stream. The live operator TUI is shc hud; there is no --watch flag anywhere in shc.