Merge pull request #2172 from splunk/pwilliams-o11ydocs-6365

Add troubleshooting section for duplicate spans in RUM

Author: pauljwil

gdi/get-data-in/rum/browser/troubleshooting.rst

@@ -105,7 +105,7 @@ Make sure you're initializing the agent synchronously and as early as possible.
 
 .. _browser-rum-break-site:
 
-Browser RUM is causing issues in my site
+Browser RUM is causing issues in your site
 ================================================================
 
 If you think Browser RUM might be causing issues in your website or breaking existing behavior or design, check the following:
@@ -129,3 +129,21 @@ If you think Browser RUM might be causing issues in your website or breaking exi
       }
 
 .. include:: /_includes/troubleshooting-components.rst
+
+Browser developer tools display events from Splunk instrumentation
+==================================================================
+
+If there are network requests displayed in your browser developer tools from
+Splunk OTel instrumentation such as ``splunk-otel-web.js`` or
+``SplunkContextManager``, this is because the application code calls the
+instrumentation, which then calls the browser API. As a result, your browser
+developer tools indicate that such events are initiated by the RUM agent.
+
+You can identify the original application code initiator by navigating to the
+network request and hovering over or selecting the value in the initiator
+column, for example, ``splunk-otel-web.js``. This displays additional events
+from the stack trace.
+
+You can also configure your browser developer tools to omit the instrumentation
+layers from the initiator list. See your browser documentation for details.
+