Sentry SDK for .NET
https://github.com/getsentry/sentry-dotnet- Category
- Developer Tools
- Rank
- No. 364Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- getsentry
- GitHub
- 770 stars
- Latest release
- 6.10.0
- Date
About
Official Sentry SDK for .NET. Crash reporting, performance monitoring, and structured logging for .NET, MAUI, Xamarin, and Unity apps.
What it does
This is a family of NuGet libraries that sends application failures and operational telemetry into Sentry. Teams start with the core package, then add adapters for their web framework, logging stack, database layer, tracing system, cloud runtime, or mobile application. The repository also includes native bindings where platform behavior requires them.
Why it's ranked here
The broad integration surface makes this a strong default for .NET teams already using Sentry. It covers modern and legacy framework targets, major logging libraries, OpenTelemetry, web applications, cloud functions, background jobs, and mobile platforms. Extensive test projects, integration tests, samples, benchmarks, and API snapshots show serious compatibility discipline.
What's good
Package boundaries let teams install only the integration they need. Dedicated adapters exist for ASP.NET Core, Blazor WebAssembly, gRPC, Entity Framework, OpenTelemetry, Serilog, NLog, log4net, Hangfire, Google Cloud Functions, and MAUI. Public API snapshots catch accidental surface changes, while unit, integration, device, browser, and performance testing cover distinct failure modes.
Tradeoffs
The repository reflects substantial platform complexity. Android needs Java, iOS and Mac Catalyst need macOS plus Xcode, and MAUI needs additional workloads. Native SDKs and tooling arrive through submodules, so an incomplete checkout can break builds or silently produce incomplete solution filters. Full development across every target demands several operating systems and specialized toolchains.
How to use it well
Choose it when a .NET application reports telemetry to Sentry and needs an adapter matched to its framework or logging stack. Begin with the smallest relevant NuGet package, use the non-mobile solution filter for routine contribution work, and validate public API changes through snapshots. It does not replace the native mobile toolchains required to build and test Android or Apple targets.
Technical notes+
README.md presents the NuGet package matrix. Sentry.slnx shows separate source projects, mirrored test projects, samples, benchmarks, integration tests, native modules, and CI workflows. build.sh and build.cmd build the Release configuration, then run tests with coverage and without rebuilding. dev.cs is a Cocona-based repository CLI whose cleanslate command cleans untracked files, initializes submodules, restores a platform-specific solution, and installs agent files; it also supports dry runs, workload restoration, hook configuration, and idempotent hook removal. global.json pins both the SDK and workload version with roll-forward disabled. AGENTS.md documents xUnit, NSubstitute, Verify snapshots, Pester integration tests, conditional platform code, opt-in features, and backward-compatibility expectations.
Observed
- License
- MIT License
- Primary language
- C# and .NET, with PowerShell and shell tooling
- Packaging
- Distributed as a core NuGet package plus framework and platform integration packages
- Interface
- Application library and integration SDK; the repository also includes a developer helper CLI
- Platform support
- Linux, macOS, Windows, Android, iOS, Mac Catalyst, MAUI, Blazor WebAssembly, and Alpine pipelines are documented
- Framework targets
- Targets include modern .NET, .NET Standard, and .NET Framework
- Repository structure
- Separate source, test, sample, benchmark, integration-test, module, and script areas are present
- Testing
- Uses xUnit, NSubstitute, Verify API snapshots, Pester integration tests, device tests, and Playwright coverage
Read from README.md, dev.cs, LICENSE, build.sh, AGENTS.md, CLAUDE.md, build.cmd, .craft.yml, Sentry.slnx, agents.toml, global.json, warden.toml, .codecov.yml, CHANGELOG.md, nuget.config.
What it can do
Capture and report application crashes
Unhandled exceptions and crash data → Detailed crash reports with stack traces
Monitor application performance
Application execution metrics → Performance insights and bottleneck identification
Log structured application events
Custom log messages and application events → Organized, searchable log entries
Track user sessions
User interaction data → Session analytics and user behavior insights
Capture breadcrumbs for debugging
Application state changes and user actions → Sequential trail of events leading to issues
Set custom tags and context
User-defined metadata and context variables → Enhanced error reports with custom information
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.