Changelog History
Page 12
-
v1.0.1-beta3 Changes
Lowering Newtonsoft.Json requirements; #138
-
v1.0.1-beta2 Changes
๐ฆ
Sentry
package Includesnet461
target #135 -
v1.0.1-beta Changes
๐ Features:
- ๐ฒ Use log entry to improve grouping #125
- ๐ Use .NET Core SDK 2.1.401
- ๐ Make
AddProcessors
extension methods on Options public #115 - Format InternalsVisibleTo to avoid iOS issue: 94e28b3
๐ Bug fixes:
- Disabled SDK throws on shutdown: #124
- Log4net only init if current hub is disabled #119
-
v1.0.0 Changes
๐ First major release of the new .NET SDK.
Main features
๐ฆ Sentry package
- Automatic Captures global unhandled exceptions (AppDomain)
- Scope management
- Duplicate events automatically dropped
- ๐ป Events from the same exception automatically dropped
- ๐ Web proxy support
- ๐ง HttpClient/HttpClientHandler configuration callback
- Compress request body
- Event sampling opt-in
- Event flooding protection (429 retry-after and internal bound queue)
- ๐ Release automatically set (AssemblyInformationalVersionAttribute, AssemblyVersion or env var)
- DSN discovered via environment variable
- ๐ Release (version) reported automatically
- CLS Compliant
- Strong named
- BeforeSend and BeforeBreadcrumb callbacks
- ๐ป Event and Exception processors
- ๐ฆ SourceLink (including PDB in nuget package)
- Device OS info sent
- Device Runtime info sent
- Enable SDK debug mode (opt-in)
- Attach stack trace for captured messages (opt-in)
๐ฒ Sentry.Extensions.Logging
- ๐ฆ Includes all features from the
Sentry
package. - BeginScope data added to Sentry scope, sent with events
- LogInformation or higher added as breadcrumb, sent with next events.
- LogError or higher automatically captures an event
- ๐ง Minimal levels are configurable.
Sentry.AspNetCore
- ๐ฆ Includes all features from the
Sentry
package. - ๐ฆ Includes all features from the
Sentry.Extensions.Logging
package. - 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. - ๐ฒ Any event sent will include relevant application log messages
- RequestId as tag
- URL as tag
- Environment is automatically set (
IHostingEnvironment
) - ๐ฐ Request payload can be captured if opt-in
- ๐ Support for EventProcessors registered with DI
- ๐ Support for ExceptionProcessors registered with DI
- ๐ Captures logs from the request (using Microsoft.Extensions.Logging)
- ๐ Supports configuration system (e.g: appsettings.json)
- Server OS info sent
- Server Runtime info sent
- Request headers sent
- Request body compressed
๐ฆ All packages are:
- Strong named
- ๐ Tested on Windows, Linux and macOS
- โ Tested on .NET Core, .NET Framework and Mono
Learn more:
- Code samples
- ๐ Sentry docs
Sample event using the log4net integration: ๐ฑ
Download it directly from GitHub or using NuGet:
Integrations NuGet Sentry Sentry.AspNetCore ๐ฒ Sentry.Extensions.Logging Sentry.Log4Net -
v1.0.0-rc2 Changes
๐ Features and improvements:
SentrySdk.LastEventId
to get scoped idBeforeBreadcrumb
to allow dropping or modifying a breadcrumb- Event processors on scope #58
- Event processor as
Func<SentryEvent,SentryEvent>
๐ Bug fixes:
- #97 Sentry environment takes precedence over ASP.NET Core
Download it directly below from GitHub or using NuGet:
Integrations NuGet Sentry Sentry.AspNetCore ๐ฒ Sentry.Extensions.Logging Sentry.Log4Net -
v1.0.0-rc Changes
๐ Features and improvements:
- ๐ง Microsoft.Extensions.Logging (MEL) use framework configuration system #79 (Thanks @pengweiqhca)
- ๐ฒ Use IOptions on Logging and ASP.NET Core integrations #81
- 0๏ธโฃ Send PII (personal identifier info, opt-in
SendDefaultPii
): #83 - When SDK is disabled SentryMiddleware passes through to next in pipeline: #84
- ๐ฒ SDK diagnostic logging (option:
Debug
): #85 - ๐ป Sending Stack trace for events without exception (like CaptureMessage, opt-in
AttachStackTrace
) #86
๐ Bug fixes:
- MEL: Only call Init if DSN was provided https://github.com/getsentry/sentry-dotnet/commit/097c6a9c6f4348d87282c92d9267879d90879e2a
- Correct namespace for
AddSentry
https://github.com/getsentry/sentry-dotnet/commit/2498ab4081f171dc78e7f74e4f1f781a557c5d4f
๐ฅ Breaking changes:
๐ The settings for HTTP and Worker have been moved to
SentryOptions
. There's no need to calloption.Http(h => h...)
anymore.option.Proxy
was renamed tooption.HttpProxy
.๐ New sample using GenericHost
Download it directly below from GitHub or using NuGet:
Integrations NuGet Sentry Sentry.AspNetCore ๐ฒ Sentry.Extensions.Logging Sentry.Log4Net -
v0.0.1-preview5 Changes
๐ 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:
- ๐ On-prem without chuncked support for gzip #71
- ๐ป Exception.Data key is not string #77
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 -
v0.0.1-preview4 Changes
๐ 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, #54- ๐ป
Exception.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 -
v0.0.1-preview3 Changes
โ 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 -
v0.0.1-preview2 Changes
๐ 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 breadcrumbs- ๐ฒ
ASP.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 - โ Added