Download the PHP package our-ticketing/error-monitor without Composer
On this page you can find all versions of the php package our-ticketing/error-monitor. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download our-ticketing/error-monitor
More information about our-ticketing/error-monitor
Files in our-ticketing/error-monitor
Package error-monitor
Short Description Laravel SDK that captures exceptions, queue failures and diagnostics and ships them to the TicketGo Application Monitoring platform.
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 error-monitor
our-ticketing/error-monitor
Laravel SDK for the TicketGo Application Monitoring & Crash Analytics platform. It captures unhandled exceptions, queue failures and (optionally) slow queries, sanitizes secrets/PII, and ships signed reports to your TicketGo instance — which deduplicates, groups, and auto-creates tickets.
Designed to be fail-safe: a misconfiguration or network error never throws into your app.
Install
Add the credentials issued when you registered the application in the TicketGo admin panel:
That's it — the package auto-discovers its service provider and starts reporting unhandled
exceptions. No changes to bootstrap/app.php are required.
What it captures
| Source | Toggle (config/monitoring.php) |
|---|---|
| Unhandled exceptions / fatal errors | capture.exceptions (on) |
| Failed queue jobs | capture.queue_failures (on) |
| Slow queries (≥ threshold ms) | capture.slow_queries (off) |
Each report includes: exception class, message, severity, full stack trace, sanitized HTTP context and request payload, framework/PHP versions, release, hostname, route/controller, request id, and the authenticated user id.
Manual reporting
Data protection
Keys listed in config('monitoring.sanitize.fields') are redacted (case-insensitive substring match)
from request payloads, headers and context before anything leaves your app. Emails and long digit
sequences are obfuscated. Exceptions in config('monitoring.dont_report') (auth, validation, 404 by
default) are never sent.
How signing works
The transport sends the JSON body with two headers:
X-Monitor-Key: your public keyX-Monitor-Signature:hash_hmac('sha256', $rawJsonBody, $secret)
The platform recomputes the HMAC with the stored secret and rejects mismatches (HTTP 401).
Performance
By default (MONITORING_DEFERRED=true) the HTTP call is deferred to the framework's terminating phase,
so reporting adds no latency to the user's response. In console/queue context it sends inline with a
short timeout.
All versions of error-monitor with dependencies
illuminate/support Version ^10.0|^11.0|^12.0|^13.0
illuminate/http Version ^10.0|^11.0|^12.0|^13.0