Your First Caught Error

Throw a test error

Add this to any API route or server component in your app:

export async function GET() {
  throw new Error("Testing DeepTracer — delete this!")
}

export default function TestErrorPage() {
  throw new Error("Testing DeepTracer — delete this!")
  return null
}

app.get("/test-error", () => {
  throw new Error("Testing DeepTracer — delete this!")
})

Check your dashboard

Open your DeepTracer dashboard at app.deeptracer.dev and click the Errors tab in the sidebar.

You should see your test error appear within a few seconds. It will show up as an error group with:

• The error message: "Testing DeepTracer — delete this!"
• Severity: Medium (the default)
• Occurrence count: 1

Click into the error

Click on the error group to see the full details:

• Stack trace — The exact file and line where the error was thrown
• Metadata — Request info, environment, service name
• Timeline — When this error first appeared and when it last occurred

Run an AI investigation

Click the "Investigate" button. DeepTracer's AI will analyze the error in real-time. You'll see each section stream in as it works:

• Summary — A one-paragraph explanation of what happened
• Root cause — The specific line of code that caused the error
• Evidence — Surrounding logs and trace data
• Suggested fix — What to change in your code

For a test error like this, the investigation will be straightforward — but for real production bugs with complex stack traces and related logs, this is where DeepTracer really shines.

Mark it as resolved

Once you've read the investigation, click "Resolve" to close the error group. You can add a resolution note like "Test error — removed."

If this error ever happens again, DeepTracer will automatically reopen the group and notify you.

Clean up

Delete the test error from your code:

// Delete the test route / component you added in step 1

That's it. You've seen the full error lifecycle: throw, catch, investigate, resolve.