Address comments from GTM team

Author: ada

gdi/get-data-in/rum/android/add-mapping-file.rst

@@ -11,12 +11,13 @@ Add a mapping file
 
 When you set the ``minifyEnabled`` property to true in your Android application source code, your build process minifies, optimizes, and obfuscates the code and generates a single mapping file, ``mapping.txt``. This mapping file contains the information Splunk RUM needs to convert stack traces containing obfuscated classes and filenames back into a human readable form. This conversion is called deobfuscation in Android.
 
+In order to associate a specific mapping file with a specific application build, Splunk RUM compares the ``applicationId`` and ``versionCode`` properties of the application to the parameters that you specify for the mapping file upload. You specify these parameters either as ``--app-id`` and ``--version-code`` in the ``splunk-rum android upload`` command or by including your application's merged or packaged manifest (``AndroidManifest.xml``), which includes these properties by default, in the ``splunk-rum android upload-with-manifest`` command. 
 
- .. note::
-    Make sure that the mapping file you upload to Splunk RUM matches the binary you deploy to production. To ensure this, the best practice is to integrate the ``splunk-rum`` usage into your CI pipeline so that whenever you re-build your Android application, you also re-upload its mapping file.
 
+.. note::
+    Splunk recommends that you follow the steps on this page to upload your mapping files to Splunk RUM before you distribute corresponding binaries. To ensure that the mapping files you upload to Splunk RUM match the binaries you deploy to production, the best practice is to integrate the ``splunk-rum`` commands below into your CI pipeline so that whenever you re-build your Android application, you automatically re-upload its mapping file. Alternatively, you can :ref:`upload source maps on demand<mobile-connect-source-files>`.
 
-In order to associate a specific mapping file with a specific application build, Splunk RUM compares the ``applicationId`` and ``versionCode`` properties of the application to the parameters that you specify for the mapping file upload. You specify these parameters either as ``--app-id`` and ``--version-code`` in the ``splunk-rum android upload`` command or by including your application's merged or packaged manifest (``AndroidManifest.xml``), which includes these properties by default, in the ``splunk-rum android upload-with-manifest`` command. 
+    Splunk RUM stores your mapping files permanently. You cannot delete them from Splunk RUM at this time. 
 
 
 Prerequisites

gdi/get-data-in/rum/browser/set-up-javascript-source-mapping.rst

@@ -19,10 +19,16 @@ Setting up JavaScript source mapping involves these steps:
 * Deploying your minified files to your production environment.
 
 
+.. note::
+    Splunk recommends that you follow the steps on this page to upload your source maps to Splunk RUM before you distribute corresponding binaries. To ensure this, the best practice is to integrate these steps into your CI pipeline so that whenever you build your application, your pipeline automatically uploads the corresponding source maps to Splunk RUM. Alternatively, you can :ref:`upload source maps on demand<browser-connect-source-maps>`.
+
+    Splunk RUM stores your source maps permanently. You cannot delete them from Splunk RUM at this time. 
+
+
 Prerequisites
 =====================================================================
 
-* Update your browser RUM agent to v0.19.2 or later. Otherwise, Splunk RUM can't symbolicate stack traces from browser apps.
+* Update your browser RUM agent (``splunk-otel-web.js``) to v0.20.2 or later. Otherwise, Splunk RUM can't symbolicate stack traces from browser apps.
 * :ref:`Install the splunk-rum CLI<rum-gdi-install-cli>`.
 
 

gdi/get-data-in/rum/ios/add-dsyms.rst

@@ -14,7 +14,7 @@ When you build your iOS application in release mode, your build process generate
 
 The ``splunk-rum`` CLI compresses dSYM directories into ``.zip`` files for you and uploads them. When you upload a zipped dSYM  to Splunk RUM, you enable Splunk RUM to symbolicate the debug symbols contained within that dSYM.  This in turn enables you to view stack traces with the names of functions and offsets into those functions to help you identify the line of code that was executing when the application crashed.
 
-You can upload dSYMs from your main application code and from third-party frameworks, but not from system libraries. Splunk RUM does not yet support the symbolication of stack frames for system libraries.
+You can upload dSYMs from your main application code and from third-party frameworks. Splunk RUM does not yet support the symbolication of stack frames for system libraries.
 
 
 Prerequisites
@@ -48,7 +48,9 @@ Upload dSYMs
 To upload dSYMs use the ``splunk-rum`` CLI as follows.
 
 .. note::
-    Splunk recommends that you upload dSYMs to Splunk RUM before you distribute corresponding binaries. To ensure this, the best practice is to integrate the ``splunk-rum`` CLI into your CI pipeline so that whenever you archive your iOS application, your pipeline uploads the corresponding dSYMs to Splunk RUM.
+    Splunk recommends that you upload dSYMs to Splunk RUM before you distribute corresponding binaries. To ensure this, the best practice is to integrate the following ``splunk-rum`` commands into your CI pipeline so that whenever you archive your iOS application, your pipeline automatically uploads the corresponding dSYMs to Splunk RUM. Alternatively, you can :ref:`upload dSYMs on demand<mobile-connect-source-files>`.
+
+    Splunk RUM stores your dSYMs permanently. You cannot delete them from Splunk RUM at this time. 
 
 
 #. Upload your application's dSYMs: 

rum/error-aggregates.rst

@@ -94,10 +94,11 @@ To learn more about Tag Spotlight, see:
 Connect source files
 ------------------------------------------------------------------------------------------
 
-The information in most raw crash stack traces is not fully human-readable. To make a stack trace readable, you must provide platform-specific mapping information that translates that stack trace into human-readable form:
+The information in most raw crash stack traces is not fully human-readable. To make a stack trace readable, you must provide platform-specific mapping information that translates that stack trace into human-readable form. You can either upload mapping information now ("on-demand”) or at the time that you instrument your mobile application:
 
+
+* To upload mapping files now, select :guilabel:`Add dSYMs` for iOS applications or :guilabel:`Add a mapping file` for Android applications on this dashboard. 
 * To upload mapping files at instrumentation time, see :ref:`add-dsyms` for iOS applications or :ref:`add-mapping-file` for Android applications.
-* To upload mapping files using the widget on this dashboard, select :guilabel:`Add dSYMs` for iOS applications or :guilabel:`Add a mapping file` for Android applications. 
 
 
 
@@ -115,13 +116,14 @@ To see errors from a specific browser application:
 
 
 
-.. _browser-connect-source-files:
+.. _browser-connect-source-maps:
 
 Upload source maps for readable stack traces
 ------------------------------------------------------------------------------------------
 
 The information in most raw stack traces is not fully human readable. To make your raw stack traces easier for you to read, you need to provide source maps that correspond to this browser application. Source maps enable Splunk RUM to translate raw stack traces back into a human-readable form. You can either upload source maps now ("on-demand”) or at the time that you instrument your browser application:
 
+
 * To upload source maps now, select :guilabel:`Upload` on this dashboard.
 * To upload source maps at instrumentation time, see :ref:`set-up-javascript-source-mapping`.