Download the PHP package shootalert/shootalert-laravel without Composer
On this page you can find all versions of the php package shootalert/shootalert-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download shootalert/shootalert-laravel
More information about shootalert/shootalert-laravel
Files in shootalert/shootalert-laravel
Package shootalert-laravel
Short Description Laravel SDK for ShootAlert: ships uncaught exceptions to the platform with breadcrumbs and request context.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package shootalert-laravel
ShootAlert Laravel SDK
Ship uncaught exceptions from your Laravel app to ShootAlert with stack traces, breadcrumbs (recent log lines + DB queries), request context, and authenticated user info.
Requirements
- PHP 8.0+
- Laravel 8, 9, 10, 11, 12, or 13
Install
Add to your .env:
Wire the channel into your default logging stack in config/logging.php:
Done. Any uncaught exception Laravel logs will be shipped to ShootAlert asynchronously via your queue.
Configure (optional)
Publish the config file to override defaults:
The published file at config/shootalert.php lets you:
- Toggle the SDK on/off (
SHOOTALERT_ENABLED=false) - Choose a specific queue connection/name for the ship job
- Tune the breadcrumb buffer size or disable query/log capture
- Extend the list of key substrings stripped from outgoing payloads
What gets captured
- Exception class, message, top-of-stack file:line
- Full stack trace, with frames inside your app marked
in_projectfor grouping and AI diagnosis anchoring - Breadcrumbs (ring buffer of 25): every
info/warning/noticelog line + every DB query the request fired before the throw - Request context: URL, method, IP, route name, user agent
- Authenticated user ID (if any) — never the email or anything else from the user model
- Runtime info: PHP version, Laravel version, app environment, SDK version
What gets redacted before send
Any array key matching password, secret, token, api_key, authorization, auth, or cookie (case-insensitive substring) is replaced with [redacted] in the request context before the payload leaves the process. Add your own substrings via shootalert.redact_keys.
The platform applies a second pass of regex-based redaction (emails, IPv4 addresses, bearer tokens, hex tokens) on the receiving side.
How it ships
Each exception becomes a queued job (ShipErrorEventJob) so the HTTP response that triggered the error returns immediately. The job POSTs one HMAC-signed request to ShootAlert with up to two retries on transient failure. If the platform is permanently unreachable, the job logs to stderr and gives up — your app is never broken by SDK failures.
Disabling for local dev
In .env.local or wherever you keep dev settings:
That short-circuits the Monolog handler before any work is done.
All versions of shootalert-laravel with dependencies
illuminate/contracts Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0
illuminate/queue Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0
illuminate/http Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0
monolog/monolog Version ^2.0|^3.0