-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[node] Stack locals #6369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
summarizing some internal discussions on this issue in story form: @lforst found out
|
1 similar comment
https://github.com/kamilogorek/sentry-node-local-variables @kamilogorek example
https://github.com/kamilogorek/sentry-node-local-variables/blob/master/vars.js |
Oh this is really nice! |
How do you want this adding? Keep it as an integration? Should I do some testing to see how long this suspends the event loop to determine if this can be enabled by default? |
Yes please!
This would be great, but we can also put this off. We can make this opt-in to start, and default it in v8. So we do it the following way.
|
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 label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Question - is there anything we need to do/tell the customer to do on the issues details page to enable this if this is not enabled? |
@therealarkin user need to configure like this covered here blog post and SDK docs here not sure how to detect if they are missing, in terms of the event payload |
Problem Statement
Node js does not capture stack locals similar to a few other server side SDKs
comment from an unrelated NextJs issue: #6321 (comment)
Could this be easily applied to remix, next, and any other fromworks depending on Node?
Solution Brainstorm
There are possible concerns in Node that this would create some overhead (if it is possible at all)
If it was to be implemented could it be controlled by some user flag?
The text was updated successfully, but these errors were encountered: