Updates to Resque support and documentation #768
Merged
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.
While testing a solution to handle master-worker architectures, I found an occasional error in the resque spy when the
@payload
class
value is a String, not aClass
object.Also, I discovered that Resque calls
exit!
when terminating a fork, which bypassesat_exit
hooks. If the agent'sat_exit
hook is not called, the events aren't flushed so some may not make it to the APM server. Therefore, users must set the Resque env variableRUN_AT_EXIT_HOOKS
totrue
in order to ensure that all agent events created in a fork are sent to the APM server.