Closed as not planned
Closed as not planned
Copy link
Labels
Description
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
7.64.0 7.73.0
Framework Version
Node 18.15.0
Link to Sentry event
[private]
SDK Setup
import * as Sentry from '@sentry/node'
Sentry.init({
environment: ...,
dsn: ...,
tracesSampleRate: 1.0,
includeLocalVariables: true,
integrations: [
new Sentry.Integrations.LocalVariables({
captureAllExceptions: true,
}),
],
debug: true,
})Steps to Reproduce
I'm trying to use @sentry/node's new includeLocalVariables (https://blog.sentry.io/local-variables-for-nodejs-in-sentry/).
I'm using Sentry SDK 7.73.0 with Node 18.15.0 (TypeScript, without ESM modules), which should work fine. But my caught errors do not show any local variables in the Sentry Dashboard.
Expected Result
Each caught error would the values of show local variables as such on the Sentry dashboard (picture from the blog post):
Actual Result
The errors show up fine as before, but no local variables can be seen anywhere from the dashboard:
┆Issue is synchronized with this Jira Improvement by Unito
Reacted by Riccardo Albertazzi, Henrikh Kantuni, David Axelrod, G and amaurymercier
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsNo status
- StatusShow more project fieldsNo status
- StatusShow more project fieldsWaiting for: Community


Activity
[-]`@sentry/node` with `includeLocalVariables` is not showing local variables with errors[/-][+]`@sentry/node` with `includeLocalVariables` is not showing anything about local variables on any errors on the Sentry dashboard[/+]timfish commentedon Sep 4, 2023
martson77 commentedon Sep 15, 2023
+1
64 remaining items
maximlopin2 commentedon Feb 22, 2024
Yes, now it at least shows one of the variables 🤔
lforst commentedon Feb 23, 2024
@maximlopin2 I think that is as good as it gets for now 🤔 @timfish we need a stack frame to match stuff right? Maybe there's an issue with top level calls.
Also @maximlopin2 are just doing plain Node.js code or ts-node or something like that. I am thinking that the runtime optimized
someVariable2away when the exception was recorded...timfish commentedon Feb 23, 2024
I'll add some tests for top level capture and see if we can add any special handling for that.
getsantry commentedon Jul 5, 2024
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label
Waiting for: Community, I will leave it alone ... forever!"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀