Releases: logfellow/logstash-logback-encoder
Releases · logfellow/logstash-logback-encoder
logstash-logback-encoder-4.2
logstash-logback-encoder-4.1
- Changed async and tcp appenders to use daemon threads by default, so that shutdown is not required for the jvm to exit properly.
- Changed async and tcp appenders to use
BlockingWaitStrategyto consume less CPU resources when idle - Added ability to configure wait strategy using simple string configuration
- Added custom SSL configuration support to all TCP appenders (using SSL support provided by logback)
- SSL can now be used for AccessEvents
logstash-logback-encoder-4.0
Changes in 4.0:
- New
CompositeJsonFormatter/Encoder/Layoutwere created to allow customizing the JSON output through the use of providers.- Each provider contained within the composite contributes to the JSON output.
- All existing functionality was converted to individual providers
LogstashFormatter/Encoder/Layoutwere refactored to be just extensions of the composite concept that contain a pre-defined set of providers
- A new pattern-based provider was added. This provider allows usage of standard
PatternLayoutpatterns within a JSON template. This allows much easier configuration, since you can layout your JSON event as a JSON string with embedded patterns for values. - Added a new
AsyncDisruptorAppenderthat is similar to logback'sAsyncAppender, but uses an LMAX DisruptorRingBufferas the inter-thread data exchange mechanism (as opposed to aBlockingQueueused by theAsyncAppender)- Refactored the tcp appender to extend the
AsyncDisruptorAppenderso it can take advantage of the benefits of using aRingBuffer
- Refactored the tcp appender to extend the
- Add ability to define a prefix and suffix on the encoder/layouts that appear before/after the JSON output
- Lots of doc improvements
XML configuration is fully backwards compatible except for the following:
- The
queueSizefor the tcp appenders must now be a power of 2. Also, recommend you switch to usingringBufferSizeinstead ofqueueSize. - The
eventDelayLimitfor the tcp appenders is no longer used (since the the appender will never block the logging thread)