View logs in context — with your errors and traces (in Beta)

See the logs behind a failed cron job, dropped webhook, or bad deploy—right from the issue.

• View logs alongside stack traces, releases, and traces—like seeing job_type:"refresh_tokens" right next to the exception

• Understand what happened before and after an error—like the status:500 response from a third-party API that preceded a crash

Sentry connects structured logs to traces, so you can spot retry loops, fallback logic, or silent failures that don’t throw exceptions.

• View logs inline with spans—like seeing retry=true or response_time:3000 right where the delay occurred

• Understand slowness across services by following logs tied to span_id, trace_id, or custom fields

Structured logs in Sentry make it easy to search by real metadata—not just raw strings.

• Attach properties like customer_id or payment_id to your log messages

• Filter and search logs with queries like customer_id:"cus_123" or payment_id:"pay_456" to zero in on specific issues

• Group logs by fields like payment_id to surface repeat failures tied to the same transaction

• Trigger alerts based on structured values—like a spike in errors for a single customer