- How do I install and set up Notify Exceptions in a Laravel app?
- Install it with Composer using composer require andrey-helldar/notify-exceptions, then publish the package config and set your notification recipients and channels. The package hooks into Laravel's exception handling, so you typically wire it through the documented exception report path or middleware integration. Start in a non-critical environment and verify a staged exception produces the expected notification.
- Which Laravel and PHP versions are supported by andrey-helldar/notify-exceptions?
- Check the package composer.json and README for the exact Laravel and PHP constraints before adding it to your app. The package is designed for Laravel and follows Laravel's notification and exception-handling patterns, but support depends on the release line. For v4.1.0, confirm compatibility with your stack, such as Laravel 9.x or 10.x and PHP 8.1+, in a sandbox first.
- How do I configure recipients and notification channels for exception alerts?
- Publish the package config and define the recipients and channels using Laravel's notification conventions. You can route alerts to mail, Telegram, or custom notification channels, and you can scope configuration by environment. Keep production recipients separate from development recipients to avoid noisy alerts.
- Can Notify Exceptions send alerts to Telegram, Slack, or custom channels?
- Yes. Notify Exceptions integrates with Laravel's Notification system, so supported channels include mail, Telegram, Slack, and custom drivers where configured. You configure the channel and recipient details in the published config rather than building a separate alerting path. Verify each channel's Laravel notification prerequisites and credentials in a staging environment.
- How do I stop exception notification floods during an incident?
- Use the package's configurable throttling to cap how often exception notifications are sent and to prevent floods during an error spike. Pair throttling with exception filtering so repeated or low-value exceptions do not hit your channels. If you expect high volume, queue notifications so alerting does not add request latency.
- How can I ignore or filter specific exception types?
- Configure the package's ignore or filter rules for exception types that should not trigger notifications. This is useful for expected exceptions, third-party noise, or exceptions already covered by another alerting path. Test the filters with staged exceptions so you do not accidentally suppress critical production errors.
- Should I queue exception notifications in production?
- Yes, for production it is usually better to queue exception notifications so dispatch is decoupled from request handling. Queueing reduces overhead during failures and lets Laravel workers retry or absorb notification work. Make sure queue failures and notification failures still leave a fallback log entry for the original exception.
- How do I test exception notifications safely?
- Test in a local or staging environment by publishing the config, setting a test channel and recipient, and throwing a controlled exception. Verify filtering, throttling, formatting, and queue behavior before enabling production recipients. Avoid pointing test runs at shared production alert channels.
- What happens if the notification channel is down or the notification fails?
- A notification failure should not hide the original exception, so keep Laravel's normal logging in place as a fallback. Test behavior with an unavailable channel or bad credentials and confirm the package fails gracefully without disrupting core exception handling. For critical services, monitor notification delivery and have a secondary alerting path.
- Is Notify Exceptions maintained, and are there alternatives if it is abandoned?
- The package has recent releases, including v4.1.0 from v4.0.1, which suggests active maintenance and a low-risk minor upgrade. Review the changelog before upgrading and assign an internal owner to watch GitHub issues and package updates. If maintenance lapses, alternatives include Laravel's native logging and notification setup or a small custom exception reporter using Laravel notifications.