Once your application sends a new crash report to the Logify Alert service, the report travels through the following steps.
Filtration using the Ignoring settings. If the report matches any of the specified criteria, the report is automatically rejected.
Verifying reports that passed step 1 according to the Duplicate Fields setting.
By default, Logify Alert treats several crash reports as duplicate reports if these reports provide equal values for the following fields: ApiKey, ApplicationName, Version, ExceptionType, NormalizedStackTrace. Duplicate reports are stored along with the initial report. The number of duplicate reports that correspond to the required crash report is shown on the right of the report line on the Crash Reports tab.
Unique reports (unduplicated) are automatically added to the Crash Reports tab as separate items marked with the Active status.
Finally, each crash report that passes step 2 is added to the Crash Reports tab, which lists crash reports and provides you with additional searching and filtering mechanisms. For more information on features available on the tab, follow the links below.
Besides the features that assists you in working with the entire reports list, Logify Alert provides you with a set of options concerned with specific reports. For more information on these options, follow the links below.
Additionally, Logify Alert allows you to manage call stack lines bound to crash reports. For more information on the available approaches, refer to the links below.