Dynatrace Managed release notes version 1.280

  • Release notes

Rollout start: Nov 30, 2023

Announcements

Red Hat Enterprise Linux support

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

Mainframe Monitoring with DPS

Application Observability | Mainframe

Dynatrace Mainframe Monitoring provides automatic end-to-end application performance monitoring for transactions, regions, and apps deployed on IBM z/OS. It includes distributed tracing, metrics, topology, and code-level insight for 30+ supported technologies.

With the DPS capability for Mainframe Monitoring:

  • You get flexibility in licensing for incremental monitoring rollouts (for example, you can start small and expand coverage over time).
  • You only pay for the active monitoring period (for example, downtimes are not charged).
  • You get cost transparency and budget management in Account Management.

For more details, see Mainframe Monitoring.

Log source and storage configuration upgrade

Infrastructure Observability | Logs

With the release of Dynatrace version 1.285 (March 2024), Dynatrace will automatically convert your log source and log storage configurations to the latest version.

You can also upgrade to the new configuration by selecting Upgrade configuration. All of your current settings will be fully upgraded.

The upgraded configuration (see Log ingest rules) defined on the Custom log source configuration and Log sources and storage pages will give you:

  • Greater flexibility in defining log sources (for example, log path, log level, Kubernetes namespace, Kubernetes deployment)
  • Flexibility in defining log sources (using environment, host group, and host scopes)
  • Granularity in managing log source access rights
  • Use of the REST API for managing log sources
  • Ability to filter and mask log data at capture

Breaking changes

Settings REST API change: Host auto-injection

Breaking change Infrastructure Observability | Hosts

In the Dynatrace web UI, on the Host monitoring page for a selected host, the Auto-injection toggle has been moved from the Monitoring tab to the Advanced Settings tab and renamed to ProcessAgent injection.

  1. Go to Hosts and select the host that you want to configure.
  2. On the host details page, select More > Settings.
  3. On the Host settings page, select Host monitoring.
  4. Select the Advanced Settings tab.

If you're using any automation tools to manage this setting and you're leveraging the Dynatrace API (for example, Dynatrace Configuration as Code via Monaco or Terraform), the auto-injection settings schema ID was renamed.

Before:

builtin:host.monitoring/autoInjection

After:

builtin:host.monitoring.advanced/processAgentInjection

You need to pull the new settings schemas and update the value. The old settings schema will be ignored.

Unified attribute privacy settings

Application Observability | Distributed traces

Breaking change

The Span attributes, Resource attributes, and Span events settings have been merged into the Attribute capturing settings.

The separation by attribute origin is replaced to make the privacy configuration simpler and clearer. Existing settings are automatically migrated and in case of duplicate attribute keys, only the most restrictive masking option is migrated. We recommend you verify your environment configuration for attribute-masking.

  1. Go to Settings.
  2. Select Server-side service monitoring > Attribute capturing.
  3. On the Attribute capturing page, perform the following actions.
    • Select Allowed attributes to see the list of stored attributes key.
    • Select Attribute data masking to verify the masking configuration for a stored attribute.

To learn more about attribute settings, see Attributes.

New features and enhancements

Product news

Peer certificate information hidden in execution details of HTTP monitors

Digital Experience | Synthetic Monitoring

You can opt to hide sensitive information from being displayed in the execution details of HTTP monitors via the Do not store and display request and response bodies and header values in execution details setting. Enabling this setting now also hides peer certificate information in the execution details.

OS service monitoring events

Infrastructure Observability | Hosts

OS service monitoring events now also match the tags from the host entity where they originate.

New API to unblock auto-update

Infrastructure Observability | Hosts Infrastructure Observability | Deployment

Certain types of auto-update failures block further rollout of that version as a safety measure. A self-service API, /api/v1/oneagents/autoUpdateProblems, has been added to get and delete these problems to unblock an autoupdate rollout.

Kubernetes service ingress DNS names

Infrastructure Observability | Kubernetes

Kubernetes service ingress DNS names are now displayed on the Kubernetes service page. This is typically used in AWS load balancers.

Relevant field in Kubernetes API: service.status.loadBalancer.ingress.hostname

Attribute data privacy: Possibility to store all attributes by default

Application Observability | Distributed traces

You can now store all attributes by default.

Alerting profile property filter negation

Infrastructure Observability | Problems Infrastructure Observability | Alerting

Alerting profile property filters can now be negated, so an alert will not be triggered if an event of a problem matches the property filter.

Disk anomaly detection rule limit

Infrastructure Observability | Hosts

The maximum number of disk anomaly detection rules is now 1,000.

Custom-influenced Adaptive Traffic Management

Application Observability | Distributed tracing

You can set up traffic management rules for HTTP-based traffic. By customizing the contribution of specific transactions, you have better control of capturing within your environment's available trace volume and can immediately understand the capture rate of a specific service, (key) request, or result. To get started, see URL-based sampling. OneAgent version 1.281 is required to activate the rules.

Streamlined the Premium HA procedure - Replicate nodes across DCs

Platform | Deployment

We have simplified the Premium HA - Replicate nodes across DCs procedure. The Update Elasticsearch and Prepare cluster data for replication steps are no longer needed and have been removed.

Dynatrace API

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

Operating systems support

Support added

Added support for:

  • Red Hat Enterprise Linux 9.3
  • Rocky Linux 9.3
  • Oracle Linux 9.3

Current Dynatrace Managed operating systems support changes

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

Future Dynatrace Managed operating systems support changes

The following operating systems will no longer be supported starting 01 January 2026
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

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

Resolved issues

General Availability (Build 1.280.115)

The 1.280 GA release contains 13 resolved issues.

ComponentResolved issues
Application Security1
Cluster10
Synthetic monitoring2

Application Security

  • Third-party monitoring rules now only consider entities for evaluation when they are stable in the environment. New hosts, which cannot immediately be evaluated against the monitoring rules, are now initially set to “Do not monitor”. (RSA-12164)

Cluster

  • Retry-on-error executions of Synthetic browser monitors are no longer triggered during maintenance windows. (SYNTH-6635)
  • Corrected a Deployment page reference to point to the newly released Dynatrace Operator v0.14.1. (K8S-8042)
  • Events can now be ingested via REST API into the future even if the end timestamp is not set. The timeout parameter is then used to calculate how long the event stays open. (DAVIS-6977)
  • The Hosts table now displays a problem indicator for a host not only when the problem affects the host directly, but also when a related entity has an ongoing problem. (HOST-4230)
  • Users without write access to OneAgent update settings can no longer select the "Update now" button to trigger a OneAgent update. (The button was incorrectly enabled; selecting it without the required permission resulted in a 403 error page.). (DMX-6248)
  • Improved robustness of the classic problem list, which in rare cases could crash if you hover over the display ID of a problem with numerous details. (DAVIS-7086)
  • Stuck navigation for distributed traces and MDA has been fixed. You can access the global MDA and distributed traces by selecting the first item in the breadcrumbs. (TI-9716)
  • The metric selector no longer allows the `:filter` operator without arguments. (CLUSTER-10442)
  • Fixed long loading of data when switching tabs on Unified Analysis screens. (TI-9521)
  • Resolved an issue in which, starting with OneAgent version 1.273, the cluster was no longer able to process nodes with ESB and messaging attachments with priority for the Enterprise Service Bus service, but instead resorted to displaying a simple messaging service. (OA-24051)

Synthetic monitoring

  • Added API ownership to the generic ingest events API. (SYNTH-9071)
  • When the option not to store HTTP request sensitive data (i.e., request and response bodies and header values) is selected, peer certificate details are also hidden. (SYNTH-9132)

Update 229 (Build 1.280.229)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.280 release.

Cluster

  • Fixed a bug that caused high memory usage when reading availability data. (CLUSTER-11683)

Update 246 (Build 1.280.246)

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