Laravel Discord Error Tracker Laravel Package

Product Decisions This Supports

• Add lightweight exception alerting: Use the package to send Laravel exceptions to a Discord webhook, improving time-to-awareness for development, staging, and lower-criticality production environments without building a custom notifier.
• Platform upgrade planning: v2.0.0 aligns the package with PHP 8.2+ and Laravel 12/13. Teams planning those upgrades can include this package in the compatibility review; teams staying on older versions should use the maintained v1 branch or defer.
• Build vs. buy: Favor adopting this package over building an internal Discord exception reporter. It covers automatic exception reporting, Discord embed limits, stack-trace truncation, safe webhook failure handling, and configurable mention/trace/timeout options.
• Operational configuration decisions: Evaluate mention behavior, trace limits, and timeouts as part of alert routing and noise-control decisions.
• Use-case fit: Best suited for teams already using Discord for operational visibility, early-warning alerts, or lightweight incident notification. It is not positioned by these release notes as a replacement for full incident-management, on-call, or compliance tooling.

When to Consider This Package

• Consider it when the application runs PHP 8.2+ on Laravel 12/13, uses Discord as an operational notification channel, and needs low-effort exception reporting.
• Consider it when you want automatic exception reporting without custom Handler changes, using the service provider’s reportable callback and DISCORD_ERROR_AUTO_REPORT.
• Consider it when you need safe failure behavior: a failing webhook should not break the app and should not create a reporting loop back to Discord.
• Consider it when you need practical safeguards such as Discord embed-limit handling, long stack-trace truncation, mention configuration, trace limits, and timeouts.
• Look elsewhere or treat as insufficient if you need enterprise incident management, on-call escalation, deduplication, rate limiting, retries, PII redaction, audit/compliance controls, multi-channel routing, or high-volume production alerting. These release notes do not claim those capabilities.
• If the application is on older Laravel/PHP versions, assess the v1 branch or delay adoption until the platform upgrade is complete.

How to Pitch It (Stakeholders)

For executives: This package provides a low-cost, low-risk way to surface Laravel exceptions in Discord, improving operational awareness without building and maintaining custom alerting code. The v2 release supports Laravel 12/13 and PHP 8.2+, and its failure handling is designed so a broken webhook does not take down the application. It is a useful lightweight alerting layer, not a replacement for a full incident-management platform.

For engineering: v2.0.0 adds Laravel 12/13 support and requires PHP 8.2+. It auto-registers exception reporting for Laravel 11+ patterns, so apps need no Handler changes, and it handles Discord embed limits and truncates long stack traces. It includes mention, trace-limit, and timeout options, plus a Pest test suite, PHPStan, and a Laravel 12/13 CI matrix. The main adoption note is the platform requirement: the 1.x line remains on the v1 branch for older applications.