Dynatrace Managed release notes version 1.176

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

SAML response fields validation

Increase your productivity by activating your Dynatrace Community account

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:

Additionally, we’ve updated the activation endpoint to sso.internal.dynatrace.com.

Other changes

  • Straightforward scaling down of clusters with a single click. No more need to disable OneAgent traffic beforehand.
  • Backup process was improved to not utilize all available host network and CPU resources. Network bandwidth utilization is limited to 30MB/s which is appropriate for 1 Gbps connections.
  • Cluster node's firewall now explicitly allows responses to any outgoing connections so, for example, the export of user session data is possible
  • Cluster upgrade notification emails now contain a link to the release notes page so you can quickly understand recent and upcoming changes. See also product idea at  Dynatrace Community forum.

Resolved issues

Critical issues

Other

  • User session REST export sends data with invalid format (APM-187767)
    Impact: Data sent to REST endpoints was provided in an invalid format, thus parsing of this data likely failed and thus some data was not received correctly by the downstream system.
    Cause: An internal rework of the functionality caused an unintended change in export format.
    Solution: A hotfix was implemented and deployed on all affected systems to mitigate the problem as soon as possible.

Other issues

Installer and Upgrade

  • Improvements to stopping of Managed processes during upgrades (APM-184641)
  • "Cannot set 'readahead 512' " message is not displayed anymore after installation (APM-188056)
  • Installation of new node in cluster can fail with generic error if the node doesn't fulfill Managed requirements (APM-188772)
  • Upgrade of cluster fails when custom.settings file is located under non-default path (APM-189075)
  • Fixes to restoring of Elasticsearch data performed by restore-elasticsearch-data.sh script (APM-190132)
  • New node cannot be installed when cluster-nodes.conf has invalid access permissions set (APM-190555)
  • Fix for "java.lang.OutOfMemoryError: Java heap space" error in Nodekeeper (APM-191605)
  • Fix for log spam in nodekeeper.log file (APM-194710)

Cluster Management Console

  • 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)
  • Make user identifier case insensitive for OpenID connect integration (APM-190201)
  • License consumption was not updated after conversion from offline license to full online license (APM-195155)

Core UI

  • "logoutInactiveUsersEnabled" setting produces timeouts despite user interactions (APM-185039)
  • 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)
  • Request attribute method argument capturing now disallows instrumentation of java core classes. (APM-190493)
  • Exception summary view sometimes showed too many asterisks, making the message unreadable. (APM-187970)

Session Replay

  • Timeline legend not shown for load events when all contain session errors (APM-184845)
  • Enabling Session Replay will check for ASP traffic in order to upgrade to Session State V4 (APM-187134)
  • An issue on playback of mouse movements prevents hover styles to be displayed (APM-188274)
  • Session Replay enabling switch toggle does not accurately show the current state (APM-191706)
  • Mouse pointer disappears when hovering events on the timeline (APM-192677)

Synthetic monitoring

  • Synthetic HTTP monitors problems lacking information about failing request (APM-189242)

Cluster

  • In case of non synchronised time on Active gate and cluster no data for HTTP Monitor with script (APM-186303)
  • For multi request HTTP check pattern validation not working (APM-189561)
  • Fix Azure dashboard UI glitch - list of functions might not have been refreshed. (APM-188999)
  • Fix UI problem with moving some charts to the left using mouse pointer. (APM-190099)
  • Fixed an issue when filtering by tags. (APM-192162)
  • Symbolication: fixed some symbol names were displayed as filenames (APM-190641)
  • Mobile App: fixed no more closed problems visible in mobile app when AI 2 was used (APM-192856)

Autonomous Cloud

  • Changed Kubernetes CPU metrics to be displayed as mCores (APM-190540)
  • Fixed update of Cloud Foundry Foundation and Kubernetes Cluster entity names when updating via Dynatrace Config API (APM-189734)
  • 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)
  • Network overview - wrong sorting of entities (case-sensitive problem) (APM-186647)
  • Fixed processes list display issues - cropped view on narrows screens (like tablet) (APM-187476)
  • 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)
  • Change wrong Elastic Compute Service label to Elastic Compute Cloud on hosts list. (APM-189708)
  • 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)

RUM

  • Disabling anomaly detection for mobile apps was fixed. (APM-191374)

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)

.NET

  • Hide empty .NET garbage collection charts on .NET metrics tab in process details. (ONE-27595)

Totals

72 total resolved issues

Component Resolved issues
Installer and Upgrade 8
Cluster Management Console 1
Mission Control 1
Cluster Management Console 13
Core UI 7
Code level analytics 5
Session Replay 5
Synthetic monitoring 1
Cluster 7
Autonomous Cloud 4
Agent & SG 1
Cluster & Core 4
Other 12
RUM 1
Log monitoring 1
.NET 1