Releases: getsentry/sentry-dotnet
Releases · getsentry/sentry-dotnet
0.0.1-preview5
Features:
- Support buffered gzip request #73
- Reduced dependencies from the ASP.NET Core integraiton
- InAppExclude configurable #75
- Duplicate event detects inner exceptions #76
- HttpClientHandler configuration callback #72
- Event sampling opt-in
- ASP.NET Core sends server name
Bug fixes:
Watch on youtube how to use the ASP.NET Core integration.
Download it directly below from GitHub or using NuGet:
Integrations | NuGet |
---|---|
Sentry | |
Sentry.AspNetCore | |
Sentry.Extensions.Logging | |
Sentry.Log4Net |
0.0.1-preview4
Features:
- Using Sentry Protocol as a dependency
- Environment can be set via
SentryOptions
#49 - Compress request body (configurable: Fastest, Optimal, Off) #63
- log4net integration
- SDK honors Sentry's 429 HTTP Status with Retry After header #61
Bug fixes:
Init
pushes the first scope #55, #54Exception.Data
copied toSentryEvent.Data
while storing the index of originating error.- Demangling code ensures Function name available #64
- ASP.NET Core integration throws when Serilog added #65, #68, #67
Improvements to the docs like:
- Release discovery
ConfigureScope
clarifications- Documenting samples
Watch on youtube how to use the ASP.NET Core integration.
Download it directly from GitHub or using NuGet:
Integrations | NuGet |
---|---|
Sentry | |
Sentry.AspNetCore | |
Sentry.Extensions.Logging | |
Sentry.Log4Net |
0.0.1-preview3
This third preview includes bug fixes and more features. Test coverage increased to 96%
Features and improvements:
- Filter duplicate events/exceptions #43
- EventProcessors can be added (sample 1, 2)
- ExceptionProcessors can be added #36 (sample 1, 2)
- Release is automatically discovered/reported #35
- Contexts is a dictionary - allows custom data #37
- ASP.NET integration reports context as server: server-os, server-runtime #37
- Assemblies strong named #41
- Scope exposes IReadOnly members instead of Immutables
- Released a documentation site
Bug fixes:
#46 Strong name
#40 Logger provider gets disposed/flushes events
Watch on youtube how to use the ASP.NET Core integration.
Download it directly from GitHub or using NuGet:
Integrations | NuGet |
---|---|
Sentry | |
Sentry.AspNetCore | |
Sentry.Extensions.Logging |
0.0.1-preview2
This second release includes bug fixes and more features. Test coverage increased to 93%
Features and improvements:
- Added
CaptureMessage
BeforeSend
callback errors are sent as breadcrumbsASP.NET Core
integration doesn't add tags added byMicrosoft.Extensions.Logging
- SDK name is reported depending on the package added
- Integrations API allows user-defined SDK integration
- Unhandled exception handler can be configured via integrations
- Filter kestrel log eventid 13 (application error) when already captured by the middleware
Bugs fixed:
- Fixed #28
- HTTP Proxy set to HTTP message handler
Download it directly from GitHub or using NuGet:
Integrations | NuGet |
---|---|
Sentry | |
Sentry.AspNetCore | |
Sentry.Extensions.Logging |
0.0.1-preview1
Our first preview of the SDK:
Main features:
- Easy ASP.NET Core integration, single line:
UseSentry
. - Captures unhandled exceptions in the middleware pipeline
- Captures exceptions handled by the framework
UseExceptionHandler
and Error page display. - Captures process-wide unhandled exceptions (AppDomain)
- Captures logger.Error or logger.Critical
- When an event is sent, data from the current request augments the event.
- Sends information about the server running the app (OS, Runtime, etc)
- Informational logs written by the app or framework augment events sent to Sentry
- Optional include of the request body
- HTTP Proxy configuration
Also available via NuGet: