2. Home
  4. Android Docs
  6. Dashboard

Dashboard

The Crashes dashboard provides a centralized view of crash-related data, allowing teams to monitor application stability and respond quickly to critical issues.
The dashboard presents high-level metrics, visual trends, and detailed crash information to support effective analysis and resolution. The dashboard also includes Fusion AI, which enables AI-assisted summaries and visualizations based on the available crash data.

Image 2
Image 2
Dashboard Summary

At the top of the dashboard, you will find key metrics that provide a quick overview of crash activity:

  • Crash-Free Sessions: Indicates the percentage of user sessions completed without experiencing crashes.
  • Crash-Free Users: Indicates the percentage of users who did not encounter any crashes, helping assess how widespread crash issues are.
  • Occurrences: Shows the total number of crash occurrences recorded during the selected time period. These metrics help evaluate overall application stability at a glance.
  • Version Filter: You can filter crash data by app version to analyze stability across different releases. This helps identify versions with higher crash rates and prioritize fixes accordingly.
  • Crash Reporting Graph: This graph displays the trend of crashes over time across different app versions. It helps identify patterns and determine whether specific versions are contributing more significantly to crash activity.
  • Affected Users Graph: This graph shows the number of users affected by crashes over time. It provides insight into the overall impact of crashes on the user base and helps assess severity.
  • Crash List: The Crash List provides a detailed view of individual crash reports, including:
    • App version where the crash occurred
    • Number of occurrences
    • Number of affected users
    • Assigned team member
    This view allows teams to investigate specific crashes and track resolution progress.
  • Assignee and Status: Each crash is assigned to a team member and includes a status to track progress. This helps ensure accountability and visibility throughout the resolution process.
  • Filtering: Crash reports can be filtered using multiple criteria, including:
    • Device ID
    • Status
    • Type
    • App version
    • Date
    • Assignee
    Filtering helps quickly locate relevant crash reports and manage large datasets effectively.
  • Sorting: Crash reports can be sorted by:
    • Most Recent
    • Most Affected Users
    • Least Affected Users
    • Highest Occurrences
    • Least Occurrences
Fusion AI (AI Chatbot)

The Crashes dashboard includes Fusion AI, accessible through the AI Chatbot option.

Image 2

Using Fusion AI, you can:

  • Generate a summary of crash data, including crash counts, affected users, versions, and trends
    Image 2
  • Ask questions about crashes using natural language
  • Visualize crash-related data using charts and graphs (for example, crash distribution by version or affected users over time)
    Image 2

Fusion AI converts user queries into structured summaries and visual insights based on the crash data available in the project.

Crash Free Sessions

The table below the graph provides version-wise session metrics:

  • Total Sessions: Total number of sessions recorded during the selected period. Each session represents one complete use of the app.
  • Crash-free Sessions: Number of sessions completed without crashes, indicating application stability.
  • Affected Sessions: Number of sessions that experienced at least one crash, highlighting instability impact.

Image 3
Crash Free Users

The table below the graph lists app versions along with user metrics:

  • Crash-free Users: Number of unique users who did not experience any crashes.
  • Total Users: Total number of unique users who used the application.
  • Affected Users: Number of unique users who experienced at least one crash during the selected period.

A higher number of affected users indicates a broader impact and may require immediate attention.

Image 2
Occurences

This metric represents the total number of crashes captured. Each occurrence corresponds to a single crash event. Similar crashes may occur multiple times across the same or different users.

Image 2