Technical restrictions for Session Replay for web applications
Session Replay is compatible with page-based applications, single-page applications, and applications that use IFrames. However, certain restrictions apply.
The following technologies aren't supported:
Web Animations API
Plugins, such as Adobe Flash Player, Java applets, and non-HTML technologies
Documents, such as PDF files and Word documents
Pseudo CSS files
IFrame and nested IFrame recording are supported. However, the following restrictions are applicable:
If you disable resource capture for Session Replay, the following restrictions apply. These restrictions also apply to images and fonts even when resource capture for Session Replay is enabled.
Resources must be available on the browser that's used for replay. There must be a direct connection to the server that serves the resources.
Resources can't be protected. If resources are protected, ensure that the player can access them without authentication.
Resources can't be personalized. This applies to resources that are different for each user but are served by the same URL. However, the restriction doesn't apply to URLs that are different for each personalized resource. An example of this is avatar images that use the same URL to deliver different avatars for different users.
If you're dynamically updating the values in your form, and they're not being displayed in your Session Replay recording, check your application code and verify how you're effecting the update—you might be updating the
.value property of your form element. While we understand that this is a valid update method, it doesn't trigger any events on the page, so Dynatrace doesn't know that something has changed. As an alternative solution, we suggest updating the attribute value (in case of
<input> elements) or the
.textContent property (in case of
<textarea> elements). This way, Dynatrace will be notified of the changes and will record them correctly.
On average, a minute of session recording and replay consumes 100 kB of storage space. This is also the required amount of upstream bandwidth from the client system to the Dynatrace servers that is consumed. However, this value can't be guaranteed because it depends on the web application. Applications with very frequent DOM changes, big initial sizes, or heavy usage of IFrames can create large amounts of data.
Data transmission and OneAgent
Ensure that you're using OneAgent version 1.193+ because it supports a high volume of beacon transmission.
High volume beacon support is available for all Real User Monitoring capable agents:
Web applications are complex. While Session Replay is built to work with any web application and includes support for IFrames and single-page applications, there might be cases in which the reproduction of user interactions isn't perfect. For this reason, Session Replay may not recreate user experiences adequately for all web applications.
Session Replay must send data from client browsers to your Dynatrace Cluster. Data transmission can fail depending on the environment, available network connectivity, speed, network latency, connection problems, bandwidth, and other environment-related issues.