July 2016 Summaries

To integrate Feedback in Laravel, you need to configure a custom 500 error page that passes context from Sentry, which involves modifying the App/Exceptions/Handler.php file and adding a feedback widget to the error template. This allows customers to interact with your team when an issue occurs.

The new feature highlights information about a specific environment with a focus on the most recent release. To get started, users need to configure the release and environment attributes in the SDK. By default, Sentry automatically selects the most production-like environment and overlays details from there. The First Seen and Last Seen attributes reflect the chosen environment, and the frequency chart highlights occurrences from the most recent release in that environment. This makes it easier to monitor errors that are only happening in legacy versions of an application. Additionally, Sentry has added new features such as selecting a default environment via Project Settings, creating conditions that match the 'environment' attribute for rules, and improving tooltips and chart renderings. These updates aim to provide the best possible experience for users and their teams.

Sentry has expanded its support to include error tracking, crash reporting, and bug monitoring for iOS, macOS, and tvOS apps, enabling developers to send proper crash reports with detailed stacktraces. This development allows Sentry to improve symbolication quality through the collection of system symbols from older versions of iOS. The new feature is currently available in preview mode, offering a potential alternative to traditional debugging tools like CocoaPads and Carthage.

The new workflow notifications system in Sentry splits notifications into two core systems: alerts and workflow. The new workflow emails are focused on improving triage and issue management workflows, with a focus on participation. Users can change their notification settings to control when they receive workflow emails, which will include notifications for regressions if not already opted out. Additional activity-based notifications have been added, including weekly summaries, to improve the error monitoring experience.

While thousands of teams use hosted Sentry, tens of thousands are running it on-premise. Keeping on-premise deployments up-to-date with the latest error monitoring features and fixes is a priority for us. We've adopted a more formal release schedule to make updates easier for operations teams. The new schedule includes major versions for significant changes, minor versions for database migrations and feature additions, and patch versions for critical bug fixes only. This change aims to improve open source compliance, predictability, and ease of upgrading for users.