Dynatrace Managed release notes version 1.284

Rollout start: Feb 6, 2024

Breaking changes

Allow all attributes by default

Application Observability | Distributed traces

If you haven't changed the environment attribute persistence settings in the past 365 days, all OpenTelemetry attributes are stored by default and you can explicitly block unwanted ones in the Blocked attributes list.

For environments using the Allowed attributes list, we recommend migrating your settings to the Blocked attributes list for a better monitoring experience. If you prefer to have all attributes blocked by default and allow only specific ones, you can return to the Allowed attributes list, however, only one setting preference is possible.

To change the default OpenTelemetry attribute persistence, go to Settings > Server-side service monitoring > Attribute capturing > Preferences and select Allow all attributes (to use the Blocked attributes list) or Block all attributes (to use the Allowed attributes list). Note that these settings apply both to OpenTelemetry and OpenTracing.

Log Monitoring v1 end-of-life

Log Monitoring version 1 has reached end-of-life and is switched off with this release (Dynatrace Managed version 1.284). As a result, the following changes apply:

Log Viewer doesn't show any log data.
Log Monitoring API version 1 is disabled.
Log metrics (v1) are not captured. Configuration is read-only.
Log events (v1) are not triggered. Configuration is read-only.
Log ingest (v1) is disabled.
Log source configuration is persisted for future use.
Entity pages like Host, Process, and Process Group don't show any log files.
The attached NFS volume for storing logs is no longer used.

Learn more about how to upgrade to the Log Monitoring Classic version of Dynatrace log monitoring.

New features and enhancements

DPS Usage Details DEMO dashboard

The Dynatrace Platform Subscription (DPS) offers a range of built-in billing metrics to help you understand and analyze the consumption of all Dynatrace (DPS) capabilities.

The new DPS Usage Details DEMO preset dashboard distributed with the Dashboards Classic app shows some of the available metrics and included dimensions.

To view the dashboard

Go to Dashboards.
In the Dashboards table, select the DPS Usage Details DEMO dashboard.

It's a preset dashboard, so you can't edit it, but it's easy to make a copy and edit the copy.

To copy the dashboard

In the upper-right corner of the dashboard, select More (…) > Clone. The copy is displayed with "-cloned" appended to the dashboard name.
In the upper-right corner of the dashboard, select Edit.

Use your copy as a starting point for creating a customized overview of DPS consumption.

These DPS billing metrics are also available under Dynatrace classic licensing, in which case they provide insights into what your usage would have been like under the DPS model.

Option to choose format of cURL commands in API Explorer

Platform | API

In the API Explorer, you can now choose the format of cURL commands:

bash
PowerShell (Windows)
CMD (Windows)

AWS Lambda service data display

Infrastructure Observability | AWS

The Lambda service page now seamlessly displays data from both AWS Lambda (built-in) and the new AWS Lambda CloudWatch integration to allow for a smooth transition.

Old and new Lambda service data coming from AWS integration are displayed now on the Lambda service page (Lambda layer integration) together with OneAgent data when AWS CloudWatch integration is enabled and a Lambda service (built-in or the new one) is monitored.
On the Lambda service page, you can now find CloudWatch metrics and properties for the new Lambda service.
There is a link to a separate page for the new Lambda service if you want to investigate more metrics from CloudWatch.
Logs from OneAgent integration and AWS log forwarder are also linked to the new AWS Lambda service.
You can enable a predefined metric event configuration for a high Lambda error rate based on the new AWS Lambda service on the settings page for AWS integrations.

Ability to download full logs result set

Infrastructure Observability | Logs

Log Monitoring now offers the possibility to download the full result set for a selected time frame. The new log viewer option expands the web UI capability to list a maximum of 1,000 log records and enables log analysis on all relevant logs ingested into Dynatrace.

Kubernetes Node creation timestamp

Infrastructure Observability | Kubernetes

Added Kubernetes Node creation timestamp information to properties card and API.

Update of minimum ActiveGate version to 1.279

Infrastructure Observability | Kubernetes

With the recent changes in Kubernetes monitoring, the minimum ActiveGate version has been updated to 1.279 to make sure that the latest features are available.

OneAgent Foundation & Discovery

Infrastructure Observability

Discovery mode is a new monitoring mode for OneAgent. It's lighter and less expensive, which makes it a good fit for very broad deployments. To use it, Foundation & Discovery must be added to your DPS rate card. Discovery mode is also supported for Application Security and is handled similarly to OneAgent running in Infrastructure Monitoring mode.

For more information, see:

Improved handling of event and problem queries for multi–data center environments

Handling of event and problem queries for multi-datacenter environments has been improved, adding stability with regards to duplicate problem/event documents between different data centers and resolving issues such as a closed problem being erroneously displayed as open.

Limit changes in NGINX

NGINX limits have been changed as follows:

worker_rlimit_nofile: 102,400
worker_connections: 100,000

Dynatrace API

To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.284 and Dynatrace API changelog version 1.283.

Operating systems support

Update of Dynatrace Managed cluster is no longer possible at Red Hat Enterprise Linux 8.4, Oracle Linux 8.4, and Suse Linux Enterprise Server 12.4.

Support added

Upgrade to this release of Dynatrace Managed is supported for cluster nodes running on Red Hat Enterprise Linux 8.x or 9.x.

Elasticsearch is now running on Java Runtime Environment 17.0.8.

Current Dynatrace Managed operating systems support changes

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

Linux: SUSE Enterprise Linux 15.2
- x86-64
- Vendor announcement
- Last compatible version: 1.300

Past Dynatrace Managed operating systems support changes

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

Linux: Amazon Linux AMI 2018.x
- x86-64
- Vendor announcement
- Last compatible version: 1.290

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

Linux: Oracle Linux 8.9
- x86-64
- Vendor announcement
- Last compatible version: 1.292

Resolved issues

General Availability (Build 1.284.104)

The 1.284 GA release contains 2 resolved issues.

Cluster

Fixed an error in VMware credentials disablement that occurred after five failed connections. (HOST-5121)
Fixed a bug that caused high memory usage when reading availability data. (CLUSTER-11683)

Update 116 (Build 1.284.116)

This cumulative update contains 23 resolved issues and all previously released updates for the 1.284 release.

Component	Resolved issues
Cluster	19
Health	1
Synthetic Monitoring	3

Cluster

Improved handling of relations between entities in a problem context timeframe while building links in the UI. (PAPA-10371)
Fixed an issue where users without settings write permissions but relevant management zone permissions were getting an error when trying to bulk-close problems in the Problems list (web UI) on environments where settings write is not required to execute a problem close (default setup). This also fixes the problem close REST API handling to require settings write permissions only on environments where settings write is not required to execute a problem close. (DI-7609)
Fixed problem timing information on the problem details page (in the section below the problem header) for problems that began as frequent issues. (The correct timestamps are now used for when events were reported and when the problem changed from frequent to abnormal.). (DI-7375)
Fixed overflowing text on the problem details page, "Grail query" section, that occurred for some browsers (for example, Firefox) for problems with long DQL queries. (DI-7427)
Dashboards Classic: The host is now correctly highlighted in red in a honeycomb visualization on a dashboard when a related entity has an open problem. (HOST-4961)
To more accurately show what was used for analysis, the problem details metric chart for metric events on top now uses a 1-minute resolution if the problem timeframe is shorter than a day. (DI-7581)
It's possible to use opening and closing brackets inside matching operators as a part of a service or host property. (HOST-4737)
Resolved an issue that prevented access to a few global settings pages for users with conditional IAM policies assigned. (PS-13100)
A maintenance window can suppress events for alerting or problem creation. If a new event report came after the end of a previously matching maintenance window for its existing event, the end time of the suppressed event was set to the end timestamp of the new report. This fix changes this behavior to be the start timestamp of the new report, so that the suppressed event ends at the same time where the new non-suppressed event is opened and alerted. (DI-7631)
Users can no longer revert extracted services if they don't have tenant-wide settings write permissions. (TI-11033)
Fixed an error in VMware credentials disablement that occurred after five failed connections. (HOST-5121)
To prevent large response times and delayed problems caused by the problem manager spending too much time evaluating alerting profile regexes, the regexes in a new alerting profile event title/description filters are now restricted. (DI-7612)
Disabled editing of locations assigned to a Synthetic monitor and the "Install OneAgent" button for users to whom a read-only policy applies. (SYNTH-9526)
In Data Explorer, selecting the "Open with" button no longer displays an error message when no error has occurred. (PAPA-9897)
Fixed an issue that caused certain apps that require permissions to be invisible to users bound to management zones. (K8S-8648)
Default limits are now correctly applied in existing tenants for Kubernetes log, availability, and metric event reports. (DI-7415)
The risk level of the affected entities count metric is now based on risk level in the context of the given entity. This makes the metric even more management zone aware. (RSA-12903)
Fixed metric selector filter evaluating conditions independently and returning too much data. (GRAIL-25039)
In the Data Explorer, selecting the "Open with" button no longer displays an error message when no error has occurred. (EXA-9897)

Health

The calculation for Critical status for OneAgents has been fixed for overdue dates. (TI-10853)