Dynatrace SaaS release notes version 1.283

Rollout start: Jan 17, 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.

Breaking changes

Allow all attributes by default

Application Observability | Distributed traces

If you haven't changed the environment attribute persistence settings in the past 365 days, all OpenTelemetry attributes are stored by default and you can explicitly block unwanted ones in the Blocked attributes list.

For environments using the Allowed attributes list, we recommend migrating your settings to the Blocked attributes list for a better monitoring experience. If you prefer to have all attributes blocked by default and allow only specific ones, you can return to the Allowed attributes list, however, only one setting preference is possible.

To change the default OpenTelemetry attribute persistence, go to Settings > Server-side service monitoring > Attribute capturing > Preferences and select Allow all attributes (to use the Blocked attributes list) or Block all attributes (to use the Allowed attributes list). Note that these settings apply both to OpenTelemetry and OpenTracing.

SAML certificate migration

Your action is needed if you use SAML federation in your Dynatrace account.

The certificate used to authenticate Dynatrace with your Identity Provider (IdP) via SAML federation expires on February 28, 2024. After this date, the certificate will be invalid. As a result, your users will be unable to log into Dynatrace because your IdP won't be able to verify SAML requests from Dynatrace. We strongly recommend that you update your Dynatrace SAML certificate before February 28, 2024.

New features and enhancements

Apps automatically updated

Latest Dynatrace Dynatrace Hub

All Dynatrace Apps installed via Dynatrace Hub in your latest Dynatrace environment are now automatically updated to ensure fast security and bug fixes and to reduce your manual maintenance effort.

New DQL function

Platform | DQL

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

OneAgent Foundation & Discovery

Infrastructure Observability

Discovery mode is a new monitoring mode for OneAgent. It's lighter and less expensive, which makes it a good fit for very broad deployments. To use it, Foundation & Discovery must be added to your DPS rate card. Discovery mode is also supported for Application Security and is handled similarly to OneAgent running in Infrastructure Monitoring mode.

For more information, see:

DPS Usage Details DEMO dashboard

The Dynatrace Platform Subscription (DPS) offers a range of built-in billing metrics to help you understand and analyze the consumption of all Dynatrace (DPS) capabilities.

The new DPS Usage Details DEMO preset dashboard distributed with the Dashboards Classic app shows some of the available metrics and included dimensions.

To view the dashboard

  1. Go to Dashboards or Dashboards Classic (latest Dynatrace).
  2. In the Dashboards table, select the DPS Usage Details DEMO dashboard.

It's a preset dashboard, so you can't edit it, but it's easy to make a copy and edit the copy.

To copy the dashboard

  1. In the upper-right corner of the dashboard, select More (…) > Clone. The copy is displayed with "-cloned" appended to the dashboard name.

  2. In the upper-right corner of the dashboard, select Edit.

    Use your copy as a starting point for creating a customized overview of DPS consumption.

These DPS billing metrics are also available under Dynatrace classic licensing, in which case they provide insights into what your usage would have been like under the DPS model.

Access token authentication for the Business events API

Business Analytics

Access token authentication is now available for the /bizevents/ingest endpoint of the Business events API—use the https://{your-environment-id}.live.dynatrace.com/api/v2/bizevents/ingest endpoint URL in the previous Dynatrace. You require the Ingest bizevents token scope.

Updates to app names and icons

Latest Dynatrace Platform

We've updated app names and icons for easy identification.

  • Some apps now have the word "Classic" in the name (for example, Kubernetes Classic), which signals that you can use a corresponding new app that was developed specifically for the latest Dynatrace.
  • The word "New" appears on the icon of new apps. Some new apps might have corresponding "Classic" equivalents, for example, the new Kubernetes app Kubernetes (new).
  • Sample apps now have the word "Sample" in the name, for example, Multi-Monitor Updater Sample.

Option to choose format of cURL commands in API Explorer

Platform | API

In the API Explorer, you can now choose the format of cURL commands:

  • bash
  • PowerShell (Windows)
  • CMD (Windows)

Update of minimum ActiveGate version to 1.279

Infrastructure Observability | Kubernetes

With the recent changes in Kubernetes monitoring, the minimum ActiveGate version has been updated to 1.279 to make sure that the latest features are available.

Expose root_cause_entity_name in problem Grail document

Infrastructure Observability | Problems

The name of the root cause entity at the time where the root cause is found is now part of a problem document in Grail as root_cause_entity_name.

Kubernetes Node creation timestamp

Infrastructure Observability | Kubernetes

Added Kubernetes Node creation timestamp information to properties card and API.

AWS Lambda service data display

Infrastructure Observability | AWS

The Lambda service page now seamlessly displays data from both AWS Lambda (built-in) and the new AWS Lambda CloudWatch integration to allow for a smooth transition.

  • Old and new Lambda service data coming from AWS integration are displayed now on the Lambda service page (Lambda layer integration) together with OneAgent data when AWS CloudWatch integration is enabled and a Lambda service (built-in or the new one) is monitored.
  • On the Lambda service page, you can now find CloudWatch metrics and properties for the new Lambda service.
  • There is a link to a separate page for the new Lambda service if you want to investigate more metrics from CloudWatch.
  • Logs from OneAgent integration and AWS log forwarder are also linked to the new AWS Lambda service.
  • You can enable a predefined metric event configuration for a high Lambda error rate based on the new AWS Lambda service on the settings page for AWS integrations.

AWS Systems Manager Distributor

Infrastructure Observability | AWS Infrastructure Observability | OneAgent

With the new release of AWS Systems Manager Distributor, we've updated Deploy OneAgent using AWS Systems Manager Distributor with more options.

  • Two more operating system versions supported:

    • Ubuntu 22.04 for x86-64, ARM64 (AArch64)
    • Red Hat Enterprise Linux 9.x for x86-64

  • A new section about AWS CLI being required if you're using Parameter Store or Secrets Manager to store the PaaS token.

  • Updated DynatraceOneAgent distributor package installation process.

  • Updated installation parameters:

    • SSM_DYNATRACE_MONITORING_MODE parameter replaces deprecated SSM_DYNATRACE_INFRA_ONLY.

    • SSM_DYNATRACE_TOKEN_SECRET_NAME parameter was removed.

    • Three new parameters have been added:

      • SSM_DYNATRACE_TOKEN_SECRET_ID
      • SSM_DYNATRACE_TOKEN_PARAMETER_NAME
      • SSM_DYNATRACE_TOKEN_REGION

Dashboards and Notebooks updates

Latest Dynatrace Platform | Dashboards Platform | Notebooks

  • Single value tile color: In Dashboards and Notebooks, under Single value options, the Apply threshold color to setting (can be Value or Background) determines whether to display either the value or the tile background in the threshold color.

  • Thresholds: In Dashboards and Notebooks, we improved visualization-specific handling of threshold settings.

  • Data mapping: In Dashboards and Notebooks, the tile configuration pane now includes a dedicated Data mapping section where you can map the result to the visualization.

Dynatrace API

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

Resolved issues

General Availability (Build 1.283.56)

The 1.283 GA release contains 14 resolved issues.

Component
Resolved issues
1
3
10

ActiveGate

  • To avoid possible different data from OneAgent and ActiveGate, the CGI ImageID attribute (CGI_IMAGE_ID) is no longer written by default based on ActiveGate data. This can be re-activated via feature flag `com.compuware.persistContainerImageIdAttribute.feature`. (K8S-8528)

Application Security

  • Corrected aggregated values in single-vulnerability dashboards. There was an issue in the Code Analysis, Risk Analysis, Exposure Summary, and Environment Analysis sections of single-vulnerability dashboards that caused incorrect reporting for related and affected entities in the dashboard. This issue has been resolved and can be remediated by using the "Open with" button in the Third-Party Vulnerabilities App to create a new dashboard. Data from older dashboards should be considered incorrect. Users who have not used the "Open with" button until now are not affected. (SIA-2111)
  • Fixed behavior of status filter in generated dashboards to hide muted vulnerabilities when not selecting a status, or selecting open or resolved in the Third-Party Vulnerabilities App. (SIA-2034)
  • Fixed DQL query creation for blank templates on the "Third-party vulnerabilities" page. (SIA-2373)

Dynatrace Cluster

  • Fixed overflowing text on the problem details page, "Grail query" section, that occurred for some browsers (for example, Firefox) for problems with long DQL queries. (DAVIS-7427)
  • Fixed a bug that caused the web UI to be inaccessible due to thread exhaustion. (CLUSTER-11190)
  • It's possible to use opening and closing brackets inside matching operators as a part of a service or host property. (HOST-4737)
  • Fixed problem timing information on the problem details page (in the section below the problem header) for problems that began as frequent issues. (The correct timestamps are now used for when events were reported and when the problem changed from frequent to abnormal.). (DAVIS-7375)
  • Fixed a bug that caused entity-level state reports to be exported with an incorrect mute state in a particular case. (SIA-2207)
  • Default limits are now correctly applied in existing tenants for Kubernetes log, availability, and metric event reports. (DAVIS-7415)
  • Disabled editing of locations assigned to a Synthetic monitor and the "Install OneAgent" button for users to whom a read-only policy applies. (SYNTH-9526)
  • Fixed a bug in forwarding to Grail metrics extracted from bizevents. The issue applied only to the metric extraction stage in the bizevents pipeline, and only when more than one batch of bizevents for a given tenant was being ingested on a server concurrently. (PPX-1034)
  • The risk level of the affected entities count metric is now based on risk level in the context of the given entity. This makes the metric even more management zone aware. (RSA-12903)
  • Fixed an issue that caused certain apps that require permissions to be invisible to users bound to management zones. (K8S-8648)