With this release, the following are the oldest supported OneAgent versions.
| Support level | Oldest supported version |
|---|---|
| Standard Support | 1.299 |
| Enterprise Success and Support | 1.293 |
For details, see How long are versions supported following rollout?.
Infrastructure Observability | Hosts
Fixed the issue of Oracle Net Listener processes not being split by name when OS Services are not collected on Windows. Also, now a correct listener name is used instead of the Oracle home name.
Fixed an issue in which Oracle Net Listener processes were not being split by name when OS Services are not collected on Windows. Also, now a correct listener name is used instead of Oracle home name. This might result in a change of PG/PGI IDs.
Definition of the technology support version schema with examples:
Major version 5 is supported
Minor version 5.1 is supported
Patch version 5.1.1 is supported
Version range 5.1 – 5.3 is supported
The minimum required version is 5+
For more information, see New technology support.
For more information, see End-of-support announcements.
Application Observability | Distributed Traces
PHP Redis Cluster is a new feature for PHP OneAgent.
We've added a new sensor to detect and show in Distributed Traces the Redis Cluster calls from the phpredis extension. In a distributed trace, the Redis Cluster method calls will show on which cluster node the command was executed, when possible.
The OneAgent PHP module supports PHP Redis from version 3.1.6 to 6.2.0.
Infrastructure Observability | Log Monitoring
Log analytics persistence and its snapshots have been moved from:
/var/lib/dynatrace/oneagent/agent/config
to:
/var/lib/dynatrace/oneagent/datastorage/loganalytics
Logs
Starting with this release, structured data can be collected from Windows Event Logs in the User Data or Event Data branches (depending on availability), along with their sub-branches. The collected data is transmitted along with the record content in the form of attributes.
Attribute names are assigned based on available information, such as tag names, the value of the Name field, or—if tag names are repeated and the Name field is absent—a sequential number is added to the tag name.
Sub-branches without values and tags labeled as Binary are omitted.
Application Observability
Specifying Query Parameter capturing will no longer also capture POST Parameters of the specified name.
If needed, Post Parameters will now have to be separately defined in a Body-Capture-Rule.
Infrastructure Observability
Nettracer, Host Availability, Process Availability, and Disk Device Extensions metrics will now be sent via a MINTv2 message instead of being forwarded from a pre-existing MINTv1 message. As a result, it's now possible to enrich them with all host- and process-level resource attributes available.
Software Delivery
With this release, we have implemented span context propagation for PHP.
Platform | OneAgent
The Java code module now adds the dimension dt.process_group.detected_name to all schemaless JMX and PMI metrics.
Platform | OneAgent
OneAgent Java now allows adding variables as dimensions in Extensions 2.0 framework JMX extensions.
Infrastructure Observability | Hosts
Tomcat technology detection for Tomcat server running as a service has been improved.
Application Observability | Queues
We now support automatic tracing of the Reactor Kafka API for sending and receiving messages in Java applications using:
Infrastructure Observability | AWS
We now support automatic DynamoDB tracing of the AWS SDK calls for Python applications.
Infrastructure Observability | AWS
We now support automatic SQS tracing of the AWS SDK for sending and receiving messages in Python applications.
Infrastructure Observability | AWS
We have made the following Amazon SDK support improvements with this release:
Infrastructure Observability | AWS
We now support automatic SQS and SNS tracing of the AWS SDK for sending and receiving messages in Java applications (AWS SDK for JavaScript versions 1.11 and 2.*). This also includes SQS Annotation Spring Boot support.
Digital Experience | RUM Mobile
We have updated Kotlin to version 2.0.21.
Digital Experience | RUM Mobile
We have added a new case to the withCustomInstrumentationConfig view modifier that allows you to specify the action name. Use .useControlName(customName) to define the action name.
Digital Experience | RUM Web
To streamline RUM, we have removed compatibility code for browser versions that don't support PerformanceEntry (all supported browsers support PerformanceEntry). The RUM JavaScript no longer initializes on those browsers.