Splunk Observability Mobile RUM
Prerequisites
| Tool or access |
Purpose |
Verify |
| Bash and Python 3 |
Run bundled setup and validation helpers |
bash --version && python3 --version |
| Required product/platform access |
Inspect or configure the selected target |
Complete the documented preflight |
| Credential files for live modes |
Keep secrets out of chat |
Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Instrumenting mobile apps with Splunk RUM, preparing Mobile Session Replay, preparing mobile-side Digital
Experience Analytics (DXA), validating RUM-to-APM linking, or rendering mobile source patches. Do not use for
AppDynamics EUM or.
- Preview and review the splunk observability mobile rum setup workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Examples
Inspect the supported setup modes before selecting one:
bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed
without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/splunk-observability-mobile-rum-setup/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the
skill supports them; help exits without mutation.
Troubleshooting
| Issue |
Cause |
Resolution |
| Preflight fails |
A required tool or access path is missing |
Resolve it before rendering or applying |
| Rendered assets are incomplete |
Required non-secret inputs are absent |
Complete intake and render again |
| Apply is blocked |
Review, credentials, or explicit acceptance is missing |
Use the documented handoff |
| Validation is incomplete |
Live evidence is unavailable |
Record the gap and keep completion open |
This skill configures Splunk Observability Cloud Mobile RUM, separate from
Kubernetes Browser RUM injection and AppDynamics EUM. It is render-first:
snippets and runbooks are the default output; patch files are optional; app
source is changed only when --apply-patches --accept-mobile-rum-source-edit
is explicitly used. Use it as the mobile instrumentation handoff when a Digital
Experience Analytics (DXA) request needs supported iOS or Android RUM agents,
user tracking, readable stack traces, or Mobile Session Replay.
Scope
- Native iOS and iPadOS 15+ with the Splunk iOS agent.
- Native Android with Maven Central dependencies, API 24+ default runtime,
desugaring, network/crash/ANR/slow-rendering/interaction/lifecycle modules,
mapping upload, and WebView bridge snippets.
- React Native 0.75.0+ and React 18.2.0+ for bare apps and Expo development
builds, with native-side dSYM/mapping handoffs.
- Flutter 3.32.0+ and Dart 3.8.0+ with
splunk_otel_flutter, native-side
dSYM/mapping handoffs, route/manual instrumentation, and WebView handoff.
- Session Replay behind
--accept-session-replay-enterprise.
- RUM-to-APM linking validation for
Server-Timing: traceparent;desc="00-<32 hex>-<16 hex>-01".
Version Pins
Every default below was verified against its upstream registry on 2026-08-20 and
is the current release on that date. No pin is knowingly behind upstream.
| Component |
Default |
| iOS agent |
2.4.1 |
| Android agent |
2.3.3 |
| Android Gradle plugins |
2.3.3 |
| React Native agent |
1.2.0 |
| React Native Session Replay |
1.2.0 |
| Flutter agent |
1.2.0 |
| Flutter Session Replay |
1.2.0 |
Flutter agent and Flutter Session Replay must stay on the same minor line:
1.2.0 pins both platform interfaces to >=1.2.0 <1.3.0.
Deployment environment attribute rename
iOS 2.4.1 and Android 2.3.2 renamed the deployment environment resource
attribute from deployment.environment to deployment.environment.name. Both
agents emit only the new key; there is no transitional dual-emit. Dashboards,
detectors, and saved searches that filter or group mobile RUM data on the old
key go blank as soon as an app ships these pins. While a fleet straddles the
rename, accept both keys rather than switching outright.
The Swift and Kotlin configuration property is still named
deploymentEnvironment, so rendered initialization snippets are unaffected.
The renderer rejects latest, +, ranges, wildcard, and otherwise unpinned
versions unless --allow-latest-version is set.
Workflow
Render snippets:
bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \
--render \
--spec skills/splunk-observability-mobile-rum-setup/template.example
Review splunk-observability-mobile-rum-rendered/:
runbook.md
preflight-report.md
- platform snippet directories
version-lock.json
- dSYM/mapping upload helpers
- Browser RUM and backend auto-instrumentation handoff scripts
Optionally render source patches:
bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \
--render-patches \
--spec mobile-rum.yaml
Optionally apply source patches after review:
bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \
--apply-patches \
--accept-mobile-rum-source-edit \
--spec mobile-rum.yaml
Validate static output and optional RUM-to-APM response headers:
bash skills/splunk-observability-mobile-rum-setup/scripts/validate.sh \
--output-dir splunk-observability-mobile-rum-rendered \
--check-server-timing https://api.example.com/health
Safety Rules
- Never pass raw tokens with CLI flags.
--rum-token, --access-token,
--token, --bearer-token, --api-token, --o11y-token, --sf-token,
--hec-token, --platform-hec-token, and --api-key are rejected.
- RUM tokens are client-exposed after release, but this skill still refuses to
commit or render raw token values into tracked source. Use token references,
build-time config, CI secrets, or mobile platform secret delivery.
- Server-to-server dSYM and Android mapping upload helpers use
SPLUNK_O11Y_TOKEN_FILE; they do not accept token literals.
source_mode: apply-patches requires --accept-mobile-rum-source-edit.
- Session Replay requires
--accept-session-replay-enterprise and reviewed
masking rules.
References
Read the platform file that matches the app being instrumented:
- references/ios.md
- references/android.md
- references/react-native.md
- references/flutter.md
- references/privacy-session-replay.md
- references/apm-linking.md
Hand-offs
Out Of Scope
- AppDynamics EUM, BRUM, MRUM, or AppDynamics Session Replay.
- Kubernetes Browser RUM HTML injection for web frontends.
- Uploading React Native JS bundle source maps as a Mobile RUM artifact.
Browser source maps only apply to WebView pages instrumented with Browser RUM.
- Running mobile app builds or live Splunk uploads by default.
1---2name: splunk-observability-mobile-rum-setup3description: "Use when instrumenting mobile apps with Splunk RUM, preparing Mobile Session Replay, preparing mobile-4 side Digital Experience Analytics (DXA), validating RUM-to-APM linking, or rendering mobile source5 patches. Do not use for AppDynamics EUM or Kubernetes Browser RUM injection. Render, validate, and6 optionally apply guarded source patches for Splunk Observability Cloud Mobile RUM and mobile-side7 Digital Experience Analytics (DXA) prerequisites across native iOS, native Android, React Native, and8 Flutter apps. Covers pinned agent versions, Session Replay enterprise gating, privacy controls, release9 attributes, dSYM and Android mapping upload helpers, React Native and Flutter native artifact handoffs,10 WebView Browser RUM bridge snippets, and RUM-to-APM Server-Timing traceparent validation."11compatibility: "No direct Splunk Platform runtime dependency. This workflow can be used alongside Splunk Cloud Platform 10.5.2605 through its documented external APIs or handoffs."12metadata:13 source: https://skillmd.com/skills/chambear2809/splunk-observability-mobile-rum-setup14 splunk_cloud_10_5: "not-applicable"15 compatibility_verified: "2026-08-20"16---1718# Splunk Observability Mobile RUM1920## Prerequisites2122| Tool or access | Purpose | Verify |23|---|---|---|24| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |25| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |26| Credential files for live modes | Keep secrets out of chat | Verify paths only |2728## Workflow Overview2930```text31┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐32│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │33└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘34```3536## When to Activate3738- Instrumenting mobile apps with Splunk RUM, preparing Mobile Session Replay, preparing mobile-side Digital39 Experience Analytics (DXA), validating RUM-to-APM linking, or rendering mobile source patches. Do not use for40 AppDynamics EUM or.41- Preview and review the splunk observability mobile rum setup workflow before any live apply phase.42- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4344## Examples4546Inspect the supported setup modes before selecting one:4748```bash49bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh --help50```5152Expected output: usage, supported modes, and required arguments are displayed53without changing the target environment.5455Inspect validation modes before running completion checks:5657```bash58bash skills/splunk-observability-mobile-rum-setup/scripts/validate.sh --help59```6061Expected output: offline, live, and completion options are displayed when the62skill supports them; help exits without mutation.6364## Troubleshooting6566| Issue | Cause | Resolution |67|---|---|---|68| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |69| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |70| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |71| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7273This skill configures **Splunk Observability Cloud Mobile RUM**, separate from74Kubernetes Browser RUM injection and AppDynamics EUM. It is render-first:75snippets and runbooks are the default output; patch files are optional; app76source is changed only when `--apply-patches --accept-mobile-rum-source-edit`77is explicitly used. Use it as the mobile instrumentation handoff when a Digital78Experience Analytics (DXA) request needs supported iOS or Android RUM agents,79user tracking, readable stack traces, or Mobile Session Replay.8081## Scope8283- Native iOS and iPadOS 15+ with the Splunk iOS agent.84- Native Android with Maven Central dependencies, API 24+ default runtime,85 desugaring, network/crash/ANR/slow-rendering/interaction/lifecycle modules,86 mapping upload, and WebView bridge snippets.87- React Native 0.75.0+ and React 18.2.0+ for bare apps and Expo development88 builds, with native-side dSYM/mapping handoffs.89- Flutter 3.32.0+ and Dart 3.8.0+ with `splunk_otel_flutter`, native-side90 dSYM/mapping handoffs, route/manual instrumentation, and WebView handoff.91- Session Replay behind `--accept-session-replay-enterprise`.92- RUM-to-APM linking validation for93 `Server-Timing: traceparent;desc="00-<32 hex>-<16 hex>-01"`.9495## Version Pins9697Every default below was verified against its upstream registry on 2026-08-20 and98is the current release on that date. No pin is knowingly behind upstream.99100| Component | Default |101| --- | --- |102| iOS agent | `2.4.1` |103| Android agent | `2.3.3` |104| Android Gradle plugins | `2.3.3` |105| React Native agent | `1.2.0` |106| React Native Session Replay | `1.2.0` |107| Flutter agent | `1.2.0` |108| Flutter Session Replay | `1.2.0` |109110Flutter agent and Flutter Session Replay must stay on the same minor line:111`1.2.0` pins both platform interfaces to `>=1.2.0 <1.3.0`.112113### Deployment environment attribute rename114115iOS `2.4.1` and Android `2.3.2` renamed the deployment environment resource116attribute from `deployment.environment` to `deployment.environment.name`. Both117agents emit only the new key; there is no transitional dual-emit. Dashboards,118detectors, and saved searches that filter or group mobile RUM data on the old119key go blank as soon as an app ships these pins. While a fleet straddles the120rename, accept both keys rather than switching outright.121122The Swift and Kotlin configuration property is still named123`deploymentEnvironment`, so rendered initialization snippets are unaffected.124125The renderer rejects `latest`, `+`, ranges, wildcard, and otherwise unpinned126versions unless `--allow-latest-version` is set.127128## Workflow1291301. Render snippets:131132 ```bash133 bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \134 --render \135 --spec skills/splunk-observability-mobile-rum-setup/template.example136 ```1371382. Review `splunk-observability-mobile-rum-rendered/`:139 - `runbook.md`140 - `preflight-report.md`141 - platform snippet directories142 - `version-lock.json`143 - dSYM/mapping upload helpers144 - Browser RUM and backend auto-instrumentation handoff scripts1451463. Optionally render source patches:147148 ```bash149 bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \150 --render-patches \151 --spec mobile-rum.yaml152 ```1531544. Optionally apply source patches after review:155156 ```bash157 bash skills/splunk-observability-mobile-rum-setup/scripts/setup.sh \158 --apply-patches \159 --accept-mobile-rum-source-edit \160 --spec mobile-rum.yaml161 ```1621635. Validate static output and optional RUM-to-APM response headers:164165 ```bash166 bash skills/splunk-observability-mobile-rum-setup/scripts/validate.sh \167 --output-dir splunk-observability-mobile-rum-rendered \168 --check-server-timing https://api.example.com/health169 ```170171## Safety Rules172173- Never pass raw tokens with CLI flags. `--rum-token`, `--access-token`,174 `--token`, `--bearer-token`, `--api-token`, `--o11y-token`, `--sf-token`,175 `--hec-token`, `--platform-hec-token`, and `--api-key` are rejected.176- RUM tokens are client-exposed after release, but this skill still refuses to177 commit or render raw token values into tracked source. Use token references,178 build-time config, CI secrets, or mobile platform secret delivery.179- Server-to-server dSYM and Android mapping upload helpers use180 `SPLUNK_O11Y_TOKEN_FILE`; they do not accept token literals.181- `source_mode: apply-patches` requires `--accept-mobile-rum-source-edit`.182- Session Replay requires `--accept-session-replay-enterprise` and reviewed183 masking rules.184185## References186187Read the platform file that matches the app being instrumented:188189- [references/ios.md](references/ios.md)190- [references/android.md](references/android.md)191- [references/react-native.md](references/react-native.md)192- [references/flutter.md](references/flutter.md)193- [references/privacy-session-replay.md](references/privacy-session-replay.md)194- [references/apm-linking.md](references/apm-linking.md)195196## Hand-offs197198- Browser RUM inside WebViews:199 [splunk-observability-k8s-frontend-rum-setup](../splunk-observability-k8s-frontend-rum-setup/SKILL.md)200- Backend response header enablement:201 [splunk-observability-k8s-auto-instrumentation-setup](../splunk-observability-k8s-auto-instrumentation-setup/SKILL.md)202- Dashboards:203 [splunk-observability-dashboard-builder](../splunk-observability-dashboard-builder/SKILL.md)204- Detectors:205 [splunk-observability-native-ops](../splunk-observability-native-ops/SKILL.md)206207## Out Of Scope208209- AppDynamics EUM, BRUM, MRUM, or AppDynamics Session Replay.210- Kubernetes Browser RUM HTML injection for web frontends.211- Uploading React Native JS bundle source maps as a Mobile RUM artifact.212 Browser source maps only apply to WebView pages instrumented with Browser RUM.213- Running mobile app builds or live Splunk uploads by default.