PHPackages                             t3n/flow-log - 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. t3n/flow-log

AbandonedArchivedNeos-package[Logging & Monitoring](/categories/logging)

t3n/flow-log
============

Small package that provides several Logger for the Flow Framework

1.0.5(1y ago)011.3k↓66.7%PHP

Since Dec 13Pushed 8mo agoCompare

[ Source](https://github.com/t3n/FlowLog)[ Packagist](https://packagist.org/packages/t3n/flow-log)[ RSS](/packages/t3n-flow-log/feed)WikiDiscussions master Synced 1w ago

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

Warning

**This plugin is no longer being maintained and there is no superseding package at this time**

t3n.FlowLog
===========

[](#t3nflowlog)

This package adds a few helper to log Flow Messages.

🔧 Still Work in Progress 🔧

ConsoleStorage
--------------

[](#consolestorage)

If you'd like to log your Exceptions to the console, for instance stderr or stdout, he ConsoleStorage is for you. It will log all throwables directly to the console as JSON. The JSON is formatted to be [parsed by google Stackdriver](https://cloud.google.com/error-reporting/reference/rest/v1beta1/projects.events/report#ReportedErrorEvent).

To enable the ConsoleStorage you need to adjust your Settings.yaml like this:

```
Neos:
  Flow:
    log:
      throwables:
        storageClass: t3n\FlowLog\ThrowableStorage\ConsoleStorage
        optionsByImplementation:
          't3n\FlowLog\ThrowableStorage\ConsoleStorage':
            streamName: 'stderr'
```

The StreamName could either be `stderr` or `stdout`.

BigQueryLogger
--------------

[](#bigquerylogger)

The BigQueryLogger is an `AbstractBackend` so that you can use it like an normal Logger like `FileBackend`. If you want to log into BigQuery, here is your 3 Step manual:

- configure BigQuery (dataset, table, keyFile)
- create a `BigQueryLogger` via `PsrLoggerFactory`
- map your custom `BigQueryLogger` via `Objects.yaml` to actually use it

### 1) Configure BigQueryLogger

[](#1-configure-bigquerylogger)

```
t3n:
  FlowLog:
    bigQuery:
      dataset: 't3n_flowlog'
      table: 'application_log'
      expirationMs: '7776000000' # 90 days
      keyFilePath: '/path/to/google/key.json'
```

ℹ️ All logs will be written into a partitioned table in BigQuery. This means that you have a "overall" table with multiple tables for each day. This day-tables can be deleted automatically via `expirationMs`. If you want to store your logs forever just ignore this Setting and let it blank.

### 2) Create your own Instance of BigQueryLogger

[](#2-create-your-own-instance-of-bigquerylogger)

To actually use the BigQueryLogger you have to define your own in your `Settings.yaml`. The important part is `loggerName` ("applicationXyImportLogger") and the internal Name `bigQueryLogger`.

`bigQueryLogger` will be used in Step 3, `loggerName` is the actual name for the BigQueryTable (inserted for each row).

```
Neos:
  Flow:
    log:
      psr3:
        'Neos\Flow\Log\PsrLoggerFactory':
          bigQueryLogger:
            class: 't3n\FlowLog\Backend\BigQueryLogger'
            options:
              loggerName: 'applicationXyImportLogger'
```

You can create as many loggers as you want. This is really usefull if you want to "split" your logs in your BigQueryTable. E.g. one Logger for Imports, one for User-Requests, etc.

### 3) Map your BigQueryLogger via Objects.yaml

[](#3-map-your-bigquerylogger-via-objectsyaml)

Last but not least you have to define your Logging-Factory to use your BigQueryLogger.

Therefore edit your `Objects.yaml` like this:

```
t3n\FlowLog\Command\ExampleCommandController: # logger->log(LogLevel::INFO, 'First log entry.', ['test' => true]);
```

[![First entry in BigQuery - example](docs/bigquery_example.png "First entry in BigQuery - example.")](docs/bigquery_example.png)

ServiceContext
--------------

[](#servicecontext)

ℹ️ Important if you want to log multiple applications/environments (e.g.) in BigQuery.

You should also set the ServiceContext that is used by StackDriver and BigQueryLogger:

```
t3n:
  FlowLog:
    serviceContext:
      service: 'flow-app'
      version: 'master'
```

###  Health Score

40

—

FairBetter than 88% of packages

Maintenance49

Moderate activity, may be stable

Popularity22

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity66

Established project with proven stability

 Bus Factor1

Top contributor holds 62.5% 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 ~65 days

Total

16

Last Release

445d ago

Major Versions

0.2.2 → 1.0.02021-12-30

0.2.3 → 1.0.22023-01-26

0.1.4 → 1.0.32024-06-13

### Community

Maintainers

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

---

Top Contributors

[![johannessteu](https://avatars.githubusercontent.com/u/769789?v=4)](https://github.com/johannessteu "johannessteu (10 commits)")[![das-nagnag](https://avatars.githubusercontent.com/u/5262896?v=4)](https://github.com/das-nagnag "das-nagnag (6 commits)")

### Embed Badge

![Health badge](/badges/t3n-flow-log/health.svg)

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

###  Alternatives

[psr/log

Common interface for logging libraries

10.4k1.2B9.2k](/packages/psr-log)[itsgoingd/clockwork

php dev tools in your browser

5.9k27.6M94](/packages/itsgoingd-clockwork)[graylog2/gelf-php

A php implementation to send log-messages to a GELF compatible backend like Graylog2.

41838.2M138](/packages/graylog2-gelf-php)[bugsnag/bugsnag-psr-logger

Official Bugsnag PHP PSR Logger.

32132.5M2](/packages/bugsnag-bugsnag-psr-logger)[consolidation/log

Improved Psr-3 / Psr\\Log logger based on Symfony Console components.

15462.2M7](/packages/consolidation-log)[open-telemetry/api

API for OpenTelemetry PHP.

1933.0M214](/packages/open-telemetry-api)

PHPackages © 2026

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