Download the PHP package davidcolquhoun/monitor-exceptions-laravel without Composer
On this page you can find all versions of the php package davidcolquhoun/monitor-exceptions-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download davidcolquhoun/monitor-exceptions-laravel
More information about davidcolquhoun/monitor-exceptions-laravel
Files in davidcolquhoun/monitor-exceptions-laravel
Package monitor-exceptions-laravel
Short Description Light weight PHP exception monitoring for Laravel.
License proprietary
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 monitor-exceptions-laravel
Monitor Exceptions (Laravel)
Lightweight Laravel client for reporting exceptions to the DataSmugglers monitoring API. Events appear in a dashboard where you can filter, search, and inspect them.
Requirements
- PHP 8.1+
- Laravel 12.x
Installation
The package registers its service provider automatically. It merges default config from config/monitor-exceptions.php; you can override values in your app by publishing the config or setting env vars.
Configuration
Set these in your .env:
- environment_id: Identifies the environment (e.g.
myapp-dev,myapp-prod) for grouping in the DataSmugglers UI. - environment_key: Secret key that authenticates this app with the DataSmugglers API.
If either is missing or empty, the client does not register and no exceptions are sent.
To publish the config file and edit it in your project:
That creates config/monitor-exceptions.php, which reads from the same env vars by default.
Usage
In your Laravel app, register the client in the exception handler. In bootstrap/app.php:
Once registered, every exception reported to Laravel (e.g. via report($e)) is also sent to the monitoring API.
What gets sent
The client does not send request bodies, client IP, or query strings. It sends a JSON payload with:
| Field | Type | Description |
|---|---|---|
environmentId |
string | Your environment identifier. |
environmentKey |
string | Your environment key. |
reportedByHandler |
string | Always laravel. |
errorSeverity |
int | null | PHP error level when available (e.g. ErrorException). |
exceptionClass |
string | Exception class name. |
errorMessage |
string | Exception message. |
errorCode |
string | null | Exception code when set. |
errorFile |
string | File where the exception was thrown. |
errorLine |
int | Line number. |
stackTrace |
string | Stack trace as a string. |
requestUrl |
string | null | Request URL without query string (null in CLI). |
requestMethod |
string | null | HTTP method (null in CLI). |
requestHeaders |
array | Request headers with sensitive ones stripped (empty in CLI). |
Sensitive headers (e.g. authorization, cookie, x-api-key) are removed before sending.
Behaviour
- Registration: If
environment_idorenvironment_keyis empty,register()does nothing and no handler is attached. - CLI: When running in CLI,
requestUrl,requestMethod, andrequestHeadersare null/empty. - Failures: Errors inside the client (e.g. network) are caught and ignored so your app’s error handling is not affected.
- Blocking: The HTTP send is blocking (up to the configured timeout) so the report is sent before the request ends when possible.
Testing
After configuring env vars, trigger an exception (e.g. throw new \RuntimeException('Test');) and check the DataSmugglers dashboard for the event.
