Official Sentry SDK for .NET applications, providing error monitoring, performance tracking, and crash reporting.
Sentry SDK for .NET is an official client library that integrates .NET applications with the Sentry error monitoring and performance tracking platform. It automatically captures exceptions, logs, and performance data, providing developers with detailed insights into application failures and bottlenecks. The SDK supports a wide range of .NET frameworks and platforms, including ASP.NET Core, Blazor, MAUI, and cloud functions.
.NET developers and teams building applications with frameworks like ASP.NET Core, Blazor, MAUI, or using logging libraries such as Serilog, NLog, or log4net, who need robust error monitoring and performance insights.
Developers choose this SDK for its official Sentry integration, extensive framework support, and seamless performance tracking capabilities. It provides a unified solution for error monitoring across the entire .NET ecosystem with minimal setup.
Sentry SDK for .NET
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports a wide range of .NET frameworks including ASP.NET Core, Blazor, MAUI, and gRPC, as detailed in the integrations table, ensuring broad compatibility.
Integrates with OpenTelemetry and provides profiling via Sentry.Profiling, enabling detailed latency and performance monitoring across applications.
Includes Sentry.Extensions.AI for monitoring AI agent interactions and specific packages like Sentry.Google.Cloud.Functions, catering to modern use cases.
Offers dedicated packages for major logging frameworks like Serilog, NLog, and log4net, making it easy to enhance existing logging setups without overhaul.
Tightly integrated with Sentry's proprietary cloud service, making it difficult to switch to other monitoring tools without significant rework or data migration.
Enabling performance profiling requires additional configuration and the Sentry.Profiling package, which can add overhead and complexity compared to basic error monitoring.
All error and performance data must be sent to Sentry's servers, which can fail in offline environments or introduce latency, as highlighted by the cloud-based nature.