@sentry/node

What is @sentry/node?

The @sentry/node package is a tool designed for real-time monitoring and fixing crashes in Node.js applications. It provides error tracking and performance monitoring, helping developers to quickly identify, diagnose, and fix problems in their applications. Sentry integrates seamlessly with your existing codebase, offering a range of features to enhance application reliability and user experience.

What are @sentry/node's main functionalities?

Error Tracking

Automatically capture exceptions and errors in your Node.js applications. The code initializes Sentry with your project's DSN and demonstrates how an uncaught exception is automatically reported to Sentry.

const Sentry = require('@sentry/node');
Sentry.init({ dsn: 'YOUR_DSN_HERE' });

app.get('/', function mainHandler(req, res) {
  throw new Error('Broke!');
});

Performance Monitoring

Track the performance of your application, including request times and slow operations. This code sample starts a transaction, simulates an operation with a timeout, and then finishes the transaction, which is then reported to Sentry for performance analysis.

const Sentry = require('@sentry/node');
const transaction = Sentry.startTransaction({ op: 'test', name: 'My First Test Transaction' });

setTimeout(() => {
  transaction.finish();
}, 99);

Custom Event Capturing

Send custom messages or events to Sentry. This is useful for capturing non-exception events that are significant for your application's health monitoring and diagnostics.

const Sentry = require('@sentry/node');

Sentry.captureMessage('Something went wrong', 'error');

Other packages similar to @sentry/node

bugsnag-js

Bugsnag provides error monitoring for web, mobile, and server applications. Similar to @sentry/node, it offers real-time error reporting and allows for detailed error diagnostics and performance monitoring. Bugsnag differentiates itself with features tailored to mobile app monitoring.

rollbar

Rollbar offers real-time error tracking and debugging tools for developers. Like @sentry/node, it supports multiple programming languages and frameworks, including Node.js. Rollbar emphasizes its ability to help teams with workflow integrations and automated error grouping for efficient management.

raygun

Raygun provides crash reporting, real-user monitoring, and deployment tracking. It's similar to @sentry/node in its core functionalities of error tracking and performance monitoring but also offers unique features like user journey tracking and version comparisons to understand the impact of deployments.

README

The README file is missing

Changelog

10.0.0

Version 10.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes. The goal of this release is to primarily upgrade the underlying OpenTelemetry dependencies to v2 with minimal breaking changes.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 9 to version 10. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v9-to-v10/

A comprehensive migration guide outlining all changes can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

• feat!: Bump to OpenTelemetry v2 (#16872)
• feat(browser)!: Remove FID web vital collection (#17076)
• feat(core)!: Remove BaseClient (#17071)
• feat(core)!: Remove enableLogs and beforeSendLog experimental options (#17063)
• feat(core)!: Remove hasTracingEnabled (#17072)
• feat(core)!: Remove deprecated logger (#17061)
• feat(replay)!: Promote _experiments.autoFlushOnFeedback option as default (#17220)
• chore(deps)!: Bump bundler plugins to v4 (#17089)

Other Changes

• feat(astro): Implement Request Route Parametrization for Astro 5 (#17105)
• feat(astro): Parametrize routes on client-side (#17133)
• feat(aws): Add SentryNodeServerlessSDKv10 v10 AWS Lambda Layer (#17069)
• feat(aws): Create unified lambda layer for ESM and CJS (#17012)
• feat(aws): Detect SDK source for AWS Lambda layer (#17128)
• feat(core): Add missing openai tool calls attributes (#17226)
• feat(core): Add shared flushIfServerless function (#17177)
• feat(core): Implement strictTraceContinuation (#16313)
• feat(core): MCP server instrumentation without breaking Miniflare (#16817)
• feat(deps): bump @prisma/instrumentation from 6.11.1 to 6.12.0 (#17117)
• feat(meta): Unify detection of serverless environments and add Cloud Run (#17168)
• feat(nestjs): Switch to OTel core instrumentation (#17068)
• feat(node-native): Upgrade @sentry-internal/node-native-stacktrace to 0.2.2 (#17207)
• feat(node): Add shouldHandleError option to fastifyIntegration (#16845)
• feat(node): Add firebase integration (#16719)
• feat(node): Instrument stream responses for openai (#17110)
• feat(react-router): Add createSentryHandleError (#17235)
• feat(react-router): Automatically flush on serverless for loaders/actions (#17234)
• feat(react-router): Automatically flush on Vercel for request handlers (#17232)
• fix(astro): Construct parametrized route during runtime (#17190)
• fix(aws): Add layer build output to nx cache (#17148)
• fix(aws): Fix path to packages directory (#17112)
• fix(aws): Resolve all Sentry packages to local versions in layer build (#17106)
• fix(aws): Use file link in dependency version (#17111)
• fix(cloudflare): Allow non uuid workflow instance IDs (#17121)
• fix(cloudflare): Avoid turning DurableObject sync methods into async (#17184)
• fix(core): Fix OpenAI SDK private field access by binding non-instrumented fns (#17163)
• fix(core): Fix operation name for openai responses API (#17206)
• fix(core): Update ai.response.object to gen_ai.response.object (#17153)
• fix(nextjs): Flush in route handlers (#17223)
• fix(nextjs): Handle async params in url extraction (#17162)
• fix(nextjs): Update stackframe calls for next v15.5 (#17156)
• fix(node): Add mechanism to fastifyIntegration error handler (#17208)
• fix(node): Ensure tool errors for vercelAiIntegration have correct trace connected (#17132)
• fix(node): Fix exports for openai instrumentation (#17238)
• fix(node): Handle stack traces with data URI filenames (#17218)
• fix(react): Memoize wrapped component to prevent rerenders (#17230)
• fix(remix): Ensure source maps upload fails silently if Sentry CLI fails (#17082)
• fix(replay): Fix re-sampled sessions after a click (#17008)
• fix(svelte): Do not insert preprocess code in script module in Svelte 5 (#17114)
• fix(sveltekit): Align error status filtering and mechanism in handleErrorWithSentry (#17157)

Work in this release was contributed by @richardjelinek-fastest. Thank you for your contribution!