Real User Monitoring Solution for Web and Mobile

What RUM should answer

Which users were affected, where, and by which part of the journey?

RUM should show the affected page, view, action, device, browser or app version, geography, and session, then preserve enough correlation context to test whether the cause sits in the frontend, network, API, backend service, or dependency.

Solution overview

Guance RUM captures documented browser and mobile telemetry through the relevant SDK. Teams can segment experience by user and technical dimensions, inspect errors and resources, and continue into backend evidence when tracing and correlation are configured.

Operational challenges

Averages hide affected users: Aggregate server health can look normal while a region, device, version, or journey is failing.

Frontend and backend timelines diverge: Browser errors, network requests, traces, and releases often live in separate views.

Reproduction is unreliable: Intermittent client failures depend on real devices, networks, sessions, and user actions.

Privacy needs deliberate design: Identity, attributes, replay, and retention must follow data-minimisation and access policies.

How Guance supports the workflow

Instrument the actual client: Use the documented Web or mobile SDK and verify environments, versions, sampling, and data scope.

Segment the affected experience: Compare pages, views, actions, devices, browsers, apps, versions, regions, and user groups.

Connect frontend and backend evidence: Use configured request and trace correlation to continue from a user action into APIs and services.

Operate with privacy controls: Limit captured attributes, configure masking and replay deliberately, and control access and retention.

Investigation workflows

Prioritise issues by real user impact

Start with affected journeys: Compare experience and error signals by page, action, region, device, and version instead of relying only on global averages.

Follow a slow action into the backend

Keep correlation configured: Connect client requests to API and trace evidence, then inspect related logs and dependencies.

Investigate hard-to-reproduce client errors

Preserve session context: Use the available session, error, resource, and replay evidence within the configured privacy boundary.

Continue exploring

Synthetic monitoring

Add scheduled API and browser checks for controlled coverage.

Real-time business monitoring

Connect user journeys with service and business indicators.

Log management and analytics

Search frontend, gateway, and backend log evidence.

Frequently asked questions

What data can RUM collect?

Documented Web and mobile SDKs can report supported views, actions, resources, errors, performance, sessions, device and environment attributes. Exact fields and availability depend on the SDK, platform, version, and configuration.

How do I move from a slow page to a backend problem?

Configure the supported request and trace correlation path, then use shared service, environment, version, and request context to inspect the corresponding API, trace, log, and infrastructure evidence.

How should Session Replay be used responsibly?

Enable it only for a defined troubleshooting need, configure privacy and masking controls, minimise captured data, restrict access, and set retention according to your policy and applicable requirements.

Is RUM the same as synthetic monitoring?

No. RUM measures traffic from real users and their environments. Synthetic monitoring runs controlled checks on a schedule. Teams often use both to compare actual impact with repeatable tests.