We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When an error occurs the sentryMiddleware never reports an error. The error should be reported in
transformOutput({ result, step }) { // Capture step output and log errors if (step) { Sentry.setTags({ "inngest.step.name": step.displayName, "inngest.step.op": step.op, }); if (result.error) { Sentry.captureException(result.error); } } },
but step is always undefined.
step
To Reproduce Add example middleware as per https://www.inngest.com/docs/reference/middleware/examples#adding-sentry-error-reporting-and-tracing.
Throw an error in a handler.
Expected behavior Error should be report to Sentry
Screenshots / Stack trace dump If applicable, add screenshots or paste what is output in your terminal to help explain your problem.
System info
Additional context Workaround is to report the error without the step metadata
transformOutput({ result, step }) { // Capture step output and log errors if (step) { Sentry.setTags({ "inngest.step.name": step.displayName, "inngest.step.op": step.op, }); } if (result.error) { Sentry.captureException(result.error); } },
The text was updated successfully, but these errors were encountered:
INN-3159 Sentry middleware example doesn't work
Sorry, something went wrong.
INN-3161 Sentry middleware example doesn't work
Hi, @opsb! 👋
Ah - good find. What version of Sentry are you using?
We have some discussion in #471 which results in the release of a new @inngest/middleware-sentry package in #598.
@inngest/middleware-sentry
I'd love it if you could test out the new package and see if this also solves your issue, though we're targeting @sentry/node>=8.0.0 for that.
@sentry/node>=8.0.0
Closing this - please address any further issues here in #471 or #598.
djfarrelly
No branches or pull requests
Describe the bug
When an error occurs the sentryMiddleware never reports an error. The error should be reported in
but
step
is always undefined.To Reproduce
Add example middleware as per https://www.inngest.com/docs/reference/middleware/examples#adding-sentry-error-reporting-and-tracing.
Throw an error in a handler.
Expected behavior
Error should be report to Sentry
Screenshots / Stack trace dump
If applicable, add screenshots or paste what is output in your terminal to help explain your problem.
System info
Additional context
Workaround is to report the error without the step metadata
The text was updated successfully, but these errors were encountered: