Rust Error Tracking and Performance Monitoring

Debug Rust apps and prevent crashes across your entire stack. Trace Rust performance issues back to a poor performing API call and surface any related code errors. Sentry provides a single platform to optimize the performance of Rust code and deliver fast customer experiences.

Getting Started is Simple

Grab the Sentry Rust SDK:

Click to Copy
[dependencies] sentry = "0.32.3"

The most convenient way to use this library is the sentry::init function, which starts a Sentry client with a default set of integrations, and binds it to the current Hub. :

Click to Copy
let _guard = sentry::init(("", sentry::ClientOptions { release: sentry::release_name!(), ..Default::default() }));

In Rust, you can capture and std::error::Error type.

Click to Copy
let result = match function_returns_error() { Ok(result) => result, Err(err) => { sentry::capture_error(&err); return Err(err); } }

Check our documentation for the latest instructions.

See all platforms

Rust Error Monitoring With Complete Stack Traces

See details like filename and line number so you never have to guess with Rust errors. Filter and group Rust exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.

Fill In The Blanks About Rust Errors

Reproduce errors without user feedback. Sentry’s Rust error monitoring includes each bug’s history of events and actions.

Understand The Bigger Picture

Use issue graphs to understand frequency, scope, and impact of Rusterrors and prioritize what needs to be fixed. Get alerts via email, SMS, or chat when bugs make it into production without disrupting your development workflow.

“Sentry helps our team fix the most important issues in each release.”

Jaylum Chen
Staff Software Engineer, Eventbrite

See The Full Picture Of Any Rust Error

Understand the context that contributed to errors with tags and relevant information about your software, environment, and users.

You can also submit optional custom data to provide extra context for bug tracking that is unique to your application and business.

Find answers to key questions: Which clients’ users experienced this bug? Was their game running in 32 bit or 64 bit mode?

It’s why companies that don’t have a complete view of their infrastructure are being punished:

The average cost of network downtime is around $5,600 per minute — or $300,000 per hour.

1 out of 5 online shoppers will abandon their cart because the transaction process was too slow.

On average, a two-second slowdown in page load decreases revenues by 4.3 percent.


Traditional logging provides you with a trail of events. Some of those events are errors, but many times they’re simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail here and on our blog.

Sentry supports every major language, framework, and library. You can browse each of them here.

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.

Sentry doesn’t impact a web site’s performance.

If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

Supporting Resources

Two Keys to Faster Resolution of Ruby Errors

A better experience for your users. An easier life for your developers.

© 2024 • Sentry is a registered Trademark
of Functional Software, Inc.