Weave Code
Honeybadger Laravel Laravel Package
honeybadger-io/honeybadger-laravel
Honeybadger for Laravel integrates Honeybadger.io error monitoring into your app, automatically reporting exceptions and logs with rich context. Configurable via a single config file, it also supports custom notifications and deploy tracking.
PHP/Laravel library for reporting errors to Honeybadger.io :elephant: :zap:
Frequently asked questions about Honeybadger Laravel
- How do I install honeybadger-io/honeybadger-laravel in a Laravel app?
- Install the package with Composer using composer require honeybadger-io/honeybadger-laravel. Laravel package discovery registers the service provider automatically, and you configure your Honeybadger API key through the package config or environment variables. Publish the config file if you need to customize reporting behavior, then clear or cache config as appropriate for your environment.
- Does honeybadger-laravel automatically report exceptions and logs to Honeybadger?
- Yes, the package integrates with Laravel's exception handler and logging stack so exceptions and logs can be reported automatically with rich context. It is designed to work alongside your existing Laravel observability setup rather than replacing it. You can also customize notifications and reporting behavior through the package configuration.
- Which Laravel versions are supported by honeybadger-laravel?
- The package is built for modern Laravel applications, and the 5.x line is intended for Laravel 8 and newer, but you should confirm the exact Composer constraint in composer.json before installing. Laravel version support is unchanged in the 5.1 minor release. Check the repository README and release notes if you are running an older or newly released Laravel version.
- How do I configure Honeybadger in Laravel?
- Configuration is handled through a single package config file, typically config/honeybadger.php, with values such as your API key sourced from environment variables. After changing configuration in a production environment, run php artisan config:cache if your app caches configuration. Review the config file after upgrades because new features such as Insights may add default settings.
- What is Honeybadger Insights and is it enabled by default?
- Honeybadger Insights is event tracking that is enabled by default in the 5.1 release. It introduces an additional data pipeline that sends event data to Honeybadger, so teams should review it against data governance and privacy policies. Decide whether to keep it enabled, sample or restrict it, or disable it before deploying to production.
- How do I disable Insights or opt out per environment?
- Insights can be disabled through the package configuration, so review config/honeybadger.php after upgrading to 5.1 and set the opt-out appropriately for each environment. Disabling it per environment is useful when staging or production has stricter privacy or data-volume requirements. Roll out the configuration change through staging first so you can confirm event traffic stops as expected.
- Does Honeybadger capture sensitive data or PII?
- Automatic event tracking increases the risk of sending sensitive data, so a PII and data-governance review is required before enabling Insights broadly. Honeybadger and the package offer filtering and scrubbing options, but you should verify exactly what Insights captures for your application. Restrict or disable Insights in compliance-sensitive environments if the captured data does not meet your policies.
- What is the performance overhead of Honeybadger in Laravel?
- Normal exception and log reporting usually adds little overhead, but Insights increases outbound data volume and can affect performance if reporting calls are made synchronously. Use sampling, queuing, or disable Insights in high-throughput environments if you observe latency or excessive network egress. Test in staging and monitor request latency, outbound traffic, and Honeybadger plan limits before a production rollout.
- How do I upgrade to honeybadger-laravel 5.1 safely?
- Upgrade with composer require honeybadger-io/honeybadger-laravel:^5.1 in a branch and deploy to staging before production. It is a minor release from 5.0.0 and should be backward compatible, but the default-on Insights behavior requires a configuration audit and an explicit opt-out decision. The package is actively maintained by Honeybadger, so review release notes and update internal runbooks for the new data pipeline.
- How do I test Honeybadger reporting in Laravel?
- Test with Honeybadger disabled or pointed at a non-production key, trigger a known exception, and verify the expected reporting path without making CI depend on the vendor endpoint. The 5.1 mock test fix improves reliability for teams writing their own tests. Keep integration tests separate from unit tests so local and CI runs stay deterministic.
Weaver
How can I help you explore Laravel packages today?