PHPackages                             exs/error-bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Logging &amp; Monitoring](/categories/logging)
4. /
5. exs/error-bundle

ActiveSymfony-bundle[Logging &amp; Monitoring](/categories/logging)

exs/error-bundle
================

Error logging bundle for Symfony2

v2.1.0(8y ago)16.2k11MITPHPPHP &gt;=5.3.9

Since Jun 1Pushed 8y ago9 watchersCompare

[ Source](https://github.com/ExSituMarketing/EXS-ErrorBundle)[ Packagist](https://packagist.org/packages/exs/error-bundle)[ Docs](https://github.com/ExSituMarketing/EXS-ErrorBundle)[ RSS](/packages/exs-error-bundle/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (3)Dependencies (1)Versions (10)Used By (1)

Symfony 2.x ErrorBundle
=======================

[](#symfony-2x-errorbundle)

Error bundle to log 4xx and 5xx errors and exceptions in the database.

Bundle is installed as a service listening for all 4xx and 5xx http exceptions and logs them in the database. When used in conjunction with a crontab enabled monitor we can then alert the dev team when there are hightened number of errors on the site and issue a rapid fix if necessary.

Installing the ErrorBundle in a new Symfony2 project
----------------------------------------------------

[](#installing-the-errorbundle-in-a-new-symfony2-project)

So the ErrorBundle is ready for installation, great news but how do we install it. The installation process is actually very simple. Set up a new Symfony2 project with Composer.

Require from the command line directly:

```
composer require 'exs/error-bundle:1.0'

```

Once the new project is set up, open the composer.json file and add the exs/error-bundle as a dependency:

```
//composer.json
//...
"require": {
        //other bundles
        "exs/error-bundle": "~1.0@dev"
```

Save the file and have composer update the project via the command line:

```
php composer.phar update
```

Composer will now update all dependencies and you should see our bundle in the list:

```
  - Installing exs/error-bundle (dev-master 0c644b1)
    Cloning 0c644b1315e75cd4ff521eeea0ee3243faad0ce3
```

Now just update the app/AppKernel.php and app/config/routing.yml to include our bundle, clear the cache and update the schema:

```
//app/AppKernel.php
//...
    public function registerBundles()
    {
        $bundles = array(
            //Other bundles
            new EXS\ErrorBundle\EXSErrorBundle()
        );
```

add routing.yml:

```
#app/config/routing.yml
#...
contact:
    resource: "@EXSErrorBundle/Controller/"
    type:     annotation
    prefix:   /

```

add the bundle to orm configuration:

```
#app/config/config.yml
#...
    orm:
        auto_generate_proxy_classes: "%kernel.debug%"
        default_entity_manager: default
        entity_managers:
            default:
                connection: default
                mappings:
                    AppBundle:  ~
                    EXSErrorBundle: ~

```

add deprecated errors params:

```
# parameters.yml:
    deprecated_errors_logging: false

```

clear cache and update database:

```
php app/console cache:clear
php app/console doctrine:schema:update --force
```

and now you're done.

You can test that it works by throwing 500 and 400 series errors from your app. The errors will be logged (along with useful debugging information) in your database in the following tables:

- exception4xx
- exception5xx

If you wish to test the exceptions being thrown via the included controller you can try the following routes

- [http://www.example.com/app\_dev.php/\_test/error/http/500](http://www.example.com/app_dev.php/_test/error/http/500)
- [http://www.example.com/app\_dev.php/\_test/error/http/404](http://www.example.com/app_dev.php/_test/error/http/404)
- [http://www.example.com/app\_dev.php/\_test/error/http/403](http://www.example.com/app_dev.php/_test/error/http/403)
- [http://www.example.com/app\_dev.php/\_test/error/http/405](http://www.example.com/app_dev.php/_test/error/http/405)
- [http://www.example.com/app\_dev.php/\_test/error/http/410](http://www.example.com/app_dev.php/_test/error/http/410)
- [http://www.example.com/app\_dev.php/\_test/error/php/fatal](http://www.example.com/app_dev.php/_test/error/php/fatal)
- [http://www.example.com/app\_dev.php/\_test/error/php/notice](http://www.example.com/app_dev.php/_test/error/php/notice)

If you want to test the console exceptions try:

```
php app/console _test:command:fatal
php app/console _test:command:notice
php app/console _test:command:exception
```

#### Contributing

[](#contributing)

Anyone and everyone is welcome to contribute.

If you have any questions or suggestions please [let us know](http://www.ex-situ.com/).

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community15

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 81.3% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~127 days

Recently: every ~161 days

Total

7

Last Release

3239d ago

Major Versions

v1.0.2 → v2.x-dev2017-06-09

PHP version history (2 changes)v1.0PHP &gt;=5.3.2

v2.x-devPHP &gt;=5.3.9

### Community

Maintainers

![](https://www.gravatar.com/avatar/af284ff600087e33c35e00252ade1cc1dc3987f969661b91b036254dbe4bbb9c?d=identicon)[rumpranger](/maintainers/rumpranger)

---

Top Contributors

[![damien-qc](https://avatars.githubusercontent.com/u/12374806?v=4)](https://github.com/damien-qc "damien-qc (26 commits)")[![rumpranger](https://avatars.githubusercontent.com/u/718301?v=4)](https://github.com/rumpranger "rumpranger (6 commits)")

---

Tags

bundleloggingerror404500

### Embed Badge

![Health badge](/badges/exs-error-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/exs-error-bundle/health.svg)](https://phpackages.com/packages/exs-error-bundle)
```

###  Alternatives

[rollbar/rollbar-laravel

Rollbar error monitoring integration for Laravel projects

14110.4M7](/packages/rollbar-rollbar-laravel)[analog/analog

Fast, flexible, easy PSR-3-compatible PHP logging package with dozens of handlers.

3451.5M24](/packages/analog-analog)[jenssegers/rollbar

Rollbar error monitoring integration for Laravel projects

3301.1M2](/packages/jenssegers-rollbar)[justbetter/magento2-sentry

Magento 2 Logger for Sentry

1851.5M3](/packages/justbetter-magento2-sentry)[saasscaleup/laravel-log-alarm

Laravel log Alarm help you to set up alarm when errors occur in your system and send you a notification via Slack and email

27025.0k](/packages/saasscaleup-laravel-log-alarm)[jenssegers/raven

Sentry (Raven) error monitoring integration for Laravel projects

90197.2k1](/packages/jenssegers-raven)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
