Skip to content

Viewing Crash Group Analytics

(Native Apps Only) View analytics for crash groups and crash dumps that could not be analyzed.

The developer must enable the iOS and Android application to catch exceptions with a global catch-all handler and upload them to mobile services server. In SAP mobile service cockpit, the application must also be enabled to upload crash logs.

Crash logs can be an important source of information during the development process. You can enable your test apps to catch exceptions and upload the data. Configure mobile services to automatically gather crash logs and report failures by group. View the reported data in SAP mobile service cockpit, and use to fix issues and ensure quality.

  1. In SAP mobile service cockpit, select Analytics > Crashes.

  2. (Optional) You can narrow the focus of crashes by selecting the platform, application ID, application version, and time frame filters. The affected applications appear for selection in application ID. If you select a platform and an application ID, the available application versions appear for selection. Time frame is required. Select Reset to clear your filters.

    Two charts provide visual information about crashes and users:

    • Crashes ‒ the number of crashes that occurred over time.
    • Users ‒ the number of users affected by crashes over time.
  3. Under Crash Group view the detected crash groups.

    Crash Groups

    Column Description
    Title The title of the crash group.
    Count The crash group count.
    Affect Users The number of affected users.
    Platform The platform, such iOS or Android.
    Application Versions The range of application versions.
    Application ID The application identifier.
    Last Report (UTC) The date and time of the last report update in UTC format (YYYY-MM-DD HH:MM:SS).
    Status The crash dump status by platform. Select a status button to navigate to the specific application for details.

    For iOS crash dump status:

    • Symbolicated - the crash dump is fully symbolicated.
    • Processing - the uploaded crash dump is being processed (whether or not dSYMs have been uploaded).
    • Missing dSYM - the crash dump has been processed. Some debug symbols (dSYMs) are missing, so this crash dump is only partially symbolicated. See Managing Symbol Files (iOS). Once the required dSYM files have been uploaded, the symbolication process will be triggered again.
    • Initial - the crash dump has been uploaded and is waiting to be processed.

    For Android crash dump status:

    • The crash dump is deobfuscated.
    • The crash dump is obfuscated.
  4. Select a crash group to see more details.

  5. Select the Overview tab to view KPIs, charts and the stack trace for the selected crash group.

    • KPIs for:

      • Occurrences ‒ the number of reported occurrences.
      • Users ‒ the number of affected users.
      • Application Version ‒ the application version reporting the crash.
    • Charts for:

      • Affected Device Models ‒ the device models that are reporting the crash.
      • Affected Platform Versions ‒ the operating system platforms that are reporting the crash.
    • Stack trace: the common stack trace parts for the crashes, with additional system details.

  6. Select the Reports tab to view information for individual crash dumps by device.

    1. View a summary of devices reporting crashes.

      Device Reports

      Column Description
      Device The device type, such as Pixel.
      Platform Version The operating system platform version, such as x.
      Date (UTC) The date and time of the device report in UTC format (YYYY-MM-DD HH:MM:SS).
    2. Select one of the device reports to view its details.

      • Report Details - device details such as model, language, screen size, application version, SDK product and version, and platform version.
      • Raw Data - crash data for the device. You can download the data.

Subscribe to Crash Alerts

You can subscribe to crash logs at the tenant level to receive notifications, and manage the subscriptions through My Alerts.

When you subscribe to crash alerts from SAP mobile service cockpit, you can configure the option to send the alerts to the SAP Alert Notification service. This enables you to control how often and when to send events from mobile services to the Alert Notification service. You can set a threshold value for when to send events (for example, after one alert, or after five alerts), or set a schedule for when to send events (for example, every hour, every eight hours, or every 24 hours). This reduces the number of repetitive alerts that are sent, so that the Alert Notification service is not overwhelmed.

The actual condition for notifications must be created through Alert Notification service. If you create a condition for the subscription via the Alert Notification service, you can continue to receive alert notifications for three months. You can extend the subscription for another three months using My Alerts.

  1. In SAP mobile service cockpit, select Analytics > Crashes.

  2. You can narrow the focus of crashes by selecting the Platform, Application ID, Application Version, and Time Frame filters. Select Go to search.

  3. To subscribe to the filtered crash log, select Subscribe.

    In Subscribe Crash Log, assign a subscription name and review or edit the subscription. The entries reflect the original filters you selected, but you can modify them.

    Crash Log Subscription

    Setting Description
    Subscription Name Enter a subscription name that is meaningful to you, such as "TEST.sample.basic".
    Category Crash Log
    Application ID The application identifier, such as TEST.sample.basic.
    Platform The platform, such as Android or iOS.
    Send to ANS Whether to send crash log alerts to the Alert Notification service. Select this option if you plan to configure a condition for alert notifications in the Alert Notification service. If you enable the Send to ANS option, two additional fields appear. They are used to configure how often and when to send events to the Alert Notification service.
    Threshold (ANS) If you enable the Send to ANS checkbox, you can provide a Threshold for when alerts are sent, such as 0, 1, or 5. If the event count number is greater than the threshold number, an alert notification is sent to the Alert Notification service.
    Schedule (ANS) If you enable the Send to ANS checkbox, you can select a schedule, such as Every Hour, Every 8 Hours, and Every 24 Hours. Alert notifications are sent to the Alert Notification service periodically based on your selection.
    Alert Notification service If you enable the Send to ANS checkbox, note the Alert Notification service information. You'll need this to manually create the condition in the Alert Notification service.
  4. Select Save.

    Once you save, the subscription appears in My Alerts. The alert subscription remains until you delete it.

  5. To receive ongoing alert notifications for the subscription, create a condition in the Alert Notification service. See Subscribe to Crash Log Notices.

    With the condition, you receive alert notifications for three months. You can extend alert notifications for another three months using My Alerts. See Managing My Alerts. Sample Alert Notification service conditions:

    To receive alert notifications for a specific crash log subscription:

    Key: tags.mobile_crash_log_alert
    Predicate: Is Equal To
    Value: MyCrashLogSubscription
    

    To receive alert notifications for all crash log subscriptions in the space/tenant:

    Key: eventType
    Predicate: Is Equal To
    Value: MobileServicesCrashLogAlert
    

Last update: July 28, 2022