Skip to main content

FAQ

  • After configuration changes, it takes about 5 minutes to take effect due to server-side caching, and it applies only to new sessions.

  • Since many customers may not always provide a user ID, to facilitate queries, the user name field matches against: user ID / user name / device ID; the user ID field matches against: user ID / device ID.

  • Permission note: Which data is displayed in the page, action, and network request lists is determined by finding applications through resource domain tags and then retrieving the corresponding content, rather than directly locating pages, actions, or network requests via resource domain tags.

  • After upgrading to ONE 4.0.0, the request metrics used for health scoring are switched to business request metrics. Even if you roll back from ONE 4.0.0 to a previous version, the health scoring will still use business request metrics.

  • URL path special character configuration: applies to URL path processing for all event types in the RUM controller. Special characters listed are not truncated; otherwise, content after a special character would be discarded.

  • Protocol extension aggregation is fixed based on IP subnet. IP addresses are merged by subnet: IPv4 is merged to the /24 prefix (C segment), and IPv6 is merged to the first 64 bits. Example for IPv4: http://192.168.1.8/test/ becomes http://192.168.1.*/test/. Example for IPv6: http://[cdcd:910a:2222:5498:8475:1111:3900:2020]/test/ becomes http://[cdcd:910a:2222:5498::::]/test/.

  • Control text in user action naming rules: The control text collected by the SDK, after removing special characters \t and \n, if it exceeds 20 units (where 1 unit = 1 Chinese character, 1 English letter, or 1 punctuation mark), the control text field is skipped and other fields such as title are matched.

  • Device brand and device type are mapped based on SDK-collected content; the mapping table supports configuration modifications. If issues are found, please contact technical support for adjustments.

  • Country, province, city, district, and carrier are obtained by querying an IP database using the IP collected by the SDK. The IP database supports modifications. If issues are found, please contact technical support for adjustments.

  • Default dimension visibility for metrics: For endpoint application‑related metrics, the carrier dimension is not displayed by default. For page‑related metrics, the access method, city, and carrier dimensions are not displayed by default. For action‑related metrics, the device, access method, city, carrier, action method type, and control ID dimensions are not displayed by default. For network request‑related metrics, the operating system, action ID, and action name dimensions are not displayed by default. Display of these dimensions can be enabled via configuration. If needed, please contact technical support for adjustments.

  • RUM records store the specific carrier, but the carrier dimension in metrics defaults to only China Mobile, China Unicom, China Telecom, plus Other (all carriers other than these three are aggregated into "Other"). The specific carrier dimension in metrics can be enabled via configuration. If needed, please contact technical support for adjustments.

  • When the main frame and most resources have completed loading, the onload event is triggered, but LCP (Largest Contentful Paint) may finish painting after onload. In this case, the page fully loaded duration can be less than the LCP duration.

  • When above-the-fold content and resources have finished loading, but heavy JavaScript execution continues after onload with long tasks on the main thread, the page fully loaded duration can be less than the TTI (Time to Interactive) duration.

  • After modifying SDK‑related configurations, the changes only apply to new sessions; sessions already in progress continue to follow the previous logic.

  • When the list data contains 10,000 or more items, the data may become inaccurate. The current design queries 10,000 items first, then calculates certain metrics, performs sorting and pagination in code. Many metrics are computed in code and cannot be pushed into SQL for sorting and pagination. To improve accuracy, you can add filtering conditions to reduce the number of items in the list.

  • In cross‑origin scenarios, it may not be possible to achieve end‑to‑end traceability between RUM and APM.

  • RUM definition: By default, the URL path truncates content after the # (fragment). For example, for https://a.b.com/deploy#a/b, the URL path is extracted as deploy, not including #a/b. If you want the URL path to be deploy#a/b, you can add # to the configuration. Change from alt text to alt text This means that any character listed in the parameter value will not be truncated. Note that the comma , is used as a delimiter between different special characters.

  • Based on the provided glossary, the translation of the previous message is as follows:

  • Unique identifier for a application in RUM: Account ID, Environment ID, Application Name (corresponding to the Identification Name field of the data model)

  • Unique identifier for a page in RUM: Account ID, Environment ID, Page Type, Page Name (corresponding to the Identification Name field of the data model)

  • Unique identifier for an action in RUM: Account ID, Environment ID, Application ID, Action Name (corresponding to the Identification Name field of the data model)

  • Unique identifier for an request in RUM: Account ID, Environment ID, Protocol Extension Data Type, Request Source, Request Name (corresponding to the Identification Name field of the data model)

  • MiniProgram view and single-page detail pages do not support navigation-related recording

  • Alerts for Applications in RUM: If an alert rule selects a metric from the Application category in the predefined metric system, and groups by Application + other dimensions (which may be absent), then it is considered an Application alert; if a non-Application metric is selected and grouped by Application + other dimensions (which may be absent), it is not counted as an Application alert

  • Data Collection / Collection limit: Configuration is not supported for Web Applications

  • If both the frontend and backend use our Client SDK, end-to-end tracing is enabled by default

  • Data Processing / Application / Symbolic File Management: Uploads are supported only for Android, iOS, and HarmonyOS NEXT applications

  • Data Processing / Application / JS SourceMap Management: Uploads are supported only for Android, iOS, HarmonyOS NEXT, and Web applications

  • Data Processing / Application / Crash Identification: Supported only for Android, iOS, and HarmonyOS NEXT applications

  • Health Score / Native view: Configuration is supported only for Android, iOS, and HarmonyOS NEXT applications

  • Health Score / H5 page: Configuration is supported only for Android, iOS, HarmonyOS NEXT, and Web applications

  • Slow Detection / Application Startup: Configuration is not supported for Web applications

  • Slow Detection / Page Loading: Configuration is supported only for Android, iOS, HarmonyOS NEXT, and Web applications

  • Slow Detection / View Startup: Configuration is supported only for Android, iOS, and HarmonyOS NEXT applications

  • RUM metrics may have some discrepancies compared to record details due to the use of deduplication functions

  • Anomaly Detection / Application: Configuration is supported only for Android, iOS, and HarmonyOS NEXT applications

  • Anomaly Detection / Issues / Crash: Configuration is supported only for Android, iOS, and HarmonyOS NEXT applications

  • Anomaly Detection / Issues / Lag: Configuration is supported only for Android, iOS, and HarmonyOS NEXT applications

image-20260609165711996

  • AppFreeze Related Metrics Carrier dimension is not included by default. You may enable the carrier dimension via API. Contact technical support if this dimension is required.
  • Support backend toggle configuration to control whether click actions without triggered network requests are displayed on the platform. By default, only click actions that trigger network requests and crash actions are shown.
  • Support backend toggle configuration to enable deduplication for repeated reports such as lags. Deduplication is disabled by default due to performance degradation after enabling it.
  • Support backend toggle configuration to control whether crash stacks without the "caused by" string are displayed. Hidden by default.
  • RUM / Application: The Create Application button is a quick entry for Deployment Status / Application. Newly created applications are displayed in the Deployment Status / Application list. An application will only appear in the RUM / Application list after completing SDK integration and reporting metric data.