Remove barnes require so that Heroku can track Puma metrics #1451
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What it does
I noticed that we weren't seeing any Ruby metrics in Heroku, despite having followed the directions a while back to set them up:
I am interested in these metrics to help figure out how to tune the app's concurrency and ideally address the memory errors we've been seeing.
The app was setup according the the Heroku instructions, but evidently they are out of date and having an explicit require of
barnesinconfig/puma.rbloads the library before Rails, causing the Barnes server to not start properly and therefore not report metrics.