When using sentry local run -- <cmd>, the inline output does not surface trace or transaction event details. The only feedback is a high-level confirmation that events are being ingested:
Setup verified — your app is sending events to Sentry
Running sentry local serve as a separate tail server and pointing sentry local run --port at it does surface full event details, e.g.:
{"type":"transaction","op":"chat.route_thinking","label":"anthropic/claude-haiku-4.5","duration_ms":3946,"status":"ok","span_count":1,"source":"server"}
{"type":"span"}
So traces are flowing correctly — the inline run output just doesn't expose them.
Workaround: run sentry local serve --port <PORT> --format json in a separate terminal and pass --port <PORT> to sentry local run.
When using
sentry local run -- <cmd>, the inline output does not surface trace or transaction event details. The only feedback is a high-level confirmation that events are being ingested:Running
sentry local serveas a separate tail server and pointingsentry local run --portat it does surface full event details, e.g.:{"type":"transaction","op":"chat.route_thinking","label":"anthropic/claude-haiku-4.5","duration_ms":3946,"status":"ok","span_count":1,"source":"server"} {"type":"span"}So traces are flowing correctly — the inline
runoutput just doesn't expose them.Workaround: run
sentry local serve --port <PORT> --format jsonin a separate terminal and pass--port <PORT>tosentry local run.