Track errors and exceptions through the most popular Saas platforms

v0.2.0 2015-02-23 12:20 UTC


Build Status Total Downloads Latest Stable Version

Track errors and exceptions through the most popular SaaS platforms.

Error Tracker Adapter is a PHP library which helps you track exceptions and errors in your application by providing a powerful abstraction layer for error tracker SaaS platforms and / or local repositories like emails and log files.

It has been created on three main principles:


SaaS Platforms

SaaS platforms are supported via the use of adapters, the currently supported platforms are:

Local Repositories

Local repositories like emails, logs or database are supported via the use of providers, the currently supported repositories are:

If you use Monolog, you now have the ability to log your exceptions into any of it's handlers - Pushover notifications, HipChat, Flowdock, Slack etc..

$monolog = new Monolog\Logger();
$monolog->pushHandler(new FlowdockHandler('apiToken', Monolog\Logger::ERROR));
$logger = new Morrislaptop\ErrorTracker\Provider\Log($monolog);

Grouping Trackers

Also, you can use Group trackers which can use multiple trackers in different ways:

  • Chain Reporter for reporting until one is successful (e.g. falling back to a log if Sentry is down)
  • Net Reporter for reporting to all trackers (e.g. logging AND reporting to Sentry for redundancy)

Extending Things

You can write your own provider or adapter by implementing the Tracker interface. Optionally you can use the other interfaces Adapter, Provider or Group and/or extend the abstract classes AbstractAdapter, AbstractProvider or AbstractGroup to help classify your trackers.


The recommended way to install is through Composer:

$ composer require morrislaptop/error-tracker-adapter

Quick Start

For convenience, a generic exception handler is included with the library so you can quickly get started, by simply creating it and calling the bootstrap() method.

$tracker = new Morrislaptop\ErrorTracker\Adapter\Sentry(new Raven_Client(''));
// or
$tracker = new Morrislaptop\ErrorTracker\Adapter\BugSnag(new Bugsnag_Client('2344324342'));

$handler = new Morrislaptop\ErrorTracker\ExceptionHandler($tracker);


The use of this library is a reporter and not a renderer. So it's recommended that you handle exceptions in your application with your own class and then report to the interface if it's the right error type and/or environment.

An example exception handler for your application might look like..

<?php namespace App;

use Exception;
use Morrislaptop\ErrorTracker\Tracker;

class ExceptionHandler
	 * @var Tracker
	protected $tracker;

	 * @param Tracker $tracker
	function __construct(Tracker $tracker)
		$this->tracker = $tracker;

	 * Bootstrap this class into the runtime
	public function bootstrap() {
		set_error_handler([$this, 'handleError']);
		set_exception_handler([$this, 'handleException']);
		register_shutdown_function([$this, 'handleShutdown']);

	 * Convert a PHP error to an ErrorException.
	 * @param  int  $level
	 * @param  string  $message
	 * @param  string  $file
	 * @param  int  $line
	 * @param  array  $context
	 * @return void
	 * @throws \ErrorException
	public function handleError($level, $message, $file = '', $line = 0, $context = array())
		if (error_reporting() & $level)
			throw new ErrorException($message, 0, $level, $file, $line);

	 * Handle an uncaught exception from the application.
	 * Note: Most exceptions can be handled via the try / catch block in
	 * the HTTP and Console kernels. But, fatal error exceptions must
	 * be handled differently since they are not normal exceptions.
	 * @param  \Exception  $e
	 * @return void
	public function handleException($e)

		throw $e; // throw back to core PHP to render

	 * Handle the PHP shutdown event.
	 * @return void
	public function handleShutdown()
		if ( ! is_null($error = error_get_last()) && in_array($error['type'], [E_ERROR, E_CORE_ERROR, E_COMPILE_ERROR, E_PARSE]))
			$this->handleException(new ErrorException($error['message'], $error['type'], 0, $error['file'], $error['line']));


Group Providers

$monolog = new Monolog\Logger();
$monolog->pushHandler(new StreamHandler('path/to/your.log', Monolog\Logger::ERROR));
$logger = new Morrislaptop\ErrorTracker\Provider\Log($monolog);

$sentry = new Morrislaptop\ErrorTracker\Adapter\Sentry(new Raven_Client(''));
$bugsnag = new Morrislaptop\ErrorTracker\Adapter\BugSnag(new Bugsnag_Client('2344324342'));

// If you wanted to fallback to a log if reporting to Sentry fails..
$chain = new Morrislaptop\ErrorTracker\Group\Chain();
$chain->report(new \Exception('This will be logged to file if Sentry is down'));

// If you wanted to report to Bugsnag AND Sentry to compare those platforms
$chain = new Morrislaptop\ErrorTracker\Group\Chain();
$chain->report(new \Exception('Which is the better platform? This exception will go to both'));


Many platforms support the idea of contexts to give you more information about exceptions occuring in your application. This can happen on the user, environment or event level.

This will be implemented via a ContextInterface in the future. In the mean time you can pass extra information via the report() method like..

$this->tracker->report($e, ['user_id' => Session::get('user_id')]);


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D


Unit Tests

In order to run the test suite, install the developement dependencies:

$ composer install --dev

Then, run the following command:

$ phpunit && phpspec run

PHP-VCR is used to record the outgoing requests to the SaaS platforms and the requests are committed to the repo. By default PHP-VCR is set to not allow any requests that don't match the existing, verified request signatures. If you're sure that you've made a change that results in a different request and that should be recorded as the correct request you can:

  • Update the setMatchers() function in your test to return true
  • Delete the fixture, run the test and commit the new signature


Follows Semantic Versioning.




MIT license. For the full copyright and license information, please read the LICENSE file that was distributed with this source code.