Open andy-tazxap opened 2 weeks ago
Hey @andy-tazxap thanks for writing in! The current local variables implementation only grabs local variables from in_app
frames (errors from direct app code)
We can consider exposing an opt-in option to attach variables to any kind of frame. Would you be interested in making a PR for this change?
Hey @AbhiPrasad thanks for getting back to me! Ahh that explains it, is that specified in the docs anywhere, just wondering if I was reading the wrong thing?
Yeah maybe making this opt-in would make sense me, I could definitely make the PR but I probably won't have the chance to do this for a month or so. I'll update here when I have it ready, if anyone needs this feature more urgently feel free to create the PR ahead of me!
is that specified in the docs anywhere
This is something we missed, I added a PR to update the docs accordingly: https://github.com/getsentry/sentry-docs/pull/10461
Thanks for letting us know about this!
No worries, thanks for the speedy response here!
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
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.