Improved splitting Oracle Net Listener processes by listener name
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.
Technology support
Definition of the technology support version schema with examples:
Major version 5 is supported
Major version 5 is supported, including all of its minor versions like 5.1 and 5.2
Other major versions are not supported like 6 and 7
Minor version 5.1 is supported
Minor version 5.1 is supported, including all of its patch versions like 5.1.1 and 5.1.2
Other minor versions are not supported like 5.2 and 5.3
Patch version 5.1.1 is supported
Patch version 5.1.1 is supported
Other patch versions are not supported like 5.1.2 and 5.1.3
Version range 5.1 – 5.3 is supported
Minor versions 5.1, 5.2, and 5.3 are supported, including all of their patch versions like 5.1.1, 5.2.1, and 5.3.1
Other minor versions are not supported like 5.0 and 5.4
The minimum required version is 5+
All major, minor, and patch versions starting from version 5 are supported, like 5, 5.1, 5.1.1, and 6
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 repositioning
Log analytics persistence and its snapshots have been moved from:
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
POST Parameters no longer captured with Query Parameters
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, Availability, and Disk Extension metrics are now fully enriched
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
Span context propagation for PHP now available
With this release, we have implemented span context propagation for PHP.
Platform | OneAgent
Process group name is added to all JMX/PMI metrics
The Java code module now adds the dimension dt.process_group.detected_name to all schemaless JMX and PMI metrics.
Platform | OneAgent
Extension variables now allowed as dimensions for Java JMX extensions
OneAgent Java now allows adding variables as dimensions in Extensions 2.0 framework JMX extensions.
Infrastructure Observability | Hosts
Improved Tomcat process detection
Tomcat technology detection for Tomcat server running as a service has been improved.
Application Observability | Queues
Support for Reactor Kafka reactive API tracing (Java module)
We now support automatic tracing of the Reactor Kafka API for sending and receiving messages in Java applications using:
Fixed a OneAgent Go module crash that occurred when the Go application provided its own implementation of `pthread_create`. (OA-48411)
Fixed an issue with retrieving function metadata for Go libraries. (OA-46829)
General
Fixed an issue where in some cases OS Agent could shortly switch to a tenant-level Declarative Process Grouping configuration when the Dynatrace cluster restarts, leading to potential process availability alerts and metrics loss. (OA-49022)
The priority of resource attributes provided with the OTEL environment variable `OTEL_RESOURCE_ATTRIBUTES` has been changed to match the process level, so it's possible to overrule resource attributes with the same name defined on the host level. (OA-47355)
Logging module
OneAgent Log module will no longer add an "<empty>" string to a non-empty attribute value when expanding the wildcard from the custom log source path. Now, an "<empty>" string will be used only when the attribute value is empty. (OA-48029)
Fixed crashes that occurred when the number of containers tracked by the OneAgent log module was greater than the limit of open file descriptors for its process. (OA-48727)
OS module
Fixed an issue where OneAgent sometimes did not send an availability metric during OneAgent upgrade. (OA-48105)
Fixed an issue that caused file aging in agent/bin on Windows to attempt to remove agent binaries that were in use. (OA-47131)
Java
The FeatureSet element within the extension YAML is now taken into consideration when loading a PMI extension. (OA-45518)
Fixed a bug that caused entries in JSONLayout to be deleted when OneAgent log enrichment was enabled. (OA-46249)
After updating OneAgent to a version that supports a new Java version, the web UI no longer shows "Activation of deep monitoring was unsuccessful.". (OA-46478)
Extensions framework
Fixed an issue where a missing Content-Type header in a Prometheus metrics endpoint prevented it from being recognized correctly. (DAQ-9201)
Live Debugger
Improved sampling of breakpoint executions to also work based on the number of concurrent thread executions. (OA-47093)
Mainframe
Fixed log streaming for CICS and IMS logs. Log streaming was disabled for CICS and IMS due to a missing schema file in the zRemote deployment. (OA-49318)
zAgent log parsing is now able to parse log levels and timestamps from previously unparsable log entries. (OA-48336)
Fixed an issue where the `dt.host.zos.msu_hours` metric was missing in Grail, but the corresponding `builtin:host.zos.msu_hours` metric was present. (OA-48552)
The zRemote now allows distinct DB2 instances connecting to a zRemote via the same zDC. (OA-48606)
Node.js
Resolved an issue in which Node.js applications sometimes crashed when CpuSampling was enabled (when the OneAgent features "Capture background CPU method hotspot information" and/or "Capture method hotspot information in PurePaths" were enabled). The probability of a crash increased when the application was using worker threads. (OA-49632)
Python
Fixed an issue that could sometimes cause a monitored Python process to deadlock while a child process was forked if a OneAgent configuration update was received at that time. This also applied to non-obvious uses of forking such as `subprocess.run`. (OA-48114)
The OneAgent Python code module now uses locking around the fork handlers it registers with the Python interpreter. This prevents issues where the code module might leave additional threads running during forks happening in parallel on separate Python threads or might stop reporting data afterwards. Since parallel forking from Python is always unsafe, even without the code module involved, these situations should be rare. Despite the additional locking, no performance impact is expected from this change due to the Python GIL, which prevents parallelism. (OA-48354)
Update 46 (Build 1.317.46)
This is a cumulative update that contains all previously released updates for the 1.317 release.
The 8.317 GA release doesn't contain any user-facing resolved issues.
OneAgent for iOS
Digital Experience | RUM Mobile
Custom control label for action name
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.
The 8.317 GA release doesn't contain any user-facing resolved issues.
OneAgent for JavaScript
Digital Experience | RUM Web
Streamlined RUM browser compatibility code
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.
Fixed an issue where the return type of the fetch call would not be of type Promise, due to creating an additional Promise wrapper layer that would be created using Promise ponyfill instead of the native Promise constructor. (DEM-11280)
Fixed an issue causing User Interaction events not to be captured. (DEM-11224)
RUM
Fixed an issue occurring in applications using the Wistia media player with “Use Proxy API for XHRs” enabled, where the RUM JavaScript triggered a warning message in Wistia. (DEM-9721)