Operation
Operation Analysis
Operation analysis is mainly used to monitor and analyze the response time and availability of user click events on the page. Optimizing the operation user experience is conducive to improving the conversion rate of key steps of users. Monitoring the availability of operations can ensure that key operations such as adding to the shopping cart and payment are stable and available, avoiding major losses to the business.
Operation Definition
| Indicator Name | Indicator Definition |
|---|---|
| Number of Operations | The number of times the specified operation is requested. Calculation Rules: The operation is requested once and recorded once |
| Operation Time | The time when all requests in the specified operation are completed. Calculation Rules: When the operation is an Ajax request, the end time of the last Ajax of the multiple Ajaxs corresponding to the operation - the start time of the operation click. |
| Operation Availability | The ratio of the number of successful operations to the total number of operations. Calculation formula: Operation availability = (number of successful operations/total number of operations) * 100% |
| Operation request time | Pure request time in the specified operation, excluding the blank time waiting for execution in the operation time. |
| Failed operation | If any request in the operation is sent as an error, the operation is counted as failed. (For request errors, you can set network error status code filtering in the application settings to filter out statistics of non-network errors). |
Operation identification principle and identification scenario
Keynote Listening Cloud automatically identifies user click event operations through non-embedded point technology, and associates network requests and interface calls.
The identification scenarios are as follows:
-
Events bound by bindtap(catchtap) in WXML
-
Network requests in associated binding event functions
-
WeChat interface calls in associated binding event functions
-
Mixed calls of network requests and interfaces in associated binding event functions
Other related content:
-
For lower versions of WeChat Mini Program SDK, the operation name is obtained as element content (such as button name) first, and if it cannot be obtained, the event method name is used.
-
The timing of uploading operation information is the same as the page, which is uploaded when the page onHide or onUnload is triggered.
-
The ongoing operation will not be terminated when switching pages. If the operation is started in the current page and ends after switching to the second page, the operation data will be uploaded with the second page, but the page will still be recorded as the initiating page, and the track in the operation details will show the final ending page.
The operation is named by the "operation method name" of the operation by default, and the operations with the same method name on the same page will be aggregated, and custom operation aliases are supported.
Introduction to the operation analysis interface
Operation list
The operation is named by the "operation method name" of the operation by default. At the same time, operations with the same method name on the same page will be aggregated, and custom operation aliases are supported.
The operation list includes indicators such as the operation name, the page where the operation is located, the number of operations, the operation time, the operation availability, the number of operation requests, the request time, and the average server time, and supports sorting. At the same time, the list can be searched based on the operation name.
Operation analysis details
Indicator trend chart
You can analyze the corresponding relationship between the operation time and availability trend and the number of operations; you can also switch to different quantiles to view the quality of the operation time.
Region
Time consumption distribution
You can view the time consumption distribution of the three indicators of operation time, operation request time, and operation server.
Exception tracking
Exception tracking mainly includes two parts of data: failed operations and slow operations. (Failed operations can be filtered in the settings to determine whether they are failed operations; slow operations can be determined by setting thresholds in the application settings)
The overview analysis module can be analyzed from multiple dimensions. The failed operations and slow operations are mainly concentrated in which dimensions, which can help us know which dimensions to focus on and solve the problems in which dimensions. At the same time, it supports multi-dimensional combined filtering, which can help us quickly locate the problem.
The exception tracking list can support searching and tracking the user's operation records according to user IP, userID, and sessionID.
Request
This module displays all requests corresponding to the operation, and the number of requests, request error rate, request time, server time, callback time, slow ratio and request data availability corresponding to each request. Click to track and analyze to the [Request] function module.
Operation tracking details
Operation tracking details record the complete request process and user trajectory of the user's operation as well as the user's system environment, helping IT personnel reproduce and restore the scene of the user's abnormal experience and locate the problem more quickly.
User basic information
User operation waterfall chart
Shows the start time, end time and status code of the request and API interface corresponding to the operation, and can also show the nested hierarchical relationship between requests.
Full stack traceability
One-click location of Server transactions.
User track
The user track shows the complete track of the user, from the beginning of entering the page, how to browse the page, and finally the operation error on that page.
