Dynatrace Inc.

07/07/2025 | Press release | Archived content

Dynatrace Managed release notes version 1.318

  • Release notes
  • 10min
  • Rollout start on Jul 7, 2025

This page showcases new features, changes, and bug fixes in Dynatrace Managed version 1.318.

New features and enhancements

All | Distributed Traces

Improved attribute visualisation for individual trace view

All available horizontal screen space is now utilized by attributes until either the space is fully occupied or all attributes have been displayed.

Settings

Fixed incorrect placing of buttons when configuring Java service definitions

Fixed an issue where buttons were rendered off-screen when configuring Java service definitions on certain display sizes.

Platform

Improved Cassandra repair stability

When a Cassandra repair operation is executed manually for some reason, we now run it table by table in order to avoid causing too much overhead on the overall cluster.

Platform

Upgrade of Cassandra to version 4.1.9

As part of this release, the Cassandra nodes are upgraded to version 4.1.9 to provide bug and security fixes.

No manual user invention or downtime is necessary. The upgrade should happen via rolling updates as part of normal version updates.

Platform | OneAgent

Collect structured data from Windows event logs via new feature flag

OneAgent version 1.317+

Introduced a new feature flag on the Log Agent Feature Flag configurations page for enabling structured Event Data parsing. This flag is disabled by default.

When enabled, structured data is collected from Windows event logs-first from the User Data branch, or if unavailable, from the Event Data branch and its sub-branches. The collected data is transmitted as attributes alongside the recorded content.

Attribute names are derived from available information such as tag names, the value of the name field, or, when tag names are repeated and the name field is empty, a sequential number is appended to the tag name.

Sub-branches without values and tags labeled as Binary are omitted.

Digital Experience | Synthetic

Deprecation and replacement of Location and Node health status metrics

We have deprecated the following Location and Node health status metrics and replaced them with the new self-monitoring metrics.

Breaking changes

Infrastructure Observability | Hosts

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 Oracle home name.

Dynatrace API

To learn about changes to the Dynatrace API in this release, see:

Operating systems support

FutureDynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 December 2025

The following operating systems will no longer be supported starting 01 January 2026

PastDynatrace Managed operating systems support changes

The following operating systems are no longer supported since 01 November 2024

The following operating systems are no longer supported since 01 December 2024

The following operating systems are no longer supported since 01 February 2025

The following operating systems are no longer supported since 01 July 2025

Resolved issues

General Availability (Build 1.318.60)

The 1.318 GA release contains 14 resolved issues.

Application Security

  • Fixed an issue that prevented the correct event trigger type and user from being set. (RSA-24464)

Cluster

  • 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)
  • Fixed an issue where AWS Lambda Function service was showing incorrect properties when the service was linked to multiple entities. (DAQ-6572)
  • Resolved an issue with OneAgent messages not being processed cluster-wide due to a locking issue when many OneAgents of a single environment changed monitoring mode at the same time. (PS-34471)
  • Fixed a problem that caused certain service pages to show unnecessary tags. (DAQ-7630)
  • The OpenPipeline Events ingestion API no longer accepts empty HTTP request bodies. The JSON payload must have a positive length and contain at least one valid JSON object. If these conditions are not met, the server responds with a 400 status code. (PPX-5831)
  • Resolved an issue with `settings:objects:read` and `settings:objects:write` IAM permissions that caused policy conditions to be ignored when combined with the `environment:management-zone` condition. (PS-33948)
  • Fixed a rare case where problems could lose some root cause evidence information with further problem updates. (DI-20644)
  • Fixed an issue with configs not being updated when migrating from one tenant to another. New configs used to be provided by the server only if a newer revision was available. Now configs are provided when revisions differ. (OA-34023)
  • Declarative grouping, VMware monitoring, and Process Availability no longer incorrectly accept double parentheses in the condition field. (OA-48636)
  • Prior to version 1.318, the tenant URL was not correctly communicated from the cluster to OneAgents and environment ActiveGates in PrivateLink-enabled environments for Live Debugger. Starting with version 1.318, the cluster correctly reports the tenant URL to OneAgents and environment AGs for Live Debugger in PrivateLink-enabled environments. (MGD-5311)
  • Removed timeframe from Honeycomb visualization in classic dashboards, now aligning with all non-timeseries-based visualizations that don't have a timeframe. (PAPA-25301)
  • Fixed an issue with Davis event reports not considering the `dt.query` field. (DI-20795)

Session Replay

  • Resolved an issue in which sessions with long views under some conditions stopped working every 5 minutes. (DEM-10704)
Dynatrace Inc. published this content on July 07, 2025, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on July 21, 2025 at 10:39 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at support@pubt.io