v3.8.4

What's Changed

This release contains several improvements on the servlet instrumentation contributed by @j-denner. It also features an improvement for the OpenTelemetry Dynatrace exporter: By default the preferred aggregation temporality is now set to always_delta instead of the delta_preferred provided by the OpenTelemetry SDK. The difference is, that the exporter will also use delta aggregation temporality for up-and-down counters. This is necessary, since Dynatrace will otherwise drop metrics of this type. You can switch the aggregation temporality with system property otel.exporter.dynatrace.metrics.temporality.preference.

• Fix typo in fields documentation by @vtintillier in #176
• DynLogEnvironment - Also wrap configuration with a LazyInitializer. by @j-denner in #182
• Some corrections and performance improvements in CorrelationIdFilter by @j-denner in #183
• AddHttpHeaderToLogContextFilter: Filter immediately for getField presence by @j-denner in #184
• Fix Aggregation Temporality in Dynatrace Exporter by @KarstenSchnitter in #181

New Contributors

• @vtintillier made their first contribution in #176

Full Changelog: v3.8.3...v3.8.4

Many thanks to all contributors to this release.

v3.8.3

This is a bugfix release for the dynatrace exporter for metrics. Dynatrace requires metrics of kind sum to have delta aggregation temporality. Metrics with cumulative aggregation temporality are currently dropped by the API.

What's Changed

• Fix Dynatrace Exported to Generate DELTA Temporality by default and allow manual reconfiguration by @KarstenSchnitter in #174

Full Changelog: v3.8.2...v3.8.3

v3.8.2

This release just improves on the cf-java-logging-support-opentelemetry-agent-extension. It now provides a dynatrace exporters for metrics. This will detect bindings to SAP BTP APM and allow the OpenTelemetry Java Agent to forward metrics to Dynatrace. See the documentation on the required configuration.

What's Changed

• Provide Dynatrace Exporter by @KarstenSchnitter in #170
• Fix default property names by @KarstenSchnitter in #171

Full Changelog: v3.8.1...v3.8.2

v3.8.1

This release upgrades Logback to version 1.2.13 to mitigate CVE-2023-6378. Please upgrade your dependencies. Note, that the CVE issue is within an optionally configurable log receiver of an application, that not only requires explicit configuration in the logback files, but also adding an appropriate route in the CF manifest of the application.

The release also extends the module: cf-java-logging-support-opentelemetry-agent-extension. It now provides an cloud-logging exporter to be used with the OpenTelemetry Java Agent. This allows to combine the SAP Cloud Logging support with other OpenTelemetry targets. Additionally, all bound service instances will now be configured as data sinks.

What's Changed

• Upgrade logback to 1.2.13 by @KarstenSchnitter in #168
• Introduce Cloud Logging Exporter by @KarstenSchnitter in #169

Full Changelog: v3.8.0...v3.8.1

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