With this release, the oldest supported OneAgent versions are:
Standard Support
Enterprise Success and Support
1.241
1.235
Updating OneAgent from version 1.257 to 1.259.339 using the OneAgent updates option was successful for Linux and Windows OS but encountered issues on AIX OS.
See the following steps on how to solve this problem.
Uninstall OneAgent version 1.257 from AIX Servers (AIX version 7.2 TL 3, SP 2 and AIX version 7.2 TL 4, SP 1).
Starting with OneAgent version 1.259, code-level vulnerability ID calculation has changed. After updating the OneAgent, all existing code-level vulnerabilities that are based on the restarted process will be closed and new ones will be opened if the code-level vulnerability is still present. This does not affect third-party vulnerabilities.
Host uptime metric
Infrastructure Monitoring | Hosts
OneAgent now reports the Host uptime metric (builtin:host.uptime). Metric isn't available for application-only deployments.
Node.js module can capture BizEvents
Infrastructure Monitoring | Hosts
Now available: The OneAgent Node.js module can capture BizEvents based on incoming web requests.
Grouping of oneagenthelper process
Infrastructure Monitoring | Hosts
(Linux only) The oneagenthelper process is now assigned to the OneAgent system monitoring process group.
Grouping of oneagenteventstracer process
Infrastructure Monitoring | Hosts
The oneagenteventstracer process is now assigned to the "OneAgent system monitoring" PGI.
Grouping of MongoDB executables with names containing version number
Infrastructure Monitoring | Hosts
MongoDB executables with names containing a version (for example, "mongod-4.0") are now detected as members of the MongoDB group.
PostgreSQL instance name now displayed as node in PGI name
Infrastructure Monitoring | Hosts
PostgreSQL process group instance names are now displayed as "Postgres (INSTANCE_NAME)" in the web UI. The default value of INSTANCE_NAME is Default instance.
Simultaneously use OneAgent and OpenTelemetry exporters for Java
Apps & Microservices | Distributed traces
When you deploy OneAgent to automatically collect OpenTelemetry span data for Java, 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.
Other support changes
OneAgent for z/OS
Build 1.259.1
Fixed S0C4 when IMS DL/I monitoring is enabled and ICAL functions are performed (OA-15052)
Resolved issue with service name correlation caused by incorrectly overwriting application ID already set by the sensor. (OA-12815)
Infrastructure Monitoring
Vulnerability: The Python runtime used in Extensions 1.0 has been updated to version 3.8.16. (EXT-3401)
Improved EEC memory failsafe mechanisms on Linux. (EXT-3554)
Mainframe
Resolved load management issues with zRemote (was unable to handle the proper load from CICS or IMS). (OA-12255)
Node.js
The Node.js script file was incorrectly detected on Azure WebApps for Windows if particular command line arguments were used, resulting in unexpected process IDs. To prevent this, we’ve improved the process ID calculation: existing IIS processes on Azure WebApps will change once after an update to OneAgent version 1.259. (OA-11225)
Resolved issue with OneAgent Node.js code module that sometimes caused application crash ("Segmentation fault"). (OA-12888)
OS module
Corrected problem with process group instance (PGI) in OpenTelemetry traces not being recognized by Dynatrace due to incorrect Process Group ID calculation. (HOST-1901)
OneAgent no longer reads data for OS services when there are no rules defined in settings. (HOST-1825)
The Hyper-V hypervisor is now properly reported. (HOST-1864)
Fixed missing metric graph in problem card for process group instance (PGI) events. (HOST-2034)
Resolved issue in which some processes (such as ElasticSearch) were incorrectly grouped and handled by the OneAgent OS module. (HOST-1934)
Java
Fixed a warning in the OneAgent Java code module when OpenTelemetry was present in an application and its instrumentation was turned off. (OA-12451)
Fixed issue with OneAgent Java code module causing crash of WebSphere Application Server startup on AIX. (OA-12949)
Update 369 (Build 1.259.369)
This cumulative update contains 6 resolved issues and all previously released updates for the 1.259 release.
Resolved issue that caused OneAgent OS module startup failure in some containerized environments. (HOST-2129)
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)
.NET
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)
Infrastructure Monitoring
EEC no longer fails to deploy multiple extensions because the download is not fast enough. (EXT-4064)
Mainframe
MQPuts for CICS are now correctly linking CICS-to-CICS (outbound MQPUTs from CICS were not linking to the inbound MQGET). (OA-14142)