Dynatrace Managed release notes version 1.174

New features and enhancements

Other improvements

  • Security vulnerability fixes and bug fixes are delivered with the update of JRE to version 8u212
  • To improve security quality by limiting information disclosure, cluster nodes no longer reveal Server header

Resolved issues

Critical issues

Installer and Upgrade

  • Rolling upgrade might get stuck if one of nodes fails to upgrade successfully (APM-187662)
    Impact: Cluster event spam and all cluster operations were on hold
    Cause: Improper handling of retrying to upgrade following nodes
    Solution: Cluster node restart
  • Cluster was not upgraded successfully due to an issue in Elasticsearch indices migration (APM-187830)
    Impact: Cluster event spam and all cluster operations were on hold
    Cause: Improper handling of a proxy that was defined in Linux environment variables under 'HTTP_PROXY' or 'http_proxy'
    Solution: New installers in version 1.172.119 and 1.174.42

Other issues

Installer and Upgrade

  • Installer now checks if self-monitoring OneAgent path (SELFMON_AGENT_INSTALL_PATH, SELFMON_AGENT_HOME_PATH) don't point to any of other Managed paths (APM-181147)
  • Upgrade of a managed node could have been delayed due to an issue in communication over the proxy (APM-183663)
  • Restore from backup fails with an error message: `/opt/dynatrace-managed/config/cluster-nodes.conf: No such file or directory` (APM-184124)
  • Upgrade with custom settings fails if nothing was customized (APM-184256)
  • Restore from backup did not extract all the Metric storage files causing failures in restore procedure (APM-184827)
  • Custom settings should be applied to current version of config files instead of the default one (APM-184936)
  • Restore from backup does not check that other installation of Dynatrace Managed already exist on the node (APM-184978)
  • If joining a new node fails cluster should not be left in inconsistent state (APM-185363)
  • Joining a new node fails if other nodes are offline (APM-185482)
  • Joining a new node fails if there are other nodes with the same IP (APM-185485)
  • Cluster node with OneAgent traffic disabled should be a valid seed node (APM-185853)
  • Cluster upgrade failed due to lack of read permissions to `/var/log/dynatrace/installer-status.log` (APM-187938)
  • Joining a node fails when Cassandra service is starting longer than expected (APM-188280)
  • Joining third node to Managed cluster fails immediately during installation (APM-188772)
  • Upgrade of cluster fails when custom.settings file is located under non-default path (APM-189075)
  • New node cannot be installed when cluster-nodes.conf has invalid access permissions set (APM-190555)

Cluster Management Console

  • LDAP group names validation was improved so it supports names with only non-latin characters (APM-179858)
  • Cannot add a new user account when an e-mail's username part contains more than 1 dot or top-level domain part contains more that 4 characters (APM-188204)
  • Cannot add a new user account when e-mail's username part contains '-' (APM-188268)
  • Dynatrace deployment health monitoring setting is reverted after upgrade (APM-188896)
  • Logout of Managed environment using SAML results in SSO Error (APM-189375)
  • Cluster cannot remove high number of Elasticsearch backup snapshots (APM-182530)
  • Event stream shows that adding a cluster node failed with empty error message (APM-184144)
  • Cluster with a trial license should not enforce to allow Dynatrace Support employees remotely access monitoring settings (APM-184930)
  • Intermittent logouts of active managed users caused by failures in Nginx upstream forwarding (APM-188648)

Mission Control

  • Could not process billings for clusters that have synthetic monitors with atypical unicode characters in their name (APM-185598)

Code level analytics

  • Cannot create web request naming rule based on existence of confidential request attribute (APM-183100)
  • Two queues from same vendor and with the same display name are wrongly created as separate queues (APM-183521)
  • Default limit for supported number of different message queues is too low (APM-183615)
  • Request Attribute Argument Capturing UI: The wrong element was selected when reopening a data source. (APM-185567)
  • Better detection of TIBCO EMS temporary queues (APM-181328)
  • Request attributes didn't correctly handle conversion of, for example, "1,234.0". (APM-185421)
  • Request attribute argument capture UI: The wrong element was selected when reopening a data source. (APM-185567)
  • Correctly classify several .NET methods as network IO (APM-182840)
  • Service flow: avoid locking the view when expanding a grouped node and switching to throughput mode. (APM-186438)

Session Replay

  • Accessing Session Replay site from IE gives a TDP (APM-183687)
  • Pointers for load events in the timeline are misplaced on top of user interactions (APM-182221)
  • Clicking and replaying a session before closing extension message leads to TDP (APM-184078)
  • Session replay data is properly masked based on Management Zones. (APM-184164)
  • Accessing Session Replay player on IE11 gives a TDP (APM-183687)
  • Legend for user actions and events is shown when there are none recorded (APM-183843)
  • Legend for usability issues is not shown (APM-183435)
  • Starting playback before closing the extension install message raises a TDP (APM-184078)

Log monitoring

  • Host id information is missing for docker container logs (APM-181651)

Cluster

  • Odd UI behavior when setting the value of the global setting for Infra memory usage. (APM-180907)
  • We have wrong label for ec2 machines. It was AWS Elastic Container Service instead of AWS Elastic Compute Service. (APM-182008)
  • Firefox - tooltips on infographic not showing up (APM-182009)
  • Old network overview - nic/pgi list is not filtered by management zone (APM-182335)
  • In special case, when two plugins creates the same group of chart we may create a single chart with series from two different plugins. (APM-182657)
  • On Network overview page, appears a filter even though we have no monitored networks (APM-182814)
  • Deployment status filter: inconsistency of operating system name 'linux' vs. 'Linux' (upper / lower case) (APM-183150)
  • Technology tiles - affected instances not displayed correctly (APM-183968)
  • zLinux agent install command line contains parameter that is not valid for this platform (APM-184354)
  • Filter bar suggestion incorrectly positioned after deleting a filter (APM-177148)
  • Demo state incorrectly set when switching screens through a dashboard (APM-176964)
  • Missing "Process group" label in the global search on some screens (APM-182133)
  • Oracle DB Insights: Configurations were not visible when configuration entries with the same fields were added (APM-183675)
  • USQL: Selecting useraction.navigationStart and grouping by useraction.navigationStart leads to empty results (APM-184069)
  • Specific USQL query returns the fully qualified Java class in the user-visible response (APM-182883)
  • Customer is unable to change the sensitivity for Anomaly detection on service RentalAgreement. Possible UI Bug. (APM-182527)
  • Not being alerted on problems (APM-182316)
  • Fixed notification bug that if a problem was already notified to an integration and a new event correlated into the problem afterwards which is part of a maintenance window which is configured to suppress problem creation/alerting, no resolved notification would be sent out and problems would forever stay open in stateful integrations (e.g. PagerDuty, OpsGenie) (APM-182919)
  • AWS initial connection test is now checking all regions in partition (APM-182129)
  • Users which have a very large number of Management Zones assigned may have issues sharing dashboards (APM-172801)
  • Dashboard sharing: Sharing cannot be disabled if sharing token cannot be created (APM-182130)
  • Single host view response time regression (APM-182957)
  • ActiveGates before sprint 154 may cause performance impact on cluster nodes if the cluster has a very large number of API tokens. (APM-183401)
  • Previously available token permissions are no longer possible to assing in the token REST API. (APM-183782)
  • Default behavior of the VMWare monitoring flag of old Environment ActiveGates corrected: AGs < Sprint 100 now have the flag "on" as default AGs >= Sprint 100 act as configured by the customer (APM-181908)
  • Improved Agent HEAD request handling in ActiveGates: Previously the ActiveGate defaulted to a valid 204 if an Agent sent a HEAD request due to the missing server information on the Http request. ActiveGates now check if at least one server is reachable to return a valid 204. This improves re-connection of agents if the ActiveGate has network connectivity problems (as in this case where the ActiveGate had a problem with certificate resolution due to missing certificate store) (APM-182700)
  • The introduction of a quality of service control mechanism in release 170 introduced an unexpected thread pool bottleneck that temporarily blocked the Cluster REST API endpoints under very heavy load scenarios for one particular customer. Data ingest from agents was not affected and therefore no data was lost during that timeframe. The original default values have been restored. (APM-183527)
  • A new PHP Agent flag was introduced which can lead to an agent crash if sent to PHP agents with a version older than Sprint 171. The cluster now handles this case and skips the flag for older agents (APM-184726)
  • Can not save User-Agent value while configuring HTTP monitor (APM-181229)
  • Fixed problems with selecting sections of infographic on process overview page. (APM-184910)
  • Improvements for value formatting in network charts. Values may be slightly different from real values. (APM-183891)
  • AWS ASGs that were defined empty and didn't have any EC2s assigned during selected timeframe were removed from list of ASGs. (APM-184290)
  • [Deploy Dynatrace] Windows link directs to Linux installer (APM-184544)
  • Improvement when selecting a build unit based on the associated version. Now we check all installer versions in build unit matching by type, not only the first matching installer version, as was done previously (APM-184610)
  • AWS Custom Alerts - Elastic Load Balancer should be called Classic Load Balancer (APM-184999)
  • Limits on Docker overview page for displaying more data and not limiting view too early. (APM-185506)
  • Problem notifications tiles are too short (APM-186314)
  • Oracle DB tablespaces monitoring was showing summed metrics instead of current information about space used by database. The fix has changed the way of consuming metrics responsible for tablespaces usage information and allowed customer to using aggregations. (APM-184503)
  • USQL: Selecting useraction.navigationStart and grouping by useraction.navigationStart leads to empty results (APM-184069)
  • Fixed changing of log perspective on sources selection (APM-175844)

RUM

  • Fixed that users that only had the rights to Access the environment on a Management zone could not pin USQL tiles to a dashboard. (APM-186103)
  • Fixed an issue where Internet Explorer users experienced an error when clicking in the suggestion list. (APM-185605)

Synthetic monitoring

  • Regular error message about Private Synthetic location that does not exist (APM-184125)
  • HTTP Monitor Request is executed even if preceding Request is failing (APM-185782)

Autonomous Cloud

  • Allow users with partial tenant access to access specific Kubernetes clusters (APM-183657)

User Interface

  • Clicking on the turquoise bubble in the user icon doesn't open the menu. (APM-185175)
  • Clicking on global search results doesn't work in some cases (APM-182946)

Totals

93 total resolved issues

Component Resolved issues
Installer and Upgrade 18
Cluster Management Console 9
Mission Control 1
Code level analytics 9
Session Replay 8
Log monitoring 1
Cluster 40
RUM 2
Synthetic monitoring 2
Autonomous Cloud 1
User Interface 2