Dynatrace SaaS release notes version 1.279

Rollout start: Nov 7, 2023

Want to ask questions or give feedback? Head over to Dynatrace Community.

Announcements

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:

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:

New features and enhancements

OS service monitoring events

Infrastructure Observability | Hosts

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

Log metrics are stored in Grail

Infrastructure Observability | Logs

Log metrics are now stored in Grail and can be accessed and queried with Dynatrace Query Language.

Disk anomaly detection rule limit

Infrastructure Observability | Hosts

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

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

New API to unblock autoupdate

Infrastructure Observability | Hosts Infrastructure Observability | Deployment

Certain types of autoupdate 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.

New DQL commands and functions pages

Platform | DQL

We've split the DQL commands and functions pages into subpages for each category for easier browsing. You can also view all the commands and functions on the overview pages.

Pinning for JavaScript source maps

Digital Experience | RUM Web

You can now pin JavaScript source map files on Settings > Web and mobile monitoring > Source maps and symbol files.

Attribute capturing: Possibility to store all attributes by default

Application Observability | Distributed traces

You can now store all attributes by default.

Get user groups from Microsoft Entra ID with Azure for Workflows

Automations | Ecosystem

The new Dynatrace Azure for Workflows app enables you to programmatically get user group data from Microsoft Entra ID (formerly Azure Active Directory) for use in Dynatrace, for example, to define teams for entity ownership. Once installed and configured, Azure for Workflows provides the get_groups action in Workflows for retrieving Entra ID data.

New Ownership action to import teams for entity ownership

Automations | Ownership

The import_teams action from the Ownership app is available within Workflows for setting up ownership teams from:

When importing Entra ID data, a group's Object Id from Entra ID is automatically set as the ownership team's Team identifier in Dynatrace, while a human-readable name from Entra ID is set as the Team name.

Support for annotations to link ownership teams to Kubernetes objects

Automations | Ownership

In addition to Kubernetes labels, we now support Kubernetes annotations to link ownership teams with Kubernetes objects. You can use either annotations or labels to assign ownership teams to Kubernetes objects. The sample code below shows an annotation for ownership at the Deployment level.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: demo
  annotations:
    dt.owner: my-team # Ownership defined for the Deployment

Adjusted memory calculation for per memory-gibibyte-hour DPS capabilities

Cross Solutions | Monitoring Consumption

The minimum memory size is 4 GiB for the GiB-hour consumption calculation of physical and virtual hosts for the following DPS capabilities:

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.

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.

Dynatrace API

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

Resolved issues