Download the PHP package irabbi360/laravel-debugmate without Composer
On this page you can find all versions of the php package irabbi360/laravel-debugmate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download irabbi360/laravel-debugmate
More information about irabbi360/laravel-debugmate
Files in irabbi360/laravel-debugmate
Package laravel-debugmate
Short Description Error tracking, log viewing, and performance monitoring SDK for Laravel
License MIT
Informations about the package laravel-debugmate
DebugMate SDK
Error tracking, log streaming, and performance monitoring for Laravel apps.
Features
- Error tracking with stack frames and fingerprinting
- Performance monitoring with OpenTelemetry-style spans
- Log streaming
- Request analytics
- Query / job / command / view / HTTP / Livewire collectors
- Uptime / SSL / domain monitor registration (checks run on DebugMate)
- Async reporting via queues
Installation
Quick Start
1. Environment
Package auto-registers TrackPerformance when DEBUGMATE_TRACK_PERFORMANCE=true (no bootstrap/app.php edit needed).
2. Register exception handler
3. Manual reporting
Performance monitoring
Logs
Only channels listed in config/debugmate.php log_channels are streamed when DEBUGMATE_TRACK_LOGS=true.
Uptime / SSL / domain monitors
DebugMate servers run the checks. This package only registers target URLs.
Register (add to client scheduler daily):
Verify setup
Auth
SDK sends X-DebugMate-Key and Authorization: Bearer {DEBUGMATE_PROJECT_KEY} on every request.
debugmate:verify POSTs /api/debugmate/verify-token so it tests the same auth path as error ingest.
| Endpoint | Method |
|---|---|
/api/debugmate/verify-token |
GET, POST |
/api/debugmate/project |
GET |
/api/debugmate/errors |
POST |
/api/debugmate/metrics |
POST |
/api/debugmate/logs |
POST |
/api/debugmate/queries |
POST |
/api/debugmate/analytics |
POST |
/api/debugmate/monitors |
POST |
Configuration
Publish config (optional):
Key env vars: DEBUGMATE_ENABLED, DEBUGMATE_API_URL, DEBUGMATE_PROJECT_KEY, DEBUGMATE_TRACK_*, DEBUGMATE_ASYNC_REPORTING.
What is never traced
Three exclusion lists keep the SDK from measuring itself. Each is a plain array
in config/debugmate.php and supports * wildcards.
| Key | Excludes | Why |
|---|---|---|
ignore_paths |
HTTP paths | Skips DebugMate's own ingest endpoints. |
ignore_commands |
Artisan commands | Long-running daemons must stay listed. A daemon fires CommandStarting but not CommandFinished until it exits, so tracing one keeps a root span open for the life of the process and the worker leaks memory. queue:work, horizon*, octane:start and friends are enforced in code and cannot be re-enabled. |
ignore_tables |
Database tables | Stops writing telemetry from generating telemetry. Covers the queue tables, sessions, cache, and DebugMate's own ingest tables — essential when an app reports to a DebugMate instance sharing its database. |
Trace limits
Every trace is capped so a single request, job, or bug cannot exhaust memory:
Overflow is counted rather than buffered. When a trace is truncated, the metric
payload carries dropped_spans / dropped_queries in its context so the gap is
visible rather than silent.
Reporting to a DebugMate instance on the same database
If you self-host DebugMate and point an app at it, give the SDK its own queue
connection (Redis, for example) so telemetry jobs do not write rows into the
database they are measuring. ignore_tables covers the query-tracking half of
the loop; a separate connection covers the rest.
Testing
License
MIT — see LICENSE.md
All versions of laravel-debugmate with dependencies
illuminate/support Version ^10.0 || ^11.0 || ^12.0 || ^13.0
illuminate/queue Version ^10.0 || ^11.0 || ^12.0 || ^13.0
guzzlehttp/guzzle Version ^7.0