New features and enhancements

More flexible SAML configuration

Our default settings work well for most SSO servers that utilize the SAML protocol. However, for legacy services, testing and development purposes, or to reduce the time-to-start with SSO, you need to perform an advanced adjustment. To support these cases, we now provide an advanced Single Sign-on settings page that enables the following features:

Signature algorithm – Used to encode/decode SAML requests and responses. Two algorithms are available: RSA-SHA256 and RSA-SHA1

Digest algorithm – Validates the integrity of messages. Two algorithms are available: SHA-256 and SHA-1

SAML response signature validation – Used for configuration of different security levels by validating the integrity of messages. Available options include: document, assertion, both, or none.

SAML response fields validation

Following your first sign-in to Dynatrace Managed, you should receive an email inviting you to activate your Dynatrace Community account as part of your subscription. The updated email alerts you to the fact that having a Community account enables you to:

Fix for “Upgrade now” button not available even if upgrade is ready to start (APM-193841)

Mission Control

Community SSO user could not be created when email address contained two “.” (dots) in the username, e.g. xxx.yyy.zzz@dynatrace.com (APM-192060)

Cluster Management Console

Group name should be displayed instead of group id in the breadcrumb at CMC (APM-192738)

Updating user repository to LDAP should be followed by disabling group import in SSO configuration (APM-184379)

Creating and updating internal users should be possible in Standard+SSO mode (APM-185790)

Misleading error message when user is created with password via REST API (APM-187260)

Login emails parsed incorrectly when user name part contains more than 1 dot or top-level domain part contains more that 4 characters. (APM-188204)

Login emails parsed incorrectly when user name part contains more than 1 dot or top-level domain part contains more that 4 characters. (APM-188268)

“Upgrade now” button was disappearing for the time of system check and appeared again after some time (APM-188792)

Dynatrace deployment health monitoring is not changed after upgrade when it is not defined explicitly in config.properties (we used to fallback to true if Dynatrace deployment health monitoring was not present in config file) (APM-188896)

Special characters are properly escaped in the link sent in “Reset password” email (APM-189345)

SAML logout messages handling fixed (APM-189375)

Email from SAML response is not being parsed correctly in CMC (APM-189539)

An error page after deleting the currently selected management zone (APM-184082)

Management zone filter is incorrectly autocompleted by the browser (APM-187946)

Problem counter does not take management zones into account on some pages (APM-188984)

“Pin to dashboard” panel is not preselected with the default dashboard (APM-190087)

Global timeframe dates are not always normalized in the URL (APM-189656)

Non-latin characters in the name are not properly displayed in the user menu (APM-192632)

Code level analytics

Service call IO times must be stored on database nodes (currently they are not, even if they are available). This fix will change the values of the displayed times in the PurePath view and in Response Time Hotspot/Analysis. (APM-187868)

Sometimes, instead of its name, an internal ID for request attributes is shown. (APM-188621)

In a chain [web request] -> [custom service] -> [outgoing web request], a request attribute captured on the client side is not propagated to the parent web request. (APM-190448)

A TLS exception is now displayed correctly instead of a pending request (APM-192039)

Fix caching issue of Kubernetes limit configuration (APM-194269)

Agent & SG

Oracle DB Insights: query about most time consuming statements was forced to not perform unnecessary merge. (APM-191332)

Cluster & Core

Switching the “Infrastructure Only” flag while a rolling cluster update is in progress may lead to config updates being missed by restarting servers. This may ultimately lead to missing switches of OneAgents to this mode. The race condition is now fixed (APM-183831)

Support for .NET core dumps with a different naming concept was missing. We added support for .NET core dumps as well. (APM-185913)

If you open the api explorer url without the index.jsp, there is an endless redirect between ‘/rest-api-doc/’ and ‘/rest-api-doc’. This was caused by a filter inconsistency regarding the path naming resolution, (APM-186323)

The filecache directory on the ActiveGate to host raw installer files resides in the “temp” directory which was cleared while the ActiveGate was running (removing the filecache directory along the way). The filecache did not try to recreate the directory (this was only done on startup). Now we always ensure that the directory exists. (APM-187549)

Other

Host page for PaaS hosts was presenting reclaimable memory series which should not be visible for such type of hosts. (APM-187445)

Performance improvements on process details page. (APM-186621)

On process page description of availability section was not properly adjusted to currently selected timeframe. (APM-190630)

On process further details page, some isolated points might have duplicates created at 9 seconds after the real point. (APM-187699)

HTTP request for synthetic module details for ActiveGates is now sent only if user has permission to do it (CONFIG_READ permission) (APM-188282)

HTTP request for PAAS tokens was always sent, even if user didn’t have permission to get them and it eventually ended in error page. Now this request is only sent if user has permission (has CONFIG_READ permission). In addition, possibility to add new tokens is allowed only if user has CONFIG_WRITE and DOWNLOAD_AGENT permission. (APM-188539)

USQL: Filtering by bounce true/false does not always work (APM-189548)

ActiveGate now discards beacons of unmonitored mobile/custom apps that did not yet receive the configuration update to turn off capturing (APM-186296)

Log monitoring

Log monitoring search pattern input field HTML escaping has been fixed – now it is again possible to type tags as a part of search query. Another issue fixed is displaying search pattern validation error on log event settings screen, which before the fix has not been shown. (APM-191614)