I'm unhappy with Sentry because it only catches some errors

That’s a common frustration. Sentry is good for capturing exceptions that actually get thrown and reach its instrumentation, but it won’t catch everything by default.

Why Sentry may only catch “some” errors

Common reasons:

• Errors are handled/caught before they bubble up
• Async errors aren’t wired up correctly
• Frontend errors happen outside supported hooks
• Server crashes / fatal errors happen before Sentry flushes
• Sampling / filtering is dropping events
• Network issues prevent events from being sent
• Logging-only problems aren’t exceptions, so Sentry never sees them
• Background jobs / workers aren’t integrated

What to do

1) Make sure you’re capturing more than uncaught exceptions

Depending on your stack, add:

• manual captureException(err)
• captureMessage("...") for non-exception failures
• middleware/error handlers
• global handlers like:
  • window.onerror
  • unhandledrejection
  • process-level handlers in Node

2) Check async paths

A lot of “missing” errors are in:

• promises
• timers
• event handlers
• job queues
• fetch/API error handling

3) Verify Sentry setup

Look for:

• dsn correctness
• environment / release
• beforeSend filters
• sampling settings
• integrations enabled
• flushing before process exit

4) Don’t rely on Sentry alone

For “catch everything” visibility, pair it with:

• structured logs
• centralized log aggregation
• APM/tracing
• alerting on error rates
• health checks / crash monitoring

If you want, I can help you diagnose the gap

If you share:

• your stack (React, Node, Python, etc.)
• one example of an error Sentry misses
• how you initialize Sentry

…I can tell you exactly why it’s not being captured and how to fix it.