JLog Improvements

[pasamio]

1. Introduction
With Joomla! 1.5, there is now the ability to do centralised logging that wasn't present without third party support in the earlier 1.0 series. However the 1.5 support only includes a single logging method to a text file.

2. Scope
Whilst logging to a text file is easy, it is not the most friendly format because it can be hard to parse this file within an extension (memory and time issues for large files), in some cases it is preferable to log to an external source or even to the database. The reason why one would want to log to the database is to provide the ability for easy searching within the system without having to handle large amounts of data.

3. Implementation
Include the development of a facility for JLog to natively handle more than one logging format than what is available. Ideally a database logging mechanism should be provided for easy use.

4. Impacts
This should be done in a way that is transparent to users of JLog. An additional option will appear to handle different logging engines.

[AmyStephen]

Optional core logging to a database table would be great.

[ircmaxell]

I agree here... One thing we SHOULD add IMHO is a set of plugin events to JLog. So that I can create a plugin to send me an email any time someone tries to login to the admin account (for example)...

[pasamio]

Actually you could write that plugin already with Joomla! 1.5 by using the User triggers that occur when a user logs in, check out the /plugins/user/joomla.php file to see what it does, all you'd have to do is write another user plugin that implements onLoginUser and handles mailing a user.

[Chris Davenport]

Sam, I'm glad you included this white paper. I remember the work you did on this ages ago and I was looking forward to seeing it implemented one day. For me the killer application of this facility is to be able to extend JLog with a standard *nix logger interface. It's really easy to implement and it would mean that log messages get sent to a background log process running on the same, or a different server, in real-time. It is then easy to write scripts that can monitor log entries as they come in and fire off alarms/emails/whatever as appropriate. A single, central, log server can provide this service for multiple Joomla! instances.

Chris.

[joomlacorner]

Sam,
this's Thailand's Law Computer Related Crime Act B.E 2550
http://www.etcommission.go.th/documents ... ficial.pdf

may be you can do it to compatible with this law.