Dynatrace Managed release notes version 1.290

  • Release notes

Rollout start: Apr 29, 2024

Announcements

Direct acquisition of AWS logs via AWS Data Firehose

Infrastructure Observability | Log Monitoring

Amazon Data Firehose integration (available in preview from Dynatrace Managed version 1.288) is now in General Availability. Firehose integration allows ingest of cloud logs directly, without additional infrastructure needed, and at higher throughput. It replaces the deprecated AWS log forwarder. Full production support starts from cluster version 1.288.

Breaking changes

Additional failure detection rules for Unified services

Application Observability | Distributed traces

We improved unified service failure detection rules for requests on endpoints and incoming services mesh proxies to evaluate

  • Span status failure
  • Server-side errors with HTTP status code 500-599
  • Any exception

New features and enhancements

Search/filtering API-ingested OpenTelemetry spans by span/resource attribute

Application Observability | Distributed traces

It is now possible to search/filter OpenTelemetry spans by span/resource attributes, in the Distributed traces app.

Distributed traces: Search/filtering API-ingested OpenTelemetry spans by span/resource attribute

This feature only applies to API-ingested OpenTelemetry spans. For OpenTelemetry spans automatically ingested via the OneAgent code module, filtering data is accomplished by creating request attributes.

Third-party default monitoring mode

Application Security | Vulnerabilities

Third-party Vulnerability Analytics has a configurable monitoring mode.

In Settings > Application Security > General settings > Third-party Vulnerability Analytics, you can now define the default monitoring mode for all processes, thus reducing complexity when defining monitoring rules.

For details, see Configure the global third-party vulnerability detection control.

Span kind endpoint detection

Application Observability | Services

Endpoint detection rules for unified services evaluate spans at the beginning of the trace.

Improved concurrent autoupdate handling

Infrastructure Observability | Hosts Infrastructure Observability | Deployment

The default limit for concurrent OneAgent autoupdates has been increased to 5, so the overall speed of the update process will increase. Higher limits will of course not be reduced. Also, potential problem handling has been changed to be more tolerant.

.NET support for RVA and RAP

Application Security | Vulnerabilities

.NET technology is now available for Runtime Vulnerability Analytics (code-level vulnerability detection) and Runtime Application Protection (attack protection).

Action required

With this release, preview customers for .NET technology (RVA and RAP) need to upgrade to OneAgent version 1.289 to reactivate this functionality. After that, no further configuration is necessary.

Switching to cloud-native full-stack deployment as default

Infrastructure Observability | Kubernetes

With the release of Dynatrace Operator version 1.0.0, the deployment page for Kubernetes Classic has been updated to default to cloud-native full-stack instead of the classic full-stack. Additionally, we have shifted to using Helm by default instead of manifests.

All previously available deployment options, including the manifest-based approach, remain accessible through our documentation. For more details on the differences between these deployment options, see How it works.

Dynatrace API

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

Operating systems support

Current Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 July 2024

Future Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 June 2026
The following operating systems will no longer be supported starting 01 July 2026
The following operating systems will no longer be supported starting 01 November 2026

Past Dynatrace Managed operating systems support changes

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

Resolved issues

General Availability (Build version_1.290.53)

The version_1.290 GA release contains 10 resolved issues.

ComponentResolved issues
Access Control1
Cluster9

Access Control

  • Fixed an issue for Managed clusters, where the policy update API call returned 403 but applied part of the changes. The described situation occurred only if the changed policy was bound to a deleted environment. (PS-22769)

Cluster

  • Muted requests are filtered out at the baseline configuration page. (TI-11899)
  • Resolved an error that occurred when using the browser back button while editing a filter attribute from the "Logs and events" page. (LOG-6688)
  • Fixed an issue where the service entity is visible on the service detail page, but the entity not found error is shown when changing to the new detail page. (TI-11968)
  • The `faultyVersion` property of the code module provided as a response for the "OneAgent on a host API" now takes into account two reasons a code module could be considered faulty: (1) the code module itself is marked as faulty or (2) the installer is marked as faulty. (DMX-7196)
  • Resolved an issue caused by new default settings in Firewalld in Red Hat Enterprise Linux 9.5 that blocked Dynatrace firewall rules. (MGD-1220)
  • Fixed an issue where the JavaScript code module for version 1.287 was not visible in the web UI although it was successfully downloaded. (PS-22736)
  • Resolved an issue causing cross-environment dashboards to not work after updating to Dynatrace Managed 1.288. (PAPA-17822)
  • Resolved issue causing the latest JavaScript code module to not appear on the Managed cluster. (RUM-19305)
  • Updated to Openssl 1.1.1w for Managed installers. (CLD-10758)

Update 155 (Build 1.290.155)

This cumulative update contains 30 resolved issues and all previously released updates for the 1.290 release.

Application Security

  • Fixed an issue where offline PGIs were still considered for monitoring and usage. (RSA-17167)

Cluster

  • Aggregation conversion to MDA has been improved for built-in and calculated service metrics. (TI-14032)
  • MonitoringState REST API now accepts 'from' and 'to' time selection. Only statuses for active entities in the selected timeframe are returned. (HOST-6406)
  • OneAgent diagnostics: when you generate a support archive, an inaccessible Health Control link is no longer displayed. (Link is displayed for internal access only). (TI-13932)
  • Fixed an issue in which, for premium high availability Managed clusters, after a data center failover, problems created during the failover period were not manually closeable. (DI-15087)
  • Fixed a case where two problems referred to each other as duplicates when one of the problems should have been the main one. (DI-15839)
  • Disk options settings are available in Discovery mode. (OA-34186)
  • Permissions checks for service extraction is fixed. (TI-14133)
  • Fixed empty event titles for informational Davis events that have an end time already at creation. (DI-15999)
  • Disabled assigning null locations to synthetic monitors. (SYNTH-12353)
  • Fixed an issue with the Log Events log detail viewer that occurred when a log had a `null` value in an attribute. (LOG-7172)
  • The throughput chart for calling/called services is fixed on the service overview page. (TI-14156)
  • To prevent rejected problem notification emails due to an oversized email body, problem notification email bodies are now truncated to approximately 4 million characters. (DI-15755)
  • Resolved an issue in which some events created by the root cause engine were referenced on a Grail problem record in `dt.davis.event_ids` but never stored as events themselves. (DI-16063)
  • Fixed an issue where PUT requests to save AWS monitoring configurations wiped non-required fields from the database (regions, enabled, runningOnDTInfrastructure, tagsToMonitor). (PCLOUDS-4764)
  • Fixed an issue in which, when requesting the details for a specific update job for a particular ActiveGate via the "GET an auto-update job" endpoint, a 404 error was returned if the job was older than 7 days, even though the maximum requested timeframe is for the last 31 days. (DMX-8235)
  • In the Format Table dialog, searching for columns is now caps agnostic. (LOG-7769)
  • Lowered the log verbosity to info. (APPOBS-1693)
  • Fixed issue with wrongly reported synthetic AG status, causing false alerts for private location outages. (SYNTH-11276)
  • Scrolling sensitivity in the single trace view of distributed traces has been improved. (TI-13794)
  • A client IP hint is no longer shown if no client IP is available. (TI-13978)
  • Fixed an issue that could result in a broken remote environment integration link in the service overview. (TI-13948)
  • Fixed broken remote environment integration links in service overview and trace view when "Latest Dynatrace" is enabled. (TI-13976)
  • The mobile OS version is now displayed correctly in sessions for hybrid apps. (RUM-21070)
  • . (TI-13832)
  • Fixed an issue where PGIs excluded from monitoring were generating usage. (RSA-17259)
  • On Davis events in Grail triggered by service anomaly detection, `endpoint.name` is now written as an array. (DI-16285)

Session Replay

  • Added a minimum height for the player container to avoid sessions being rendered too small. (SR-5941)
  • Some long split sessions were taking too long to load, so to improve the load time, we are skipping the operations that can be skipped until the time to start the replay. (SR-6017)

Synthetic Monitoring

  • No release notes are necessary because this bug was not visible to customers. (SYNTH-12235)

Update 161 (Build 1.290.161)

This is a cumulative update that contains all previously released updates for the 1.290 release.