S
Core Concepts/Error Monitoring

🔴 Error Monitoring

Capture and monitor JavaScript errors, HTTP errors, and more.

📋 What Gets Captured

Sypnia can capture multiple types of errors automatically:

🔴 JavaScript Errors

  • • Runtime exceptions
  • • Syntax errors
  • • Reference errors
  • • Type errors

⚡ Unhandled Rejections

  • • Failed promises
  • • Async/await errors
  • • Fetch failures

🌐 HTTP Errors

  • • 4xx client errors (400, 401, 403, 404...)
  • • 5xx server errors (500, 502, 503...)
  • • Network failures

📝 Console Errors

  • • console.error() calls
  • • Third-party library errors
  • • Framework warnings

🔴 JavaScript Errors

When enabled (track_errors: true), Sypnia captures:

// Example error event captured
{
  "event_type": "error",
  "properties": {
    "error_type": "js_error",
    "message": "Cannot read property 'map' of undefined",
    "filename": "https://example.com/app.js",
    "line_number": 42,
    "column_number": 15,
    "stack_trace": "TypeError: Cannot read property 'map'..."
  }
}

The SDK hooks into window.onerror and unhandledrejection events automatically.

🌐 HTTP Error Tracking

Sypnia intercepts fetch() and XMLHttpRequest to capture HTTP errors:

// Example HTTP error captured
{
  "event_type": "error",
  "properties": {
    "error_type": "http_error",
    "message": "HTTP 403 Forbidden",
    "http_status": 403,
    "http_method": "GET",
    "http_url": "https://api.example.com/users",
    "duration": 245
  }
}

Configuring HTTP Error Codes

In your project settings, you can select which HTTP status codes to capture:

Client Errors (4xx)

400401403404405408409422429

Server Errors (5xx)

500501502503504

🚫 Exclude URL Patterns

Prevent noise by excluding certain URLs from error tracking:

// URLs matching these patterns won't be tracked:
*google-analytics*      // Third-party analytics
*hotjar*                // Session recording tools
*/api/health*           // Health check endpoints
*facebook.com*          // Social widgets
*cdn.example.com*       // CDN errors you can't fix
Configure exclude patterns in your project's Settings → Error Capture tab.

📊 Error Dashboard

The Errors page in your dashboard shows:

  • Error list - All captured errors grouped by message
  • Stack traces - Full stack traces for debugging
  • Occurrence count - How many times each error occurred
  • Status management - Mark errors as resolved, ignored, or open
  • Browser/OS info - See which environments are affected

🔔 Error Alerts

Configure alerts in Settings to get notified when:

New Error Type

Get notified when an error you've never seen before occurs

Error Spike

Get notified when error rate exceeds your threshold (e.g., 10 errors/hour)