PHPackages                             slimen/log-tracker - 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. slimen/log-tracker

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

slimen/log-tracker
==================

Display symfony logs in more elegant way and track exceptions by sending real time mails containing details about the exception.

v1.3.2(5y ago)03142MITHTMLPHP &gt;=5.5.9

Since Sep 14Pushed 5y ago1 watchersCompare

[ Source](https://github.com/SlimenTN/LogTrackerBundle)[ Packagist](https://packagist.org/packages/slimen/log-tracker)[ RSS](/packages/slimen-log-tracker/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (1)Versions (10)Used By (0)

LogTrackerBundle
================

[](#logtrackerbundle)

Sometimes symfony does not display the exception in the browser, so you have to go to the log file and check the lastest log details so you can read the exception and locate the source of the problem.
Pretty annoying isn't ? Well `LogtrackerBundle` will make your life easier by displaying the details of the log file (dev.log and prod.log) in more elegant way with the possibility of filtering and searching inside the file.
`LogTrackerBunlde` helps you also to track any thrown exception in your project by sending real time email with the details of the exception.

Installation
============

[](#installation)

1. `composer require slimen/log-tracker`
2. Enable the bundle in AppKernel.php `new SBC\LogTrackerBundle\LogTrackerBundle(),`
3. Add this in `config/routing.yml`:
    ```
    log_trucker:
        resource: "@LogTrackerBundle/Resources/config/routing.yml"
        prefix:   /logger
    ```
4. run `php bin/console asset:install`

Usage
=====

[](#usage)

1. To display `dev.log` got to `localhost:/YourProject/web/dev_app.php/logger/_dev`
2. To display `prod.log` got to `localhost:/YourProject/web/dev_app.php/logger/_prod`
3. To keep track of thrown exception you need to add this in your `config.yml` file:
    ```
    # LogTracker Configuration
    log_tracker:
        app_name: 'Your app name'
        sender_mail: 'your_mail@company.com'
        recipients: ['mail1@company.com', 'mail2@company.com'] #you can add as much as you want of addresses
        # optional (default value: 'twig')
        # type of response you want to return
        # 'twig' if you want to display a twig page
        # 'json' if you want to return a json response (in case of API)
        response:   'twig'
        # choose which exception code to exclude from the listener (optional)
        exclude_exceptions: [404, 403, ...]
    ```

### How it works

[](#how-it-works)

In **production** mode `LogTrackerBundle` will catch any type of exception (except `NotFoundException` assuming that it will be handled to display **404 Not Found** page) and will display this view (Of course unless you override it):

[![Default error catcher view](Resources/docs/images/error_catcher.png)](Resources/docs/images/error_catcher.png)

### Override the default view

[](#override-the-default-view)

You can override the whole view and display any view you want by following [Symfony's override style](https://symfony.com/doc/3.4/templating/overriding.html)
To override the view just add a view called `error_catcher.html.twig` under the folder `app/Resources/LogTracker/views/` and create the view you want to display for your users.

### License

[](#license)

This project is under the [MIT license](LICENSE)

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity14

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 91.7% 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 ~125 days

Recently: every ~103 days

Total

9

Last Release

2161d ago

### Community

Maintainers

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

---

Top Contributors

[![SlimenTN](https://avatars.githubusercontent.com/u/17424180?v=4)](https://github.com/SlimenTN "SlimenTN (33 commits)")[![isomT](https://avatars.githubusercontent.com/u/14231173?v=4)](https://github.com/isomT "isomT (2 commits)")[![romeritoCL](https://avatars.githubusercontent.com/u/301758?v=4)](https://github.com/romeritoCL "romeritoCL (1 commits)")

---

Tags

loggersymfonysymfony-bundletrackinglog filelog trackexceptions track

### Embed Badge

![Health badge](/badges/slimen-log-tracker/health.svg)

```
[![Health](https://phpackages.com/badges/slimen-log-tracker/health.svg)](https://phpackages.com/packages/slimen-log-tracker)
```

###  Alternatives

[liip/monitor-bundle

Liip Monitor Bundle

4728.7M16](/packages/liip-monitor-bundle)[inspector-apm/inspector-symfony

Code Execution Monitoring for Symfony applications.

2830.1k2](/packages/inspector-apm-inspector-symfony)

PHPackages © 2026

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