All Versions
14
Latest Version
Avg Release Cycle
74 days
Latest Release
92 days ago

Changelog History
Page 1

  • v1.6.0

    December 03, 2020
    • โž• Added structured logging feature with AppendKeyValue (#40, #41)
    • โž• Added support for %{field} syntax in prefix patterns (in addition to %field)
    • โž• Added file open/close hooks to DateAndSizeRollingFileAppender
    • ๐ŸŒฒ Log thread name instead of id when available
  • v1.5.0

    July 09, 2020
    • โšก๏ธ Updated dependencies: replaced Jil with Newtonsoft.Json (#39)
    • โž• Added ReadOnlySpan<byte> and ReadOnlySpan<char> overloads to AppendAsciiString (#37)
  • v1.4.3

    February 28, 2020
    • โž• Added nullable reference types annotations (#36)
    • ๐Ÿ›  Fixed a NullReferenceException which happened when using the default constructor of ConsoleAppender
  • v1.4.2

    September 23, 2019
    • โž• Added support for specifying an appender type with an assembly-qualified name - #35
  • v1.4.1

    June 26, 2019
    • โž• Added exception handling to unmanaged struct formatting
    • โž• Added exception message to the log when an exception occurs during formatting
  • v1.4.0

    May 10, 2019
  • v1.3.2

    March 14, 2019
    • ๐Ÿ›  Fixes uncaught exception when running on Linux
  • v1.3.1

    December 06, 2018
    • ๐Ÿ›  Fixed an accidental breaking change in the public API
  • v1.3.0

    December 05, 2018
    • ๐Ÿ›  Fixed silent allocations which could occur when more than 10 Append calls were issued.
    • โž• Added a LogEventArgumentCapacity option which sets the max count of expected Append calls. The default value is 32.
    • โž• Added a LogEventArgumentExhaustionStrategy option which controls what to do when too many Append calls are issued. Messages can either be truncated (default behavior) or cause allocations.
    • โž• Added a global TruncatedMessageSuffix option which controls the suffix which will be appended to a truncated message. Default value: " [TRUNCATED]".
    • โ™ป๏ธ Refactored configuration options. There is a breaking change in a public interface that should have remained internal and is not expected to be implemented outside of ZeroLog, hence only the minor version is increased.
    • ๐Ÿ›  Fixed an access violation that could occur if a logger is used after a call to LogManager.Shutdown. Note that this could still happen if a log event is acquired before the shutdown and is retained for more than 100ms before Append is called, but this is incorrect ZeroLog usage and is not expected. Log events acquired after the shutdown are safe.
    • ๐Ÿ›  Fixed an error that caused ZeroLog to shutdown when a message longer than 16KB was logged. Such messages will either be truncated or cause an error to be logged.
  • v1.2.0

    August 29, 2018
    • Many optimizations
    • ๐ŸŒฒ Automatic flushing at the end of a log burst. Can be disabled with LogManager.Config.FlushAppenders
    • โž• Added LogManager.GetLogger<T>()
    • โœ‚ Remove shutdown timeout which caused access violations with large buffers

    ๐Ÿš€ Note that this release changes the API surface of appenders. It didn't get a major version bump as it should not be a breaking change for most users (it will only break if you use custom appenders). More API changes will be made in v2.0.