Sentry Moves From Error Tracking to APM

Sentry’s move into APM changes it from a single purpose bug catcher into a broader observability product that can sell to whole engineering teams. The same SDK that already sits inside app code can now record slow requests, database calls, and cross service traces, so engineers can move from seeing that something broke to seeing exactly where time was spent and which deploy or dependency caused it.

• The product shift is concrete. Sentry tracing measures latency and throughput across services, records transactions and spans, and lets teams inspect traces to find slow page loads, API calls, and database queries. Session Replay adds the user session next to the error and trace, so debugging happens in one workflow instead of across separate tools.
  2 sentry 3 sentry 5 sentry
• The business shift is just as important. Error tracking was typically adopted by an individual developer or small team, with roughly $1,500 ARPU, while APM budgets are owned by broader engineering orgs, where Datadog and New Relic have realized roughly $50,000 to $100,000 ARPU. That is why moving into APM expands both Sentry’s market and contract size.
  1 sacra 4 sacra
• Sentry is not trying to beat incumbents by covering every infrastructure metric first. Its wedge is developer workflow. Datadog and New Relic can connect errors to logs and infrastructure out of the box, but Sentry starts from the error screen developers already use, then layers in traces, replay, and code context. That makes it easier to upsell its existing self serve base into broader monitoring.
  1 sacra 4 sacra 5 sentry

The next step is a fuller developer operations stack built around the code level debugging moment. As Sentry adds logs, AI debugging, and more workflow specific monitoring, it can keep moving up from point solution pricing toward platform pricing, while pulling more observability spend away from older enterprise tools.