Error Tracking
The Error Tracking tool automatically captures uncaught JavaScript errors in your application, helping you monitor code health and quickly identify issues affecting users.
The Errors Dashboard
The main dashboard provides a high-level overview:
Error Trends
A line graph showing errors over the last 30 days. Use this to:
- Spot sudden spikes after deployments
- Track error reduction over time
- Identify recurring patterns
Key Metrics
- Last 7 Days — Total errors compared to the previous week
- Affected Devices — Number of unique devices impacted out of your total active users
The Error List
The left sidebar shows a chronological list of every captured error:
- Error Message — The specific error that occurred
- File and Line Number — Where in your code the error happened
- Occurrence Count — How many times this error has occurred
Click any error to see full details including the stack trace.
How to Use Error Tracking
Prioritize Fixes
Use the Affected Devices metric to prioritize errors impacting the most users. A single error affecting 100 users is more urgent than 10 errors each affecting 1 user.
Debug with Replays
Each error includes a replay ID or session ID. Use this to:
- Find the session where the error occurred
- Watch the replay to see what the user was doing
- Understand the exact sequence of actions that triggered the error
Monitor Releases
After each deployment:
- Watch the error trend graph for spikes
- Check for new error types
- Verify that fixed errors don’t recur
Automatic Capture
Error tracking is enabled by default when you integrate Overcentric. Errors are captured with:
- Full stack trace
- Current page URL
- User and session information
- Browser and device details
Configuration
You can disable error capture if needed:
overcentric.init('YOUR_PROJECT_ID', {
context: 'product',
errorCapture: false // Disable error tracking
});Or via Project Settings in the dashboard.