June 2017 Summaries

Rollbar's recent introduction of manual merging provides users with multiple options for combining error occurrences into a single item, complementing their existing default fingerprinting algorithm and custom fingerprinting rules. The default algorithm generates a fingerprint by combining filenames, method names, and exception class names, but users can create custom rules using a JSON-based syntax to achieve more precise error grouping based on specific project needs. Despite the ease of use offered by the UI for manual merging, custom fingerprinting rules remain valuable for automating error combination, especially for recurring errors like OperationalErrors, as they can ensure consistent treatment of future occurrences without additional manual intervention. While manual merging allows for flexibility in organizing errors and the ability to un-merge, custom rules offer a more automated and sophisticated approach to error tracking, although they apply only to future occurrences and require familiarity with JSON syntax.

Rollbar's latest feature, error merging, allows users to dynamically merge and un-merge related errors through the user interface, addressing the previous limitations of static custom fingerprinting rules. The implementation required creating a dual identity system for items: Native Items, which are individual error occurrences identified by fingerprints, and Group Items, which are collections of Native Items merged under user direction. This system enables users to manage complexity by reducing the number of visible items on their dashboards while maintaining accurate data through a logical view that stores mappings from Group Items to their constituent Native Items. The engineering team introduced a new database table to track these mappings and a unique transaction ID for each merge or un-merge action, ensuring a complete historical record. The user experience was also enhanced with new views and functionalities for Group Items, alongside restrictions on editing Native Items once merged, providing a comprehensive solution for application error monitoring.

In an insightful interview with Andrew Childs, CTO of Shortcut, conducted by Adam Stacoviak from Changelog, the discussion centers around the importance of error tracking and management in software development. Shortcut, a project management tool for software teams, relies heavily on Rollbar for tracking and resolving errors, which is crucial due to their small team size and the absence of a dedicated QA department. Andrew highlights how Rollbar's features, such as combining similar JavaScript errors, providing stack traces with source-map support, and sending real-time notifications to Slack, enhance their ability to swiftly address issues and maintain customer satisfaction. The tool's customization options, such as sending arbitrary data and tracking user interactions, allow Shortcut to proactively resolve errors and improve user experiences. Prior to Rollbar, Shortcut faced challenges with other tools like Google Analytics and Sentry, which lacked in-depth error reporting and visibility. The conversation underscores Rollbar's critical role in enabling Shortcut to manage errors effectively, maintain a positive customer perception, and continue building a successful product.