Merge pull request #2695 from splunk/adasplunk-DOCGUILD-28874

[DOCGUILD-28874] Bugfix to match DEMRUM-1675

Author: adasplunk

rum/rum-session-replay.rst

@@ -12,7 +12,8 @@ Replay a session to take a look at exactly what a user experienced and make info
 
 
 Use cases
-===================
+======================================================================
+
 There are many reasons why you might want to replay sessions. Here are a few: 
 
 * Reduce the amount of time support teams take to troubleshoot a problem. By seeing errors from the perspective of an actual user, support teams can quickly identify what happened, and take action. Without session replay, support teams could spend a long time investigating a variety of possible causes based on an incomplete description of the problem. 
@@ -21,19 +22,20 @@ There are many reasons why you might want to replay sessions. Here are a few:
 
 
 Prerequisite
-=================
+======================================================================
 
 Session replay is available for enterprise customers only. For more information on each type of subscription, see :new-page:`Splunk RUM Pricing <https://www.splunk.com/en_us/products/pricing/faqs/observability.html#splunk-rum>`.
 
 
 Set up session replay 
-=====================
-There are two ways to set up session replay: CDN or NPM. 
+======================================================================
 
-.. admonition:: Note
-    
+There are three ways to set up session replay: CDN, self-hosted, or NPM. 
+
+.. note::
     Initialize Splunk Browser RUM before you initialize the session recorder package. 
 
+
 This example shows the order in which to initialize the scripts:
 
 .. code-block:: html
@@ -71,38 +73,53 @@ Initialize this code snippet to set up session replay through Splunk CDN.
 
 
 
-NPM
+Self-hosted
 --------------------------------------------
 
-Use the following command to set up session replay with NPM through a package named ``@splunk/otel-web-session-recorder``.
+#. Download the desired version of :new-page:`splunk-otel-web-session-recorder.js <https://github.com/signalfx/splunk-otel-js-web/releases/latest/download/splunk-otel-web-session-recorder.js>`.
+#. Deploy the file in a location accessible by the users of your application.
+#. Add the following session replay snippet after the ``SplunkRum.init`` snippet:
 
+   .. code-block:: javascript
 
-.. code-block:: html
+      <script src="<your-self-hosted-path>/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
 
-    npm install @splunk/otel-web-session-recorder
 
-Next, initialize this code snippet: 
+To avoid gaps in your data, load and initialize the Splunk JavaScript Agent asynchronously and as early as possible.
 
-.. code-block:: html
 
-    import SplunkSessionRecorder from '@splunk/otel-web-session-recorder'
+NPM
+--------------------------------------------
 
-    SplunkSessionRecorder.init({
-        realm: '<realm>',
-        rumAccessToken: '<your_rum_token>'
-    });
+#. Use the following command to set up session replay with NPM through a package named ``@splunk/otel-web-session-recorder``.
+
+   .. code-block:: html
+
+      npm install @splunk/otel-web-session-recorder
+
+#. Next, initialize this code snippet: 
+
+   .. code-block:: html
+
+      import SplunkSessionRecorder from '@splunk/otel-web-session-recorder'
+
+      SplunkSessionRecorder.init({
+          realm: '<realm>',
+          rumAccessToken: '<your_rum_token>'
+      });
 
 
 Deactivate session replay 
 --------------------------------------------
+
 To deactivate session replay you can either:
 
 * Turn it off for the particular session replay. 
 * Remove the instrumentation if you want to deactivate it completely. 
 
 
 Additional instrumentation settings
-------------------------------------
+--------------------------------------------
 
 For more information on configuration options, see :new-page:`rrweb guide <https://github.com/rrweb-io/rrweb/blob/rrweb%401.1.3/guide.md#guide>` on GitHub.