Releases: rollbar/pyrollbar
Releases · rollbar/pyrollbar
0.14.1
- Django middlewares that differentiate between 404 and other exceptions #270
- Make werkzeug request handling more general #271
- Obviously handle scrub_fields in rollbar.init() #235
- requests.Session is not thread-safe, use thread local storage #269
- Swallow known error that happens in add_person_data #268
- Only write a log about a rate limit once #267
- Adapt Django view monkey patch to support Django 2 #257
- Support request objects from Django REST framework #18
- Add support for Falcon framework requests #51
- Support Django Channels' AsgiRequest #272
v0.14.0
- Create the configuration options,
capture_username
andcapture_email
. Prior to this release,
if we gather person data automatically, we would try to capture the id, email, and username.
Starting with this release by default we will only capture the id. If you setcapture_username
toTrue
then we will also attempt to capture the username. Similarly forcapture_email
with
the email. (See #262) - Create the configuration option
capture_ip
. This can take one of three values:True
,
'anonymize'
, orFalse
. This controls how we handle IP addresses that are captured from
requests. IfTrue
, then we will send the full IP address. This is the current behaviour and the
default. If set to the string'anonymize'
which is also available as the constantANONYMIZE
on
therollbar
module, we will mask out the least significant bits of the IP address. If set to
False
, then we will not capture the IP address. (See #262) - Fix
request.files_keys
for Flask #263 - If you call
init
multiple times we will update the settings at each call. Prior to
this release we emitted a warning and did not update settings. #259 - Better Tornado support #256
v0.13.18
-
Fix bug with KeyError related to extra data with a trace chain #218
-
Add support for parsed POST variables using Django REST Framework #86
-
Add additional hooks on django middleware #139
-
You can now add custom filtering logic to determine if the error/message/payload should be sent to Rollbar via the events module within rollbar #81
-
Extract and send additional request data from Sanic framework #227
-
Better handle 502 API errors #224
v0.13.17
- Fix deprecation warning related to Logging.warn
- Fix bug where non-copyable objects could cause an exception if they end up trying to get passed to
one of the logging methods. - Fix bug where both
trace
andtrace_chain
could appear in the final payload, which is not
allowed by the API.
v0.13.16
0.13.15
0.13.14
- Fix bug that caused some payload objects to be turned into the wrong type when
shortening is applied. This would lead to API rejections. See #200 - Add
suppress_reinit_warning
option if you want to allow calling init twice. See #198 - Pass through keyword arguments from the logging handler to the underling Rollbar init call. See #203