Starting with Dynatrace version 1.219, we will provide you with a Call to action card allowing you to switch all your web application to the latest beacon
format. All prior versions will reach its end-of-life with Dynatrace version 1.229. If you don't manage to switch prior to this version, due to the format change, a beacon
could be blocked by your firewall/security appliance or if your agents and RUM JavaScript versions are outdated, actions will be dropped and you won't be able to see any monitoring data for your application. For more information, see Firewall constraints for RUM.
Dynatrace tokens are displayed only once upon creation. Dynatrace stores them encrypted and you can't reveal them after creation.
To enhance token security, we modified the OneAgent and ActiveGate download dialog. You now have to provide the PaaS token in the dedicated field or create a new token on spot. The token is automatically appended to the provided download and installation commands. For more information, see
In all multidimensional analysis pages for Real User Monitoring, the Filter by field lists all the matching page and page group names as you type, so that you can select multiple entries containing a string, rather than a single exact match as in previous releases.
We have published a document explaining how Session Replay offers best-in-class security and data protection. The document is intended to be shared with your chief information security officers and other stakeholders who decide, based on data protection regulations applicable to your markets, whether you should enable Session Replay. To access the document, go to Application settings for your application and select Session Replay and behavior > Session Replay.
For more information on Session Replay, see Session Replay.
We have removed the limit of 10,000 problems and events in a single query.
Now you can filter the problem feed by affected entities.
In addition, new tooltips are available in the problem feed:
In Dynatrace versions 1.214-1.218, the Windows services availability monitoring configuration at the host level took precedence over the host group configuration, which in turn took precedence over the environment configuration.
In Dynatrace version 219+, this is no longer the case. Configurations at the environment, host group, and host level are combined. For details, see Windows services availability.
We added the following metrics:
builtin:cloud.kubernetes.pod.containers
. Number of containers per pod.builtin:cloud.kubernetes.pod.desiredContainers
. Provides the number of desired containers per pod. Includes the dimension indicating the container state.builtin:cloud.kubernetes.node.conditions
. Provides information about the status and health of a Kubernetes node.To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.219.
The 1.219 GA release contains 12 resolved issues.
This is a cumulative update that contains all previously released updates for the 1.219 release.
This is a cumulative update that contains all previously released updates for the 1.219 release.