C# Error Tracking

Debug C# apps and prevent crashes across your entire stack with Sentry. Improve the entire C# monitoring workflow with a full view of releases so you can mark errors as resolved and prioritize live issues.

Try Sentry For FreeRequest a Demo

Getting Started is Simple

Add the Sentry dependency:

Install-Package Sentry -Version 3.0.6

Initialize the SDK as early as possible, like in the Main method in Program.cs/Program.fs:

using (SentrySdk.Init("https://<key>@sentry.io/<project>"))
    // App code

That’s it. There’s no step three. Don’t believe us? Check out our Documentation.

See all platforms

C# Monitoring with Complete Stack Traces

See the detail you need, whether your app is .NET Core, .NET framework, or Mono. Enable asynchronous reporting so errors are logged quickly in a background task. Capture a message without being bound by a C# exception.

Fill In The Blanks About C# Errors

Expose the important events that led to each C# error: storage exceptions, past errors, SQL queries.

Resolve C# Errors With Maximum Efficiency

Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release. Add commit data to automatically suggest an owner of each C# error and instantly send deploy emails.

“Seeing only my issues out of thousands makes resolution easy. With Sentry, I can fix a million problems all at once.”

Andy Tuba
Sr. Software Engineer, Reddit

See the Full Picture of Any C# Exception

Aggregate errors by factors linke runtime, operating system, and build number to see what’s new, a priority, or a trend.

Assign custom key-value tags to reproduce the error environment specific to your application, business, and users.

Find answers to the key questions: In which C# release version did the bug occur? What transaction actually caused the app to crash?

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 Sentry.io. 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

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

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