Automatic Sentry Error Handling

[thepratt]

We're in a situation that Sentry receives error logs from workflow runs (within "use workflow" and "use step" stages) but isn't creating issues without manual instrumentation of captureException. We could enable captureConsoleIntegration, but that would likely result in quite a lot of duplicates across the rest of the codebase.

Has anyone done anything special to get automatic instrumentation of workflow errors? Or is manual the way? I know errors for retry and the like are thrown, and I'd be fine with some of that noise in Sentry - I can always filter out on the Sentry side. For additional context: the rest of the application is fine, it's only code run within workflows that has this issue.

We're using the @sentry/nextjs Sentry adapter, with workflow/next, and Vercel as the workflow world.

[pranaygp]

hey @thepratt! I gave this a spin a while back - as I wanted to get errors properly propagated (FatalError vs Retryableerror etc showing up correctly on Sentry) and also to get otel spans working (datadog traces already work out of the box with workflow but I couldn't easily figure out sentry).

Ultimately we use datadog here at Vercel so we haven't felt the pain enough

Seems like like something claud should easily be able to open a PR for if you ask it in the workflow source code. wanna give it a shot? i'd be happy it review and merge something to make jt work well :)

[thepratt]

In getting datadog to work, was anything special done as part of the build toolchain (e.g. special transformations over "use step" and "use workflow") or everything worked well with normal otel exports? If the path ends up being very sentry specific I could look at a build time wrapper that runs after the workflow transformations; similar to the sentry vite plugin.

[pranaygp]

nothing special. in fact the nextjs turbopack workbench in this monorepo is hooked up to a vercel deployment with a datadog log and trace drain setup on the vercel project and it just works and emits everything. The instrumentation.ts file was the only thing needed to get tracing working - and also just this line:

registerOTel({ serviceName: 'example-nextjs-workflow' });

The rest doesn't apply on vercel and is only needed for the postgres world to startup in the CI tests

[pranaygp]

I couldn't figure out the same when hooking it up to sentry on a test project - but admittedly I also didn't spend too much time on it