Releases: MindscapeHQ/raygun4ruby
Releases · MindscapeHQ/raygun4ruby
1.2.1
1.2.0
Features:
- Added two new configuration options,
filter_payload_with_whitelist
andwhitelist_payload_shape
- See README.md for an example of how to use them
- When raygun4ruby encounters an exception trying to track an exception it will try once to send that exception to Raygun so you are notified
Bugfixes:
- raygun4ruby will no longer crash and suppress app exceptions when the API key is not configured
Version Updates :)
Some small version updates to keep us up with the latest & greatest! ✨
1.1.6 - Affected User Fixes
This release includes some small fixes, most notably for Raygun's affected user tracking.
Enjoy!
Small Feature & Fix Release
This release adds two new features:
- You can now pass a Proc to filter_parameters in order to control what's sent to Raygun
- You can now use the proxy_settings hash to configure Raygun4Ruby to use a Proxy.
Along with a few small fixes.
Minor Fixes
Small fix to failsafe logger, plus an issue where serialising IP addresses was causing JSON problems.
Version 1.1.3
This release includes a minor change to how IP addresses are reported to Raygun.
Raygun4Ruby will now use the following env hash keys in order to try to determine the correct IP address to report.
- action_dispatch.remote_ip - this is set by Rails, you can see their logic here
- raygun.remote_ip - a custom key, in case you have logic you want to use or some specific constraints
- REMOTE_ADDR - this is the existing behaviour