v2.6.0

Features

• Enhanced debug logging for assisting in support requests

v2.5.0

Features

• Teach tags configuration how to handle a proc to allow dynamically settings tags (#127)

Bugfixes

• Fix crash when recording breadcrumb with uninitialized store (#126)
• Make raw data handling more robus and fix in unicorn (#125)
• Backwards compatible affected_user_identifier_methods (#120)

v2.4

Features

• Add functionality to track affected user in Sidekiq jobs, refer to the README for more information, under the "Affected User Tracking in Sidekiq" heading

v2.3

Bugfixes

• Fix issue preventing affected users for a crash report from showing up in the affected users page (#119)

v2.2

Features

• Opt in support for sending exceptions in a background thread to not block web request thread during IO (#117)

Bugfixes

• Don't attempt to read raw data during GET requests or if rack.input buffer is empty

v2.1

Features

• Ability to record breadcrumbs in your code that will be sent to Raygun along with a raised exception (#113)

v2.0

With the 2.0 release, we are taking this opportunity to drop support for Ruby 1.9.3

Bugfixes:

• Fix broken handling of raw request body reading in Rack applications (#116)
  • This is a breaking change to how raw data was being read before so it requires a major version bump
  • Raw request data reading is now disabled by default and can be enabled via the record_raw_data configuration option

1.5.0

Features

• Send utcOffset with Raygun payload to calculate local server time in Raygun dashboard

1.4.0

Features:

• Raygun API url is now configurable via Configuration.api_url
• Added support for Exception#cause to be tracked as innerError on Raygun. Only supported on Ruby >= 2.1

1.3.0

Features:

• Improve affected user handling to let you specify all Raygun parameters, identifier, email, first name, full name and uuid. See README.md for details
• Pass a user object as the third parameter to Raygun.track_exception to have affected user tracking for manually tracked exceptions, see the above link for more information on configuring this
• If the exception instance responds to :raygun_custom_data that method will be called and the return value merged into the custom_data hash sent to Raygun. For convenience a Raygun::Error class is provided that takes this custom data as a second argument
• Allowed Configuration.custom_data to be set to a proc to allow a global custom data hook for all exceptions. It is passed as arguments the exception and the environment hash
• Added Configuration.debug to enable logging the reason why an exception was not reported