Releases: exceptionless/Exceptionless.Net
v4.3.0
Version 4.3.0 is a maintenance release that focused on improving GDPR support and fixing bugs.
General Data Protection Regulation
We've added new controls to help meet GDPR requirements. By default the Exceptionless Client will report all available metadata including potential PII data. You can fine tune the collection of information via Data Exclusions or turning off collection completely. Please visit the wiki for detailed information on how to configure the client to meet your requirements.
New Features
- Added
IncludeUserName,IncludeMachineName,IncludeIpAddress,IncludeCookies,IncludePostData,IncludeQueryStringproperties toclient.Configurationthat give you fine grained data controls to limit what data is sent. Please note some of these properties are already being handled by Data Exclusions. - Added
includePrivateInformationto theexceptionlessconfig section which allows you to quickly disable collection of extra metadata in your apps. - Added ability to configure the client configuration end point via
client.Configuration.ConfigServerUrl. - Added
Exceptionless.Linking.PreserveAttributeto the main client. This attribute allows easier integration into Xamarin to insure the linker doesn't remove any required components (Contrib @GeirGrusom #189).
Bug Fixes
- Fixed a bug where configuration could be retrieved concurrently causing extra requests to be made.
- Updated logic around Settings management to help prevent any race conditions when updating values.
Upgrading to 4.3.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.2.2
Version 4.2.2 is a maintenance release that focused on improving logging and fixing bugs around storage.
New Features
- Add StoragePath to AspNetCore configuration to control whether to use FolderObjectStorage (Contrib @edwardmeng #178).
- Add new Microsoft.ExtensionsLogging internal log client for troubleshooting. This can be configured via
ExceptionlessClient.Default.UseLogger(new Exceptionless.Extensions.Logging.ExtensionsExceptionlessLog(loggerFactory));
Bug Fixes
- Fixed a bug where InMemoryObjectStorage would only store 100 events, this could cause events to be discarded. We've increased the count to 1000 by default (exceptionless/Exceptionless#356).
- Fixed a bug where FolderObjectStorage would throw an exception and suspend processing while processing the queue if the queue folder didn't exist.
- Fixed a bug where the internal log wasn't respecting the min log level.
Upgrading to 4.2.2
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.2.1
Version 4.2.1 is a maintenance release that focused on optimizations to the NLog target (that were identified by @snakefoot while doing a code review) and optimized the default value for submitting heartbeats and retrieving settings.
New Features
- Reduced the number of allocations that occurred while using the NLog target (Contrib @snakefoot #172 #173 #174).
- Ensure we correctly handle non async NLog targets. (Contrib @snakefoot #171).
- Optimized the default interval for submitting heartbeats and retrieving settings when idle.
Upgrading to 4.2.1
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.2.0
Version 4.2.0 focused on client improvements and adding support for high performance persisted storage using Message Pack.
New Features
- Added ASP.NET Core 2.0 support for .NET Framework. Previously it only targeted the .NET Core runtime.
- Added improved support for EU General Data Protection Regulations for 2018. You can limit the sending of personal identifiable information like user names and IP Addresses by setting
ExceptionlessClient.Default.Configuration.IncludePrivateInformation = false. - Added new IStorageSerializer MessagePack implementation which allows us to have high performance serialization for offline storage (Contrib @edwardmeng #168).
Upgrading to 4.2.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.1.0
Version 4.1.0 focused on adding support for .NET Standard 2.0, performance improvements and bug fixes.
New Features
- Added .NET Standard 2.0 support. You can now easily integrate with UWP applications!
- Added Microsoft.Extensions.Logging support via the Exceptionless.Extensions.Logging client (Contrib @moogle001 #162).
- Allow
nullanddefaultvalues to be serialized. This allows greater insight into contextual data (Contrib @jamierushton #157). - Added new IStorageSerializer interface to control how events and settings are serialized to disk. This allows you to easily replace the default storage serializer from json to any format like MessagePack for increased IO throughput (Contrib @edwardmeng #163).
- We now use GitLink for easier debugging of packages!
Bug Fixes
- Replace GetFiles with EnumerateFiles method to improve peformance in FolderObjectStorage (Contrib @edwardmeng #161).
- Improved diagnostic logging to include timestamps and log level (Contrib @edwardmeng #167).
Upgrading to 4.1.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.0.4
Version 4.0.4 focused on bug fixes and updating package dependencies.
Bug Fixes
- Fix issue that the logging content cannot be recognized in Chinese environment (Contrib @edwardmeng #156).
- Fixes ProcessQueue method so it blocks until queue has been processed (Contrib @MihaMarkic #147).
Upgrading to 4.0.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.0.3
Version 4.0.3 focused on bug fixes and improvements to the .NET Core and ASP.NET Core clients.
New Features
- Added log4net .NET Core support.
- Added support for reporting 404's in ASP.NET Core.
- Add ability to set the min log level in configuration by calling
SetDefaultMinLogLevel. This allows you to set a min log level until server configuration is applied. - Added Client IP support for X-Forwarded-For (Contrib @barankaynak #132). This helps when using proxy servers and would enable us to properly identify individual users.
- Made it easier to capture the HttpActionContext by adding
SetHttpActionContextextension methods to the web clients. This allows request and user info to captured by default when manually submitting events. - Added SetException overload so you can submit any event type that contains an exception (#139).
Bug Fixes
- Fixed an issue where the ASP.NET Core 1.1 runtime was preventing clients from reporting any data (#142).
- Fixed an issue where exceptions converted to 404's were not running the event exclusion logic.
- Fixed an issue where the duplicate checker plugin could DOS itself. This could only have occurred if you had client logging enabled, which is disabled by default and is only meant for diagnostic logging.
- Fixed an issue where the nlog logger wasn't setting event type.
- Fixed an issue with package configuration of signed web packages (#137).
- Fixed an issue where adding our trace listener could blow up due to other invalid configured trace listeners (#136)
- Upgraded to the latest version of BenchMarkDotNet and ensure benchmarks run (Contrib @adamsitnik #146)
Upgrading to 4.0.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.0.2
Version 4.0.2 focused on bug fixes and making it easier to consume the package in Xamarin projects.
New Features
- Added support for Asp.Net Core's application lifetime. This means that the client is smarter about event submission on shutdown and more (#120).
- Added support for specifying a default proxy via
client.Configuration.Proxy(#123). The proxy information is automatically picked up via configuration. This allows you to manually specify the proxy to use in code.
Bug Fixes
- Fixed an issue where Line breaks were being removed from the Exception message (#119).
- Replaced Global Mutex locks which were windows only to file based locks which works cross platform (#124).
- Fixed a concurrency issue when adding or removing plugins (#62).
- Fixed an issue where the request stream might not be seekable (#124).
- Fixed multiple issues where a exception could be thrown while running plugins (#123).
- Fixed an installation issue where the install script would fail if the xml document was empty (#119).
- Fixed an issue where the deduplication plugin wasn't calling the Submitted event handler (#110).
- Fixed an issue where the WPF Client could keep the application silently running in the background (#113).
Breaking changes
- Removed Isolated storage support (Removed only in .NET Core targets) until it's supported cross platform. This was causing a bunch of issues when installing in Xamarin Projects.
Upgrading to 4.0.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.0.1
Version 4.0.1 includes a work around for a bug that could cause the NuGet packages to fail to install.
Upgrading to 4.0.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
v4.0.0
Version 4.0 includes support for .NET Core and ASP.NET Core! This means you can now use Exceptionless to build .NET applications on Linux, macOS and Windows!!
New Features
- Added .NET Core support! The Exceptionless NuGet package now also supports .NET Standard 1.2+
- Added new ASP.NET Core client and sample applications (#28)!
Breaking changes
- We merged in the
Exceptionless.PortableandExceptionless.Extrasfunctionality into theExceptionlesspackage and dropped support for .NET 4.0. TheExceptionlessNuGet package now supports.NET Standard 1.2+,PCL Profile 151, and.NET 4.5This is the main reason for bumping the major version.- The
Exceptionless.PortableNuGet package still exists and has a dependency on theExceptionlessPackage. This should make upgrading a breeze. - If you need to use .NET 4.0, please stick with the 3.5 NuGet Packages which will continue to work as expected 👍.
- The
- Properties marked deprecated (in
v2.0.0) were removed:ExceptionlessClient.Currentproperty was replaced withExceptionlessClient.Default.- Configuration
EnableSSLproperties were removed.
Upgrading to 4.0.0
If upgrading from v2 or v3 the upgrade process should include just updating your NuGet packages. Please see the upgrade guide for more information.
Please take a look at the change log for a full list of the changes.
Feedback
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!