By default, Sentry error events will not get trace context unless you configure the scope with the transaction, as illustrated in the example below.

const Sentry = require("@sentry/node");
// Note: You MUST import @sentry/tracing package before @sentry/profiling-node
const {ProfilingIntegration} = require("@sentry/profiling-node");

  dsn: "",
  integrations: [
    // Add our Profilling integration
    new ProfilingIntegration(),
  tracesSampleRate: 1.0,
  // Set sampling rate for profiling
  profilesSampleRate: 1.0,

const transaction = Sentry.startTransaction({
  op: "transaction",
  name: "My Transaction",

// Any code executed between startTransaction and transaction.finish
// will now be automatically profiled.


How Does It Work?

Under the hood, the Sentry profiler uses V8's CpuProfiler to collect stack samples. This means that sentry/profiling-node is written as a native add-on for Node and won't run in environments like Deno or Bun. Profiling enhances

tracingThe process of logging the events that took place during a request, often across multiple services.
by providing profiles for individual transactions. This allows you to look at higher level performance information like transaction and span durations before diving deeper and looking at profiles.

Runtime Flags

The Profiling package enables you to run the profiler in either eager or lazy mode. When a profile is started while no other profiles are running, the default profiling mode (lazy) sometimes causes startProfiling calls to take a long time (sometimes in the range of a couple hundred milliseconds). The benefit of lazy logging is that it doesn't add any overhead when profiles aren't running.

If this behavior is prohibitive for your use case, you can set the environment flag shown below, which will cause the profiler to run in eager mode. Eager mode improves the performance of calls to startProfiling, but the tradeoff is small, constant CPU overhead.

// Run profiler in eager mode

We recommend you have your own CPU resource-monitoring in place, because the actual resource use could be environment-dependent.

If you have feedback or experience different behavior, please open an issue on sentry/profiling-node repository.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").