-
Notifications
You must be signed in to change notification settings - Fork 378
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
Use process.getActiveResourcesInfo()
in process metrics
#485
Use process.getActiveResourcesInfo()
in process metrics
#485
Conversation
cc @SimenB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, but the tests need to be skipped in Node.js <v17 for CI to pass.
It would be great to provide upgrade guidance in the changelog since the metric name (and maybe labels?) change. (Also noting that this PR is semver major for that reason.)
52240f0
to
0711bc5
Compare
We should use process.getActiveResourcesInfo() here because it is a public alternative of the private APIs process._getActiveHandles() and process._getActiveRequests(). Refs: https://nodejs.org/api/process.html#processgetactiveresourcesinfo Signed-off-by: Darshan Sen <[email protected]>
0711bc5
to
1fe6ef6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you!
@RaisinTen - @cjihrig suggested that we actually keep both of these sets of metrics for now: https://twitter.com/cjihrig/status/1481433837255155717. What do you think? |
@zbjornson yes, I agree that we should keep both the set of metrics for now. I sent #488 to do so. :) |
We should use
process.getActiveResourcesInfo()
here because it is apublic alternative of the private APIs
process._getActiveHandles()
andprocess._getActiveRequests()
.Refs: https://nodejs.org/api/process.html#processgetactiveresourcesinfo
Signed-off-by: Darshan Sen [email protected]