Sentry Adds Laravel Logs Support: A New Era of Error Tracking

In the daily development of Laravel applications, error monitoring and log management are critical parts of the workflow. Sentry has long been a popular choice for error tracking, and now it’s getting even better — **Sentry officially supports Laravel Logs**. This means that beyond capturing exceptions, you can now send `Log::info()`, `Log::warning()`, `Log::error()`, and other log messages directly into Sentry, creating a more complete view of your application’s health. --- ## What’s New in This Update? ### 1. Not Just Exceptions Anymore Previously, Sentry’s Laravel integration focused mainly on catching exceptions. With log support, **every message from Laravel’s logging system** can now be captured and sent to Sentry. ### 2. Easy Integration Enabling log support is straightforward. Just update your `config/logging.php` file: ```php 'sentry' => [ 'driver' => 'sentry', 'level' => 'debug', ], ``` And include it in your `stack` channel: ```php 'stack' => [ 'driver' => 'stack', 'channels' => ['single', 'sentry'], 'ignore_exceptions' => false, ], ``` Once configured, Laravel’s logs and exceptions will automatically flow into Sentry. ### 3. Better Context for Debugging With logs included, developers can now see the surrounding context of errors — what happened before, during, and after an issue. This provides deeper insights and accelerates debugging. --- ## Value for Development Teams * **Full Event Visibility**: Exceptions plus logs give you the complete picture. * **Unified Monitoring Platform**: No need to switch between tools for errors and logs — everything is centralized in Sentry. * **Flexible Alerts**: Teams can define rules for different log levels (info, warning, error) and catch potential issues early. --- ## My Take This update fills a major gap in Laravel monitoring. Previously, teams often had to rely on ELK stacks or third-party log services to get the same visibility, which can be costly and complex to maintain. With Sentry’s log support, small and mid-sized teams can now have **error tracking + log management in one place**. It reduces overhead and allows developers to focus more on building features instead of maintaining monitoring infrastructure. --- ## Conclusion If you’re already using Sentry in your Laravel projects, it’s worth enabling this feature right away. If you haven’t adopted Sentry yet, now is the perfect time — it’s no longer just an error tracker but evolving into a **core monitoring platform** for Laravel teams. --- ✍️ How about you? How do you currently manage logs and errors in your Laravel projects? Would you consider making Sentry your main monitoring platform? ---