I am trying to develop the Stats/Log/Events Engine for Jahia.Regarding users logs or stats, please take care of understanding the various Jahia caches mechanisms first. For example Jahia integrates an HTML cache proxy. The goal is to avoid as much as possible any connexion to the database. So if your logging system enforces a database access for each user hit in order to record this information, this will just break the HTML cache proxy and the overall performance of Jahia. That is of course mainly for all the read accesses to a page. In such a case you will need to find a way to cache the hits logs in memory and to flush them in the database once a while (or to reuse the Apache or Tomcat front-end logs files)... Similar if you want to trace each logged user in order to see which pages he has the more consulted, how he is navigating in the sitemap, etc...
- Is there any specifications or guidelines that I should follow?
- I look at each page as some object to which various contents(big text, date etc) is added and persisted in the DB. I intend to make one more such object as page named as Audit Log to which I can add contents like user info and his actions. Is this the correct approach? If so how do i persist in the db so that it could be used as any other content object.
If you only plan to log the field modifications (as it is the case now), this is of course a bit more simplier but clearly more limited. Then which kind of information do you exactly want to log:
-all the information user by user (how much time he logged into the system, which was his last access, which searches he did on the system, how much time he spent on the site, in which mode, how much information he input, modifed, validate, etc...)
- relationships between pages (similar to Amazon, users on this page frequently went on this other page)
- hits (cf above = integration of a kind of small Webtrends tools inside Jahia. Other CMS integrates for example third party tools in order to do that: http://www.jahia.org/jahia/webdav/shared/temp/logs.jpg which allows the end-user to get informartion on a page per page basis (and not only global information for a site).
This Stats/logs/Events subject is quite large... So perhaps it would be great if could refine it a bit and/or make some fake photoshop screenshots of your future GUI in order to let us better understand what you exactly want to achieve in a first stage and then how to develop something as generic and as extendable as possible.
Regards
St�phane
