base-14 · nimishgj · Jul 7, 2026 · Jul 9, 2026 · Jul 9, 2026 · Jul 10, 2026
diff --git a/docs/instrument/mobile/rum-opentelemetry.md b/docs/instrument/mobile/rum-opentelemetry.md
diff --git a/docs/operate/rum/_category_.json b/docs/operate/rum/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "RUM",
+  "position": 8,
+  "link": {
+    "type": "generated-index",
+    "title": "Mobile Real User Monitoring with RUM",
+    "description": "Monitor real mobile user experience with RUM in base14 Scout. Track crash-free rates, app startup performance, screen load times, network calls, and session timelines for your Flutter applications."
+  }
+}
diff --git a/docs/operate/rum/anr.md b/docs/operate/rum/anr.md
@@ -0,0 +1,147 @@
+---
+title: RUM ANR
+sidebar_label: ANR
+sidebar_position: 5
+description:
+  Detect Application Not Responding (ANR) events in your Flutter apps with RUM
+  in base14 Scout. Group frozen-UI events by screen and analyze thread state
+  to find what blocked the main thread.
+keywords:
+  [
+    rum,
+    anr,
+    application not responding,
+    frozen ui,
+    mobile performance,
+    jank,
+    base14,
+    scout,
+  ]
+---
+
+The **ANR** (Application Not Responding) tab tracks frozen-UI events - periods
+where the app's main thread was blocked and unresponsive to user input -
+grouped by the screen where they occurred.
+
+![ANR](/img/rum/anr/list.png)
+
+---
+
+## ANR List
+
+### Table Columns
+
+| Column | Description |
+| ------ | ----------- |
+| **Screen** | The screen the ANR occurred on (or `unknown` if it couldn't be attributed to a screen) |
+| **Occurrences** | Total times an ANR was recorded for this screen |
+| **Sessions** | Number of distinct sessions affected |
+| **Users** | Number of distinct users affected |
+| **App Version** | Version most recently associated with this screen's ANRs |
+| **Last Seen** | When an ANR was last observed on this screen |
+
+The **Errors** filter category (`error.message`, `crash.kind`, `crash.type`,
+`crash.last_screen`) is available here too, alongside the shared
+[Filters](./getting-started.md#filters) sidebar.
+
+---
+
+## ANR Details
+
+Click a screen's ANR group to open the detail view, scoped to a specific
+occurrence.
+
+### Summary Stats
+
+![ANR title, badges, and Total Occurrences/Affected Users/Affected Sessions stat cards](/img/rum/anr/summary-stats.png)
+
+**Total Occurrences**, **Affected Users**, and **Affected Sessions** for the
+selected screen and time range.
+
+### Occurrence Breakdown
+
+![Occurrences by App Version, OS Version, and Device Model charts](/img/rum/anr/occurrence-breakdown.png)
+
+Here - unlike the list page - occurrences are broken down **by App
+Version**, **by OS Version**, and **by Device Model**, each with the usual
+multi-line-chart-plus-table pattern. This is where you find out which builds
+and devices freeze most often for this screen.
+
+### Attributes
+
+![Attributes panel showing app.*, device.*, session.*, and other grouped attributes](/img/rum/anr/attributes.png)
+
+A grouped attribute panel:
+
+| Group | Example attributes |
+| ----- | ------------------- |
+| `app.*` | `app.build`, `app.bundle_id`, `app.version` |
+| `crash.*` | `crash.type` (`anr`) |
+| `device.*` | `device.brand`, `device.manufacturer`, `device.model.name`, `device.locale`, `device.orientation`, `device.type` |
+| `error.*` | `error.message` (for example "Application Not Responding") |
+| `os.*` | `os.name`, `os.version`, `os.build` |
+| `screen.*` | `screen.name` |
+| `service.*` | `service.name`, `service.version` |
+| `session.*` | `session.id`, `session.sample_rate`, `session.start_time`, `session.type` |
+| `telemetry.sdk.*` | `telemetry.sdk.name`, `telemetry.sdk.language`, `telemetry.sdk.version` |
+| `user.*` | `user.anonymous_id` |
+
+### Stack Trace (Main Thread) and All Threads
+
+![Stack Trace (Main Thread) frames and All Threads list with state badges and frame counts](/img/rum/anr/stack-trace.png)
+
+The **Stack Trace (Main Thread)** panel shows where the main thread was
+blocked. Below it, **All Threads** lists every thread with its state
+(`RUNNABLE`, `TIMED_WAITING`, `WAITING`) and frame count - expand a thread to
+see its own stack. This is how you find which thread was holding the lock
+the main thread was waiting on.
+
+As with [crash stack traces](./crashes.md#stack-trace-and-translated-report),
+frames resolve to readable file, line, and symbol names once the matching
+debug artifacts for that build have been uploaded.
+
+### Breadcrumbs
+
+![Breadcrumbs table with Time, Type, and Message columns](/img/rum/anr/breadcrumbs.png)
+
+A chronological table (**Time**, **Type**, **Message**) of lifecycle,
+navigation, and tap events leading up to the freeze.
+
+### Affected Devices and Affected Users
+
+![Affected Devices and Affected Users tables](/img/rum/anr/affected.png)
+
+Same structure as [Crashes](./crashes.md#affected-devices-and-affected-users).
+
+Use **View Session Timeline** to jump into the full
+[session](./sessions.md) where the ANR occurred.
+
+---
+
+## Use Cases
+
+### Finding the Worst Frozen Screen
+
+1. Sort the **ANR List** by **Occurrences**
+2. Open the top screen and check **Occurrences by App Version** to see if
+   it's a regression in a specific release
+3. Use **All Threads** to identify what was blocking the main thread (a
+   `RUNNABLE` thread holding a lock the main thread is `WAITING` on is a
+   common culprit)
+
+### Confirming a Fix Reduced Freezes
+
+1. Open the screen's ANR group
+2. Filter to the version containing the fix
+3. Confirm **Occurrences by App Version** drops for that version
+
+---
+
+## Related Guides
+
+- [Getting Started](./getting-started.md) - Interface layout and shared filters
+- [Overview](./overview.md) - ANR duration trend alongside crashes and sessions
+- [Screens](./screens.md) - Per-screen performance, including jank and load time
+- [Sessions](./sessions.md) - Full session timeline for a specific occurrence
+- [traceX](../tracex/index.md) - Distributed tracing explorer
+- [logX](../logx/index.md) - Log explorer with trace correlation
diff --git a/docs/operate/rum/crashes.md b/docs/operate/rum/crashes.md
@@ -0,0 +1,177 @@
+---
+title: RUM Crashes
+sidebar_label: Crashes
+sidebar_position: 3
+description:
+  Investigate mobile app crashes with RUM in base14 Scout. Group crashes,
+  view symbolicated stack traces and translated crash reports, and see
+  affected devices, users, app versions, and OS versions.
+keywords:
+  [
+    rum,
+    crashes,
+    crash reporting,
+    symbolication,
+    stack trace,
+    native crash,
+    mobile crash,
+    base14,
+    scout,
+  ]
+---
+
+The **Crashes** tab groups individual crash events into deduplicated crash
+groups so you can prioritize by impact instead of triaging one crash at a
+time.
+
+![Crashes List](/img/rum/crashes/list.png)
+
+---
+
+## Crash List
+
+Filter chips at the top let you toggle between crash **Kind** values; the
+table below lists every crash group ranked by occurrence.
+
+### Table Columns
+
+| Column | Description |
+| ------ | ----------- |
+| **Title** | The crash's grouping title (exception name or synthetic label) |
+| **Kind** | High-level classification badge for the crash, for example `Native` or `JS Error` |
+| **Type** | More specific classification, for example `native_signal`, `mach`, `jvm_exception`, `jvm_crash`, `exit_self`, `excessive_resources`, `user_requested`, `unknown` |
+| **Occurrences** | Total times this crash group has been seen |
+| **Sessions** | Number of distinct sessions affected |
+| **Users** | Number of distinct users affected |
+| **App Version** | Version most recently associated with the group |
+| **Last Seen** | When the crash group was last observed |
+
+Sort by **Occurrences** to prioritize the crashes affecting the most sessions
+first.
+
+---
+
+## Crash Details
+
+Click a crash group to open the detail view, scoped to a specific occurrence
+(pick a different occurrence from the dropdown at the top).
+
+### Summary Stats
+
+![Crash title, Kind/Type badges, and Total Occurrences/Affected Users/Affected Sessions stat cards](/img/rum/crashes/summary-stats.png)
+
+**Total Occurrences**, **Affected Users**, and **Affected Sessions** for the
+selected crash group and time range.
+
+### Occurrence Breakdown
+
+![Occurrences by App Version, OS Version, and Device Model charts](/img/rum/crashes/occurrence-breakdown.png)
+
+Three charts pair a multi-line time series with a Name / Min / Mean / Max
+table, showing how many occurrences hit each App Version, OS Version, and
+Device Model:
+
+- **Occurrences by App Version**
+- **Occurrences by OS Version**
+- **Occurrences by Device Model**
+
+### Attributes
+
+![Attributes panel showing app.*, crash.*, and other grouped attributes](/img/rum/crashes/attributes.png)
+
+A scrollable panel with the full attribute set captured at crash time. A
+small `app.*` group sits above a single large `crash.*` block - the raw
+crash report, flattened - followed by the same resource attributes you see
+on other detail pages:
+
+| Group | Example attributes |
+| ----- | ------------------- |
+| `app.*` | `app.build`, `app.bundle_id`, `app.launch_id`, `app.version` |
+| `crash.*` (app state) | `crash.app_id`, `crash.app_version`, `crash.app_in_foreground`, `crash.app_start_time`, `crash.app_sessions_since_launch` |
+| `crash.*` (binary/build) | `crash.binary_cpu_type`, `crash.build_configuration`, `crash.build_type` |
+| `crash.*` (process/report) | `crash.pid`, `crash.parent_pid`, `crash.process_name`, `crash.report_id`, `crash.report_type` |
+| `crash.*` (signal/memory/threads) | `crash.signal`, `crash.signal_code`, `crash.memory_usable_bytes`, `crash.thread_count` |
+| `crash.*` (type/timing) | `crash.type`, `crash.timestamp`, `crash.time_zone`, `crash.translated` |
+| `device.*` | `device.model.name`, `device.locale`, `device.timezone`, `device.is_physical` |
+| `host.*` | `host.arch`, `host.name`, `host.os.name`, `host.processors` |
+| `os.*` | `os.name`, `os.version`, `os.build`, `os.type` |
+| `process.*` | `process.executable.name`, `process.num_threads`, `process.runtime.name`, `process.runtime.version` |
+| `service.*` / `session.*` | `service.name`, `service.version`, `session.id`, `session.start_time` |
+
+Use **Search attributes** in the sidebar to jump straight to a specific key
+instead of scrolling.
+
+### Stack Trace and Translated Report
+
+![Stack Trace (Native) frames and Translated Report text block](/img/rum/crashes/stack-trace.png)
+
+The **Stack Trace (Native)** panel shows the raw symbolicated frames. Below
+it, **Translated Report** renders the full platform crash report (process
+info, exception type and codes, thread and register state, binary images) as
+plain text, with a **Copy** button so you can paste it straight into an issue
+tracker or share it with a native engineer.
+
+Frames only resolve to readable file, line, and symbol names once you've
+uploaded the matching debug artifacts for that build (dSYM, Dart symbols,
+NDK symbols, ProGuard mappings) - see
+[scout artifacts upload](../../scout-cli/scout-access/artifacts.md). Without
+an uploaded artifact, frames show raw addresses or obfuscated names instead.
+
+### Breadcrumbs
+
+![Breadcrumbs table with Time, Type, and Message columns](/img/rum/crashes/breadcrumbs.png)
+
+A chronological table (**Time**, **Type**, **Message**) of what the user was
+doing right before the crash: session start, screen navigation, taps, long
+tasks, and UI hangs. Use it to reproduce the exact sequence that triggered the
+crash.
+
+### Affected Devices and Affected Users
+
+![Affected Devices and Affected Users tables](/img/rum/crashes/affected.png)
+
+- **Affected Devices** - device model, architecture, OS, app version, and
+  occurrence count
+- **Affected Users** - user identifier, session count, crash count, and last
+  hit
+
+Use **View Session Timeline** to jump from a specific occurrence into the
+full [session](./sessions.md) where it happened.
+
+---
+
+## Use Cases
+
+### Triaging After a Release
+
+1. Filter by the new **App Version**
+2. Sort the **Crash List** by **Occurrences**
+3. Open the top crash group and check **Occurrences by App Version** to
+   confirm it's new (or worse) in this release
+4. Use the **Translated Report** and **Breadcrumbs** to hand a native
+   engineer a reproducible sequence
+
+### Verifying a Fix
+
+1. Open the crash group you fixed
+2. Filter to the version containing the fix
+3. Confirm **Occurrences by App Version** shows zero (or near-zero) for that
+   version
+
+### Scoping a Device-Specific Crash
+
+1. Sort the **Crash List** by **Occurrences**
+2. Open a crash group and check **Occurrences by Device Model** - a spike
+   concentrated on one model points at a device-specific bug (memory limits,
+   OS fork behavior)
+
+---
+
+## Related Guides
+
+- [Getting Started](./getting-started.md) - Interface layout and shared filters
+- [Overview](./overview.md) - Crash trends alongside sessions and ANR
+- [Errors](./errors.md) - Non-fatal errors, for issues that don't crash the app
+- [Sessions](./sessions.md) - Full session timeline for a specific occurrence
+- [traceX](../tracex/index.md) - Distributed tracing explorer
+- [logX](../logx/index.md) - Log explorer with trace correlation