I noticed when I added Sentry.init
to my Express/NodeJS application, it logs the call arguments of every Sequelize query. Specifically I have:
Sentry.init({
dsn: process.env.SENTRY_DSN,
integrations: [
// HTTP calls tracing
new Sentry.Integrations.Http({ tracing: true }),
// enable Express.js middleware tracing
new Tracing.Integrations.Express({ app }),
],
environment: process.env.NODE_ENV,
tracesSampleRate:
parseFloat(process.env.SENTRY_TRACE_SAMPLE_RATE as string) || 1.0,
enabled: process.env.NODE_ENV !== "test",
});
And it logs:
Executing (default): SELECT "id", "firebase_auth_id", "private", "disabled", "admin", "geo_activated", "provider_id", "email", "phone_number", "bio", "gender", "first_name", "last_name", "profile_pic_url", "latitude", "longitude", "location_timestamp", "maximum_distance_km", "ntrp_rating", "partner_ntrp_rating_min", "partner_ntrp_rating_max", "tennis_match_type", "createdAt", "updatedAt", incomplete_profile("User".id) AS "incomplete" FROM "Users" AS "User" WHERE "User"."firebase_auth_id" = 'XXX' LIMIT 1; {
plain: true,
raw: false,
logging: [Function: log],
attributes: [
'id',
'firebase_auth_id',
'private',
...
including query replacements, which is problematic.
Is there a config I can toggle to disable this? It seems the only way is to remove Sentry.init
entirely (commenting out all of the integrations an other config does not help).