Check size of extradata in bemodule, mail and gelf transports about typo3-mklog HOT 7 CLOSED

Yes it is.
A lot of extensions use the old devlog api and it is still part of TYPO3. See GeneralUtility::devLog.
The devlog was removed in TYPO3 10. When we drop the support for TYPO3 9.5, than we should remove the old devlog system.

from typo3-mklog.

Wouldn't it be better to migrate to Monolog which already takes care of this type if issue?
https://github.com/Seldaek/monolog/blob/master/src/Monolog/Formatter/GelfMessageFormatter.php#L99-L101

I'm also aware that there is a TYPO3 extension which integrates monolog into it.
https://docs.typo3.org/typo3cms/extensions/logging/1.0.0/

from typo3-mklog.

There is nothing wrong to use the georgringer/logging extension for logging.
Mklog is a parallel to it, inspired by the old devlog extension.
The use of monolog would be nice, but a lot of work and you could use georgringer/logging instead.

from typo3-mklog.

So what would be the advantage of this extension? Maybe we can add it to the Readme why or better when they should use this extension rather than the logging extension from georgringer?

from typo3-mklog.

The georgringer/logging currently is just a concept and only compatible with TYPO3 8.
To use this we has to use its own monolog manager, instead the devlog or typo3 logger.
This can be very useful for special projects!

Mklog is a generic logging extension, compatible to TYPO3 9, uses the old DevLog-Hook and the new TYPO3-Logger.
So all logs are included, regardless of whether a extension uses the devlog or the typo3 core loging. No special manager class has to be implemented, just the typo3 core.

Mklog writes all the logs (your own, from the core and all other third party extensions) into the database, apart from critical messages that are sent directly to graylog. Later in the background a scheduler processes the logs (send per mail, or to graylog) to not disturb the frontend request too much.

It is certainly a good idea to port the processes to use the awesome monolog.
But currently this would be too much work.

I agree that we should include some more information about what mklog really does in the documentation/readme.

from typo3-mklog.

Thank you for this clear explanation, now understand this usecase a little bit better.

Just one more question, is the devlog still relevant in favor of the new logging system which is shipped with the core?

from typo3-mklog.

New data parser to reduce the size of extra data on watchdog transport (gelf/graylog) was added.
Release is pending.

from typo3-mklog.