Rollout start: Mar 14, 2023
With this release, the oldest supported OneAgent versions are:
New technology support
For more information, see New technology support.
- Spring Web Services 4 (Java module). OneAgent feature: Java Servlet 5.0
New features and enhancements
IBM z/OS
oneagentzos-R12610.pax
is now available. Find the upgrade instructions in Upgrade and maintenance.
zRemote max length of a fetched SQL statement increased
Apps & Microservices | Mainframe
If the SQL fetch feature is enabled on the zRemote module, the maximum length of a SQL statement fetched from a DB2 database has been increased from 500 bytes to 3,500 bytes.
New zLocal released with improved failover processing
Apps & Microservices | Mainframe
New zLocal version 1.1.0 released with improved failover processing for zDC/zRemote. See Update and maintenance on how to update your zLocal.
Detection of Python data source processes
Infrastructure Monitoring | Hosts
Python-based Extensions 2.0 data source processes are now detected and reported as follows:
- "Dynatrace Python" - for ActiveGate-based data sources
- "OneAgent Python" - for data sources running on Oneagent
Host availability state sent as metric
Infrastructure Monitoring | Hosts
The OneAgent OS module now reports the host availability state as a metric.
Metric key: builtin:host.availability.state
Reported states:
UP
- host working, OneAgent active and sending dataNO_DATA
- host working, OneAgent active but not sending dataNO_DATA_AGENT_INACTIVE
- host working, OneAgent inactive (disabled manually in configuration) and not sending dataSHUTDOWN_HOST
- host has been shut downUNMONITORED_AGENT_STOPPED
- host unmonitored: OneAgent stoppedUNMONITORED_AGENT_UPGRADE
- host unmonitored: OneAgent in upgradeUNMONITORED_AGENT_UNINSTALLED
- host unmonitored: OneAgent uninstalled
The resolution is 1 minute: states are sent every minute, always with the value 1, which means that the reported state occurred in the given minute. If there is no sample with the given state, it means that the state was not detected in this minute.
Npcap upgrade
Infrastructure Monitoring | Network
The Npcap version included with the OneAgent installer is now version 1.71, which contains security improvements. However, due to a change in the driver signing process, installation of Npcap 1.71 will fail during fresh installs on Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Desktop 8.1 hosts that haven't had Npcap installed before. As a workaround, please install an older OneAgent (with Npcap 1.31) first or install Npcap manually.
Simultaneously use OneAgent and OpenTelemetry exporters for Node.js, .NET, PHP, and Go
Apps & Microservices | Distributed traces
When you deploy OneAgent to automatically collect OpenTelemetry span data for Node.js, .NET, PHP, and Go, existing OpenTelemetry exporters are no longer suppressed by OneAgent. OpenTelemetry spans collected and integrated with end-to-end distributed traces spans by OneAgent, can now be sent by an OpenTelemetry exporter to third-party backends, such as Jaeger, without disturbing existing OpenTelemetry and third-party backends.
OneAgent resolved issues
General Availability (Build 1.261.194)
The 1.261 GA release contains 17 resolved issues (including 1 vulnerability resolution).
Infrastructure Monitoring
- Fixed timestamp synchronization with cluster time for metrics and logs ingested in the Python SDK. All metrics without a specified timestamp are now timestamp synchronized with cluster time, not local time, and all ingested logs are adjusted with cluster time. When local time on the machine is different than cluster time, metrics and logs are displayed in the web UI with cluster time. (EXT-3756)
- EEC no longer fails to deploy multiple extensions because the download is not fast enough. (EXT-4064)
- All delta count metrics (calculated based on monotonic count metrics on EEC) are now enriched by additional dimensions. (EXT-4098)
.NET
- Fixed an issue that occurred with duplicate HTTP headers. (OA-13385)
- Improved stability of the OneAgent .NET code module: fixed an issue with .NET instrumentation cache and .NET code module agent initialization and improved stability of the OneAgent .NET LogEnrichment sensor. (OA-14179)
- Improved OneAgent .NET code module HTTP WebRequest handling while logging (issue formerly caused exceptions in corner cases). (OA-13462)
All modules
- Process group ID calculation for applications in Kubernetes without injected code module has been changed: IDs will change when the `DT_CLUSTER_ID` environment variable is set, and cloud application and workload detection rule is set and enabled for Kubernetes. (HOST-141)
Mainframe
- MQPuts for CICS are now correctly linking CICS-to-CICS (outbound MQPUTs from CICS were not linking to the inbound MQGET). (OA-14142)
- Fixed issue with SQL Fetch (in zRemote) premature database disconnection. (OA-12851)
Node.js
- Resolved issue with MongoDB database information being unavailable for MongoDB 4.x in certain scenarios. (OA-12242)
OS module
- Resolved issue in which, starting with OneAgent version 1.257, the 'View Containers' option was available for some hosts. (HOST-2168)
- Declarative grouping will no longer incorrectly group child processes to the parent when they could be grouped by another declarative group rule. (HOST-2203)
- OS service events are now disabled when a new OS service config is empty. (HOST-2063)
- Fixed an issue where the timings of some host events (such as host high CPU/high memory) were incorrect. This sometimes caused Davis to be unable to correlate changepoints in that time, which could lead to missing root causes for the problems of those events and no merging with service/app-level events. (HOST-2006)
infrastructure
- Vulnerability: Fixed an issue in Extension Execution Controller (EEC) where extensions may not be executed with least privileges. (DTSEC-4369)
Java
- Fixed serialization issue of mdc variable when log enrichment is active. (OA-12068)
Go
- Fixed an issue where an injection failure message would disappear from the process. (OA-14029)
Update 204 (Build 1.261.204)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.261 release.
OS module
- To prevent generation of unnecessary short-lived events, when an OS service raises an event, it no longer generates a new event if the state change doesn't close the event. Instead, it updates the existing event with the new state of the OS service. (HOST-2362)
- When an OS service alert is active and the service status changes (but still matches the alert criteria), OneAgent now stops the current alert and raises a new one with the title updated to match the new status. (HOST-1779)
OneAgent for Android
Dynatrace Android Gradle plugin
Ending support for Java version 8, 9, and 10. The new minimum required version is Java 11.
General Availability (Build 8.261.1)
The 8.261 GA release doesn't contain any user-facing resolved issues.
OneAgent for iOS
General Availability (Build 8.261.1)
The 8.261 GA release contains 1 resolved issue.
OneAgent for iOS
- Improved performance of send interval calculation and timestamp generation. (RUM-8800)
OneAgent for JavaScript
General Availability (Build 1.261.63)
The 1.261 GA release contains 2 resolved issues.
JavaScript
- Fixed a bug where the "Visually complete" metric ignored images on the BODY tag if the JavaScript code module was injected late. (RUM-8950)
- Resolved issue where page name and page group could be unescaped, which would cause issues with parsing of such beacons. (RUM-8898)
Update 314 (Build 1.261.314)
This is a cumulative update that contains all previously released updates for the 1.261 release.