Sentry supports these Node libraries

Get Node error monitoring with complete stack traces


A minimalist illustration of a user interface that alludes to the Node error tracking information features of Sentry.

See source code at each frame instead of settling for just line and column numbers.


Get proper asynchronous context tracking — like thread-local storage in a way that fits Node’s concurrency model.


Filter and group Node exceptions intuitively to eliminate noise.

An illustration depicting a sequence of events. A user types F, Ü, N, scrolls down, clicks a checkbox, then Node throws an error due to encoding problems, which is caught by Sentry's Node error monitoring.

Fill in the blanks about Node errors


See what the app was doing when the Node error occurred: HTTP requests, database queries, console log statements, etc.

See the full picture of any Node exception


Aggregate errors by factors like request details, user ID, and event level to see what’s new, a priority, or a trend.

Assign custom tags to reproduce the error environment specific to your application, business, and users.

  • “How actionable is this error? Should I snooze the alert?”
  • “Did too many professional network matches cause the crash?”
  • “Has an error with the same stack occurred before?”
  • “In which app release did the Node error happen?”
  • “Is Mercury in retrograde?”

Sentry also supports your frontend

Resolve Node errors with max efficiency, not max effort


Improve workflow with a full view of releases so you can mark errors as resolved and prioritize live issues.

An illustration of Node error tracking, depicting a package on a conveyor belt, with marks along the belt indicating commits in a release.
Illustration of Node error monitoring, depicting a sequence of git commits depicted as platforms in a line. One of commit is crumbling and has been engulfed in lava.

Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release.

Add commit data to automatically suggest an owner of each Node error and instantly send deploy emails.

An illustration of Node crash reporting, depicting three avatars, with one highlighted as responsible for an error

Security doesn’t cost extra


All accounts get the same high quality security features, regardless of plan.

  • Two-Factor Auth
  • Single Sign On support
  • Organization audit log

Learn more about Security

  • Privacy Shield certified
  • PII data scrubbing
  • SSL encryption

Learn more about Privacy

Node debugging that looks nice too

Have some self-respect while you monitor errors

A screenshot of the Sentry crash reporting dashboard

Seriously though, stop hoping your users will report Node bugs.

Get started