Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

bad syntax for links

  • Loading branch information...
commit 5daf04250ccd8361b72d5f1c88dbfeb6bd5035e3 1 parent b3ea630
Chris authored
Showing with 1 addition and 1 deletion.
  1. +1 −1  README.md
View
2  README.md
@@ -91,7 +91,7 @@ after "instrumental:util:deploy_end", "instrumental:record_deploy_notice"
## Tracking metrics in Resque jobs (and Resque-like scenarios)
-If you plan on tracking metrics in your Resque jobs, you will need to explicitly flush your metrics when the jobs are finished. You can accomplish this by adding `after_perform` and `on_failure` hooks to your Resque jobs. See the Resque [hooks documentation][https://github.com/defunkt/resque/blob/master/docs/HOOKS.md] for more information.
+If you plan on tracking metrics in your Resque jobs, you will need to explicitly flush your metrics when the jobs are finished. You can accomplish this by adding `after_perform` and `on_failure` hooks to your Resque jobs. See the Resque [hooks documentation](https://github.com/defunkt/resque/blob/master/docs/HOOKS.md) for more information.
You're required to do this because Resque calls `exit!` when a worker has finished processing, which bypasses Ruby's `at_exit` hooks. The Instrumental Agent installs an `at_exit` hook to flush any pending metrics to the servers, but this hook is bypassed by the `exit!` call; any other code you rely that uses `exit!` should call `I.flush` to ensure any pending metrics are correctly sent to the server before exiting the process.
Please sign in to comment.
Something went wrong with that request. Please try again.