Dynatrace SaaS release notes version 1.290

Rollout start: Apr 22, 2024

Dynatrace SaaS release notes version 1.290

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

Product news

  • Stream logs to Dynatrace with Amazon Data Firehose to boost your cloud-native journey

    Your cloud logs can provide the root cause of high-impact issues or reveal the details of security incidents. Now, you can integrate an Amazon Data Firehose high-frequency data stream directly with the high-performant Dynatrace Grail™ analytics engine and use the Dynatrace AI-powered observability platform to mitigate issues with minimal impact to your business.

Announcements

Direct acquisition of AWS logs via AWS Data Firehose

Infrastructure Observability | Log Monitoring

Amazon Data Firehose integration 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.

New features and enhancements

Duration formatting starting from the largest unit

Platform | Dashboards

The duration data type is formatted to start with the largest unit, rounded to the second digit. For example, 1123123 ns is formatted as 1.12 ms.

You can use the Units and formats settings to adapt the formatting.

Dashboard variables can refer to other dashboard variables

Platform | Dashboards

Variables in dashboards can be defined to depend on other variables.

  • The value of a variable is recalculated if its definition refers to another variable and the other variable's value changes.

    For example, if the value of variable A changes, the value of any variable whose definition refers to variable A is recalculated.

  • Loops are not allowed.

    For example, if the value of variable A depends on the value of variable B, the value of variable B can't depend on the value of variable A.

For details, see Add a variable to a dashboard.

New DQL functions

Platform | DQL

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

Outer join support for the join command

You can now use outer join with the join command. The outer join returns matched and unmatched records from either or both sides.

.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.

Launch of Vulnerabilities

Application Security | Vulnerabilities

Latest Dynatrace

Vulnerabilities Vulnerabilities enables you to pursue a quick and easy analysis of third-party, code-level, and runtime vulnerabilities affecting your live environments, while providing the valuable insights and context needed to fix them. You can monitor, manage, and prioritize vulnerabilities, target affected entities, address and optimize remediation, continue your investigation in another app, and share results of your findings.

For more information and details, see Vulnerabilities.

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.

Query self-monitoring metrics with DQL

Platform | Grail

Classic self-monitoring metrics are now available on Grail via DQL with the dt.sfm prefix.

For example, dsfm:server.metrics.metric_dimensions_usage can now be queried in Grail using the following DQL:

timeseries usage = avg(dt.sfm.server.metrics.metric_dimensions_usage),
by:{metric_key}
| filter arrayAvg(usage) >= 80

Platform | Grail

Application Observability | Services

Service metrics are now available on Grail via DQL with the dt.service.request prefix. For the list of metrics, see Built-in metrics on Grail.

In most cases, a single Grail metric provides support for multiple Classic metrics. To obtain values of individual metrics, use metric dimensions.

For examples, see Service migration guide.

Dynatrace API

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

Dynatrace SaaS resolved issues

General Availability (Build 1.290.26)

The 1.290 GA release contains 12 resolved issues (including 1 vulnerability resolution).

Component
Resolved issues

ActiveGate

  • Vulnerability: Updated the AWS-java-SDK to the latest version, which does not use the ion-java dependency. (PCLOUDS-3987)

Dynatrace Cluster

  • Fixed finalization of Grail activation through no data loss migration. (LOG-6822)
  • Muted requests are filtered out at the baseline configuration page. (TI-11899)
  • When the user was granted the granular IAM policy allowing access to the update settings for ActiveGates without global configuration read permission, the setting button was missing. This has been fixed, and the button is now visible. (DMX-7282)
  • URL-based sampling works now independent from Adaptive Traffic Management enablement. (TI-11969)
  • 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)
  • Queries on live sessions now correctly show the actions of the associated user. (GRAIL-26642)
  • Fixed an issue where JS agent 1.287 is not visible in the UI although was successfully downloaded. (PS-22736)
  • Fixed a bug in the `lastIndexOf` function that, in certain cases, caused a query to fail when the substring was not found in the given expression. (GRAIL-27249)
  • Fixed the problem where the dimension statistics weren't filled immediately after a server restart. (GRAIL-26294)
  • Fixed a problem in the calendar widget (used in the service comparison page) that led to an error page for specific inputs. (TI-11916)

Synthetic Monitoring

  • We fixed the incorrect generation of the YAML deployment template for Managed offline clusters. The YAML was generated without the VUC workers section and contained improper image versions. Apart from fixing the problem with YAML generation, we added a possibility to provide custom repo, ActiveGate, and synthetic build version tag as request parameters when generating the template via REST API. (SYNTH-10729)

Update 27 (Build 1.290.27)

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

Update 32 (Build 1.290.32)

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

Update 39 (Build 1.290.39)

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

Update 40 (Build 1.290.40)

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

Update 46 (Build 1.290.46)

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