Dynatrace SaaS release notes version 1.240

Product news

  • Level up your production resiliency with automated problem remediation

    Dynatrace Davis® AI detects problems, underlying root causes, business impact, and SLO impact across your full-stack production deployments. Dynatrace® Cloud Automation uses this information to trigger and execute remediation actions and observability-based validations. This blog post explains how Dynatrace Cloud Automation protects your production environments with automated remediation actions.

Announcements

Session Replay masking v1 end-of-life

Starting with Dynatrace version 1.240, Session Replay masking v1 is no longer supported. If your application uses the RUM JavaScript version 1.192 or earlier, update the RUM JavaScript to at least version 1.193 to enable masking v2. Otherwise, Session Replay will stop working.

Classic user sessions page end-of-life

We are deprecating the classic User sessions page soon and replacing it with a more powerful page for session segmentation. To stay tuned, keep an eye on our release notes.

New features and enhancements

Service-level objectives

Application Security

  • Keep security on your radar! The spinning radar screen on Application Security pages lets you know that Application Security is actively monitoring your environment. For details, see Manage third-party vulnerabilities.
  • On the details page of a vulnerability, the number of affected process groups for vulnerable functions in use now links to remediation tracking, where filtering is now also possible by the name of a vulnerable function in use.

Kubernetes monitoring

As announced over recent Dynatrace releases, the Early Adopter (EA) version of the Kubernetes events has been removed. The former opt-in for Kubernetes events analysis and alerting is now part of the General Availability (GA) Kubernetes events monitoring and is subject to DDU consumption.

Due to DDU consumption of the GA version, environments and Kubernetes endpoints using the EA version will no longer receive events, but you can manually reenable Kubernetes event monitoring. If you opted in to Kubernetes events integration for analysis and alerting in the EA release, you will continue to receive Kubernetes events with the GA release, but now subject to DDU consumption.

OS Services

The current OS service monitoring page is now renamed to Classic Windows service monitoring.

We introduced a new OS service monitoring that can now monitor the availability of both Windows and Linux services. For more information, see OS services monitoring.

Problem detection and alerting

  • Improved ordering of Anomaly Detection Settings menu items.
  • You can now manage configurations of maintenance windows via Settings API—use the builtin:alerting.maintenance-window schema.
  • Service key request names are no longer truncated to 50 characters in problem notifications.

Kubernetes events

With release 1.240, the Early Adopter (EA) version of the Kubernetes events has been removed. The former opt-in for Kubernetes events analysis and alerting, is now part of the General Available (GA) Kubernetes events monitoring and subject to DDU consumption.

Due to DDU consumption of the GA version, tenants and/or Kubernetes endpoints using the EA version will no longer receive events, but can manually re-enable Kubernetes event monitoring. Former opt-in to the Kubernetes events integration for analysis and alerting will continue to receive Kubernetes events, by being automatically moved to the new GA version.

Dashboards

You can now filter a dashboard by a custom dimension. For details, see Add dynamic filters to a Dynatrace dashboard.

Settings security policies

These previously existing settings are now available to be used in security policies:

  • Settings > Monitoring > OS services monitoring
  • Settings > Preferences > Network zones settings
  • Settings > Preferences > Data privacy > Session Replay
  • Settings > Web and mobile monitoring > Capturing > Resource capture for Session Replay
  • Settings > Web and mobile monitoring > Web applications > Enablement and cost control
  • Settings > Web and mobile monitoring > Mobile apps > Enablement and cost control
  • Settings > Web and mobile monitoring > Custom applications > Enablement and cost control

Dynatrace API

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

Resolved issues

General Availability (Build 1.240.130)

The 1.240 GA release contains 7 resolved issues.

Component
Resolved issues
5
2

Cluster

  • ServiceNow notifications now support the ProblemDetailsText placeholder value, which was missing before. (APM-362970)
  • Fixed filtering for alternative network zones on the "Deployment status > Network zones" edit page for a single network zone. (APM-362134)
  • JVM heap memory chart no longer aggregates non-heap memory pools on Process details page. (APM-362323)
  • Auto-update can now be turned on for a newly installed Cluster ActiveGate. (APM-366384)
  • The "Refine" button tooltip/overlay information now more accurately reflects the sampling rate after refinement. (RUM-4967)

User interface

  • Alerting profile text and description filter now reflect the correct logical OR between them. (APM-362911)
  • Fixed DateTime formatting in heatmap tooltip for timeframes that include more than one day. (APM-360542)

Update 131 (Build 1.240.131)

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

Update 134 (Build 1.240.134)

This cumulative update contains 2 resolved issues and all previously released updates for the 1.240 release.

Cluster

  • Fixed showing a warning message on the Kubernetes settings page, if Kubernetes events are enabled, while Log Monitoring v2 is disabled. (K8S-2150)
  • Fixed issue that prevented the creation of custom messaging services with queue entry point type set to some technology types. (APM-368026)

Related topics