Skip to content

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

f1sherman
Copy link

@f1sherman f1sherman commented May 20, 2025

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

  • PR has a meaningful title or PR has the no-changelog label attached
  • Feature or bugfix has tests
  • Git history is clean
  • If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
  • If this PR includes a log pipeline, please add a description describing the remappers and processors.

Additional Notes

Anything else we should know when reviewing?

@f1sherman f1sherman force-pushed the add-busy-threads-to-puma-integration branch from b1655c8 to 142b249 Compare May 20, 2025 19:29
@f1sherman f1sherman requested a review from a team as a code owner May 20, 2025 19:29
@f1sherman
Copy link
Author

I created a documentation request here

@maycmlee maycmlee self-assigned this May 20, 2025
@f1sherman f1sherman force-pushed the add-busy-threads-to-puma-integration branch from 142b249 to 382bb73 Compare May 20, 2025 19:37
Copy link
Contributor

@maycmlee maycmlee left a 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.
@f1sherman f1sherman force-pushed the add-busy-threads-to-puma-integration branch from cbb53b2 to 9c2adbb Compare May 20, 2025 19:41
Copy link
Contributor

@maycmlee maycmlee left a 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?

@maycmlee
Copy link
Contributor

Getting an eng review on this.

@steveny91
Copy link
Contributor

steveny91 commented May 23, 2025

@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]>
@f1sherman
Copy link
Author

@steveny91 thanks for the suggestion, I've made that change!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants