Actionable insights to solve ASP.NET Core errors.
Add the Sentry dependency:
dotnet add package Sentry.AspNetCore
Configure Sentry in appsettings.json
.
"Sentry": { "Dsn": "https://examplePublicKey@o0.ingest.sentry.io/0", "Debug": true, },
Then add the SDK by simply calling UseSentry
:
public static IHostBuilder CreateHostBuilder(string[] args) => Host.CreateDefaultBuilder(args) .ConfigureWebHostDefaults(webBuilder => { // Add the following line: webBuilder.UseSentry(); });
Check our documentation for the latest instructions.
See all platformsSee ASP.NET Core stack trace details like filename and line number so you never have to guess. Filter and group ASP.NET Core exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.
Quickly identify ASP.NET Core performance issues before they become downtime with performance monitoring. View the entire end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors.
Expose the important events that led to each ASP.NET Core exception: debug logs, network requests, database queries, past errors.
With Sentry's exceptional exception handling in ASP.NET Core, you can triage quickly based on specific parameters like HTTP request, workflow stage, and hostname for each issue. Set custom tags to recreate the error environment relevant to your app, business concerns, and users.
”Sentry's high-quality tooling helps Disney+ maintain high-quality service to its tens of millions of global subscribers.”
Just look at all the high-quality security features all accounts get, regardless of plan.
When Spring Boot is configured to generate Git information every event triggered by Sentry will have a release field set to the current Git commit ID that will enable Monitor Release Health Sentry feature. More details 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.