Dynatrace Managed release notes version 1.184

New features and enhancements

Product news

Product news

Automated cluster extension with feedback

Our new Cluster node REST API endpoints dedicated for cluster management assist cluster administrators in setting up automation around bootstrapping a new cluster or extending cluster size. Adding a new cluster node is a blocking operation, so no other node can join the cluster at the same time. In large deployments, this operation is time-consuming and can take up to a couple of days. Previously, to check if the operation was finished, a cluster administrator could use a nodetool script to observe data synchronization in Cassandra databases. The new REST API is a robust alternative solution that can be easily incorporated into scripts or CI/CD pipelines. See the Cluster Management REST API specification for details on path and payload.

Node join status REST API

Provide Dynatrace Managed as a service to your teams (Early Adopter release)

Our new Environments REST endpoint assists administrators who need to provision Dynatrace environments to other teams at scale. Until now, the process was cumbersome as it required administrators to manually create an environment and a token for further configuration. By providing automation via a new endpoint from the Cluster API, it's possible to deliver configuration-as-code, unified dashboarding, service naming conventions, and much more with minimal effort. To get started, you need to create a Service Provider API token in the Cluster Management Console. To get the interface details, use the Dynatrace API Explorer, which is available from the user menu under Cluster Management API. Select the Cluster API definition:

Environments REST API

To create a new environment, use the POST method combined with the createToken=true query parameter in order to get an environment-level token in response.

Automatically created token for environment

Once you have this, you can continue with the Environment API or Configuration API to orchestrate the environment. An upcoming blog post will describe in detail how you can utilize the API to build powerful, manageable, and high-value environments for your teams. Note, the new REST API is still in the Early Adopter release stage and enabled by default.

Other changes

The JRE was updated to version 8u232 to take advantage of the latest security-vulnerability enhancements and bug fixes.

Resolved issues

Dynatrace Managed General Availability (Build .184)

The Dynatrace Managed .184 GA release contains 3 resolved issues.

Component
Resolved issues

ON-PREM

  • Read only user profile screen sometimes displays changes confirmation dialog (caused by password manager). (APM-205150)
  • Offline cluster tries to initialize online license during first startup. (APM-209624)

ON-PREM Console

  • Some community users were not assigned to any account, thus were not able to see jira support tickets created by other users from their organization. (APM-206568)

Dynatrace SaaS General Availability (Build .183)

The Dynatrace SaaS .183 GA release contains 14 resolved issues.

Component
Resolved issues

Code-Level

  • Request naming preview not working for client side only service calls. (APM-208319)
  • Request naming rules for URLs starting with username@password do not work. (APM-208914)

Cluster

  • Icon for processes requiring restart on Technology Overview page is now consistent with process list on host dashboard. If agent is injected a gray info icon is shown. If agent is not injected a yellow warning icon is shown. (APM-207533)
  • Filtering was not working, when user picked a filter being on different page than first one AND the filter only returned one page. Now when currently selected page doesn't exist after filtering, user will be moved to the last existing page. (APM-208327)
  • Db Insights Oracle: It was not possible to find process group instance related to monitored database when Oracle process groups were splitted by host group. In this case all data from monitored database were reported to a separate custom device. (APM-204300)
  • Enable USQL queries with combinations of PERCENTILE and FILTER. (APM-209178)
  • Fixed and issues where some entities were not correctly displayed in the auto tagging preview although they were tagged correctly. (APM-206399)

Core UI

  • Page ribbon resizes now correctly on dynamic content screens. (APM-202401)
  • Fixed the font color of disabled elements on dark theme pages. (APM-203317)
  • Fixed the wrong font color of the deployment achievement header element. (APM-205334)
  • Events card's infobox is now correctly positioned. (APM-205917)
  • Fixed an additional minute added to the chosen custom timeframe in some cases. (APM-208326)
  • Events card resizes now correctly after a viewport resize. (APM-207893)

User Interface

  • Fixes an issue that breaks the Kubernetes dashboard when the requested resources are higher than the available ones. (APM-207819)

Dynatrace SaaS General Availability (Build .184)

The Dynatrace SaaS .184 GA release contains 14 resolved issues.

Component
Resolved issues

Code-Level

  • For a given list of request naming rules it is now guaranteed that always the first completely matching rules renames the request. (APM-211692)

Cluster

  • Fixed presenting wrong data (from previously visited host) in System Load and Physical CPU headers on Host's details screen. (APM-208952)
  • Fix incorrect number of AWS Supporting services with problems on AWS dashboard's infographic. (APM-211212)
  • Affected entities are now correctly counted in Network Overview's environment details. (APM-211296)
  • Memory usage merging for restarted processes for PaaS hosts on host list is limited to 1000 processes. (APM-216884)
  • Fixed missing Network Interfaces in Network Overview with applied Management Zone. (APM-217385)
  • Enable USQL queries with combinations of PERCENTILE and FILTER. (APM-209178)
  • Screens may fail to load on a Managed Environment when internal network requests are very slow. (APM-210777)
  • Enable table USERERROR when using REST API to execute USQL queries. (APM-210805)
  • During the update from Sprint 183 to Sprint 184 it was possible in rare cases that internal migration code caused an endless loop which consumed all webserver threads in the thread pool causing a server becoming unresponsive. (APM-217530)

Core UI

  • Fixed tiles with a custom timeframe not being refreshed. (APM-210133)
  • Fixed an issue when the management zone selector was not visible for users with tenant permissions. (APM-210254)
  • Fixed issue when switching the timeframe from last 24 hours to previous and next 24 hours at midnight led to a last 5 minutes time frame. (APM-211028)

Log Analytics

  • Improved validation of search queries in Log Viewer. (APM-207256)