2017 © Pedro Peláez
 

library bugsnag-mini-php

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

image

withfatpanda/bugsnag-mini-php

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  • Friday, January 13, 2017
  • by collegeman
  • Repository
  • 1 Watchers
  • 0 Stars
  • 0 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 0 Forks
  • 0 Open issues
  • 5 Versions
  • 0 % Grown

The README.md

bugsnag-mini-php

This is the most minimal PHP client for Bugsnag that I could conceive of and create., (*1)

I wanted to be able to add Bugsnag to an aging PHP codebase I'm working on, but for various reasons, I couldn't easily incorporate the standard PHP library. Fortunately, Bugsnag has an easy to approach JSON API, so I put this client together, and now you can use it too!, (*2)

Getting Started

If you're adding this to a project that doesn't use Composer, just download this repository, and copy the file src/busnag-mini.php into your project., (*3)

If you're using Composer, you can incorporate this snip of PHP like a library as follows:, (*4)

composer require withfatpanda/bugsnag-mini-php

The next thing you'll need to do is create a constant somewhere to store your Bugsnag API key:, (*5)

define('BUGSNAG_API_KEY', 'your-key-goes-here');

The last and most important step is to hook up this client's exception and error handling functions, like so:, (*6)

set_exception_handler('bugsnag_mini_handle_exception');
set_error_handler('bugsnag_mini_handle_error');
register_shutdown_function('bugsnag_mini_handle_shutdown');

Now anytime an Exception is thrown or an error is raised or the runtime shutsdown, errors will be sent to Bugsnag., (*7)

Customizing Meta Data

You can feed more meta data into Bugsnag by setting up functions that assess the context of the error and provide more context. You can, for example, attach information about affected user, about the app, about the device running the app, and other meta data., (*8)

Each of the functions receives as their only argument the Exception that was thrown and is being reported upon., (*9)

These functions do not exist until you define them in your own codebase. The client will look for them, and will call them only if they exist—this is completely and totally optional., (*10)

The functions are as follows:, (*11)

bugsnag_mini_user

Information about the user affected by the crash., (*12)

function bugsnag_mini_user($ex) {
  return array(
    // A unique identifier for a user affected by this event. This could
    // be any distinct identifier that makes sense for your
    // application/platform.
    // (optional, searchable)
    "id" => "19",

    // The user's name, or a string you use to identify them.
    // (optional, searchable)
    "name" => "Simon Maynard",

    // The user's email address.
    // (optional, searchable)
    "email" => "simon@bugsnag.com"
  );
}

bugsnag_mini_app

Information about the app that crashed., (*13)

function bugsnag_mini_app($ex) {
  return array(
    // The version number of the application which generated the error.
    // If appVersion is set and an error is resolved in the dashboard
    // the error will not unresolve until a crash is seen in a newer
    // version of the app.
    // (optional, default none, filtered)
    "version" => "1.1.3",

    // The release stage that this error occurred in, for example
    // "development", "staging" or "production".
    // (optional, default "production", filtered)
    "releaseStage" => "production",

    // A specialized type of the application, such as the worker queue or web
    // framework used, like "rails", "mailman", or "celery"
    "type" => "rails"
  );
}

bugsnag_mini_device

Information about the computer/device running the app, (*14)

function bugsnag_mini_app($ex) {
  return array(
    // The operating system version of the client that the error was
    // generated on. (optional, default none)
    "osVersion" => "2.1.1",

    // The hostname of the server running your code
    // (optional, default none)
    "hostname" => "web1.internal"
  );
}

bugsnag_mini_meta

An object containing any further data you wish to attach to this error event. This should contain one or more objects, with each object being displayed in its own tab on the event details on the Bugsnag website., (*15)

function bugsnag_mini_meta($ex) {
  return array(
    // This will displayed as the first tab after the stacktrace on the
    // Bugsnag website.
    "someData" => array(
      // A key value pair that will be displayed in the first tab
      "key" => "value",

      // This is shown as a section within the first tab
      "setOfKeys" => array(
        "key" => "value",
        "key2" => "value"
      )
    ),

    // This would be the second tab on the Bugsnag website.
    "someMoreData" =>  array(

    )
  );
}

Sending errors manually

If ever you want to push an Exception arbitrarily, all you have to do is call bugsnag_mini_notify($ex). For example:, (*16)

bugsnag_mini_notify(new Exception('Some arbitrary error message'));

Running the unit test

To ease development and testing, I put together a simple PHPUnit-based test. To run it, you'll want to edit phpunit.xml, uncomment and modify the following section to suit:, (*17)

<php>
  <env name="BUGSNAG_API_KEY" value="your-api-key-goes-here" />
</php>

This won't actually halt the runtime., (*18)

About Fat Panda

Fat Panda is a software product consultancy located in Winchester, VA. We specialize in Laravel, WordPress, and Ionic. No matter where you are in the development of your product, we'll meet you there and work with you to propel you forward., (*19)

Contributing

If you run into a problem using this framework, please open an issue., (*20)

If you want to help make this framework amazing, check out the help wanted list., (*21)

If you'd like to support this and the other open source projects Fat Panda is building, please join our community of supporters on Patreon., (*22)

The Versions

13/01 2017

dev-master

9999999-dev

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  Sources   Download

MIT

The Development Requires

13/01 2017

1.0.3

1.0.3.0

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  Sources   Download

MIT

The Development Requires

13/01 2017

1.0.2

1.0.2.0

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  Sources   Download

MIT

The Development Requires

13/01 2017

1.0.1

1.0.1.0

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  Sources   Download

MIT

The Development Requires

13/01 2017

1.0.0

1.0.0.0

A minimal PHP-based implementation of a client for reporting application errors to Bugsnag

  Sources   Download

MIT

The Development Requires