Performance
Find the work behind the wait.
Explore transaction timing and trace waterfalls alongside errors, sessions and releases, so you can investigate slow application paths with context.
Start with the slow path
Compare endpoint latency and inspect the transactions behind a slow experience. Averages alone can hide the requests that make a product feel unreliable.
See the operations inside
Trace spans break a request into its instrumented work. Follow database calls, outgoing requests and named operations to find where time is being spent.
- Transaction and span context
- Error-to-trace navigation
- Release and environment filters
Instrument deliberately
Spans come from the JavaScript SDKs with tracing switched on, or from OpenTelemetry for .NET and other servers, sent as OTLP/HTTP JSON. The sampling rate is set in the dashboard, and errors are never sampled. See the SDK documentation for supported integrations.
Related
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- Fix what matters to your users. Bring errors, performance and feature usage together to help prioritise engineering work by its effect on the product.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.