Dynatrace SaaS release notes version 1.284

Rollout start: Jan 30, 2024

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

  • Unlock seamless access: The power of flexible identity federation

    Identity federation is a mechanism that allows users to access multiple systems or applications using a single set of credentials. It works by establishing a trusted connection between your user identity provider (which authenticates users) and a service provider (which grants access to secure services), thus facilitating single sign-on (SSO).

New features and enhancements

New DQL command

Platform | DQL

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

  • joinNested
    Adds matching results from the sub-query as an array of nested records.

New aggregation function available to use with DQL timeseries command

Platform | DQL

Now you can use the following aggregation function with the timeseriescommand:

Updated DQL command

Platform | DQL

  • timeseries
    We added the nonempty parameter to the timeseries command.
  • timeseries
    Now you can use the count aggregation function with the timeseriescommand.

Launch of code-level vulnerabilities on Grail

Application Security | Vulnerabilities

Security events on Grail now include code-level vulnerabilities. State reports and change events are generated for both third-party and code-level vulnerabilities.

Dashboards and Notebooks updates

Latest Dynatrace Platform | Dashboards Platform | Notebooks

  • Thresholds: In Dashboards and Notebooks, the Thresholds value unit is now synchronized with the Units and formats settings. Whenever there is a unit override, the threshold values also use that new unit as the base unit.

Dynatrace API

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

Resolved issues

General Availability (Build 1.284.70)

The 1.284 GA release contains 11 resolved issues (including 1 vulnerability resolution).

Component
Resolved issues

ActiveGate

  • On the OneAgent download page, "Discovery" monitoring mode can now be selected only if "Foundation and Discovery" mode is licensed. (DMX-6708)

Dynatrace Cluster

  • 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. (DAVIS-7631)
  • 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 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. (DAVIS-7612)
  • 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. (DAVIS-7609)
  • 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. (DAVIS-7581)
  • Fixed sporadic forecast analyzer run failures that failed with "Access to Grail is not possible. Please retry in a few minutes" when Grail should be reachable. (DAVIS-7677)
  • The calculation for Critical status for OneAgents has been fixed for overdue dates. (TI-10853)
  • The `vulnerability.cvss.score` in Grail data is now just the version number. For example, now 3.1 instead of the former CVSS v3.1 format containing a prefix. (SIA-2375)

Synthetic Monitoring

  • Fixed an issue in which a Synthetic Kubernetes location that was deployed on a cluster with limited resources and heavily utilized could use more memory than allowed and be OOM-killed by the Kubernetes cluster. (SYNTH-9660)

Workflows

  • Vulnerability: Improved security of workflow engine by hardening the execution environment. (DTSEC-9905)