All commands scope the read to the active workspace (from
dome config), so the server checks the workspace-level audit.view permission. Switch workspaces with dome workspace use <id> before running the command. Tenant- or org-scoped API keys with no workspace selected fall back to the tenant-level audit.view.Query
dome audit query
Query audit events with optional filters.
Stream
dome audit stream
Stream audit events in real-time via SSE. Accepts the same filters as query except --limit and --compact.
Get
dome audit get [event-id]
Get a single audit event by ID.
Enum values — event class, result, actor kind, surface — render as short tokens (governing, denied, gateway_mcp) in both the table and --format json output, and the filter flags accept those same tokens. Refer to Enum rendering reference.
Export
dome audit export
Export audit events in JSON-lines, JSON, OCSF, or CEF format. Pick the format your downstream pipeline expects:
Accepts the same filters as
query, plus:
Chains
dome audit chains
List activity chains in the active workspace. A chain is the set of audit events sharing one activity_id — a session, an LLM turn, a conversation thread, or a scripted run — computed at read time by grouping on activity_id within the workspace.
A chain is listed when any of its events matches the filter. Per-chain counts always reflect the full chain. Drill into one chain’s events with dome audit chain <activity-id>. Refer to Activity chains reference for the model and trust labels.
Per-event identity filters (
--trace-id, --operation-id, --parent-event-id) and payload filters identify a single event, not a chain, and are not offered here.
activity_id, event count, last activity timestamp, outcome breakdown, trust label (server-owned, caller-asserted, or mixed — refer to Activity trust reference), and distinct event-type count.
Chain
dome audit chain [activity-id]
Show one activity chain’s events in order. A drill-in into audit query filtered by activity_id. Accepts the same per-event filters as audit query to narrow the chain’s events further.
Emit events into a chain
Set--activity (or DOME_ACTIVITY_ID) on the root command to assert a stable activity ID. Every Connect RPC the run makes carries X-Dome-Activity-Id, so the audit events all share one activity_id and form one chain.
--activity overrides DOME_ACTIVITY_ID. The ID is opaque to Dome — pick whatever maps to your unit of work. The header is first-party only and is never forwarded to third-party LLM or MCP backends.
The --activity emit flag (root command) and the --activity-id filter flag (audit reads) are distinct: one stamps events, the other selects them.