- Release notes
- 6-min read
- Rollout start on Nov 5, 2026
This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.350. It contains:
- Feature updates: 11
- Breaking changes: 1
- Fixes and maintenance: 8
Feature updates
Application Observability | Distributed Tracing
Go static monitoring no longer requires ptrace on Linux
Go static monitoring no longer requires the Linux ptrace capability. This improvement is planned to replace the existing opt-in OneAgent feature Go improved static monitoring.
Digital Experience | Synthetic
Shadow DOM support
The recorder now supports shadow DOM interactions.
- Records clicks and keystrokes inside shadow roots
- Generates DOM locators that traverse shadow boundaries
- Provides multiple fallback locators for playback reliability
- Events correctly propagate across shadow boundaries during playback
- Player changes (new events handling API) can be reverted by setting the experimental property shouldUseLegacyEvents to true
Limitations
- Maximum 15 nested shadow boundaries
- Closed shadow roots record the host element only
- iframes inside shadow roots are not supported
Platform
Elasticsearch upgrade to version 8.19.18
The Elasticsearch nodes are upgraded to version 8.19.18 to provide bug and security fixes and leverage performance improvements introduced by this update. No manual user intervention or downtime is required; the upgrade occurs via rolling updates as part of normal version updates.
Platform
Automatic recovery after backup-and-restore migration
Key monitoring features, such as the Hosts page and filtering in Data Explorer, are now automatically restored after a backup-and-restore migration of a large environment. Recovery begins shortly after restore completion, with no manual steps or pre-migration configuration changes required. Previously, these features could remain unavailable for up to five days after a restore.
Platform
Visualize non-histogram metrics as histograms
You can now visualize non-histogram metrics as histograms in Data Explorer. Apply the new asHistogram(<buckets>) operator in advanced mode, where it appears in the suggestions, to see how values are distributed and assess the impact on specific cohorts.
This operator follows the existing histogram limitations, such as support for up to 12 buckets, and does not require the :histogram transformation. Your existing visualizations and metric selectors remain unchanged.
Platform
Improvements to metric dimension handling
We have improved handling of metric dimensions:
- Doubled the overall number of custom metric dimensions that an environment can store in the 30-day sliding window
Doubled the overall number of custom metric dimensions that an environment can store in the 30-day sliding window
- Optimized caching of metric dimension queries, achieving better query response time in certain cases
Optimized caching of metric dimension queries, achieving better query response time in certain cases
- Improved reported rejection reasons when custom metric ingestion is rejected due to too high ingest rate
Improved reported rejection reasons when custom metric ingestion is rejected due to too high ingest rate
- Improved visualization when queries are impacted by too many ingested metric dimensions
Improved visualization when queries are impacted by too many ingested metric dimensions
- You can now enable alerts with Settings > Metrics > Metric limits alerts to receive alerts when custom metrics reach ingest limits
You can now enable alerts with Settings > Metrics > Metric limits alerts to receive alerts when custom metrics reach ingest limits
Platform
OpenSSL updated to version 3.5.9
The Dynatrace Managed installer and NGINX now use OpenSSL 3.5.9.
Platform
Metric limits alerts now available in Settings
The Metric limits alerts setting is now available on Dynatrace Managed under Settings > Metrics > Metric limits alerts and via the Settings API under the new schema ID builtin:metric.limits-alerts.
Previously, these alerts were only configurable via the internal schema ID builtin:internal.metric.limits-alerts, which was not exposed in the UI.
Existing configurations are automatically migrated to the new schema ID; no manual action is required.
The setting allows you to configure alerts that fire when your environment's metric or dimension usage approaches the preset platform limits:
Number of dimension tuples for builtin metrics
% of the builtin-metrics dimension-tuple pool used in the last 30 days
Number of dimension tuples for custom metrics
% of the custom-metrics dimension-tuple pool used in the last 30 days
Number of custom metrics
% of the custom-metrics pool used
Number of dimension tuples in single metric
% of the per-metric dimension-tuple pool used, split by individual metric key
Notes
- Enabling alerts consumes metric event quota.
- All four rules are disabled by default.
Platform
Updated NGINX to version 1.30.5
We have updated NGINX to version 1.30.5.
Platform | OneAgent
OneAgent on a host API auto-update request validation improved
The OneAgent on a host API now validates the requested version more strictly on PUT /hosts/{id}/autoupdate and POST /hosts/{id}/autoupdate/validator.
The API accepts only versions higher than the installed one. Lower or equal versions return 400 Bad Request with a constraintViolations message that shows both versions.
Platform | Smartscape
Resource attributes available as part of the topology model, management zones, and auto-tagging rules
We now persist resource attributes as part of the topology model. This enables the following new features:
- You can view resource attributes as part of various entity screens in the properties section.
- You can define Monitored Entities rules and Auto-Tagging rules based on resource attributes. Resource attributes are available for hosts, processes, process groups, containers, and container groups. Defined rules can filter based on these resource attributes.
- You can configure custom resource attributes on monitored hosts and in Kubernetes Clusters via the dt_metadata.properties custom property file.
Breaking changes
Data Observability
Log record ordinal can now be set explicitly with the ordinal attribute
You can set log record ordinals explicitly with the ordinal attribute. Dynatrace reads the ordinal attribute from the log payload and uses it as the record ordinal.
Action plan:
- If you send ordinal as an integer (for example, "ordinal": 15): No action is needed. Your value now explicitly sets the record ordinal.
- If you send ordinal as a non-integer (for example, "ordinal": "15"): Your value is moved to overwrittenN.ordinal. If you read this field in pipeline processors, queries, dashboards, or alerts, either update those references or rename the field before ingest to avoid the overwrittenN indirection because the index is unpredictable at ingest time.
Fixes and maintenance
Resolved issues in this release
- Addressed a security vulnerability (CVE-2026-114820) by updating Java to versions 21.0.13+9 and 17.0.21+9 and by distrusting compromised eMudhra intermediate certificates. For details, see the security advisory . (PRISM-16311)
- Fixed an issue in which adding a new node to a Premium High Availability (PHA) cluster failed due to incorrect selection of a seed node. (PRISM-15770)
- Fixed CMC incorrectly reporting connectivity issues with embedded ActiveGate when dnsEntryPoint is set on nodes where ActiveGate has the dnsEntryPoint configuration option set to a host that doesn't appear in the node's communication URIs. (PRISM-15764)
- Fixed an issue that caused data points from calc: calculated metrics to be dropped every two hours. (PRISM-15432)
- Fixed incorrect results when :fold(<aggregation>) was followed by :rate and the aggregation was not among the metric's supported aggregations. The :rate operator calculated over a single timeslot instead of the whole timespan. (GRAIL-56104)
- Fixed a rendering bug where the visual viewport was positioned incorrectly during replay when the recorded session contained zoom or pan interactions. The replayed content would appear at the wrong offset due to the translation and page scroll not being correctly coordinated. (DEM-32904)
- Fixed an issue in EEC memory usage calculations that caused SNMP trap tasks to be counted multiple times. With a large number of tasks, EEC would close them long before reaching the RAM or CPU limit. (DAQ-28463)
- Fixed a layout bug where the tab strip in Session Replay was rendered wider than the replay area when a session contained multiple browser tabs. (DEM-32248)
Operating systems support
Future Dynatrace Managed operating systems support changes
- Linux: Amazon Linux 2x86-64Vendor announcement
- x86-64
- Vendor announcement
- Linux: SUSE Enterprise Linux 15.4x86-64Vendor announcement
- x86-64
- Vendor announcement
Past Dynatrace Managed operating systems support changes
- Linux: Oracle Linux 9.6x86-64Vendor announcement
- x86-64
- Vendor announcement
- Linux: Rocky Linux 9.6x86-64Vendor announcement
- x86-64
- Vendor announcement
- Linux: SUSE Enterprise Linux 15.3x86-64Vendor announcement
- x86-64
- Vendor announcement
- Linux: Red Hat Enterprise Linux 9.4, 9.7x86-64Vendor announcement
- x86-64
- Vendor announcement
- Linux: Ubuntu 16.04x86-64Vendor announcement
- x86-64
- Vendor announcement
Dynatrace API
To learn about changes to the Dynatrace API in this release, see:
- Dynatrace API changelog version 1.350
