PHPackages                             dopiaza/slack-exception-logger-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. dopiaza/slack-exception-logger-bundle

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

dopiaza/slack-exception-logger-bundle
=====================================

Log symfony2 exceptions to a Slack channel

2.0(8y ago)69.1k9[1 issues](https://github.com/dopiaza/slack-exception-logger-bundle/issues)MITPHPPHP &gt;=5.3.2

Since Jun 17Pushed 7y ago1 watchersCompare

[ Source](https://github.com/dopiaza/slack-exception-logger-bundle)[ Packagist](https://packagist.org/packages/dopiaza/slack-exception-logger-bundle)[ RSS](/packages/dopiaza-slack-exception-logger-bundle/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (1)Dependencies (1)Versions (5)Used By (0)

\#Slack Exception Logger Bundle for Symfony2

This bundle allows exceptions thrown in a symfony2 app to be logged automatically to a [Slack](https://slack.com) channel.

[![Alt text](Resources/documentation/exception.png)](Resources/documentation/exception.png)

To use, you first need to set up an incoming webhook in Slack - you can do this at [https://your\_slack\_instance.slack.com/services/new/incoming-webhook](https://your_slack_instance.slack.com/services/new/incoming-webhook) (replace *your\_slack\_instance* with whatever your particular Slack instance is called). Once you've done that, you'll be given a web hook URL - make a note of that, you'll need to add that to your `config.yml` file.

Install this bundle into your symfony app:

```
$ composer require dopiaza/slack-exception-logger-bundle

```

Next, add the bundle to `registerBundles` in `AppKernel.php`:

```
new Dopiaza\Slack\ExceptionLoggerBundle\DopiazaSlackExceptionLoggerBundle(),

```

And then set up your `config.yml`:

```
dopiaza_slack_exception_logger:
    webhook: https://hooks.slack.com/services/T0000000/B000000000/000000000000000000
    botname: symfony-bot
    name: My Symfony Application
    environments:
        test:
            enabled: true
            color: '#992255'
            channel: symfony-exceptions
        prod:
            channel: symfony-exceptions
            exclude_exception:
                - Symfony\Component\HttpKernel\Exception\NotFoundHttpException

```

`webhook` is the URL of the incoming web hook for your Slack instance.

`botname` is the name of the user that message will be posted as in your Slack channel. It has no default value. If no value is specified, Slack will use the name specified in your incoming web hook integration.

`name` is the name of your symfony application. This is useful if you have multiple apps all posting to the same channel.

`environments` holds all environment-specific configuration settings. Usual environment values to include in here would be `dev`, `test` and `prod`. If the environment being used isn't listed in this section, no exceptions will be posted. You probably don't really want to list `dev` in here, as that one is likely to generate quite a bit of noise, but hey, it's your choice.

`enabled` is an optional boolean to allow logging to be enabled or disabled on a per-channel basis. If not specified, it defaults to true.

`color` is an optional field used to determine the colour of the sidebar for the message. Valid values are `good` (green), `warning` (yellow), `danger` (red), or any hex value (e.g. `'#abcdef'`). Note that if you use a hex value, be sure to put it in quotes, otherwise the `#` will be interpreted as the start of a comment and the sidebar will come out an unattractive grey colour. If not specified, the default value is `danger`.

`channel` is the name of the channel to which exceptions are posted.

`exclude_exception` is an optional array of `Exception` class names which should be ignored. A typical use for this would be avoid a plethora of 'Not Found' exceptions being displayed for a production server that's publicly visible and thus subject to people randomly probing it.

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance17

Infrequent updates — may be unmaintained

Popularity27

Limited adoption so far

Community15

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 76.9% 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 ~262 days

Total

4

Last Release

3202d ago

Major Versions

1.0.2 → 2.02017-08-11

### Community

Maintainers

![](https://www.gravatar.com/avatar/17b200c013b198e7e908b957a2dc9b9d2c6a190ab1f435448bbce66dcb7b40b5?d=identicon)[dopiaza](/maintainers/dopiaza)

---

Top Contributors

[![dopiaza](https://avatars.githubusercontent.com/u/225224?v=4)](https://github.com/dopiaza "dopiaza (20 commits)")[![j4nr6n](https://avatars.githubusercontent.com/u/3661151?v=4)](https://github.com/j4nr6n "j4nr6n (3 commits)")[![jbq](https://avatars.githubusercontent.com/u/57103?v=4)](https://github.com/jbq "jbq (2 commits)")[![WackyMole](https://avatars.githubusercontent.com/u/79675808?v=4)](https://github.com/WackyMole "WackyMole (1 commits)")

---

Tags

exceptionslack

### Embed Badge

![Health badge](/badges/dopiaza-slack-exception-logger-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/dopiaza-slack-exception-logger-bundle/health.svg)](https://phpackages.com/packages/dopiaza-slack-exception-logger-bundle)
```

###  Alternatives

[facade/flare-client-php

Send PHP errors to Flare

51899.9M4](/packages/facade-flare-client-php)[spatie/flare-client-php

Send PHP errors to Flare

176148.0M15](/packages/spatie-flare-client-php)[justbetter/magento2-sentry

Magento 2 Logger for Sentry

1851.5M3](/packages/justbetter-magento2-sentry)[guanguans/laravel-exception-notify

Monitor exception and report to the notification channels(Log、Mail、AnPush、Bark、Chanify、DingTalk、Discord、Gitter、GoogleChat、IGot、Lark、Mattermost、MicrosoftTeams、NowPush、Ntfy、Push、Pushback、PushBullet、PushDeer、PushMe、Pushover、PushPlus、QQ、RocketChat、ServerChan、ShowdocPush、SimplePush、Slack、Telegram、WeWork、WPush、XiZhi、YiFengChuanHua、ZohoCliq、ZohoCliqWebHook、Zulip).

14642.7k1](/packages/guanguans-laravel-exception-notify)[simonbackx/slack-php-webhook

Post messages to your Slack channels with this easy to use library.

41837.3k2](/packages/simonbackx-slack-php-webhook)[facile-it/sentry-module

This module allows integration of Sentry Client into laminas and mezzio

19372.5k](/packages/facile-it-sentry-module)

PHPackages © 2026

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