You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/resque_stuck_queue/config.rb
+15-14Lines changed: 15 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -19,20 +19,21 @@ module StuckQueue
19
19
classConfig < Hash
20
20
21
21
OPTIONS_DESCRIPTIONS={
22
-
:triggered_handler=>"set to what gets triggered when resque-stuck-queue will detect the latest heartbeat is older than the trigger_timeout time setting.\n\tExample:\n\tResque::StuckQueue.config[:triggered_handler] = proc { |queue_name, lagtime| send_email('queue \#{queue_name} isnt working, aaah the daemons') }",
23
-
:recovered_handler=>"set to what gets triggered when resque-stuck-queue has triggered a problem, but then detects the queue went back down to functioning well again(it wont trigger again until it has recovered).\n\tExample:\n\tResque::StuckQueue.config[:recovered_handler] = proc { |queue_name, lagtime| send_email('phew, queue \#{queue_name} is ok') }",
24
-
:heartbeat_interval=>"set to how often to push the 'heartbeat' job which will refresh the latest working time.\n\tExample:\n\tResque::StuckQueue.config[:heartbeat_interval] = 5.minutes",
25
-
:watcher_interval=>"set to how often to check to see when the last time it worked was.\n\tExample:\n\tResque::StuckQueue.config[:watcher_interval] = 1.minute",
26
-
:trigger_timeout=>"set to how much of a resque work lag you are willing to accept before being notified. note: take the :watcher_interval setting into account when setting this timeout.\n\tExample:\n\tResque::StuckQueue.config[:trigger_timeout] = 9.minutes",
27
-
:warn_interval=>"optional: if set, it will continiously trigger/warn in spaces of this interval after first trigger. eg, as long as lagtime keeps on being above trigger_timeout/recover hasn't occured yet.",
28
-
:redis=>"set the Redis StuckQueue will use. Either a Redis or Redis::Namespace instance.",
29
-
:heartbeat_key=>"optional, name of keys to keep track of the last good resque heartbeat time",
30
-
:triggered_key=>"optional, name of keys to keep track of the last trigger time",
31
-
:logger=>"optional, pass a Logger. Default a ruby logger will be instantiated. Needs to respond to that interface.",
32
-
:queues=>"optional, monitor specific queues you want to send a heartbeat/monitor to. default is [:app]",
33
-
:abort_on_exception=>"optional, if you want the resque-stuck-queue threads to explicitly raise, default is true",
34
-
:heartbeat_job=>"optional, your own custom refreshing job. if you are using something other than resque",
35
-
:enable_signals=>"optional, allow resque::stuck's signal_handlers which do mostly nothing at this point. possible future plan: log info, reopen log file, etc.",
22
+
:triggered_handler=>"set to what gets triggered when resque-stuck-queue will detect the latest heartbeat is older than the trigger_timeout time setting.\n\tExample:\n\tResque::StuckQueue.config[:triggered_handler] = proc { |queue_name, lagtime| send_email('queue \#{queue_name} isnt working, aaah the daemons') }",
23
+
:recovered_handler=>"set to what gets triggered when resque-stuck-queue has triggered a problem, but then detects the queue went back down to functioning well again(it wont trigger again until it has recovered).\n\tExample:\n\tResque::StuckQueue.config[:recovered_handler] = proc { |queue_name, lagtime| send_email('phew, queue \#{queue_name} is ok') }",
24
+
:heartbeat_interval=>"set to how often to push the 'heartbeat' job which will refresh the latest working time.\n\tExample:\n\tResque::StuckQueue.config[:heartbeat_interval] = 5.minutes",
25
+
:watcher_interval=>"set to how often to check to see when the last time it worked was.\n\tExample:\n\tResque::StuckQueue.config[:watcher_interval] = 1.minute",
26
+
:trigger_timeout=>"set to how much of a resque work lag you are willing to accept before being notified. note: take the :watcher_interval setting into account when setting this timeout.\n\tExample:\n\tResque::StuckQueue.config[:trigger_timeout] = 9.minutes",
27
+
:warn_interval=>"optional: if set, it will continiously trigger/warn in spaces of this interval after first trigger. eg, as long as lagtime keeps on being above trigger_timeout/recover hasn't occured yet.",
28
+
:redis=>"set the Redis StuckQueue will use. Either a Redis or Redis::Namespace instance.",
29
+
:heartbeat_key=>"optional, name of keys to keep track of the last good resque heartbeat time",
30
+
:triggered_key=>"optional, name of keys to keep track of the last trigger time",
31
+
:logger=>"optional, pass a Logger. Default a ruby logger will be instantiated. Needs to respond to that interface.",
32
+
:queues=>"optional, monitor specific queues you want to send a heartbeat/monitor to. default is [:app]",
33
+
:abort_on_exception=>"optional, if you want the resque-stuck-queue threads to explicitly raise, default is true",
34
+
:heartbeat_job=>"optional, your own custom refreshing job. if you are using something other than resque",
35
+
:enable_signals=>"optional, allow resque::stuck's signal_handlers which do mostly nothing at this point. possible future plan: log info, reopen log file, etc.",
36
+
:disconnect_recovery=>"optional, continues running resque-stuck-queue even if there is an issue connecting to redis. Will continue looping and making attempts until connection is re-established. Default is false",
0 commit comments