Release v5.2.1

💉 Fixed

• #97 Make sure the sink respects the exponential backoff, even after numerous unsuccessful attempts to send the log events to a log server (discovered by @markusbrueckner)

Release 5.2.0

⚡ Added

• Extension method DurableHttpUsingFileSizeRolledBuffers, creating a durable sink using buffer files with a file size based rolling behavior

💤 Deprecated

• Extension method DurableHttp has been renamed to DurableHttpUsingTimeRolledBuffers, providing clarification between the two durable sink types

Release 5.1.0

⚡ Added

• Support for .NET Framework 4.6.1 due to recommendations from the cross-platform targeting guidelines
• Support for .NET Standard 2.0 due to recommendations from the cross-platform targeting guidelines

Release 5.0.1

💉 Fixed

• #54 Prevent durable HTTP sink from posting partially written log events

Release 5.0.0

⚡ Added

• #51 [BREAKING CHANGE] Support to specify queueLimit when creating a non-durable sink, limiting the number of events queued in memory waiting to be posted over the network.

Release 4.3.0

⚡ Added

• Event formatter called NamespacedTextFormatter suited for a micro-service architecture where log events are sent to the Elastic Stack. The event formatter reduces the risk of two services logging properties with identical names but with different types, which the Elastic Stack doesn't support.

💀 Removed

• Support for .NET Standard 2.0 since the sink also has support for .NET Standard 1.3

Release 4.2.1

💉 Fixed

• #32 Prevent durable HTTP sink from posting HTTP messages without any log events

Release 4.2.0

⚡ Added

• Support for .NET Core 2.0

Release 4.1.0

⚡ Added

• #22 Batch formatter ArrayBatchFormatter which is compatible with the Logstash HTTP input plugin configured to use the JSON codec

💉 Fixed

• Prevent posting HTTP messages without any log events

Release 4.0.0

⚡ Added

• #8 [BREAKING CHANGE] Support for Serilog.Settings.Configuration required changing the extension methods configuring a HTTP sink. Options and DurableOptions no longer exist, and their properties are now optional parameters on the extension methods instead.
• #11 Support for HTTP body configuration using IBatchFormatter and ITextFormatter. This enables full control of how messages are serialized before being sent over the network. (contribution by @kvpt)
• #19 Support for specifying the maximum number of retained buffer files and their rotation period on the durable HTTP sink. (contribution by @rob-somerville)