July 2014 Summaries

An enhancement has been made to the Item Detail pages by introducing a graph that displays aggregate occurrence counts per minute, allowing users to identify patterns such as regularly occurring errors that were previously difficult to detect. This feature is now available to all users and aids in quickly observing changes in occurrence rates following a deployment.

The newly released version 0.3.11 of the Node.js library, available on npm and GitHub, introduces a function called handleErrorWithPayloadData to the public API. This addition enhances the library's integration with the Rollbar API, enabling users to report errors with more detail, such as categorizing them as warnings and attaching additional data. This function is particularly useful for customizing error reports and utilizing the extensive capabilities of the Rollbar API, with further examples provided in the documentation for caught exceptions.

Newly introduced search filters enhance the ability to find errors by filenames in stack traces, offering users more precise and customizable search capabilities. Users can now search for errors based on criteria such as all filenames containing a specific string, no filenames containing a certain string, or filenames appearing in the top or bottom stack frames. Additionally, searches can be refined by specifying the number of filenames within a range or simply by any filename containing a particular string. These filters can be combined within a single query, and users can access help text by hovering over the question mark next to the search box if needed.

A recent fix has been implemented to address an issue with missing daily summary emails caused by a bug introduced during a code refactoring last week. As a result of this bug, some projects did not receive their daily summaries for the previous 24 hours. To avoid overwhelming users with outdated emails, those who wish to receive the missed summaries are encouraged to contact [email protected].

A new patch version (0.13.2) of the Ruby gem has been released to address two specific issues: the use_sucker_punch configuration option, which could lead to timeouts when used with Unicorn, and the mutation of Sidekiq payloads that affected the correct display of parameters in the sidekiq-failures UI. The patch, credited to reports by Fabio Napoleoni and Dmitry Krasnoukhov, is currently available for download on Rubygems and GitHub.

A recent update has been made to improve the rendering of Node.js stack traces so that they more closely resemble the format seen when using console.log(err.stack). Additionally, a bug was fixed that caused context lines to be indented at inconsistent levels, enhancing the readability and consistency of stack trace outputs.