Dynatrace SaaS release notes version 1.274

Rollout start: Aug 29, 2023

What is new in Dynatrace

Want to ask questions or give feedback? Head over to What's New in Dynatrace in the Dynatrace Community.

Product news

Unified services: Easily keep track of your pipelines
We’ve all been there. An important fix is waiting to be delivered, and a manager asks you why it’s taking so long and says that the pipeline was much faster a few months ago. Although you disagree with the assessment, you can’t dispute it because you don’t have the data to show that the pipeline […]

Breaking changes

Fixed data types of Grail fields for DAVIS_EVENT and DAVIS_PROBLEM events

Breaking change

We have fixed data types of Grail fields for DAVIS_EVENT and DAVIS_PROBLEM events.

This is a breaking change for string-specific DQL functions (for example, == "…", contains, startsWith). Use toString(...) to fix the behavior.

Newly written records use these types:

Field

Data type before fix

Data type after fix

event.start

string

timestamp

event.end

string

timestamp

resolved_problem_duration

string (in milliseconds)

duration (in nanoseconds)

dt.davis.timeout

string

long

dt.davis.is_frequent_event

string

boolean

maintenance.is_under_maintenance

string

boolean

dt.davis.analysis_time_budget

string

long

dt.davis.analysis_trigger_delay

string

long

dt.davis.is_frequent_issue_detection_allowed

string

boolean

dt.davis.is_merging_allowed

string

boolean

dt.davis.is_problem_suppressed

string

boolean

dt.davis.is_entity_remapping_allowed

string

boolean

If you use DQL functions that only work with string data types, you need to do a toString(...) before that so that it still works.

For example, change this:

| filter dt.davis.is_frequent_event == "true"

to this:

| filter toString(dt.davis.is_frequent_event) == "true"

There are also other options, but adding toString(...) to a changed field name will fix every query.

Announcements

Thresholds API sunset

With the release of Dynatrace version 1.275, we will turn off the Thresholds API. Any requests to these endpoints will stop working. Migrate your automations to the Settings API instead. For more information, see the migration guide.

New features and enhancements

New matcher attribute in log storage configuration

Infrastructure Observability | Logs

Now you can use Log record level attribute in log storage configuration:

New DQL keyword

Platform | DQL

Now you can use the in keyword in your DQL queries as a comparison operator.

New DQL functions

Platform | DQL

Now you can include the following functions in your DQL queries:

arrayConcat
The arrayConcat function concatenates multiple arrays into a single array.

View the origin of vulnerable libraries

Application Security | Vulnerabilities

You can now view the origin of a vulnerable Java software component on the remediation tracking for process groups and processes affected by a vulnerability.

For example:

load-origins-pg

For information on how to navigate there, see Remediation tracking.

Unified services for trace ingest

Application Observability | Services

We enhanced support for OpenTelemetry and cloud-native monitoring with a new service type, Unified service. Unified services are based on OpenTelemetry spans ingested via the ingestion APIs and provide

Automatic baselining and Davis® AI integration
Automatic endpoint detection
New service metrics, such as response time, throughput, and failure rate
Advanced horizontal topology detection
Support for custom application metrics and application logs
Agentless support for Istio service meshes
Opt-in endpoint monitoring with new metrics

To get started, see Unified services.

Share your feedback in the Feedback channel for the enhancements to OpenTelemetry trace-ingest (Unified Services) released w/ v1.274 (SaaS & Managed) in the Dynatrace Community!

Unified services for trace ingest

Detection attributes highlights

Application Observability | ServicesApplication Observability | Databases

Attributes used for detection are marked with an asterisk ✱ on the service and database, under Properties and tags.

Davis problems refresh rate

Platform | Davis AI

We now refresh Davis events and problems in Grail every 6 hours for as long as they're not closed. This guarantees query results for problems/event snapshots by querying 6-hour timeframes.

Unified analysis screens for Kubernetes nodes

Infrastructure Observability | Kubernetes

You can now access new unified analysis list and detail screens for Kubernetes nodes.

Advanced Kubernetes label filtering

Infrastructure Observability | Kubernetes

You can now apply multiple values simultaneously in the Kubernetes label filter.

Multi Label filtering

Detailed OneAgent status in unified analysis host page

Infrastructure Observability | Hosts

The Properties and tags section of the unified analysis host page features a OneAgent status:

The status can be either active or inactive, along with a reason for the status.
Detailed status information is available for up to 24 hours. Beyond that, the status will default to inactive.
An unknown status will be displayed if data is unavailable.
The status may be delayed by up to 5 minutes.

OneAgent status

RKE2 technology grouping

Infrastructure Observability | Hosts

We've added RKE2 technology per PGI. RKE2 Agents and RKE2 Servers are now grouped into separate process groups.

High System Load events trigger process instance snapshots

Infrastructure Observability | Hosts

High System Load events will now automatically trigger process instance snapshots.

Dynatrace API

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