Session Replay is compatible with page-based applications, single-page applications, and applications that use IFrames. However, certain restrictions apply.
The following are not supported:
IFrame and nested IFrame recording are supported. However, the following restrictions are applicable:
By default, Session Replay captures and stores CSS resources during the user session recording. However, Session Replay cannot reproduce blob/object URLs.
If you deactivate 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 activated.
To overcome these restrictions, we recommend that you activate resource capture for Session Replay.
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 affecting 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 page events, so Dynatrace doesn't know that anything has changed.
As an alternative to updating the .value property of your form element, we suggest updating the attribute value (in the case of <input> elements) or the .textContent property (in the 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 cannot 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.
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 technologies supported by OneAgent:
Web applications are complex. While Session Replay is built to work with any web application and supports IFrames and single-page applications, there may be cases where user interactions are not perfectly reproduced. For this reason, Session Replay might not recreate user experiences adequately for all web applications.
Websites that modify the browser's native APIs may cause conflicts with the JavaScript agent code and prevent the page from being recorded properly.
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.