A few months back, we introduced custom queries as a mechanism to run queries against the analytics data sent to us by the application. With crash analytics and custom queries, you now have the power to run queries on the data attached to the crash events. You are now able to query properties like username or any meta data attached to the crash event.
|Table of Contents|
Troubleshooting crashes reported by a user
If one of your application users is reporting an application crash, then with
App crashes happen. With the help of the custom queries interface, you
found in AMPLIFY Crash Analytics (ACA), you can findout
the most recent crash experiencedby
that user and gather more information about the reported crash.
- In the Dashboard, you browse to the
- Application and look up tabCrashIssue.
- Click on Analytics > Custom Queries.
- Select Crash as the option under Grouping to group the results and use data.meta.username as the property name to filter the username. Note: if you are using ACA version 1.2, use data.username instead of data.meta.username.
- To filter on the username value, you should set the username value with the setusername. You can also set properties that would provide diagnostic information, like battery information, network conditions, or custom app properties using setMetadata and query for those values by filtering against data.meta.key. Additionally, the custom queries interface provides options to filter on platform versions, device model, app versions, and other properties that are supported by the platform by default.
Crash Events, Feature Events, and Breadcrumbs
When you attach breadcrumbs, the breadcrumbs are sent to the platform as feature events. Breadcrumbs are not displayed by default (along with other feature events in analytics view) in the breadcrumbs view of crash details. To view the breadcrumb details, you must enable the feature events by checking the box labeled Include feature events and then expand the breadcrumb list in the breadcrumb tabs.
Since crash events are treated as another type of AMPLIFY Analytic event, the crash events are counted against the organization’s analytics event capacity. Crash events have the same retention period entitlements as analytics events (2 years for Enterprise plans and 3 months for Pro plans).