The Sentry PHP error reporter tracks errors and exceptions that happen during the execution of your application and provides instant notification with detailed informations needed to prioritize, identify, reproduce and fix each issue. Learn more about automatic PHP error reporting with Sentry.

• Automatically report (un)handled exceptions and errors
• Send customized diagnostic data
• Process and sanitize data before sending it over the network

// Instantiate a new client with a compatible DSN and install built-in
// handlers
$client = (new Raven_Client('http://[email protected]/1'))->install();

// Capture an exception
$event_id = $client->captureException($ex);

// Give the user feedback
echo "Sorry, there was an error!";
echo "Your reference ID is " . $event_id;

For more information, see our documentation.

Other packages exists to integrate this SDK into the most common frameworks.

The following integrations are fully supported and maintained by the Sentry team.

• Symfony
• Laravel

The following integrations are available and maintained by members of the Sentry community.

• Nette
• ZendFramework
• WordPress
• Drupal
• OpenCart
• ... feel free to be famous, create a port to your favourite platform!

• Documentation
• Bug Tracker
• Code
• Mailing List
• IRC (irc.freenode.net, #sentry)

Dependencies are managed through composer:

$ composer install

Tests can then be run via phpunit:

$ vendor/bin/phpunit

1. Make sure CHANGES is up to date (add the release date) and master is green.

2. Create a new branch for the minor version (if not present):

$ git checkout -b releases/1.10.x

3. Update the hardcoded version tag in Client.php:

class Raven_Client
{
    const VERSION = '1.10.0';
}

4. Commit the change:

$ git commit -a -m "1.10.0"

5. Tag the branch:

git tag 1.10.0

6. Push the tag:

git push --tags

7. Switch back to master:

git checkout master

8. Add the next minor release to the CHANGES file:

## 1.11.0 (unreleased)

9. Update the version in Client.php:

class Raven_Client
{
    const VERSION = '1.11.x-dev';
}

10. Lastly, update the composer version in composer.json:

    "extra": {
        "branch-alias": {
            "dev-master": "1.11.x-dev"
        }
    }

All done! Composer will pick up the tag and configuration automatically.