All Products
Search
Document Center

Application Real-Time Monitoring Service:Comparison between RUM and Browser Monitoring

Last Updated:Sep 27, 2024

The Real User Monitoring (RUM) and Browser Monitoring sub-services of Application Real-Time Monitoring Service (ARMS) allow you to monitor the performance of applications deployed in different terminals from the following aspects, such as page loading and network request duration. Compared with Browser Monitoring, the fully upgraded RUM sub-service supports more terminals and more flexible data visualization.

Supported application types

Application type

Browser Monitoring

RUM

Web or HTML5 application

支持

支持

Mini program

支持

支持

iOS app (including hybrid app developed through Flutter and React Native)

打叉

支持

Android app (including hybrid app developed through Flutter and React Native)

打叉

支持

Windows app

打叉

支持

macOS app

打叉

支持

Feature comparison

Feature

Browser Monitoring

RUM

User statistics

Supported.

Supported.

Session trace

Monitors session traces by page.

Monitors the traces of page loading, resource requests, user behavior events, and custom events.

Page statistics

Provides core page-specific metrics, such as page views (PVs), loading duration, First Paint, and DOM Ready Time.

Provides Web Vitals metrics in addition to key page-specific metrics.

Resource statistics (including API requests)

  • Supports collection of API request duration, the number of requests, request status, and the number of resource errors.

  • Supports end-to-end tracing based on the self-developed Eagle-eye Trace protocol.

  • Supports collection of resource information about various resources (such as JS, CSS, Image, Fetch, and XHR), including the duration, the number of loading times, and status.

  • Supports the configurations of request headers, parameters, and response headers for API requests.

  • Supports end-to-end tracing based on the open source OpenTelemetry and SkyWalking tracing protocols.

Exception statistics

JS errors: collects the number of JS errors, error rates, and error stacks.

  • JS errors: collects the number of JS errors, error rates, and error stacks.

  • White screen data: collects the proportion of white screens and displays screenshots taken when white screens occurred.

Custom statistics

Monitors custom events.

  • Monitors custom events.

  • Monitors custom exceptions.

  • Monitors custom data.

Data flexibility

Stores data in Simple Log Service (SLS) and supports flexible query and analysis.

  • Stores data in SLS and supports flexible query and analysis.

  • Data exploration: provides metric analysis capabilities with a variety of preset dimensions.

Visualization

Supports data visualization based on custom dimensions in the ARMS console.

  • Supports data visualization based on custom dimensions in the ARMS console.

  • Provides preset Grafana dashboards.

  • Provides custom Grafana dashboards.

Cost comparison

Billing rules of Browser Monitoring

For example, fee in the Chinese mainland is calculated based on the following formula: [PVs + Number of reported API calls × 0.1]/1000 × USD 0.04140.

For more information, see Billing.

Billing rules of RUM

You are charged based on the observability capacity units (OCUs). The unit price is fixed and bills are settled on a daily basis. For example, the unit price in the China (Hangzhou) region is USD 0.023 per OCU.

One OCU can be used for a certain number of sessions:

  • Web and HTML5 applications: 200 sessions = 1 OCU

  • Mini programs: 100 sessions = 1 OCU

  • Mobile apps: 200 sessions = 1 OCU

For more information, see Billing.