Observability

Find a run

Dashboard

The Traces page is the canonical UI. Filter by workspace member, source kind, status, plugin namespace, duration, and time range.

CLI

Use hrbr inspect for the run lookup operations currently exposed by the CLI:

hrbr inspect 'return await hrbr.runs.list({ limit: 20 })'
hrbr inspect 'return await hrbr.runs.get({ run_id: "<run-id>" })'
hrbr inspect 'return await hrbr.runs.graph({ run_id: "<run-id>" })'

Use SDK clients or the dashboard for artifact download, replay, export, and richer run-event APIs.

Drill into a span

In the dashboard trace tree, click a span to see its name, duration, input, output, error, and linked artifacts.

Common debugging flow

1. Find the failed run in the dashboard or with hrbr.runs.list.
2. Open the graph with hrbr.runs.graph.
3. Read the failing span's error and input.
4. Fix the source credential, argument shape, or runtime code.
5. Re-run with hrbr exec or publish a fixed Function/App file.

Audit log vs trace

Where to go next

• Runs & Traces
• Versioning & pinning