autonomy wal inspect

Print WAL entries with optional kind/time/bridge filters

Synopsis

Reads all entries from the WAL and prints them to stdout.

Filter flags (combinable):
  --since <duration>   only show entries written within this window
                       (e.g. 5m, 1h, 24h)
  --kind  <kind>       only show entries whose event kind matches
                       (e.g. autonomy.decision, ai.rollout)
  --bridge-only        only show entries whose 'bridge_origin' attr
                       names a recognized bridge (today: the governed
                       ROS 2 bridge, value 'governed_ros2_bridge').
                       Direct-node POSTs and non-ROS 2 entries — which
                       don't carry the marker — are filtered out.
                       Closes the #939 4-E.a operator-UX gap: before
                       this flag the only way to see bridge-routed
                       decisions distinctly was to pipe --json through
                       jq with 'select(.event.attrs.bridge_origin == …)'.
                       This flag is the first-class equivalent.

Output modes:
  default   human-readable table (seq, time, kind, attrs summary)
  --json    JSONL — one JSON object per line

Usage

autonomy wal inspect [flags]

Options

      --bridge-only    only show entries whose event.attrs.bridge_origin names a recognized bridge (today the governed ROS 2 bridge, value 'governed_ros2_bridge'). Direct-node POSTs are excluded. First-class equivalent of --json | jq 'select(.event.attrs.bridge_origin != null)'. (#939 4-E.a)
      --dir string     WAL directory (default: XDG_CACHE_HOME/autonomyops/telemetry)
      --json           output as JSONL (one JSON object per line)
      --kind string    filter by event kind (e.g. autonomy.decision)
      --since string   show entries written within this duration (e.g. 5m, 1h)

See also