Skip to main content

​
Overview

A RUM application is a container for frontend performance monitoring data, used to collect, store, and analyze real user experience data from frontend applications. An application represents a monitored frontend project, which can be a website, mobile app, or single-page application.
We recommend creating RUM applications based on business systems or applications, such as: official website, e-commerce store, admin dashboard, etc.
Each application has its own unique applicationId and clientToken, used to identify data sources and ensure data security. After the application is created, you need to integrate the SDK into your frontend code to start data collection and monitoring.

​
Application Permissions

To meet the data security requirements of different business scenarios, RUM applications provide flexible access level settings:
Access LevelVisibilityApplicable Scenarios
PublicVisible to all users in the account, can view data and handle IssuesGeneral business applications
PrivateOnly visible to creator, account administrator, and owner accountSensitive business data
In private applications, if other members need to view content, they can be temporarily authorized to access it by sharing the incident link.

​
Create Application

RUM Application Creation Interface
You can quickly create an application through the RUM product guide page:
1

Select Application Type

Select the frontend technology type corresponding to the application, currently supporting JavaScript (JS)、Android、iOS.
2

Set Management Team

Specify the management team for this application.
Team members have full operational permissions for this application, non-team members only have read-only access to the configuration of this application.
3

Configure Geo-information

By default, automatic collection of user geo-location data is enabled. To disable automatic collection of client IP or geo-location data, turn off the geo-information collection switch.See Data Collection.
4

Configure Alerts

By default, alert notifications are automatically enabled to facilitate timely handling of errors.See Issue Alerts.

​
SDK Configuration

You can modify parameters and preview the initialization code in real-time in Application Configuration > SDK Configuration to quickly integrate the SDK. The console provides detailed integration guides for each platform:
  • JavaScript (Web): After configuring parameters like service name, preview the flashcatRum.init() initialization code in real-time
  • Android: Shows complete integration steps including adding Gradle dependencies (cloud.flashcat:dd-sdk-android-core and cloud.flashcat:dd-sdk-android-rum), initializing the SDK in Application.onCreate() with RUM enabled, and optional WebView tracking integration
  • iOS: Shows complete integration steps including adding Swift Package Manager dependency (fc-sdk-ios, from version 0.3.0), initializing the SDK in AppDelegate.didFinishLaunchingWithOptions with RUM enabled, and optional WebView tracking integration
Each platform’s SDK configuration page automatically fills in the current application’s applicationId and clientToken, so you can copy the code directly into your project.
Modifying SDK configuration in application management will not take effect in real-time on integrated clients. All configuration changes need to be updated in your frontend code and redeployed to take effect.

​
Service Definition

A service is an independent, deployable code repository that maps to a set of pages.
If your application is built as a whole, your RUM application only needs one service name.
flashcatRum.init({
  applicationId: 'YOUR_APP_ID',
  clientToken: 'YOUR_CLIENT_TOKEN',
  service: 'my-web-app'  // Single service name
});

​
Tracing Settings

Tracing settings allow you to link RUM data with your backend distributed tracing system, enabling full-chain observability from frontend user operations to backend service calls.
1

Enable Tracing

In the “Tracing Settings” tab of the application details, turn on the Tracing switch. If a redirect link has not been configured yet, the system will prompt you to set up the link first.
2

Configure Redirect Link

Set the redirect link for your tracing system. You can use the ${trace_id} variable in the link, which the system will automatically replace with the actual Trace ID when redirecting.For example: https://your-tracing-system.com/trace/${trace_id}
The redirect link must start with http:// or https://.
Once configured, clicking a Trace ID link opens the trace details in a popup within the current page, without leaving the RUM Explorer, allowing you to quickly troubleshoot frontend-backend correlation issues.

​
Privacy Settings

Privacy settings allow you to control the scope of user privacy data collected by the RUM SDK, meeting data compliance requirements for different regions.
SettingDescriptionAssociated Fields
Geo-location InformationControls whether to collect user country, province, city, and other geographic information@geo_country, @geo_province, @geo_city
IP AddressControls whether to collect user IPv4 and IPv6 addresses@geo_ip_v4, @geo_ip_v6
After disabling geo-location or IP address collection, the related filter and analysis dimensions will no longer be available. Please adjust carefully based on your business requirements and compliance needs.

​
Delete Application

If you no longer need an application, you can find the delete button at the bottom of the “Basic Info” tab in the application details.
After deleting an application:
  • No new events will be received
  • The application’s Client Token will be immediately revoked
  • Previously collected RUM event data can still be manually exported, or you can contact the support team to restore the deleted application
This operation requires the RUM Application Delete permission.

​
Next Steps

SDK Integration Guide

Learn how to integrate RUM SDK

Advanced Configuration

Learn about advanced configuration options for the SDK

Analytics Dashboard

View and analyze RUM data