Koa request body is not captured for events

[maximedupre]

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/node

SDK Version

@sentry/node ^8.5.0

Framework Version

koa ^2.15.2

Link to Sentry event

No response

Reproduction Example/SDK Setup

This is my config:

init({
    dsn: '',
    tracesSampleRate: 0.1,
    profilesSampleRate: 1.0,
    normalizeDepth: 11,
    integrations: [nodeProfilingIntegration],
    environment: EnvVariablesUtility.NODE_ENV,
    enabled: EnvVariablesUtility.NODE_ENV !== 'local',
    beforeSend(event, hint) {
        const error = hint.originalException;

        if (isHttpError(error) && error.expose) {
            return null;
        }

        return event;
    },
});

Steps to Reproduce

The RequestData integration is a default integration and according to the doc, the request data should be included by default, however, it is not.

The issue page shows the curl request without the request data:

curl \
 -X POST \
 --compressed \
 -H "Accept: application/json, text/plain, */*" \
 -H "Accept-Encoding: gzip, br" \
 -H "Accept-Language: en-US,en;q=0.9" \
 ...
 "{the_url}"

Expected Result

The issue page shows the request body

Actual Result

The issue page doesn't show the request body

[andreiborza]

Hi @maximedupre, thanks for writing in.

Are you using @koa/bodyparser? Could you please provide a reproduction repo or stackblitz so we can further investigate?

From my testing, even with the body parser the request passed to the integration doesn't contain the body already 🤔.

[maximedupre]

Hi @andreiborza,

I'm actually using koa-better-body.

I don't have time to create a repro right now, but when I do I'll be sure to post it here.

Thanks

[andreiborza]

@maximedupre thanks, don't bother with the reproduction we identified the issue. Thanks again for reporting this.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #13746, which was included in the 8.39.0 release.