SQL Queries Missing From Performance “Queries” View

[dalnoki]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/sveltekit

SDK Version

10.25.0

Framework Version

SvelteKit 2.21.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

see internally

Steps to Reproduce

SQL queries used to appear in the “Queries” view, but now no DB spans appear at all. Postgres instrumentation should be auto-enabled in SvelteKit, but it seems inactive.

Even after setting tracesSampleRate to 1,

op: "db.sql.query" or db.system = "postgresql" or any database-related spans. This suggests auto-instrumentation is not working as expected.

Expected Result

Queries appear on the Backend -> Queries page

Actual Result

Queries don't currently appear on the Backend -> Queries page

Additional Context

PG version: pg: 8.16.0 (used by remult)

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1180

[JPeer264]

I just tried it with Svelte and almost the same code with an Express app and it seems to work for Express, but not with Sveltekit.

@Lms24 do you know if there is something missing for Sveltekit?

[Lms24]

After reading through the zendesk ticket, I assume the most likely issue here is the used Sveltekit version. The easiest fix is to upgrade to at least 2.31.0 or newer and to follow our manual setup instructions to use SvelteKit's builtin tracing and observability support. This will allow auto instrumentation like the one for pg to be correctly initialized.

The reason here is that Sveltekit emits ESM code. because of this, most auto instrumentation initialized too late when Sentry.init was called in hooks.server.ts as we previously instructed. As for why this was working earlier: My best guess would be at that time the used adapter transpiled to CommonJS (?).

If upgrading is not an option, I can only recommend to move the Sentry.init call from hooks.server.ts to something like instrument.server.mjs and start the sveltekit server with node --import ./instrument.server.mjs ./path/to/server/entry. This of course requires being able to modify the server start command.

[jycouet]

Hi @Lms24 👋

The thing is that due to houdini I have to have kit bellow 2.21.1. (I should probably try houdini@next and see how it goes!)

I understand better the state now... maybe you should update the doc https://docs.sentry.io/platforms/javascript/guides/sveltekit/ because just:

we recommend 2.31.0 or higher for best support

Is maybe a bit light.

I'll try update houdini and kit or instrument.server.mjs. Then will let you know.
Thx