[Typo3-dev] Logging in TYPO3

[Kasper Skårhøj]

[Sorry AGAIN, I'm really trigger happy this morning it seems: previous mail was sent unfinished once more!!!]

Hi Folks,

I just want to poll some opinions about loggin needs in TYPO3. We have these log types:

- Backend log which tracks user logins and changes to records. I intend to open this up for logging from extensions too (3.9.0 probably)
- page hits (goes to apache logs) - This is not what I mean to discuss here.
- Frontend log: we have no real log for frontend plugins which could be useful for tracing errors in TypoScript or plugins - but I can't come up with a powerful idea for this which could be really useful (and it most likely shouldn't go into the backend log!)
- t3lib_div::devLog() which was introduced during the development of "realurl" extension, but I personally didn't use it since (rather like debugging with debug() function....). The description of this function is seen below [1]. Output from that log is handled by extension, an example is "logit".

The motivation for writing is: 
- For 3.9.0 I plan to work on the backend syslog
- ... and it has just been suggested to me to implement he feature for unix systems that we can call the system logger to put TYPO3 messages into eg. "/var/log/syslog" - whichi of course begs the question; What messages from where makes sense...





[1]
	 * Developer log; This should be implemented around the source code, both frontend and backend, logging everything from the flow through an application, messages, results from comparisons to fatal errors.
	 * The result is meant to make sense to developers during development or debugging of a site.
	 * The idea is that this function is only a wrapper for external extensions which can set a hook which will be allowed to handle the logging of the information to any format they might wish and with any kind of filter they would like.



-- 
- kasper

*******************
Happy new year! - My email address is now: 

		kasper2005 at typo3.com