# Overview
Crasheye (opens new window)It is a simple and easy-to-use quality tracking integrated solution platform. It mainly provides mobile application developers with real-time, comprehensive and professional error analysis services for each APP, so that you will not miss any crash information and help comprehensively improve the overall quality of the APP.
# Core advantages
- Real-time - multi-dimension professional reports, APP quality at a glance
Real-time display of multi-dimension data combination such as crash rate, number of launches, equipment distribution, system distribution, user count, etc - Comprehensive - supports various crash type analysis
Support exception capture and analysis for different platforms and languages such as Android, iOS, NDK, Java, C #and Lua - Professional - fast access, continuous update, continuous maintenance
One line of code can quickly access the SDK, continuous maintenance and update by the professional test and development team in the industry
# Platform terminology
| name | Description |
|---|---|
| ProjectKey | Project Name (Project ID) |
| AppKey | Application name - globally unique Appkey (generated by the platform) such as Android application and IOS application, "Your_AppKey" in the document is the same |
| Crash | A flashback occurs when the user uses the App, which is counted as a crash |
| Script exception | Actively reported Exception, Error, or script (such as C#, Lua, JS, etc.) errors are collectively referred to as script exceptions |
| Number of crashes | A crash occurs and is recorded and reported, counted as a crash |
| Number of uses | can also be called 【Start times】. Every time the app is started and recorded and reported, the following scenarios are counted as a start 1. The app is completely exited and then restarted, which is counted as a start 2. After the app is switched to the background, it will be restarted after 30 seconds Switching to the foreground is counted as a startup (*If you switch to the foreground within 30 seconds, it is not counted as a startup |
| Crash rate | Crash Rate = Percentage of [Crashes] divided by [Launches] during the selected time period |
| Number of affected users | An exception occurs on one device, which counts as one affected user. Within the specified time range, if a device has multiple abnormalities, only one affected user will be counted |
| Number of users | is also known as [active user count]. Taking the device as the statistical object, the application is started on one device and reported, it is counted as one user. Within the specified time range, if a device reports multiple times, only one user will be counted |
| Affected user rate | Affected users rate = [Number of affected users] divided by the percentage of [Number of users] |
| Crash rate today | The percentage of [crashes] divided by [startups] today, the data is refreshed every few minutes |
| Number | In order to distinguish each downtime, the Crasheye platform gives a serial number according to certain rules, which is unique in a single Appkey |
| Statistic time | Based on the Eastern 8 time zone, if the project is released globally, it is necessary to consider the possible impact of the time zone on the data |
| Crash time | The time on the user's machine when the [Crash] occurred |
| Report time | The time when the server received the crash message. Due to the different acquisition hosts from [Crash Time], there may be a possibility that the reported time is earlier than the crash time |
| Client ID | uniquely identifies a device, and this ID can be used to retrieve all crash records of the device. App reload may generate a different client ID |
| Foreground/background | Whether the application is running in the foreground or in the background when [Crash] occurs |
| Duration of use | The time interval from the last complete exit and restart to the time when the crash occurs |
| UUID (symbol file identifier) | is the unique identification code of the symbol file, and the symbol file will be regenerated after each compilation and packaging of the project. crasheye uses this information to associate the crash stack with the symbol file |
| Mapping file symbol file | If c/c++ code is used in the Android project, the captured and uploaded stack information is incomprehensible in the platform client. It needs to be parsed in conjunction with the Mapping.txt file and the symbol file generated in the project. understand. |
# Who can use
- Enterprise Developer
- Small work team
- Individual Developer