Logs are automatically attached to the errors and traces they came from. You can see the log lines from the exact request or execution path that failed. No global searches. No manual correlation.
Logs built for debugging
Logs are most useful when in context. Sentry brings logs into the same view as errors and performance, so you can see what happened and why, without switching tools.
0 developers signed up for Sentry last week
Tolerated by 4 million developers.
- Nextdoor
- Instacart
- Atlassian
- Cisco Meraki
- Disney
- Riot Games
Less time searching, more time fixing.
Skip the manual log hunting. Structured logs make it easy to filter and search for logs by real metadata all within your debugging workflow.
Spot broken behavior early.
Not every bug throws an exception. Some return a 200. Retry loops, fallback logic, and silent failures often show up in logs long before an error fires.
Log to trace to replay in Sentry is quite magical, glad logging is finally supported there