[Next.js 14] Profiling / app router / server actions

[leonardofaria]

Hi

I am trying to add profiling in my app. Followed this page however nothing shows up in my profiling tab.

I noticed that the page only mentions changes in the sentry.client.config.ts, not in the sentry.server.config.ts.

For context, my app uses app router and the majority of the features use server actions. The goal is to track the operations from different endpoints (mostly Prisma selects)

Does make sense to use Sentry.browserProfilingIntegration() in the server config?

[lforst]

Does make sense to use Sentry.browserProfilingIntegration() in the server config?

No, browser profiling as the name indicates only works in the browser. Can you share all the changes you did and your setup? Thanks!

[lforst]

You're not using the node profiling integration in your server config: https://docs.sentry.io/platforms/javascript/guides/node/profiling/

[leonardofaria]

@lforst updated the setup:

sentry.server.config.ts / sentry.edge.config.ts

import * as Sentry from '@sentry/nextjs';
import { nodeProfilingIntegration } from '@sentry/profiling-node';

Sentry.init({
  enabled: process.env.NODE_ENV === 'production',
  dsn: 'https://REDACTED',
  tracesSampleRate: 1,
  debug: false,
  release: process.env.NEXT_PUBLIC_SENTRY_RELEASE,
  integrations: [nodeProfilingIntegration()],
});

Nothing being reported here: https://pistachio-x0.sentry.io/profiling/?project=4507376747937792
The error monitoring works fine, so the DSN and auth token are correct.

Found this similar issue in this repo, but no other documentation on how to make this work: getsentry/sentry#56153 (comment)

[lforst]

Please set a profilesSampleRate as outlined here: https://docs.sentry.io/platforms/javascript/guides/node/profiling/#enabling-profiling

[leonardofaria]

@lforst Thanks for catching that, silly mistake 🤦🏼 - added but still stuck:

// This file configures the initialization of Sentry on the server.
// The config you add here will be used whenever the server handles a request.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from '@sentry/nextjs';
import { nodeProfilingIntegration } from '@sentry/profiling-node';

Sentry.init({
  enabled: process.env.NODE_ENV === 'production',

  dsn: 'https://REDACTED',

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Set profilesSampleRate to 1.0 to profile every transaction.
  // Since profilesSampleRate is relative to tracesSampleRate,
  // the final profiling rate can be computed as tracesSampleRate * profilesSampleRate
  // For example, a tracesSampleRate of 0.5 and profilesSampleRate of 0.5 would
  // result in 25% of transactions being profiled (0.5*0.5=0.25)
  profilesSampleRate: 1.0,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  release: process.env.NEXT_PUBLIC_SENTRY_RELEASE,

  integrations: [nodeProfilingIntegration()],

  // Uncomment the line below to enable Spotlight (https://spotlightjs.com)
  // spotlight: process.env.NODE_ENV === 'development',
});

Also for context, this is a Next.js 14 app, using their appDir feature.
Tried to run this locally but I don't think I can see any trace of request going to Sentry (I don't think silent and debug does the trick)

[lforst]

We're getting to a point where we need concrete reproduction we can run.