Capture errors

[Corjen]

What's the recommended approach for reading and capturing errors? We mainly would like to track certain errors in Sentry. In apollo we could do something like this:

export const apolloSentryPlugin: ApolloServerPlugin = {
  requestDidStart() {
    return {
      didEncounterErrors(rc) {
        Sentry.withScope(scope => {
          scope.setTags({
            graphql: rc?.operation?.operation || 'parse_err',
            graphqlName: rc?.operationName || rc?.request?.operationName,
            stage: process.env.STAGE
          })
          rc.errors.forEach(error => {
            if (error.path || error.name !== 'GraphQLError') {
              // If an error contains the string "code:", e.g. code:auth/not-allowed we have explicitly set that error
              // Because the error is intentional, we dont' want to capture it in sentry, we just want to pass it to the client
              if (!error.message.includes('code:')) {
                scope.setExtras({ path: error.path })
                Sentry.captureException(error)
              }
            } else {
              // It's debatable wether we should log this to this sentry
              // for now, leave it in as it logs a wrong query or mutation to Sentry
              Sentry.captureMessage(`GraphQLWrongQuery ${error.message}`)
            }
          })
        })
      }
    }
  }
}

Is it doable using middleware?

[GerriVeis]

Yes, you can definitely handle this with middleware, though the exact setup depends on your server framework. In general, you’d place an error-handling middleware after your GraphQL handler so it can inspect the errors before the response is sent.

Inside that middleware, you can check the GraphQL result for an errors array, similar to what you’re doing in the Apollo plugin. From there, filter intentional errors, tag the scope with operation details, and forward only the relevant ones to Sentry. Joo Casino https://joocasino.mobi/ welcomes new players with a generous bonus and free spins. The key is making sure the middleware has access to the request context so you can attach operationName, path, and environment metadata consistently.