v3.8.0

This release adds a new module: cf-java-logging-support-opentelemetry-agent-extension. It provides an OpenTelemetry Java Agent extension, that scans the application environment for service bindings to SAP Cloud Logging. If such a binding is found, the OpenTelemetry Java Agent is configured to forward observability data to that service instance. See the extension documentation for details.

What's Changed

• Add OpenTelemetry Java Agent Extension by @KarstenSchnitter in #165

Full Changelog: v3.7.1...v3.8.0

v3.7.1

This minor release introduces two new fields, when exceptions are logged:

• exception_name containing the Java class name of the logged exception
• exception_message containing the message of the logged exception

The exception_name can be used to aggregate events by exception.
The exception_message may contain information that is otherwise only available in the stacktrace.
Thanks to @KaiHofstetter for suggesting this change.

What's Changed

• Add Exceptions Type and Message by @KarstenSchnitter in #161
• Use the SAP Java buildpack by @haraldfuchs in #159
• Bump jetty-server from 11.0.13 to 11.0.14 in /cf-java-logging-support-servlet-jakarta by @dependabot in #155
• Bump jetty-server from 9.4.50.v20221201 to 9.4.51.v20230217 in /cf-java-logging-support-servlet by @dependabot in #157

New Contributors

• @haraldfuchs made their first contribution in #159

Full Changelog: v3.7.0...v3.7.1

v3.7.0

This release introduces cf-java-logging-support-servlet-jakarta, a copy of cf-java-logging-support-servlet but linked against jakarta.servlet instead of javax.servlet.
The code is compatible between the artefacts, so that can be exchanged for each other if the dependencies are met.

What's Changed

• Add a new servlet logging module supporting jakarta.* packages. by @mofterdinger and @aamotharald in #153
• Upgrade dependencies by @KarstenSchnitter in #154

New Contributors

• @mofterdinger and @aamotharald made their first contribution in #153

Full Changelog: v3.6.3...v3.7.0

v3.6.3

This is a bugfix release to upgrade some dependencies because of vulnerabilities.

What's Changed

• Bump gson from 2.8.5 to 2.8.9 in /cf-java-monitoring-custom-metrics-clients by @dependabot in #147
• Bump jetty-server from 9.4.44.v20210927 to 9.4.49.v20220914 in /cf-java-logging-support-servlet by @dependabot in #148
• Bump jackson-databind from 2.13.2.2 to 2.13.4.1 in /cf-java-logging-support-servlet by @dependabot in #150

Full Changelog: v3.6.2...v3.6.3

v3.6.2

This is a bugfix release for a regression in cf-java-logging-support-logback. It affected the logging of stacktraces when using logback as a logging backend.

What's Changed

• Fix logback stacktrace information by @KarstenSchnitter in #146

Full Changelog: v3.6.1...v3.6.2

v3.6.1

This is a bugfix release to add the missing Java thread name to the log messages. It was accidentally dropped in v3.6.0

What's Changed

• Bump jackson-databind from 2.13.0 to 2.13.2.1 in /cf-java-logging-support-servlet by @dependabot in #143
• Add Thread name to JSON log events by @KarstenSchnitter in #144

Full Changelog: v3.6.0...v3.6.1

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

v3.5.7

This is a bugfix release for #135.

What's Changed

• #135 Fix UOE when using Custom Fields by @KarstenSchnitter in #136
• Fix typo and formatting by @TimGerlach in #134

New Contributors

• @TimGerlach made their first contribution in #134

Full Changelog: v3.5.6...v3.5.7

v3.5.6

This is purely a dependency update to resolve CVE-2021-44832 and CVE-2021-42550

What's Changed

Upgraded dependencies:

• log4j2 2.17.1 (resolve CVE-2021-44832)
• logback 1.2.10 (resolve CVE-2021-42550)
• jackson-jr 2.13.1
• junit 4.13.2
• spring-boot 2.6.1

Full Changelog: v3.5.5...v3.5.6

v3.5.5

⚠️ This release upgrades Log4j2 to version 2.17.0 in mitigation of CVE-2021-45105. Furthermore, it secures sample-spring-boot when build with -Plog4j2 by replacing the Spring Boot provided log4j version with 2.17.0.

What's Changed

• #128 upgrade log4j to v2.17.0
• #129 secure log4j to v2.17.0 for sample-spring-boot

Full Changelog: v3.5.4...v3.5.5