Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/return-nil/sidekiq-failures below:

return-nil/sidekiq-failures: Keep track of Sidekiq failed jobs

Keeps track of Sidekiq failed jobs and adds a tab to the Web UI to let you browse them. Makes use of Sidekiq's custom tabs and middleware chain.

It mimics the way Resque keeps track of failures.

WARNING: by default sidekiq-failures will keep up to 1000 failures. See Maximum Tracked Failures below.

Add this line to your application's Gemfile:

Simply having the gem in your Gemfile is enough to get you started. Your failed jobs will be visible via a Failures tab in the Web UI.

If you have not previously used the Web UI, it is a part of the Sidekiq gem. See Sidekiq's docs about Web UI here.

Since each failed job/retry creates a new failure entry that will only be removed by you manually, your failures list might consume more resources than you have available.

To avoid this sidekiq-failures adopts a default of 1000 maximum tracked failures.

To change the maximum amount:

Sidekiq.configure_server do |config|
  config.failures_max_count = 5000
end

To disable the limit entirely:

Sidekiq.configure_server do |config|
  config.failures_max_count = false
end

Sidekiq-failures offers three failures tracking options (per worker):

Tracks failures every time a background job fails. This mean a job with 25 retries enabled might generate up to 25 failure entries. If the worker has retry disabled only one failure will be tracked.

This is the default behavior but can be made explicit with:

class MyWorker
  include Sidekiq::Worker

  sidekiq_options :failures => true # or :all

  def perform; end
end

Only track failures if the job exhausts all its retries (or doesn't have retries enabled).

You can set this mode as follows:

class MyWorker
  include Sidekiq::Worker

  sidekiq_options :failures => :exhausted

  def perform; end
end

You can also completely turn off failures tracking for a given worker as follows:

class MyWorker
  include Sidekiq::Worker

  sidekiq_options :failures => false # or :off

  def perform; end
end

You can also change the default of all your workers at once by setting the following server config:

Sidekiq.configure_server do |config|
  config.failures_default_mode = :off
end

The valid modes are :all, :exhausted or :off.

Gives back the number of failed jobs currently stored in Sidekiq Failures. Notice that it's different from Sidekiq built in failed stat. Also, notice that this might be influenced by failures_max_count.

Gives a convenient way of resetting Sidekiq Failure stored failed jobs programmatically.

Sidekiq::Failures.clear_failures

To reset Sidekiq own failed stats.

Sidekiq::Failures.reset_failure_count

Depends on Sidekiq >= 4.0.0

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Released under the MIT License. See the LICENSE file for further details.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4