Technical restrictions for Session Replay

Session Replay is compatible with page-based applications, single-page applications, and applications that use IFrames. However, certain restrictions apply.

Browser support

Technology restrictions

The following technologies aren't supported:

  • Frames
  • Shadow DOM
  • Canvas
  • WebGL
  • Web components
  • Plugins, such as Adobe Flash Player, Java applets, and non-HTML technologies
  • Documents, such as PDF files and Word documents
  • Pseudo CSS files
  • Movie replay
  • Traditional ASP (applications residing in the same environment as the monitored application must also not use traditional ASP)

IFrames

IFrame and nested IFrame recording is supported. However, the following restrictions are applicable:

  • Each IFrame must have the JavaScript code snippet injected into it. If the JavaScript code snippet has been injected only into the parent and not into the IFrames, the IFrame content and interactions won't be displayed in the replay. This is because it isn't possible to look into IFrames from a parent page.
  • IFrame recording works only when the parent page contains the JavaScript code snippet. If only the IFrame that isn't the parent page has the code snippet, it won't be displayed properly in the replay.

Resources

Session Replay doesn't store resources. It also can't reproduce blob/object URLs.

Restrictions for resources

  • 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 they can be accessed by the player without requiring authentication.
  • Resources can't be personalized. This is applicable 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.

Volume

On average, a minute of session recording and replay consumes 100kB of storage space. This is also the required amount of upstream bandwidth from the client system to the Dynatrace servers that will be 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.163 or above, because it supports a high volume of beacon transmission.

High volume beacon support is available for all Real User Monitoring capable agents:

  • Apache
  • NGINX
  • Java
  • IIS
  • Node.JS

Application support

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.

Environment

Session Replay must send data from client browsers to Dynatrace Server. Data transmission can fail depending on the environment, the available network connectivity, speed, network latency, connection problems, bandwidth, and other environment-related issues.