SimetrikDocs
Guides

Observe and debug

Observe and debug

Goal: see in real time what the CLI is doing and react to platform events — useful for debugging a flow or for an agent to watch progress.

Tail session logs (logs tail)

Every CLI invocation writes an NDJSON session log. logs tail follows it live:

simetrik logs tail

Filter by level, command, or event type:

simetrik logs tail --level error
simetrik logs tail --command recon --event http_request

For an agent, the JSON output is line-delimited (one object per line), ready for jq:

simetrik --output json logs tail | jq 'select(.type == "http_request")'

If there's no session log yet, the command exits with code 0 and an informational message (not an error).

Forward events to your local app (listen --forward-to)

notification listen already streams platform events via SSE. With --forward-to, it forwards them over HTTP POST to a local endpoint — the webhook pattern for development:

simetrik notification listen --forward-to http://localhost:3000/webhook

All existing filters are preserved (--event, --type, --category, --channel, --timeout).

For security, the destination must be loopback (localhost, 127.0.0.1, ::1) by default. To forward to a remote host, pass --allow-remote explicitly. The payload is redacted before being sent, and a failure of the local endpoint does not break the stream.

logs tail is local (no login required). Combine it with --output json so an agent can observe execution without human intervention.

On this page