Skip to main content

Slow Identification

Slow Identification is used to configure thresholds for slow performance detection. When a specific metric reaches the configured threshold, it is considered slow and indicative of impacted user experience.

Application Startup​

The application list here includes all App applications and Mini Program applications. Select an application to configure its slow startup threshold on the current page. 1760072087505

Cold Startup Identification:

  • When the "Application Cold Startup Duration" exceeds the set threshold (e.g., 1000 ms in the example), it is identified as a "Slow Startup".
  • Supports checking the "Cold Startup Time Upper Limit" and setting a duration (e.g., 20 s in the example) to restrict the maximum tolerable time for a cold startup.

Warm Startup Identification: When the "Application Warm Startup Duration" exceeds the set threshold (e.g., 3000 ms in the example), it is identified as a "Slow Startup".

info

Feature Value: By customizing the duration thresholds for cold and warm startup, scenarios where the application "starts too slowly" can be accurately identified, providing clear criteria for subsequent startup performance optimization and troubleshooting of abnormal startup issues.

View Startup​

The application list here includes all App applications and Mini Program applications. Select an application to configure the slow startup threshold for all views under the current application on this page. 1760072107259

Tolerable Identification: When the "View Startup Duration" exceeds the set threshold (e.g., 2000 ms in the example), it is identified as a "Slow Startup".

info

Feature Value: By customizing the duration threshold for view startup, scenarios where the application "view starts too slowly" can be accurately identified, providing clear criteria for subsequent view startup performance optimization and troubleshooting of abnormal startup issues.

Page Load​

The application list here includes all App applications and Web applications. Select an application to configure the slow load threshold for all pages under the current application on this page. 1760074335516

Tolerable Identification: Set corresponding duration thresholds for different stages of page loading. When the duration is greater than or equal to the set value, it is identified as a "Slow Load":

  • When Time to Fully Loaded ≥ the set value (e.g., 5000 ms in the example), it is identified as "Slow Fully Loaded".
  • When FP (First Paint) Duration ≥ the set value (e.g., 1400 ms in the example), it is identified as "Slow White Screen Load".
  • When FCP (First Contentful Paint) Duration ≥ the set value (e.g., 2700 ms in the example), it is identified as "Slow First Screen Load".
  • When TTI (Time to Interactive) Duration ≥ the set value (e.g., 2100 ms in the example), it is identified as "Slow Interactive Load".
info

Feature Value: By customizing duration thresholds for different key stages of page loading (Fully Loaded, White Screen, First Screen, Interactive), scenarios where the application "page loads too slowly" can be accurately identified, providing clear criteria for subsequent page load performance optimization and troubleshooting of abnormal load issues.

User Actions​

Slow Action​

The ONE platform allows users to manage the identification of anomalous actions. Users can make anomaly identification meet expectations by using custom rules or modifying default rules. 1760074348836

Custom Settings: 1760074370852

Click Add to create a custom rule:

  • Condition: Used to specify the scope of user actions for which the custom rule takes effect.
  • Configuration Item: Used to define the duration threshold for identifying a "Slow Action". 'When the action duration ≥ [X] ms, it is considered a slow action' (the threshold is 3000 ms in the example). That is, when the duration of the target user action exceeds this threshold, it will be identified as a "Slow Action".

Tolerable Identification (Slow Action Scenario): When the "Action Duration ≥ Set Threshold" (e.g., 3000 ms in the example), it is identified as a "Slow Action".

info

By combining custom rules for "User Action Scope + Duration Threshold", "Slow Action" scenarios for specific user actions can be accurately identified, providing more detailed criteria for locating and optimizing performance issues related to user actions.

Request Error Action​

When a request failure occurs during an action, and that action has not been defined as a Failed Action, the system considers the action a Request Error Action. 1760074386754

Network Requests​

Slow network request detection is divided into "Default Settings" and "Custom Settings". The priority of "Custom Settings" is higher than "Default Settings". Multiple "Custom Settings" can be configured, and the order of effectiveness is consistent with their priority. 1760074401463

Tolerable Identification

  • When the Network Request Download Size ≤ 50 KB, if the "Request Response Time ≥ 1 ms", it is identified as a "Slow Request".
  • When the Network Request Download Size > 50 KB, if the "Download Speed ≤ 100 KB/s", it is identified as a "Slow Request".
info

Through the granular configuration of "Custom Rules" and the global fallback of "Default Rules", network "Slow Request" scenarios under different download scales can be accurately identified. This provides clear criteria for network request performance optimization and troubleshooting of abnormal requests, ensuring the efficiency and stability of application network interactions.

Interfaces​

Slow detection for service interfaces is used to set thresholds for identifying slow interface calls on the server side. Rules are divided into "Default Settings" and "Custom Settings". The priority of "Custom Settings" is higher than that of "Default Settings". Multiple "Custom Settings" can be configured, and the order of effectiveness is consistent with their priority.

1760074422253

  • Default Settings: Acts as a global fallback rule and applies to all service interfaces that do not match any custom rule. Click Modify to adjust the default thresholds for "slow" and "very slow" requests.
  • Custom Settings: Allows you to set slow detection rules for specific services or interfaces. Click Add to create a custom rule. When the same interface matches multiple custom rules, the system matches them by priority from high to low (a smaller number indicates a higher priority). The first matched rule takes effect. You can drag and drop rules to adjust their priority order.

Custom Settings​

Click Add to open the "Add Custom Settings" dialog, then configure Effective Scope, Condition, Configuration Item, and Description in sequence. After configuration, click Confirm to save and apply the rule immediately, or click Cancel to discard the changes.

Effective Scope​

Specifies the target objects to which the rule applies. First select the scope type from the dropdown, then select specific objects. You can click + on the right to add multiple rows. The conditional relationship between multiple rows is "Or" (the rule matches if any row is satisfied).

The following two scope types are supported:

1760001000001

  • Service: Define the scope by specific service instances (for example, third party server and business_backend in the screenshot).
  • Service tags: Define the scope in batches by service tags. All services under the selected tags are automatically included in the effective scope.

Condition​

Further defines the granularity of the rule within the effective scope. Two modes are supported: "By service" and "By interface".

By service: The rule applies to all interfaces of all services within the effective scope. No separate interface selection is required.

1760001000002

By interface: The rule applies only to the selected interfaces. Select at least one interface; otherwise, the probe side cannot match the rule (for example, com.potter.happyTour.spring.GenericPluginList$1 and /services/VerificationService in the screenshot).

1760001000003

Configuration Item​

Define different levels of "slow requests" by setting thresholds for "client-side response time":

  • Slow request: When "client-side response time > the set threshold" (for example, 1000 ms in the screenshot), the request is identified as "slow".
  • Very slow request: When "client-side response time > the set threshold" (for example, 2000 ms in the screenshot), the request is identified as "very slow".
tip

When a request is slow, the performance status is only identified as slow.

When a request is very slow, the performance status is only identified as very slow.

Description​

This is a required field used to note the purpose of the custom rule, making it easier to distinguish and maintain multiple rules in the rule list.

info

Feature Value: Through the combination of "Effective Scope + Condition (service/interface) + response time thresholds", you can define fine-grained slow detection criteria for different services and interfaces, accurately identify "slow" and "very slow" request scenarios for service interfaces, and provide clear criteria for server-side performance optimization and slow interface troubleshooting.

SQL Statements / NoSQL Operations​

Define varying degrees of "Slow Statements" by setting thresholds for "Statement Execution Time". 1760074463892

  • Slower Statement Execution: When the "Statement Execution Time > Set Threshold" (e.g., 500 ms in the example), it is identified as "Slower Statement Execution".
  • Very Slow Statement Execution: When the "Statement Execution Time > Set Threshold" (e.g., 1000 ms in the example), it is identified as "Very Slow Statement Execution".

Key Methods​

Define varying degrees of "Slow Method Invocation" by setting thresholds for "Method Invocation Time". 1760074449818

  • Slower Method Invocation: When the "Method Invocation Time > Set Threshold" (e.g., 200 ms in the interface example), it is identified as "Slower Method Invocation".
  • Very Slow Method Invocation: When the "Method Invocation Time > Set Threshold" (e.g., 500 ms in the interface example), it is identified as "Very Slow Method Invocation".