PHPackages                             yeebase/graylog - 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 & Monitoring](/categories/logging)
4. /
5. yeebase/graylog

ActiveNeos-yeebase[Logging & Monitoring](/categories/logging)

yeebase/graylog
===============

Graylog exception handler for Neos Flow

3.1.0(8y ago)823.9k6MITPHP

Since Jun 24Pushed 8y ago7 watchersCompare

[ Source](https://github.com/yeebase/Yeebase.Graylog)[ Packagist](https://packagist.org/packages/yeebase/graylog)[ RSS](/packages/yeebase-graylog/feed)WikiDiscussions master Synced yesterday

READMEChangelog (10)Dependencies (2)Versions (18)Used By (0)

Yeebase.Graylog
===============

[](#yeebasegraylog)

The Yeebase.Graylog Flow package logs your exceptions as well as single messages to a central Graylog server. This package also provides a simple backend to log message of Flows Logger classes to a Graylog server.

It depends on the official GELF php package

Installation & configuration
--------------------------------

[](#installation--configuration)

Just add "yeebase/graylog" as dependency to your composer.json and run a "composer update" in your project's root folder or simply execute:

```
composer require yeebase/graylog

```

from your project's root.

Configure your Graylog Server:

```
Yeebase:
  Graylog:
    host: '127.0.0.1'
    port: 12201
    chunksize: 'wan'
```

### Logging backend

[](#logging-backend)

To configure GraylogBackend as the default logging backend, put this in your Settings.yaml:

```
Neos:
  Flow:
    log:
      systemLogger:
        backend: Yeebase\Graylog\Log\Backend\GraylogBackend
      securityLogger:
        backend: Yeebase\Graylog\Log\Backend\GraylogBackend
      sqlLogger:
        backend: Yeebase\Graylog\Log\Backend\GraylogBackend
      i18nLogger:
        backend: Yeebase\Graylog\Log\Backend\GraylogBackend

```

### Log exceptions

[](#log-exceptions)

Activate the exception handler and configure the connection to your graylog server in your Settings.yaml:

```
Neos:
  Flow:
    error:
      exceptionHandler:
        className: 'Yeebase\Graylog\Error\GraylogExceptionHandler'
```

Now all Exceptions that are shown to the Web or CLI are logged to graylog.

*Note:* For `Development` context, the `Neos.Flow` package overrides this setting. Make sure to add this configuration in the right context Settings.yaml.

If you want to log additionally *all* Exceptions to graylog you should replace the systemLogger as well. This will log all errors that are logged with the SystemLogger to Graylog as well to the disk. By default Flow will only log a single line to the system log aka "See also ... .txt". The GraylogLogger will also log the full Exception.

```
Neos:
  Flow:
    log:
      systemLogger:
        logger: Yeebase\Graylog\Log\GraylogLogger
```

#### Filter exceptions

[](#filter-exceptions)

To skip certain exceptions from being logged you can either use the `skipStatusCodes` setting:

```
Yeebase:
  Graylog:
     # don't log any exceptions that would result in a HTTP status 403 (access denied) / 404 (not found)
    skipStatusCodes: [403, 404]
```

Since version 2.1 you can alternatively use the `renderingGroups` Flow setting, i.e. to exclude certain Exception *classes* from being logged:

```
Neos:
  Flow:
    error:
      exceptionHandler:
        className: 'Yeebase\Graylog\Error\GraylogExceptionHandler'
        renderingGroups:
          'accessDeniedExceptions':
            matchingExceptionClassNames: ['Neos\Flow\Security\Exception\AccessDeniedException']
            options:
              logException: false
```

### Manual logging

[](#manual-logging)

If you wish to log normal log messages to your Graylog server just use the provided `GraylogLoggerInterface`:

```
use Neos\Flow\Annotations as Flow;
use Yeebase\Graylog\Log\GraylogLoggerInterface;

class SomeClass
{
    /**
     * @Flow\Inject
     * @var GraylogLoggerInterface
     */
    protected $graylogLogger;

    public function yourMethod()
    {
      $this->graylogLogger->log('Your Message')
    }
}
```

By default messages will also be logged to the `SystemLoggerInterface` when Flow runs in `Development` context. You can enable or disable this function with a setting:

```
Yeebase:
  Graylog:
    Logger:
      backendOptions:
        alsoLogWithSystemLogger: true
```

### Extend the message context

[](#extend-the-message-context)

By default this package will send a bunch of values to graylog you can use to filter on. A Exception for instance has some fields like `reference_code`, `response_status_code` and so on. You can extend those values via Settings.yaml. Just pass an array of values to `Yeebase.Graylog.messageContext`. This is useful to pass some static values to your logs to filter on in Graylog.

```
Yeebase:
  Graylog:
    messageContext:
      app_context: 'stage'
```

###  Health Score

38

—

LowBetter than 83% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity29

Limited adoption so far

Community20

Small or concentrated contributor base

Maturity72

Established project with proven stability

 Bus Factor1

Top contributor holds 83.1% 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 ~44 days

Recently: every ~14 days

Total

17

Last Release

2949d ago

Major Versions

1.1.x-dev → 2.0.02017-01-20

2.3.1 → 3.0.02018-05-14

2.4.0 → 3.1.02018-06-06

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/769789?v=4)[Johannes Steu](/maintainers/johannessteu)[@johannessteu](https://github.com/johannessteu)

![](https://www.gravatar.com/avatar/1761d781f5f02019a92554a360fadb464c08ac4a1b2e7799666fd90727c0c167?d=identicon)[brgmn](/maintainers/brgmn)

---

Top Contributors

[![johannessteu](https://avatars.githubusercontent.com/u/769789?v=4)](https://github.com/johannessteu "johannessteu (64 commits)")[![brgmn](https://avatars.githubusercontent.com/u/452916?v=4)](https://github.com/brgmn "brgmn (4 commits)")[![bwaidelich](https://avatars.githubusercontent.com/u/307571?v=4)](https://github.com/bwaidelich "bwaidelich (4 commits)")[![dimaip](https://avatars.githubusercontent.com/u/837032?v=4)](https://github.com/dimaip "dimaip (2 commits)")[![robertlemke](https://avatars.githubusercontent.com/u/95582?v=4)](https://github.com/robertlemke "robertlemke (2 commits)")[![skurfuerst](https://avatars.githubusercontent.com/u/190777?v=4)](https://github.com/skurfuerst "skurfuerst (1 commits)")

---

Tags

flowframeworkgraylogneos-cms

### Embed Badge

![Health badge](/badges/yeebase-graylog/health.svg)

```
[![Health](https://phpackages.com/badges/yeebase-graylog/health.svg)](https://phpackages.com/packages/yeebase-graylog)
```

###  Alternatives

[hedii/laravel-gelf-logger

A Laravel package to send logs to a gelf compatible backend like graylog

1363.6M12](/packages/hedii-laravel-gelf-logger)[neos/neos

An open source Content Application Platform based on Flow. A set of core Content Management features is resting within a larger context that allows you to build a perfectly customized experience for your users.

1151.0M777](/packages/neos-neos)[neos/media

The Media package

101.2M53](/packages/neos-media)

PHPackages © 2026

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