In this post, you'll see how integrated dashboards and our most recent additions to the Data explorer's configuration and visualization capabilities now better enable developers, DevOps engineers, and SREs to create, tailor, and use data visualizations to address their observability needs.
New features and enhancements
Distributed traces
Apps & Microservices
When opening a distributed trace from a service perspective, it will now always show the entire trace and highlight the service call from where the trace analytics was started.
Service detection APIs
Cross solution - Settings
Added policy and API support for custom service detection.
Data Explorer now offers automatically extended metric filters based on the Dynatrace entity model and 1:1 or 1:n relationships. For example, if you’re interested in the performance of a key user action for only a certain application, you can now filter it right in the build mode.
Use the Consistent entity colors switch to determine whether the same entity, when displayed on two or more of a dashboard's tiles, is shown in the same color. Note that this applies only to tiles created with Data Explorer.
ActiveGate security
You can now filter ActiveGates on the Deployment status page by their ActiveGate token status. For maximum security, make sure all your ActiveGates use valid ActiveGate tokens. For more information, see ActiveGate security.
Kubernetes metrics sent by ActiveGate
The Kubernetes metrics sent by the ActiveGate have been updated and consolidated:
With ActiveGate version 1.245, new Kubernetes metrics were added.
With SaaS version 1.246, the existing metrics are marked as deprecated.
Old and new metrics will continue to be written in parallel for a certain migration period, during which time the Kubernetes monitoring pages and built-in dashboards will be updated. Eventually, the deprecated metrics will no longer be written.
The change impacts in particular custom-built dashboards and custom events for alerting. There, specific action is needed on the customer side. Please see this community blog post for more insights into the motivation for this change, its impact, and the concrete actions needed.
User session export now includes session part number
For technical reasons, Dynatrace splits sessions into different parts, which are shown as separate sessions in user session export. To avoid problems with finding information that is stored in other parts of the session, such as session properties, user session export now includes the session part number.
Kubernetes Dynatrace Operator version
The Dynatrace Operator version used for Kubernetes deployments has been increased to 0.7.2.
Smartscape topology now shows vulnerabilities
The Smartscape topology has been extended so that you can now highlight entities that are affected by third-party vulnerabilities.
When you select Show third-party vulnerabilities:
The affected entities (nodes) are colored according to the severity of the vulnerabilities.
You can select and clear checkboxes in the legend to determine which severities are displayed. For example, select only Critical to display only red (critical) nodes.
The counts that are shown in the vertical bar to the left are the number of affected entities (in red) over the total entity count (in white).
The default behavior (the entities affected by a problem are highlighted) has not changed.
This new functionality is available to all customers with a subscription to Dynatrace Application Security.
Additional Azure regions supported
Two new regions are now supported for your Dynatrace SaaS Clusters in Azure:
Region West US 2 (Washington)
Canada Central (Toronto)
Management zones
Management-zone settings have a refreshed web UI and workflows to allow for more consistent and flexible permission management and API features in line with other settings changes done recently.
The Management zones settings page can now be made accessible to non-admins through security policies, and management zones can be configured through the Settings API.
Fixed an issue with rule-based service detection: 'Between' and 'ReplaceBetween' transformations now work correctly in all circumstances. (APM-381261)
In the Log Viewer, improved display of facets loading indicator (indicator shown only when using search input, not on result fetching). (APM-377465)
Resolved issue (introduced in Dynatrace versions 243 and 244) that inadvertently disabled Log Source configuration updates for OneAgents that were connected to server nodes added after upgrade of a cluster. (APM-380889)
Fixed an issue in which world maps were not visible in anonymously shared dashboards. (RUM-6724)
The system notifications banner has been restored in the CMC environment. (APM-378293)
Fixed a problem that prevented customer IP address mappings from converting to Settings 2.0. (RUM-6728)
Fixed an issue with the 403 errors that some customers could get on the Host page. (APM-379830)
Fixed an issue in which alerting profiles containing multiple rules with the same severity but different duration and tag filters matched problems erroneously, sending out notifications that shouldn't have been sent. (DAVIS-1966)
Failure detection - request attribute conditions "equals" and "not-equals" on floating point numbers now work correctly. (APM-379472)
Improved refreshing access tokens table to represent latest state in the server database after using a pagination. (APM-377338)
Attempting to delete a failure detection parameter that is already in use by a failure detection rule returns an appropriate constraint violation message and prevents the operation. (APM-376691)
Configuration changes via REST API using a non-personalized token are now audited with the public token identifier instead of the user who created the token. (APM-371592)
Fixed the OpsGenie integration for problem close notification. (APM-379633)
The Infrastructure Monitoring mode `--set-infra-only` OneAgent install parameter is now correctly recognized by the server. (APM-379864)
Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions.
Resolved issue with reporting Cloud Application Security Units consumption not being correctly reported in application-only mode under certain conditions. (CASP-16582)
Fixed an issue causing events on `Requests to unmonitored hosts` services (and other grouping services) to merge (which they should never do). (APM-377546)
Environment name length is now correctly validated upon creation. (APM-374428)
Resolved issue that sometimes led to temporary disabling of log upload via OneAgent during long-running rollout cluster migration. (APM-375587)
Breadcrumbs on service-related settings pages now show correct information. (APM-376862)
Fixed a problem that caused the "copyFromHostName" flag in rule-based service detection to be lost, causing service merging/splitting to not work as configured. (APM-379679)
Full web service detection rules: fixed the Context Root - URL segments copying transformation. (APM-376414)
Fixed parsing error for embedded entity selectors that contain multiple escaped special characters in metric selectors, and fixed a bug that allowed multiple arguments to the entitySelector filter predicate in metric selectors. (APM-378450)
ActiveGate
ActiveGate ID that is sent in `dt.active_gate.id` self-monitoring dimension is now updated when the server assigns a new ID in case of collision. (APM-377304)
Application Security
Resolved issue in which the "Host coverage" percentage on the "Application Security overview" page was calculated using an excessive total number of hosts, which rendered a coverage percentage that was lower than in reality. (CASP-16608)
Expanding a resolved security problem in the third party vulnerabilities list now shows the details. (CASP-16501)
Cloud Automation
Fixed an issue where the Orchestration Page would throw an unexpected error when loading the CA-instance URLs. (APM-379341)
Infrastructure Monitoring
Due to security concerns, we have blocked custom SQL extensions using the Extensions 2.0 framework. (APM-378722)
User interface
Error Count filter can no longer be applied if it has already been applied. (APM-368957)
application monitoring solution
When opening a distributed trace from a service perspective, it will now always show the entire trace and highlight the service call from where the trace analytics was started. (PRODUCT-4034)
ui test framework
The `Synthetic` suggestion for the Region filter is now capitalized. (RUM-5407)
Update 166 (Build 1.246.166)
This is a cumulative update that contains all previously released updates for the 1.246 release.
Update 182 (Build 1.246.182)
This is a cumulative update that contains all previously released updates for the 1.246 release.