v3.6.0
Note: this version does not include the Java thread name in the log messages. This bug is fixed in v3.6.1
This release contains a major refactoring of the JSON generation code.
The implementation now uses Jackson's ObjectComposer instead of a string pattern.
This increases performance and allows several extension points to library users.
See the Wiki article on Writing Application Logs for details.
In particular it is now possible to register custom "Field Suppliers", that can add custom fields to the log message.
Furthermore, custom field support now extends to request logs.
Another major change is, that the library will no longer add CloudFoundry metadata (from env VCAP_APPLICATION) by default.
This reduces the message size considerably and improves human readability.
Usually, the missing data is unproblematic, since it is added in the message envelope by CF Loggregator.
If your logging service cannot extract the information from the envelope, you can bring back the old behaviour with the example configuration given in the Wiki article on Writing Application Logs.
What's Changed
- Add support for W3C traceparent HTTP header by @KarstenSchnitter in #139
- Introduce JHM Benchmarking for Log Backends by @KarstenSchnitter in #137
- Refactor Logback Log Generation by @KarstenSchnitter in #140
- Refactor json generation log4j2 by @KarstenSchnitter in #142
Full Changelog: v3.5.7...v3.6.0
