Closed
Description
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/nestjs
SDK Version
8.19.0
Framework Version
10.3.10
Link to Sentry event
SDK Setup/Reproduction Example
Link to reproduction in a fresh Nest.js project:
https://github.com/nino-vrijman/nest-graphql-sentry-transation-name
// eslint-disable-next-line @typescript-eslint/no-var-requires
const Sentry = require('@sentry/nestjs');
// Ensure to call this before requiring any other modules!
Sentry.init({
dsn: process.env.SENTRY_DSN,
sampleRate: 1.0,
tracesSampleRate: 1.0,
profilesSampler: 1.0,
environment: 'localhost',
integrations: [Sentry.nestIntegration(), Sentry.graphqlIntegration()],
});
Steps to Reproduce
- Run back-end using
SENTRY_DSN=<your sentry dsn> npm run start:dev
- Do a simple GraphQL request with a name of choice:
query TestTransactionName { hello }
- Check logs that the transaction name seems to have changed in multiple places, most notably in the
isolation scope
which seems to be the culprit. Only the active span name has been updated. - Check Sentry > Performance and see that every query is grouped under
POST /graphql
instead of the GraphQL query name like TestTransactionName
Expected Result
The Transaction name on the Performance page is set to GraphQL query TestTransactionName
Actual Result
Everything is grouped under POST /graphql
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
No status