-
Notifications
You must be signed in to change notification settings - Fork 784
Add busy_threads
metric to Puma integration
#2697
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
base: master
Are you sure you want to change the base?
Add busy_threads
metric to Puma integration
#2697
Conversation
b1655c8
to
142b249
Compare
I created a documentation request here |
142b249
to
382bb73
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.
Small suggestions
This new stat was [added about 6 months ago](puma/puma#3517) to track "the overall current state of work to be done and the capacity to do it". It seems like it could be useful to track, potentially for autoscaling or other applications.
cbb53b2
to
9c2adbb
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.
How does this sound to you?
Co-authored-by: May Lee <[email protected]>
Getting an eng review on this. |
@f1sherman Hello 👋 ! Looks good to me. Left a small correction for the metadata.csv. Thanks for the contribution! |
Co-authored-by: Steven Yuen <[email protected]>
@steveny91 thanks for the suggestion, I've made that change! |
This new stat was added about 6 months ago to track "the overall current state of work to be done and the capacity to do it". It seems like it could be useful to track, potentially for autoscaling or other applications.
What does this PR do?
This adds the new(ish)
busy_threads
stat as a metric.Motivation
I want to track it and experiment with using it for autoscaling
Review checklist
no-changelog
label attachedAdditional Notes
Anything else we should know when reviewing?