Feature #20591
closed
Write system log t3lib_div::sysLog() calls into sys_log
0%
Description
To view sysLog() calls in the backend "Log" modules, they just have to be logged into the sys_log table.
Why should we have a nother log system when we have this great "Log" module where we can filter...
-> <sys_log_table> should be an option...
If you are interessted in that feature, I'll writhe a patch, otherwise I'll writhe a extensions...
(issue imported from #M11295)
Updated by Martin Kutschker over 15 years ago
Sounds interesting.
I suggest to add a new "type" (database field. in the UI it's called "action"!) "system log" (id 6) and to use the severity as "action" (DB field, currently no UI but I'm working on changing that).
A problem might be that in theory the entries of sys_log are translatable by the third identifier, the message number. In case if the t3lib_div::sysLog calls I think all of the log entries will have to have the same message number (0) without a translation.
Updated by Jonas Felix over 15 years ago
That would be great.
But I would not translate those messages, they are spread all over TYPO3 and are more technical then the regular sys_log.
We jus preferre this option instead of using syslog unix deamon or textfile. We would like to have on central TYPO3 log with everything included.
Updated by Christian Weiske over 15 years ago
One can write into syslog using the BE_USER object:
http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.0.0/view/3/7/
Updated by Jonas Felix over 15 years ago
@Christian: Thank you for the tip.
But the sysLog() messages are lost on most systems, because nobody configures it. And I don't want to use logfiles, logmails, I would like to use the sys_log table for that.
Updated by Mathias Schreiber almost 10 years ago
- Description updated (diff)
- Category set to Logging
- Target version changed from 0 to 7.5
Updated by
Updated by Markus Klein about 7 years ago
- Status changed from New to Rejected
sysLog() will be replaced by Logging API