Noemi

Re-opening this to use as a tracking issue for #1053 and pending work mentioned within it (headers are still missing)

Hi @tmaier! Our ActiveJob integration aims to be compatible with all adapters, including SolidQueue, which we support. We'll look into amending our documentation to make it clearer.

Hi @scottpi! Could you let us know which `redis` gem version you're using?

Going by the linked PR, it seems that it only records exceptions in middlewares? Does that cover our needs?

The customer reports that calls to Next.js `fetch` are no longer instrumented. Research if Next.js 14 no longer emits OpenTelemetry spans for its custom `fetch` implementation?

The customer also ran into an issue when importing AppSignal's helpers from Next.js code, where Webpack fails to bundle AppSignal: > ``` > ⨯ ./node_modules/@appsignal/nodejs/build/Release/extension.node > Module parse failed: Unexpected...

Another customer ([Intercom](https://app.intercom.com/a/inbox/yzor8gyw/inbox/shared/unassigned/conversation/16410700308901)) reported an "AppSignal not starting, no valid configuration found" error, which is not of the same nature as the above issues, but should also be looked into.

Finally got around to start testing this. Ran into the Webpack bundling issue head-on, and I was able to fix it using the `serverComponentsExternalPackages` configuration option. Will reach out to...

Sent a PR to Vercel to add `"@appsignal/nodejs"` to the `serverComponentsExternalPackages` default list: https://github.com/vercel/next.js/pull/64503 Reproduced the issue with the `UNKNOWN` method and implemented a fix for it in the agent:...

I was not able to reproduce server-side calls performed with `fetch` not showing up. I will reach out to the customer.