Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 82d5115

Browse files
author
ada
committed
Address comments in GSO11Y-3367 and GSO11Y-3368
1 parent 125a548 commit 82d5115

File tree

3 files changed

+21
-3
lines changed

3 files changed

+21
-3
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,9 @@ Uploads for production builds
4646

4747
* Run the ``upload`` command with the ``--app-id`` and ``--version-code`` parameters:
4848

49+
.. note::
50+
If you didn't set the ``SPLUNK_REALM`` and ``SPLUNK_ACCESS_TOKEN`` environment variables, you must also add the ``--realm <value>`` and ``--token <your-splunk-org-access-token>`` parameters to this command.
51+
4952
.. code-block:: shell
5053
5154
splunk-rum android upload \
@@ -54,7 +57,10 @@ Uploads for production builds
5457
[optional-parameters]
5558
5659
* Run the ``upload-with-manifest`` command with the path to the application's merged or packaged ``AndroidManifest.xml`` file, along with path to the mapping file. Be sure to include the correct manifest, which is the one that's created when your application is built, and is located in the build output directory:
57-
60+
61+
.. note::
62+
If you didn't set the ``SPLUNK_REALM`` and ``SPLUNK_ACCESS_TOKEN`` environment variables, you must also add the ``--realm <value>`` and ``--token <your-splunk-org-access-token>`` parameters to this command.
63+
5864
.. code-block:: shell
5965
6066
splunk-rum android upload-with-manifest \

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,15 @@ Option 1: Use the splunk-rum CLI
3939

4040
#. Verify that your production build tool is configured to generate source maps.
4141
#. Run the production build for your project.
42-
#. Verify that your production bundles and source maps were written to the same output directory.
42+
#. Verify that your production bundles and source maps were written to the same output directory:
43+
44+
For example, if the output directory was ``./dist``, run ``ls dist`` and verify that both the ``.js`` and ``.js.map`` files were created:
45+
46+
.. code-block:: bash
47+
48+
$ ls ./dist
49+
mainBundle.js
50+
mainBundle.js.map
4351
4452
#. Find all source map/minified file pairs in the directory you specify, compute a source map ID for each pair, and inject that source map ID into each minified file as a code snippet:
4553

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,13 @@ To upload dSYMs use the ``splunk-rum`` CLI as follows.
5555

5656
#. Upload your application's dSYMs:
5757

58+
.. note::
59+
If you didn't set the ``SPLUNK_REALM`` and ``SPLUNK_ACCESS_TOKEN`` environment variables, you must also add the ``--realm <value>`` and ``--token <your-splunk-org-access-token>`` parameters to this command.
60+
61+
5862
.. code-block:: bash
5963
60-
splunk-rum ios upload --path <path-to-dSYMs>
64+
splunk-rum ios upload --path <path-to-dSYMs> [optional-parameters]
6165
6266
#. (Optional) Verify that your uploads succeeded:
6367

0 commit comments

Comments
 (0)