Analyse crashes
Crash Analytics collects information about crashes and unexpected errors that occur on your website or application. Use the Crash reports to analyse crash activity, investigate recurring errors, and manage ignored or merged crashes. Learn more about what Crash Analytics does.
- To open Crash Analytics, log in to Matomo and click Crashes in the left menu.
- Select a report to open:
- Overview: Monitor crash trends and key metrics at a glance.
- Real-time: Shows crashes as they occur to help identify and investigate issues quickly.
- All Crashes: View crashes by pages or groups, including their frequency, and source files.
- Manage Crashes: Review ignored and merged crash groups, and unignore or separate them when needed.
Overview
The Overview report provides a summary of crash activity for the selected period. You can monitor overall application stability, and identify new or recurring issues after deployments or releases.
The report includes an evolution graph visualises crash activity over time. By default, it plots Crash occurrences, New crashes, and Visits crash rate. You can also customise the graph and plot different metrics using the Choose metrics dropdown.
Tip: Add annotations for product releases or configuration changes so you can compare crash trends with significant events on your website or application.
Below the graph, sparkline summary cards highlight key crash metrics for the selected period. Click on a sparkline to display the metric in the evolution graph.
Real-time
With the Real-time report you can see what crashes your users are experiencing right now, allowing you to respond immediately if needed. The report shows crash activity from the last 30 minutes and last 8 hours to help you monitor application stability and respond to emerging issues.
The report includes live summary metrics, the most frequent crashes, and crashes that have appeared or disappeared within the last eight hours.
All Crashes
The All Crashes report provides a detailed view of every crash detected during the selected period. You can investigate individual crashes, understand where they occur, measure their impact, and prioritise fixes.
Additional reports let you analyse crashes by different dimensions:
- Identify the Pages by URL or Title with the highest number of crashes and highest crash rates.
- Group crashes by Source or Category (if defined).
- Distinguish First Party and Third-Party crashes originating from your own code and external libraries or services.
- View crashes that have recently appeared, returned after previously disappearing, or stopped occurring.
Inspecting Crash Details
Hover over a crash report and use the icons to open the segmented visit log, row evolution or Crash Details view to further investigate the error.
By default, the Crash Details report shows a summary of the error, a full stack trace and visits that experienced the crash.
The crash details can be copied or emailed using the action buttons in the report: Copy Crash Information, Email Crash Information, and Ignore Crash.
Ignore a Crash
You can choose to ignore selected crashes so they are no longer tracked nor appear in your reports. The ignored crashed will be retroactively removed from past reports. Read the guide on how to ignore and unignore a crash.
Crash Context
The Crash Context section provides additional information about recent occurrences of a crash to help you understand where and how it happened. This context can assist with reproducing issues, identifying affected pages, and determining the impact on visitors.
If the Visits Log is disabled as part of your privacy configuration, only limited information for the last five crash occurrences is displayed:
To hide all details of the Crash context for Matomo users, you can disable the context view altogether. See How to hide the Crash Context.