Feature

Laravel exception tracking

Every exception your Laravel applications throw, grouped by cause rather than by occurrence, with the full stack trace and the commit that introduced it.

Start for free Read the documentation
The installation, in full 
composer require quiet-guard/laravel-monitor

The problem

A production error reaches you through support, hours after the first user hit it. Server logs say something happened, not how many people lived it, not since when, and not what changed that day.

What you get

  • The full stack trace, at any depth, and never the call arguments
  • Occurrence counts, first and last seen, per environment and per release
  • The release tied to its GitHub commit, to go from the error to the code
  • The application logs from five minutes either side of the incident, on the same page
  • An alert on creation and on regression, never on every occurrence
  • Assignment to a team member, and bulk triage

How it works

01

One line in your application

The client package auto-discovers itself. It captures uncaught exceptions and fatal errors with nothing for you to instrument.

02

Grouped by fingerprint

The same error seen a thousand times stays one issue, with its counter. A resolved issue that comes back reopens itself and tells you.

03

Capture cannot break you

If the monitoring server does not answer, the report fails quietly. An outage on our side never becomes an outage on yours.

Start for free

No card required. Up and running in minutes.

All features