Download the PHP package zereflab/laravel-bug-bot without Composer

Laravel Bug Bot

Organized Laravel exception reports for Slack.

This package replaces noisy default Slack log messages with a clean parent alert, a full threaded exception, duplicate throttling, and Slack buttons for Solved / Ignore.

Features

• Laravel log channel integration
• Short parent Slack message with useful context
• Full exception and stack trace in the Slack thread
• Duplicate throttling by exception fingerprint
• Solved and Ignore Slack buttons
• One click updates every stored Slack message for the same error fingerprint
• Ignored fingerprints suppress future alerts
• Safe production behavior: Slack failures do not break your app
• Test command that fails loudly when Slack config is wrong
• Designed for future Discord support

Getting Started

1. Install the package

2. Publish the config

3. Run the migrations

4. Connect Slack

Install the pre-built Laravel Bug Bot Slack app into your workspace — no Slack app creation needed:

Direct install URL: https://laravelbugbot.com/integrations/slack/install

After installation, the success page shows a managed bot token. Paste the generated values into your .env:

Managed Slack installs use laravelbugbot.com as the Slack Interactivity Request URL. The package embeds a signed callback in each button so Laravel Bug Bot can forward Solved / Ignore clicks back to the Laravel app where this package is installed.

5. Add Laravel Bug Bot to your Slack channel

Slack requires you to add the installed app to the channel before it can post alerts there.

6. Copy the Slack channel ID

Copy the Channel ID from Slack, then replace the placeholder in BUG_REPORTS_SLACK_CHANNEL.

The channel value is the channel ID, not the channel name.

7. Test your setup

You should see the test exception arrive in your Slack channel. That's it — every exception in your app now lands in Slack, organized.

8. Authorize dashboard access

The dashboard is served by the Laravel application where you install this package:

Full dashboard documentation is available at https://laravelbugbot.com/docs/dashboard.

Edit app/Providers/AppServiceProvider.php and add the dashboard gate inside the boot() function:

Optionally, allow specific users by database ID:

Want To Use Your Own Slack Application?

If you prefer to create and control your own Slack app instead of using the managed Laravel Bug Bot app, follow the separate guide:

➡ Use Your Own Slack App

Environment Variables

Defaults shown below — override only what you need:

After changing config:

What The Slack Alert Looks Like

Parent message:

• Date/time
• Log level
• Exception class
• Exact exception message
• Origin: command, job, controller, route action, or application class
• Entity/user/model information when detectable
• File and line
• Solved and Ignore buttons

Thread reply:

• Exception class
• Message
• Location
• Level
• Environment
• Request details when available
• Context
• Stack trace
• Previous exception when available

Solved And Ignore

Each exception gets a fingerprint based on exception class, message, file, and line.

• Ignore suppresses future alerts for that same fingerprint.
• Solved marks the fingerprint as resolved and clears the throttle.
• In managed Slack app mode, button clicks go to laravelbugbot.com first, then get forwarded to a signed callback endpoint in your Laravel app.
• In own Slack app mode, Slack can post directly to your Laravel app's signed action endpoint.
• Both actions update stored report state for that same fingerprint.
• If a solved fingerprint happens again, it is reopened as pending.

Bug reports, occurrence counts, statuses, and Slack message references are stored in the database. By default, ignored errors are ignored forever. You can expire ignored errors:

Slack button endpoint

The package automatically registers the Slack interactivity endpoint:

By default this route uses the api middleware and is also registered without Laravel's CSRF middleware, because Slack cannot send a Laravel CSRF token. You should not add this route manually.

To avoid 404s from the common dashboard/action URL mismatch, the package also registers compatibility aliases:

If Slack reaches Laravel but BUG_REPORTS_SLACK_SIGNING_SECRET is missing or wrong, the endpoint returns 401 Invalid signature instead of 404.

Managed Slack app installs also automatically register this client callback endpoint:

Laravel Bug Bot signs each Slack button value with BUG_REPORTS_MANAGED_ACTION_SECRET (defaults to APP_KEY) and includes this callback URL. When Slack sends the click to laravelbugbot.com, Laravel Bug Bot forwards the action to this endpoint so the package can update the local database.

Make sure APP_URL is correct in the Laravel app where the package is installed. If auto-detection is wrong, set:

If you use your own Slack app and want Slack Solved / Ignore buttons, set the Slack app's Interactivity Request URL to your deployed Laravel app:

If you change BUG_REPORTS_ROUTE_PREFIX, the URL changes too. For example:

Then Slack must post to:

Dashboard

The package includes a built-in dashboard served inside your Laravel application:

Read the full dashboard guide at https://laravelbugbot.com/docs/dashboard.

The dashboard shows:

• Total error fingerprints and total occurrences
• Errors received in the last 1, 5, 7, 10, and 30 days
• Pending, resolved, and ignored counts
• Noisiest origins and exception classes
• Paginated tables for all, pending, resolved, and ignored errors
• Resolve, ignore, and delete actions

Change the dashboard path:

Dashboard authorization

The dashboard denies everyone by default. To grant access, edit app/Providers/AppServiceProvider.php and add the gate inside the boot() function:

Or allow specific user IDs without defining a gate:

Add authentication middleware so visitors are sent to login first:

Production Notes

Use this in production:

Do not use Laravel's default slack channel if you want this package's formatting. Use bug_reports.

Future Discord Support

The package is structured around reporter drivers. Slack is the first reporter. Discord can be added later with the same fingerprinting, summary formatting, threaded/detail behavior where supported, and solved/ignore state.

License

MIT