dmk/mklog

Keep track of developer logs. Provides automatic email notification about important errors.

v12.0.3 2024-05-24 11:06 UTC

Requires

• doctrine/dbal: ~2.13.1 || ^3.6
• egulias/email-validator: ^2.1 || ^3.1 || ^4.0
• graylog2/gelf-php: ~1
• typo3/cms-core: ^11.5.7 || ^v12.4.2
• typo3/cms-scheduler: ^11.5 || ^v12.4

Requires (Dev)

• friendsofphp/php-cs-fixer: ^3.3
• mikey179/vfsstream: ^1.6
• php-parallel-lint/php-parallel-lint: ^1.3
• phpcompatibility/php-compatibility: ^9.3.5
• phpmd/phpmd: ^2.11.1
• phpstan/extension-installer: ^1.1
• phpstan/phpstan: ^1.1
• saschaegerer/phpstan-typo3: ^1.0
• sebastian/phpcpd: ^5.0 || ^6.0
• typo3/testing-framework: ^7.0

Suggests

• digedag/rn-base: Needed for the backend module, so you can view the logs directly in the TYPO3 backend

Replaces

• typo3-ter/mklog: v12.0.3

GPL-2.0-or-later

• Michael Wagner
• Hannes Bochmann
• René Nitzsche

• log
• notification
• TYPO3 CMS
• devlog

README

This extension offers a developer log. Ther is a scheduler task too, the watch dog, which aggregates devlog entries and sends them via a transport. So it is possible to send a mail with fatal errors the minute they occur but warnings only every 6 hours. Or send a mail with infos from an import every night.

Or transport all the logs to a graylog server

Of course the devlog has to be used by the core and extensions. To have exceptions and errors logged to the devlog the error handling of mktools can be used.

Installation

Install TYPO3 via composer. Maybe you can use our TYPO3-Composer-Webroot Project

From project root you need to run

composer require dmk/mklog

Documentation

For usage please have a look in our Documentation

CHANGELOG