Breaking change IBM JVM version 7 (z/OS Java module). To continue monitoring on z/OS, upgrade the JVM to version 8. In some scenarios (for example, IBM CTG 9.1), certain JVM upgrade paths may be supported without upgrading the application. Refer to the respective application's documentation for instructions.
New features and enhancements
Application Observability | Mainframe
The Dynatrace z/OS module version of the zDC subsystem, the CICS module, and the IMS module are now available as a property on the respective process. It requires a minimum zRemote module version of 1.273.
RKE2 technology is reported
Infrastructure Observability | Hosts
For hosts that run on RKE2, both Kubernetes and RKE2 are now reported as host technologies.
Log storage configuration: filter by log record level
Infrastructure Observability | Log Monitoring
You can filter entries that are sent to storage by Log record level (loglevel).
In the Settings app, go to Log Monitoring > Log ingest rules
Select Add rule.
Select Add matcher.
Set Matcher attribute to Log record level.
Set Value to one or more of the available values.
Requirements: Dynatrace version 1.276+
New attribute values for Windows events logs
Infrastructure Observability | Log Monitoring
There are new attribute values for Windows events logs available. You can use them to filter entries from Windows events logs that are sent to the storage.
In the Settings app, go to Log Monitoring > Log ingest rules
Select Add rule.
Select Add matcher.
Set Matcher attribute to one of the following attributes and then enter a Value.
Windows log record event ID
Windows log record source
Windows log record task category
Windows log record operational code
Trace Google Cloud Functions in .NET with Dynatrace
Application Observability | Distributed traces
You can configure tracing of .NET services running on Google Cloud Functions, with a dedicated Dynatrace package for OpenTelemetry. For details, see Integrate on Google Cloud Functions .NET.
Vulnerability: Updated the Python runtime for Extensions Framework 1.0 to Python 3.8.17. (EXT-5516)
Limited access to Python runtime in EEC deployed with OneAgent. (EXT-5228)
OS module
Fixed a situation in which a new event start timestamp was earlier than the old event end timestamp. (HOST-3370)
To reduce `docker info` execution time, detection of the container path from `docker info` is now asynchronous. (HOST-3392)
Disabled reading process memory by the OneAgent OS module when the process agent is disabled for the process. (HOST-3413)
Added support for non-standard CRIO binary locations. (HOST-3569)
Java
Fixed a bug in the attack protection feature for SQL that could result in false positives with number literals. (OA-18707)
All modules
This release contains an updated version of oneagentmon, our Windows injection driver. The new driver contains improvements to the injection process that make it more resilient to the presence of other injection drivers, like the ones that are frequently used by third-party AV/EDR software. (OA-16439)
The OneAgent JavaScript module's signature check is temporarily disabled by default. This was done to mitigate high network traffic between the cluster and OneAgent caused by JavaScript agents older than 2 years having an out-of-date signature, which resulted in an invalid signature check. In a follow-up issue, we will update the signature checking mechanism and enable the signature check as the default again. (OA-19400)
Improved OneAgent compatibility with instructions available on older CPU generations. (OA-18945)
The OneAgent Envoy module is no longer injected into exotic configuration file types such as named pipes. Previously, OneAgent's Envoy injection would try to inject into and read from any file path that was provided to Envoy on the command line. Now, it will first check if the configuration file is a regular file (or symbolic link to a regular file). This prevents problems where it would read any data from named pipes or other file kinds, possibly resulting in data loss. If you previously used a named pipe or another exotic device successfully (on successful injection, OneAgent would create a temporary copy, which would then be read by the application), you need to switch to a regular file. (OA-19053)
Podman container injection now also checks for crun binaries that were built with the "--enable-shared" configuration flag. (OA-18355)
OpenTracing module
Envoy injection now works when camelCase naming is used in the bootstrap config. (But we still strongly recommended using snake_case as primarily shown in Envoy documentation.). (OA-19131)
.NET
Fixed an issue with the OneAgent .NET module, WCF v.2, that resulted in incorrectly structured traces. (OA-19430)
Fixed a OneAgent .NET WCF Sensor v2 issue that added the same soap header twice in routing scenarios. (OA-18858)
Fixed a OneAgent .NET code module initialization issue for applications using app domains with a restrictive permission set for accessing environment variables. (OA-19564)
Improved stability when .NET MSMQ receives messages without message ID information. (OA-19313)
Improved memory management for Real User Monitoring (RUM) for ASP.NET Core. (OA-19469)
Fixed a OneAgent .NET WCF Sensor v2 issue to now capture exceptions correctly and improve the extraction of service names for WebHttpBinding. (OA-16793)
Fixed an issue that caused the .NET code module to crash the process for an unsupported .NET library. Now, the .NET code module shuts down safely. (OA-19320)
Mainframe
Request attributes for MQGET in CICS now enabled. (OA-19413)
OneAgent Installer
The plugin module binaries and process execution have been restored to the bootstrapped OneAgent container deployment. (DMX-4807)