Add specific worker backend notes and table with collected metrics for each backend #228
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
So we can document a gotcha with using resque-scheduler and our latency extension.
Makes it easier to visualize which supports queue latency vs depth vs both, and busy support.
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.
We needed a place to document a gotcha recently discovered with
rescue-schedulerthat wasn't loading our latency extension, so I added another sub-section under "Worker adapters" for that.This also takes the opportunity to document what each adapter collects specifically, so it's easier to visualize where queue latency vs queue depth is available, and which can support busy (if enabled).
See the Readme live: https://github.com/judoscale/judoscale-ruby/tree/ca-readme?tab=readme-ov-file#specific-worker-backend-notes
Sample