GraphQL Integration in AWS Lambda doesn't instrument resolvers #16092
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/aws-serverless
SDK Version
9.13.0
Framework Version
AWS Lambda with Apollo Server GraphQL
Link to Sentry event
Reproduction Example/SDK Setup
Sentry.init({
dsn: 'MY_DSN',
release: 'MY_RELEASE',
environment: 'MY_ENVIRONMENT',
tracesSampleRate: 0.1,
profilesSampleRate: 0.1,
debug: true,
integrations: [
Sentry.rewriteFramesIntegration({ root: process.cwd() }),
Sentry.graphqlIntegration({
ignoreResolveSpans: false,
useOperationNameForRootSpan: true,
ignoreTrivialResolveSpans: false,
}),
Sentry.knexIntegration(),
Sentry.postgresIntegration(),
nodeProfilingIntegration(),
],
});Steps to Reproduce
- Set up an AWS Lambda function with Apollo Server GraphQL
- Configure Sentry with GraphQL integration as shown above
- Make GraphQL requests to the Lambda function
- Check Sentry for traces
Expected Result
- GraphQL nested resolvers should be instrumented and appear as spans in the trace
Actual Result
- Only
graphql.parsespans are created, no resolver spans appear
Additional Information
I've noticed that while the GraphQL integration is installed and appears to be patching the GraphQL module, it's not properly instrumenting resolver functions in the AWS Lambda environment. This seems to be related to issue #15699, but specifically focuses on the resolver instrumentation not working at all.
The logs show that the GraphQL parser is being instrumented, but no spans are created for resolvers despite setting ignoreResolveSpans: false.