Dynatrace: Managed Release Notes Version 1.226

These release notes are related to specific changes to Dynatrace Managed​​. To learn about the general Dynatrace changes included in this Dynatrace Managed release, see:

New features and enhancements

General

• For Dynatrace Managed customers, Kubernetes event monitoring has been released to GA, and the early adopter version has been deprecated. To use the new Kubernetes event monitoring, please opt-in through the cluster settings. (In the Dynatrace Web UI, go to set up > Cloud and virtualization > Governor, Select your cluster, and open Enable monitoring with Monitoring event.)

• You can update the system users used on Dynatrace managed nodes through the “reconfigure.sh” script.

ServiceNow integration changes

If you have integrated ServiceNow and Dynatrace, please refer to our ServiceNow integration documentation for important updated instructions on integrating Dynatrace with ServiceNow. Dynatrace support for the Dynatrace Service Graph Connector application will end on December 31, 2021. Instead, we recommend that you configure the dedicated Service Graph Connector for Observability application from ServiceNow.

Solved problem

Cluster Management (Build 1.226.84)

cluster

• On the “Deployment Status”> “ActiveGates” page, rename the ActiveGate module from `z/OS` to `zRemote`. (APM-320074)

• On the “Deployment Status”> “ActiveGates” page, rename the ActiveGate module from “DB Insight” to “Database Insights”. (APM-319086)

• Improved the performance of log monitoring aggregation queries. (APM-320500)

• When using custom generic entity types, Data Explorer now uses the correct name dimension key for the :names operator in the metric selector. (APM-309971)

• Solved the problem that when the cluster node performs memory hard cleaning and stops processing the incoming user session data, when the cluster node returns to the normal memory condition, it cannot start processing the incoming user session data again. (APM-322680)

• Fixed the problem that the extended execution controller could not be opened or closed. (APM-323227)

• Switching “Environment of monitoring host in infrastructure-only monitoring mode” in the plug-in settings can now be used normally for JMX plug-ins. (APM-320690)

• Fixed the switch to enable/disable rules on the “Operating System Service Monitoring” page. (APM-321606)

• Custom and undefined attribute keys are no longer case sensitive. (APM-320182)

• Improved the detection of pages and page groups for RUM operations. (APM-318346)

• Fixed the issue of access rights to the Kubernetes entity page for some users who only have the authority to manage the area. (APM-322118)

• Fixed an issue that reduced the number of ingestible events in some cases. (APM-322923)

• Resolved an issue where some filters were not deleted when selecting the delete filter button for location, browser, or operating system. (APM-319726)

• Resolved an issue that caused query execution to fail when adding tiles from the dashboard and then adding metrics in the “Data Explorer”. (APM-321248)

• Solved the rare issue that events configured not to be merged (for example, when the CUSTOM_ALERT event type is used with a custom event for alarms) would still be merged with another event. (APM-320550)

• Fixed a bug that the GA version of Kubernetes events was not correctly enabled when selecting “Activate Kubernetes event analysis for all clusters” or “Enable Kubernetes event visibility”. (APM-321622)

• Dashboard API calls to change the preset state of user-built dashboards can now run normally. (APM-322917)

• Fixed an issue where single-value queries (ie “resolution=Inf”) would incorrectly return “0” results for counter indicators. (APM-318188)

• Fixed the problem that the calculated service indicators would randomly lose data. (APM-316585)

• Fixed filtering the management area of ​​the remote environment. (APM-320812)

• When migrating a custom chart with two label filters applied to the Data Browser, it is now possible to use AND combinations instead of OR to apply labels correctly. The migrated chart is opened in code mode in the “Data Browser” instead of the standard build mode, because the build mode does not support AND filter values. (APM-318454)

• Added a “Location” link to the title of the user details page. (APM-316552)

• Fixed the following issue: When the geographic location of the private location was reconfigured in the settings, the private location was subsequently not taken into account in the anomaly detection of the browser monitor. (APM-321860)

• Solved the problem that HTTP monitors that use credentials do not receive credential updates when they run in a public location, so unless the monitors are specifically updated, they use the old values ​​for public location execution. (APM-320713)

• Improved maintenance window evaluation performance when configuring a large number of management areas. (APM-321489)

• Solved the problem of attaching images to chat within Intercom products. (APM-321268)

• The key issue: To avoid high Cassandra database load, REST API calls are no longer audited. (APM-321322)

• When adding an alias to a metric, the “Save” button is now enabled. (APM-321302)

• The sort order of the chart tiles in the top list now correctly reflects the endpoint results. (APM-323845)

• Filters based on the Kubernetes name now implement the “include” behavior (instead of the “startsWith” behavior) to be consistent across all Kubernetes monitoring pages. (APM-317696)

• Solved the problem of displaying detailed JVM memory metrics on the detailed information page of the process group instance. (APM-322146)

• Fixed the problem that the extension cannot be updated because the indicator used in the indicator expression does not exist. (APM-317750)

• Dashboard filters such as Kubernetes clusters, Kubernetes namespaces, and Kubernetes workloads can now be correctly applied to the “Data Explorer” tiles with built-in metrics. (APM-319031)

• Solved the problem of data loss for some modeless indicators sent through the MINT API. Affected: MINT indicators, in which the indicator keys are modified by Dynatrace on the cluster, including (1) indicator keys that do not end with counts, and (2) indicator keys that do not end with counts. (APM-321104)

• Fixed an issue where adding a space to the end of the deep object access input in the “Request Properties” page would cause the Web UI to crash. (APM-320305)

• When using the `/api/config/v1/extensions` and `/api/config/v1/plugins` endpoints to publish the configuration of remote plugins, you now need to provide the ID tenant of the online ActiveGate extension module. Use `https://{your-environment-id}.live.dynatrace.com/api/config/v1/extensions/activeGateExtensionModules` to get the IDs of all ActiveGate extension modules. The configuration of a remote plug-in that does not exist was rejected. (APM-310674)

• Dashboards filtered by “Deployment Type” now apply filters correctly. (APM-317158)

• Improved the information graph display to prevent the extended user information from being accidentally overwritten. (APM-315402)

• When obtained from a client attachment and placed in a server-side service call, the request attributes related to the web request can now be set correctly. (APM-317742)

• Data Browser: When the indicator name is empty, the `Visual settings` and `Axes` tabs now display the indicator ID (instead of displaying nothing). (APM-320521)

• The environment ID created by PUT’/api/cluster/v2/environments /{id}’ is now limited to a set of characters ([a-zA-Z0-9_-]{1,70}). Using some other characters before will cause the environment to fail to start. (APM-317514)

• Fixed an error where too many processes were displayed in the Kubernetes pod details. (APM-321838)

• Fixed an issue that caused inconsistent JSON responses when aggregating a set of empty questions. (APM-317294)

• When going from a GWT page to an Angular page, the filter for session attributes (double precision, date, string…) does not work properly. All filters for session attributes are now correctly mapped. (APM-319773)

• When exporting a dashboard with tile reading data from a remote environment and setting the management area in that environment as a filter, the management area is now correctly included in the dashboard JSON. (APM-319652)

• Filtering by the timestamp field in Log Viewer v2 no longer causes an error. (APM-309687)

Disclaimer

Dynatrace Company Post this content on September 17, 2021 And is solely responsible for the information contained therein.Distributed by the public, unedited and unchanged, on September 17, 2021 19:01:06 UTC.