Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Reconstruct full stacks for async execution context #286

Open
aalexand opened this issue Aug 29, 2018 · 0 comments
Open

Reconstruct full stacks for async execution context #286

aalexand opened this issue Aug 29, 2018 · 0 comments
Labels
api: cloudprofiler Issues related to the googleapis/cloud-profiler-nodejs API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@aalexand
Copy link
Contributor

Since a typical Node.js program is full of async execution, the profiler stacks may look confusing as the current stack does not contain the stack of the call that actually scheduled the currently executing call chain. This is a known problem of the Node.js environment, there are solutions like https://www.npmjs.com/package/stackup, see also slides https://www.slideshare.net/isharabash/cls-and-asynclistener. The profiler should do this stack reconstruction automatically.

@ofrobots Feedback / thoughts?
@JustinBeckwith JustinBeckwith added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Sep 13, 2018
@google-cloud-label-sync google-cloud-label-sync bot added the api: cloudprofiler Issues related to the googleapis/cloud-profiler-nodejs API. label Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api: cloudprofiler Issues related to the googleapis/cloud-profiler-nodejs API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JustinBeckwith @aalexand