Crashes, network lags, ANR errors, and operational app errors are collectively referred to as anomalies.
Any forced exit of the app while the user has the app open is counted as one crash.
Any single session during which the network experiences a period of latency is considered to be one network lag.
An ANR (application not responding) error is counted as each time the user uses the App and a pop-up box appears indicating that the application is not responding. ANR errors are only counted in Android applications.
Exceptions, bugs, general errors, or script errors (including errors in C# , Lua, JS, etc.) are collectively reported as errors.
Any exception that occurs, is recorded, and reported is counted as a single exception.
Each single exception in a single device is counted as one affected user. Within a specified time range, if multiple exceptions occur in a single device, only one affected user will be counted.
This incorporates user crash rate, user network lag rate, user ANR rate, user error rate, etc. Thus, this is the ratio of affected users to total networked users.
This incorporates the crash occurrence rate, network lag occurrence rate, ANR occurrence rate, and error occurrence rate. This is therefore the ratio of total anomaly occurrences to the number of network connections.
This the total number of app activations plus the number of cross-day network connections.
A cross-day network connection is one in which the user has started the application on a previous day and left it running in the background past 12 PM that day, leaving the app connected overnight.
The following scenarios are all considered a single activation:
1.When application restarts after it has been completely closed;
2.The application is switched to the background and then switched to the foreground again after 30 seconds have elapsed. If it is switched back to the foreground in less than 30 seconds, this switch-back will not be considered a separate activation.
User devices connected to the network are used as indicators for assessing the number of individual users connected to the network.
Within a specified time range, if a single device connects to the network repeatedly, only one user will be counted as being connected to the network.