Sentry and Trace: errors in your code, and what they cost your visitors.
Sentry is the place for stack traces, alerts, performance tracing and errors across every platform. Trace looks at errors from the visitor's side: how many visits each one broke, which goal it hurt, and whether the fix brought conversion back. It also takes server errors from Rust, Node.js and Ruby, without request data. Many teams will run both.
Keep Sentry if you need
- Mobile apps and platforms beyond Rust, Node.js and Ruby
- Alerts and on-call
- Performance tracing
Choose Trace if you want
- Browser errors ranked by visits broken, next to the clicks that failed
- UX problems that throw no error: dead clicks, rage clicks, drop-offs
- A verdict on the goal after the fix ships
Side by side
| Sentry | Trace | |
|---|---|---|
| Focus | Code: errors and performance | Visitors: frustration, errors and goals |
| Backend errors | Every major platform, with request context | Rust, Node.js and Ruby, error facts only |
| Request data | Headers, params and user context, with scrubbing | Never sent: no bodies, params, headers, cookies or users |
| Browser errors | With stack traces | With visits affected and the goal they hurt |
| Problems without an error | Rage and dead clicks inside replays | Dead clicks, rage clicks, forms abandoned, counted across all visits |
| Coding agents | AI fixes and an MCP server | MCP server built for UX fixes and verdicts |
| Self-host | Yes | Yes |
Sentry details from its public documentation, checked 29 October 2026. Spot something out of date? Tell us.
Moving from Sentry: what maps to what
Trace doesn't replace Sentry. Here is how the two divide the work.
| In Sentry | In Trace |
|---|---|
| Sentry SDK on the server | The tracetells client for Rust, Node.js or Ruby |
| A new browser error | Trace shows how many visits it broke and on which page |
| A release | Trace judges the goal 14 days before and after |
| A broken button with no error | Trace sees it as a dead click, across every visit |
Run them side by side for a month
Add the Trace tag next to Sentry. It adds 8.4 KB and does its work when the browser is idle.
Compare the browser errors Sentry lists with those Trace ranks by visits broken. Fix the costliest.
Read the verdict on what you shipped. Keep what still earns its place.
Questions from Sentry users
Should I remove Sentry?
Not necessarily. Keep it for alerts, performance tracing and platforms Trace has no client for. If you only used it for Rust, Node.js or Ruby errors, Trace now covers those too.
Will two scripts slow my site?
Trace adds 8.4 KB and does its work when the browser is idle.
Related: LogRocket alternative · FullStory alternative · All comparisons