Error Tracking

Temps includes Sentry-compatible error tracking built-in. Use your existing Sentry SDKs without code changes, and own your error data.

Overview

Track, debug, and resolve errors in production with enterprise-grade error tracking included in Temps.

Key Features

Sentry Compatibility

Temps implements the complete Sentry protocol, allowing you to use official Sentry SDKs without modification.

Supported Features

Compatibility Matrix

Setup & Integration

Get started with error tracking in minutes using your existing Sentry SDK.

Step 1: Get Your DSN

Each project gets a unique DSN (Data Source Name) for error reporting. The DSN format is:

https://<public_key>@<temps_app>/<project_id>

Example DSN format:

https://742ee692155dd1cb2cecd94838bb425d4b5a1184e5b57c0815e9d808a6f8d70d@your-temps-instance.com/1

Get Your DSN

Visit your project's error tracking setup page to view and copy your unique DSN:

https://<temps_app>/projects/<project_slug>/errors?tab=setup

Example:

https://app.temps.davidviejo.dev/projects/my-app/errors?tab=setup

On this page, you'll find:

• Your project's unique DSN - Copy this to use in your Sentry SDK configuration
• Setup instructions for different platforms
• Environment-specific DSNs (if configured)
• Rate limits and configuration options

Step 2: Install Sentry SDK

Install the official Sentry SDK for your platform:

npm install @sentry/react

Step 3: Configure SDK

Point the Sentry SDK to your Temps instance:

import * as Sentry from '@sentry/react';

Sentry.init({
  // Copy your DSN from: https://<temps_app>/projects/<project_slug>/errors?tab=setup
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN || 'YOUR_DSN_HERE',
  environment: 'production',
  release: 'my-app@1.0.0',

  // Performance monitoring
  tracesSampleRate: 1.0,

  // Session replay integration
  integrations: [new Sentry.BrowserTracing()],

  beforeSend(event, hint) {
    // Filter sensitive data
    return event;
  }
});

Step 4: Test Error Tracking

Trigger a test error to verify setup:

// Throw test error
Sentry.captureException(new Error('Test error from Temps'));

// Capture message
Sentry.captureMessage('Test message', 'info');

// Add breadcrumb
Sentry.addBreadcrumb({
  message: 'User clicked button',
  level: 'info',
  data: { button: 'signup' }
});

Error Grouping

Temps automatically groups similar errors together using smart fingerprinting and AI-powered clustering.

Grouping Strategies

Custom Fingerprinting

Override default grouping with custom fingerprints:

Sentry.captureException(error, {
  fingerprint: ['database-error', 'connection-timeout'],
});

// Dynamic fingerprint
Sentry.captureException(error, {
  fingerprint: ['api-error', error.response?.status],
});

Merge & Split Groups

temps error-tracking merge \
  --groups error-1,error-2,error-3 \
  --target error-1

temps error-tracking split \
  --group error-1 \
  --event-ids evt-123,evt-456

Error Details

Each error event captures comprehensive context for debugging.

Error Anatomy

Enrich Error Context

Add custom context to errors:

Sentry.setUser({
  id: 'user-123',
  email: 'user@example.com',
  username: 'johndoe',
  subscription: 'pro'
});

Trace Correlation

Temps stores a W3C Trace Context trace ID alongside errors so the unified Observe page can link an exception to the request, spans, and other events that share the same trace. This is what powers the cross-source jumps in the /projects/<slug>/observe timeline.

Schema

The m20260502_000001_add_observe_correlation migration (shipped in temps 0.1.0-beta.6) adds the correlation columns and lookup indexes. Every column is nullable, so existing rows are unaffected, and the migration is written to be safely re-runnable — each step uses IF NOT EXISTS.

Supporting indexes added by the same migration:

How the trace ID is extracted

For error events, temps-error-tracking ingestion probes the event payload for a trace ID and promotes the first valid value to error_events.trace_id_indexed. It checks, in order: data.sentry.contexts.trace.trace_id, top-level data.contexts.trace.trace_id, and data.trace.trace_id. A value is accepted only if it is exactly 32 ASCII-hex characters and is not the all-zero trace ID the W3C spec reserves as invalid.

The temps-proxy reverse proxy includes a helper, extract_traceparent_trace_id, that reads the inbound traceparent request header (matched case-insensitively against traceparent, Traceparent, and TRACEPARENT), splits on -, and takes the trace-id field. It applies the same validation: the value must be 32 ASCII-hex characters, must not be all zeros, and is lowercased before use. Six unit tests cover the valid case, a missing header, the all-zero value, the wrong length, non-hex characters, and uppercase folding.

To send a trace ID through to Temps, set a standard traceparent header on the request:

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
              │  └─ trace-id (32 hex) ────────────┘  └─ span-id ──┘  └ flags
              └─ version

Error Resolution

Manage error lifecycle from discovery to resolution.

Error States

Mark as Resolved

# Resolve error group
bunx @temps-sdk/cli error update --group-id error-123 --project-id <project-id> --status resolved

# Note: --in-release is not supported; resolution is immediate
bunx @temps-sdk/cli error update --group-id error-123 --project-id <project-id> --status resolved

# Resolve multiple groups (run per group)
bunx @temps-sdk/cli error update --group-id error-123 --project-id <project-id> --status resolved
bunx @temps-sdk/cli error update --group-id error-456 --project-id <project-id> --status resolved
bunx @temps-sdk/cli error update --group-id error-789 --project-id <project-id> --status resolved

Auto-Resolution

Configure automatic resolution rules:

# Auto-resolve errors
auto_resolution:
  # Resolve if no new events for X days
  no_events_for: 30

  # Resolve when new release is deployed
  on_release: true

  # Resolve when error rate drops below threshold
  rate_threshold:
    errors_per_hour: 1
    duration: 24h

Ignore Errors

Suppress known errors you don't want to track:

Sentry.init({
  dsn: '...',
  ignoreErrors: [
    // Ignore specific error messages
    'ResizeObserver loop limit exceeded',
    'Non-Error promise rejection',

    // Ignore error patterns
    /^Loading chunk [\d]+ failed$/,
  ],

  // Ignore errors from specific URLs
  denyUrls: [
    /extensions\//i,
    /^chrome:\/\//i,
  ],

  beforeSend(event, hint) {
    // Custom ignore logic
    if (event.exception) {
      const error = hint.originalException;
      if (error.message?.includes('Network error')) {
        return null; // Don't send to Temps
      }
    }
    return event;
  }
});

Additional Resources