Dynatrace SaaS release notes version 1.243

Announcements

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 in-product assistance (Dynatrace chat)

Starting June 21, 2022, you’ll see a new look and feel while conversing with us using in-product assistance (aka “chat”) from your Dynatrace environment.

Transition to the new system will be automatic and seamless. No action is required on your part.

  • Any open chats will be converted to support cases automatically, allowing existing conversations to continue over email.
  • To open a new conversation, or to see an update to a current conversation or support case, select the chat icon in the upper-right corner of the Dynatrace web UI.

For more information, see:

New features and enhancements

User session exports

If the authentication is active for a user session export and you perform a configuration change, you now always need to re-enter the authentication credentials for security reasons. Also, only HTTPS endpoints are allowed for exporting user sessions.

Because of these changes, we switched the Settings API schema from builtin:elasticsearch.user-session-export-settings to a new one builtin:elasticsearch.user-session-export-settings-v2.

Container pages

Container pages now use the unified analysis framework. You can now extend the container pages with additional data. For more information on unified analysis card injection mechanism, see Extend built-in unified analysis pages.

Note also that starting with Dynatrace 1.247, Docker pages will be replaced by generic container pages.

Feel free to share feedback on the new container pages. Select Share your feedback in any of the container pages to go to the Dynatrace Community feedback channel.

System notifications

With the new System notifications page, admins can monitor and act on notifications related to environment health and licensing that have been communicated through Dynatrace yellow banner messages. If you have admin privileges, you can find the new page by going to System Notifications.

Features and advantages:

  • The table gathers in one place all of the environment health (for example, OneAgent disk space running low) and licensing (for example, DDU quota running low) notifications formerly displayed as banner messages.
  • Eliminating the banner messages frees up precious vertical space for displaying your data in Dynatrace.
  • You can filter the table by severity and message contents.
  • The blue dot indicates unread/new notifications. The same indicator is displayed in the menu entry.
  • You can select any or all notifications and clear them with one click.
  • Notifications automatically expire to prevent the table from growing indefinitely.

For more information, see System notifications.

Completed product idea

Thank you for continuously innovating with us. This enhancement addresses the following product idea from the Dynatrace Community:

Final deprecation of old user action naming rules

All web applications were converted to the new user action naming as previously announced in Easily configure user action names with enhanced user action naming rules.

Kubernetes monitoring

Event cards

Event cards in the root-cause analysis section of the problem page are now grouped by the dt.event.group_label instead of the EventType by default.

Kubernetes deployment page

The Kubernetes deployment page now uses Dynatrace Operator version 0.6.0.

Cloud Automation

The new Add SLO button lets you start the SLO wizard in the context of the entity you're browsing. The pages include Service details, Databases details, or Web applications details.

Service failure detection

Service failure detection settings are now available in the new Settings 2.0 format. To find them, go to Settings, expand Server-side service monitoring, and see the Failure detection section. You can also manage the service failure detection settings using the Settings API. These settings are also available to be used in security policies.

Settings security policies

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

Settings > Server-side service detection > Failure detection parameters Settings > Server-side service detection > Failure detection rules Settings > Log audit events

Dynatrace API

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

Resolved issues

General Availability (Build 1.243.113)

The 1.243 GA release contains 17 resolved issues.

Component
Resolved issues
14
1
1
1

Cluster

  • TSM metric keys that begin with a number are treated as invalid metric key inputs. (APM-371596)
  • Resolved an issue with settings for automatically applied tags that prevented editing persisted values if the rule count for a single tag was already over the currently defined rule limit. (APM-373253)
  • Unified analysis: conditions feature now works for actions with global scope. (APM-371561)
  • Improved error message when closing a problem without any message. (APM-369830)
  • Fixed an issue with ServiceNow notifications where the description field contains HTML escaped single-quote characters. (DAVIS-1600)
  • Solved an issue that lead to an error page when configuring automatically applied tags in the UI using Azure tags in the rule conditions. (APM-372202)
  • Fixed an issue where root cause analysis max delay sometimes was not respected if the value was more than one hour. (APM-370133)
  • Fixed a bug in which, when disabling frequent issue detection, some frequent events might enter stuck state without problems. (DAVIS-1510)
  • Fixed a problem with changing RUM applications of type BROWSER_EXTENSION_INJECTED in the RUM - Web application configuration API. (RUM-5776)
  • Support for custom and resolved problem timeframe types improved (histogram and conversion and bounce charts are successfully loaded). (APM-367913)
  • Fixed a problem related to anomaly detection of JavaScript errors for web applications. (APM-371452)
  • Regular expressions in settings for automatically applied tags are no longer validated for ECMAScript compatibility (to avoid rejecting previously accepted expressions as invalid). (APM-373249)
  • Preset service ID filter is no longer lost when navigating from dashboard service health tile to service list. (APM-371487)
  • When monitoring mode is switched (for example, from "Full stack" to "Infrastructure only") while monitoring is disabled, the host monitoring history chart now remains with "Unmonitored" and only switches to the new monitoring mode when monitoring is re-enabled. (APM-368032)

ActiveGate

  • The "storage-full" state is now monitored for AWS RDS. (APM-370189)

User Interface

  • Problem timeframe is no longer lost when navigating between the problem context page and the new host details page. (APM-368738)

User interface

  • The filter bar is no longer displayed when filter data is unavailable. (APM-371497)

Update 122 (Build 1.243.122)

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

Update 135 (Build 1.243.135)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.243 release.

Cluster

  • Fixed page crash in custom events for alerting caused by entity filter. (DAVIS-1735)

Update 146 (Build 1.243.146)

This cumulative update contains 1 resolved issue and all previously released updates for the 1.243 release.

Cluster

  • Fixed problem with AWS monitoring on Dynatrace SaaS. (APM-375757)

Related topics