From f26f785b455595ad81288935ef00ae15146dc5ef Mon Sep 17 00:00:00 2001 From: CherylFrankenfield <32469854+CherylFrankenfield@users.noreply.github.com> Date: Fri, 8 Nov 2024 08:36:09 -0800 Subject: [PATCH 1/4] Update session-replay.mdx After some testing, we should add expected behavior with iframe apps and session replay content. --- .../browser-pro-features/session-replay.mdx | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx index c10c0f16264..5238b5dd924 100644 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx +++ b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx @@ -249,6 +249,29 @@ For more details on session replay, see the following sections: ``` + + ### Problem + + Session replay feature is enabled, but you're not seeing replay data for iframe content. + + ### Solution + + Assuming a web page consists of a top level window with a child iframe, here are some possible fixes: + * If the iframe is **same-origin**, + * agent placed in the top level will capture session replay events in both the window and the iframe. + * agent placed in the iframe will capture events only in its own context. + * agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above. + * If the iframe is **cross-origin**, + * agent placed in the top level will only capture session replay events in the window; iframe will appear blank. + * agent placed in the iframe will only capture events in the iframe. + * if *recordCrossOriginIframes* is not enabled (current state of agent) in the replay options, agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above. + * if *recordCrossOriginIframes* is enabled and agents are in both window and iframe, the iframe agent does not report session replay events. However, the window agent will report events with the cross-origin iframe events captured in replay. + * Please note, session replay is not compatible with elements and this is unsupported. + + ## Manually record session replays [#manual-replays] From f3f046f0451019d2c67c56fc3f63d6deb470a5c4 Mon Sep 17 00:00:00 2001 From: a-sassman Date: Mon, 11 Nov 2024 15:38:54 -0800 Subject: [PATCH 2/4] fix(browser): improved language of troubleshooting section --- .../browser-pro-features/session-replay.mdx | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx index 5238b5dd924..314d0cf9c5c 100644 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx +++ b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx @@ -1,10 +1,10 @@ --- title: "Session replay" metaDescription: "Play back user interactions to debug faster and improve page performance." -freshnessValidatedDate: 2024-04-23 +freshnessValidatedDate: 2024-11-11 --- -Session replay plays back user interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as: +Session replay captures interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as: * **Troubleshooting JavaScript errors**: Troubleshoot the cause of an error by seeing what the user was doing when the error occurred. For example, if an end user receives an error while trying to complete an ecommerce transaction, you can use session replay to see which steps they took and what data they entered before the error occurred. This can help you quickly identify and fix the root cause of the problem. * **Improving the user experience**: Discover areas of your web app that are causing users frustration. For example, you might see that users are getting lost in your navigation or clicking on buttons that don't do anything. @@ -258,18 +258,19 @@ For more details on session replay, see the following sections: Session replay feature is enabled, but you're not seeing replay data for iframe content. ### Solution + + The behavior of session replay in iframe scenarios depends on the origin of the iframe and the placement of the browser agent. - Assuming a web page consists of a top level window with a child iframe, here are some possible fixes: - * If the iframe is **same-origin**, - * agent placed in the top level will capture session replay events in both the window and the iframe. - * agent placed in the iframe will capture events only in its own context. - * agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above. - * If the iframe is **cross-origin**, - * agent placed in the top level will only capture session replay events in the window; iframe will appear blank. - * agent placed in the iframe will only capture events in the iframe. - * if *recordCrossOriginIframes* is not enabled (current state of agent) in the replay options, agents placed in both window and iframe will each report session replay events independently (with their own session) in line with the two bullets above. - * if *recordCrossOriginIframes* is enabled and agents are in both window and iframe, the iframe agent does not report session replay events. However, the window agent will report events with the cross-origin iframe events captured in replay. - * Please note, session replay is not compatible with elements and this is unsupported. + Assuming a web page consists of a top-level window with a child iframe, here are some possible fixes: + * **Same-origin iframes**: + * If you place the browser agent in the top-level window, session replay captures both the window and the iframe. + * If you place the browser agent in the iframe, session replay only captures what's in the iframe. + * If you place the browser agent in both the top-level window and iframe, session replay captures what's happening independently in both the window and iframe, resulting in two separate sessions. + * **Cross-origin iframes**: + * If you place the browser agent in the top-level window, session replay only captures what's in the window. The iframe will appear blank in session replay. + * If you place the browser agent in the top-level window, session replay only captures what's in the iframe. + + Session replay is **not** compatible with elements. From 6914befc12c86b48bad636f8e1b5ff6089ffafcf Mon Sep 17 00:00:00 2001 From: ally sassman <42753584+ally-sassman@users.noreply.github.com> Date: Mon, 11 Nov 2024 17:38:42 -0800 Subject: [PATCH 3/4] Update src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx --- .../browser-monitoring/browser-pro-features/session-replay.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx index 314d0cf9c5c..8ba3dc0ccfd 100644 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx +++ b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx @@ -268,7 +268,7 @@ For more details on session replay, see the following sections: * If you place the browser agent in both the top-level window and iframe, session replay captures what's happening independently in both the window and iframe, resulting in two separate sessions. * **Cross-origin iframes**: * If you place the browser agent in the top-level window, session replay only captures what's in the window. The iframe will appear blank in session replay. - * If you place the browser agent in the top-level window, session replay only captures what's in the iframe. + * If you place the browser agent in the top-level iframe, session replay only captures what's in the iframe. Session replay is **not** compatible with elements. From 025ed785e1ae3b7c181583d032211368344a69f4 Mon Sep 17 00:00:00 2001 From: adutta-newrelic Date: Wed, 20 Nov 2024 16:29:22 +0530 Subject: [PATCH 4/4] Updates --- .../browser-monitoring/browser-pro-features/session-replay.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx index 8ba3dc0ccfd..4175d43a9d7 100644 --- a/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx +++ b/src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx @@ -270,7 +270,7 @@ For more details on session replay, see the following sections: * If you place the browser agent in the top-level window, session replay only captures what's in the window. The iframe will appear blank in session replay. * If you place the browser agent in the top-level iframe, session replay only captures what's in the iframe. - Session replay is **not** compatible with elements. + Session replay is **not** compatible with `` elements.