Mongoose query profiles not decoding properly with @sentry/nestjs

[unix-system]

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?

Self-hosted/on-premise

Which SDK are you using?

@sentry/nestjs

SDK Version

8.16.0

Framework Version

Nest.js 10.3.10

Link to Sentry event

No response

SDK Setup/Reproduction Example

// (in instrument.ts, required first in main.ts)
import * as Sentry from '@sentry/nestjs';
import { nodeProfilingIntegration } from '@sentry/profiling-node';

// Ensure to call this before importing any other modules!
Sentry.init({
	dsn: process.env.SENTRY_DSN,
	release: process.env.SHA,
	environment: process.env.API_STAGE === 'dev' ? 'dev' : 'production',
	debug: false,

	integrations: [
		// Add our Profiling integration
		nodeProfilingIntegration(),
		Sentry.mongooseIntegration(),
	],

	// Add Tracing by setting tracesSampleRate
	// We recommend adjusting this value in production
	tracesSampleRate: 1.0,

	// Set sampling rate for profiling
	// This is relative to tracesSampleRate
	profilesSampleRate: 1.0,
});

Steps to Reproduce

1. Use Mongoose profiler (with or without explicitly declaring it) with Nest.js and new @sentry/nestjs SDK. (Mongoose version 8.5.0)
2. Look for any auto.db.otel.mongo profile spans

Expected Result

Should show rich database information, i.e. what query was performed

Actual Result

Query result in the db.statement field looks like this: {"find":"?","filter":{"userId":"?"},"limit":"?","singleBatch":"?","batchSize":"?"} or this:

{"find":"?","filter":{"_id":{"$in":[{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}},{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}},{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}},{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}},{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}},{"buffer":{"0":"?","1":"?","2":"?","3":"?","4":"?","5":"?","6":"?","7":"?","8":"?","9":"?","10":"?","11":"?"}}]}}}

[mydea]

Hey,

this is a duplicate of #11499 - sadly, we do not support mongoose v7 & v8 as of now. You can follow the progress on this in the linked issue!