graycore / magento2-stdlogging
graycore/magento2-stdlogging
A Magento 2 module that changes all logging handlers to stdout
Magento 2 StdLogging
Magento Version Support
Purpose
This module is a drop in replacement to pump all Magento 2 logs to StdOut. This is especially useful when working in a dockerized environment where you want to aggregate your logs into an external system without having to know about Magento specific log files and configurations.
Getting Started
This module is intended to be installed with composer. From the root of your Magento 2 project:
- Download the package
composer require graycore/magento2-stdlogging
- Enable the package
./bin/magento module:enable Graycore_StdLogging
Upgrading
Changelog
All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
2.1.2 (2026-05-18)
Miscellaneous Chores
- deps-dev: upgrade to phpunit 12 and magento/magento-coding-standard:40 (d3024c9)
- deps: bump graycoreio/github-actions-magento2 from @main to 8.2.0 (31c55ba)
2.1.1 (2026-03-03)
Miscellaneous Chores
- remove nodejs deps (4c9ef6e)
2.1.0 (2025-04-10)
Features
Bug Fixes
Miscellaneous Chores
2.0.0 (2022-06-26)
⚠ BREAKING CHANGES
- all: we no longer test against php7.2. Please use it at your own risk.
ci
1.1.1 (2020-10-23)
Bug Fixes
- deps: align monolog version with Magento base version (3380ca7)
1.1.0 (2020-09-16)
Features
- deps: update deps to support Magento v2.4 (0958f4a)
1.0.3 (2020-06-23)
Bug Fixes
1.0.2 (2020-03-12)
Bug Fixes
- log: Inability to Run the DI Compiler before setup (0a38687)
Build System
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| v2.1.2 | stable | Not tested | Not yet tested Details | 2026-05-18 15:22:29 |
| v2.1.1 | stable | Not tested | Not yet tested Details | 2026-03-03 18:57:18 |
| v2.1.0 | stable | Not tested | Not yet tested Details | 2025-04-10 13:52:16 |
| v2.0.0 | stable | Not tested | Not yet tested Details | 2022-06-26 18:49:04 |
| v1.1.1 | stable | Not tested | Not yet tested Details | 2020-10-23 17:09:09 |
| v1.1.0 | stable | Not tested | Not yet tested Details | 2020-09-16 14:55:13 |
| 1.0.3 | stable | Fail | Not yet tested Details | 2020-06-23 20:51:57 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2020-03-12 18:35:51 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2020-03-06 20:41:16 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2020-03-06 20:25:29 |
Requires 4
| Package | Constraint |
|---|---|
| magento/framework | ^102.0 |
| magento/module-developer | ^100.3.3 |
| monolog/monolog | 1.17 |
| php | >=7.0.0 |
Requires-dev 3
| Package | Constraint |
|---|---|
| magento/magento-coding-standard | ^5.0 |
| phpunit/phpunit | ^8.2 |
| squizlabs/php_codesniffer | ^3.4 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | ||
| 2.4.8 | not tested | not tested | ||
| 2.4.9 | not tested | not tested |
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from graycore
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.