Rollbar setup

Gemfile

@@ -68,6 +68,8 @@ gem 'redis'
 
 gem 'fake_email_validator'
 
+gem 'rollbar', '~> 1.5.3'
+
 group :development do
   # require spring 1.3.5 since shit's on fire on my local instance with 1.3.4 (Gem::LoadError)
   gem 'spring', '~> 1.3.5'

Gemfile.lock

@@ -360,6 +360,8 @@ GEM
     remotipart (1.2.1)
     responders (2.1.0)
       railties (>= 4.2.0, < 5)
+    rollbar (1.5.3)
+      multi_json (~> 1.3)
     rspec-core (3.0.4)
       rspec-support (~> 3.0.0)
     rspec-expectations (3.0.4)
@@ -529,6 +531,7 @@ DEPENDENCIES
   rake
   redcarpet
   redis
+  rollbar (~> 1.5.3)
   rspec-rails (~> 3.0.0)
   ruby-progressbar
   sanitize

config/initializers/rollbar.rb

@@ -0,0 +1,54 @@
+require 'rollbar/rails'
+Rollbar.configure do |config|
+  # Without configuration, Rollbar is enabled in all environments.
+  # To disable in specific environments, set config.enabled=false.
+  
+  config.access_token = ENV['ROLLBAR_ACCESS_TOKEN']
+
+  # Here we'll disable in 'test' and 'development':
+  if Rails.env.test? or Rails.env.development?
+    config.enabled = false
+  end
+
+  # scrub out the "confirmation_token" field
+  config.scrub_fields |= [:confirmation_token]
+
+  # By default, Rollbar will try to call the `current_user` controller method
+  # to fetch the logged-in user object, and then call that object's `id`,
+  # `username`, and `email` methods to fetch those properties. To customize:
+  # config.person_method = "my_current_user"
+  # config.person_id_method = "my_id"
+  # config.person_username_method = "my_username"
+  # config.person_email_method = "my_email"
+
+  # If you want to attach custom data to all exception and message reports,
+  # provide a lambda like the following. It should return a hash.
+  # config.custom_data_method = lambda { {:some_key => "some_value" } }
+
+  # Add exception class names to the exception_level_filters hash to
+  # change the level that exception is reported at. Note that if an exception
+  # has already been reported and logged the level will need to be changed
+  # via the rollbar interface.
+  # Valid levels: 'critical', 'error', 'warning', 'info', 'debug', 'ignore'
+  # 'ignore' will cause the exception to not be reported at all.
+  # config.exception_level_filters.merge!('MyCriticalException' => 'critical')
+  #
+  # You can also specify a callable, which will be called with the exception instance.
+  # config.exception_level_filters.merge!('MyCriticalException' => lambda { |e| 'critical' })
+
+  # Enable asynchronous reporting (uses girl_friday or Threading if girl_friday
+  # is not installed)
+  # config.use_async = true
+  # Supply your own async handler:
+  # config.async_handler = Proc.new { |payload|
+  #  Thread.new { Rollbar.process_payload_safely(payload) }
+  # }
+
+  # Enable asynchronous reporting (using sucker_punch)
+  # config.use_sucker_punch
+
+  # Enable delayed reporting (using Sidekiq)
+  # config.use_sidekiq
+  # You can supply custom Sidekiq options:
+  config.use_sidekiq 'queue' => 'rollbar'
+end

config/sidekiq.yml

@@ -10,3 +10,4 @@ production:
   - paperclip
   - mailer
   - deletion
+  - rollbar