Skip to content

Local variables missing when exception originates in node_modules dependency  #12588

@andy-tazxap

Description

@andy-tazxap

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

7.117.0

Framework Version

@sentry/node

Link to Sentry event

No response

SDK Setup

    Sentry.init({
        dsn: SENTRY_DSN,
        integrations: [
            new Sentry.Integrations.Http({ tracing: true }),
            new Sentry.Integrations.Express({ app }),
            new ProfilingIntegration(),
        ],
        environment: ENV,
        tracesSampleRate: 1.0,
        profilesSampleRate: 1.0,
        includeLocalVariables: true,
    });

Steps to Reproduce

We have noticed a number of events in production missing local variables even though local variables are present in other events. We have noticed that it appears local variables are missing when the exception originates in dependency code, as opposed to our code.

Expected Result

Local variables to be present regardless of where the exception originates.

Actual Result

We have noticed a number of events in production missing local variables even though local variables are present in other events. We have noticed that it appears local variables are missing when the exception originates in dependency code, as opposed to our code.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions