Publish Puma Listener Metrics by EC2 Instance ID #70300
Merged
+31
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephenliang
approved these changes
Jan 14, 2026
6fa7144 to
873346c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://codedotorg.atlassian.net/browse/INF-1793
Help identify whether a subset of EC2 Instances is experiencing request processing latency within
pumaby publishing puma active/calling/queued HTTP request metrics by Instance ID in addition to per system.Testing story
bundle exec rake adhoc:start RAILS_ENV=adhoc STACK_NAME=adhoc-puma-metrics-instance-idDeployment strategy
Follow-up work
Privacy
Security
Caching
PR Creation Checklist: