Dashboard
You can understand the crash situation that occurred in each app version using the IMQA Crash dashboard. The IMQA Crash dashboard also enables you to check weekly user status by app version, number of occurred crashes, and detailed error information, as well as the error rank and cumulative number set in a specific error in advance.
1. Overview
The IMQA Crash dashboard page consists of the following.
❶ Top bar (common) ❷ Project information ❸ Weekly summary ❹ Daily error ❺ Distribution by rank ❻ Error table
Top bar (common)
❶ Logo Click this logo to open the project list main screen.
❷ Crash menu Click this menu to open each Crash menu page.
❸ MPM icon This icon is displayed when the MPM service is created while creating a project. Click this icon to open the “MPM > Dashboard” page of the same app.
❹ Project navigation You can move from the current project to another project. Click the [home] icon to open the project list. When the project is changed, “Service > Dashboard” of the app in question is opened.
The comparison project settings can be set in the MPM. For more information, refer to ‘Using MPM > Management > Project Management > Project Information > Comparison Project’.
❺ Member menu The member menu of the logged-in account is displayed.
Installation guide: You can read the IMQA's installation guide. A new browser tab is displayed when clicked.
User settings: You can change the username and password. The browser timezone can change the display reference time of IMQA analysis information.
Logout: You can log out from your account.
If the logged-in user is in an environment where time zone information cannot be automatically obtained, IMQA time information may not be displayed properly. You can manually set the browser time zone according to the GMT standard time of the connected area.
2. Project information
You can view project information and change the app version. If you change the app version, dashboard information will be updated to the selected app version.
You can designate the main app version to monitor in IMQA according to the app’s management cycle. For details of app versions management, please refer to “Using Crash > Project list > All project management > App Version Management“.
3. Weekly summary
You can view the crash count, session count (user count), and app run count of a specific app version for the last week. Using the information, you can determine if the app is running properly.
Weekly User: Counts the number of users for the last week. The number of sessions refers to the next number of users excluding duplicates.
Weekly Run Count: Counts the number of app launches that occurred for the last week.
Weekly Crash: Counts the number of crashes that occurred for the last week.
Weekly Web Crash: Counts the number of web crashes that occurred for the last week.
Weekly ANR: Counts the number of ANR that occurred for the last week. * Android project only
| Index | period | value | Merging method |
|---|---|---|---|
User | Last week | Number of users | Counting |
Run Count | Last week | Number of app launches | Counting |
Crash | Last week | Number of occurred crashes | Counting |
Web Crash | Last week | Number of occurred web error loges | Counting |
ANR | Last week | Number of occurred ANR | Counting |
The unit of 1,000 is abbreviated as “1K” for quick understanding. To view actual data, move the mouse pointer on the number abbreviated as “K” and then, the actual number will be displayed on a tooltip.
If Crash Count exceeds 10% of Weekly Run Count on average, it can be deemed as an anomaly. For example, if Crash Count is 1,000 or more compared to 10,000 app launches, it means that the app should be checked quickly.
The distinction between Crash and ANR is only visible in Android projects.
4. Daily error
You can view the error count trends and error count of a specific app version on a specific date by recording the error count by date for the last week.
Crash: Counts the number of crashes by date that occurred for the last week.
Web Crash: Counts the number of web crashes by date that occurred for the last week.
ANR: Counts the number of ANR by date that occurred for the last week. * Android project only
If the error count increased sharply on a specific date, see if there were any changes in the app version in question. In addition, if you check both the session count and app launches on that date, it will be helpful to analyze the indexes that show the cause of the error.
The distinction between Crash and ANR is only visible in Android projects.
5. Distribution by rank
You can view the error ranks and ratio of a specific app version for the last week. You can set error types and ranks using the SDK. If you set the error rank for each exception object, the exception in question will be displayed together with the rank when the exception occurs.
Refer to “IMQA Crash Installation Guide > 3. [Android] Setting Crash SDK > 3.1. Custom crash occurrence”.
The type and rank of errors are not defined separately and can be set differently according to the configuration of the app. It can be set as follows.
Unhandled: The default error rank that refers to a crash that was not processed.
Critical: A crash that affects the app significantly.
Major: A crash that affects the app.
Minor: A crash that does not affect the app significantly.
Currently, ranks other than Unhandled are supported by the Android SDK only.
6. Error table
You can view the error of a specific app version for the last week. The table shows error rank, cumulative count, crash name, current status, and last occurrence date. Using this table, you can understand occurred errors quickly and open the “Error Details” page.
❶ Header(sort) By default, errors are aligned by Most recent. Other alignment types include Rate, Cumulative count, Status, Date.
❷ Error The list shows the error that has occurred in a specific app version for the past week. If you click on an error item, the “Error details” page will open.
Rank: Displays the error rank defined in the SDK in advance.
Cumulative count: Counts the occurrence of the error in question cumulatively.
Error: Displays the error name, class name, and code line number. For web crashes, it displays the error type, custom error message, and code line number. The top 3 crashes are displayed in read.
Status: Status is displayed as “New”, “Open”, “Fixed”, and “Close”, which can be changed in the “Error details” page.
Date: Displays the date and time when the error in question occurred.
“Unknown Error” means specific error information was not appropriately collected. An example of this is a case where error names are not collected from specific exception types such as SIGABRT or SIGTRAP.
❸ Error type filter It is set to ‘All’ by default, and for Android projects, errors can be filtered by ‘Crash’ and ‘ANR’.
The distinction between Crash and ANR is only visible in Android projects.
Last updated
