All,

The Liferay core engineering team and the Sun engineering team are collaborating to implement more monitoring features and capabilities. We would like to invite the community to provide feedback on the new features and let us know your thoughts.

The following wiki articles describe the features:

http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/Liferay+Monitoring
http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/Liferay+MBeans+Object+Names+Proposal

We are shooting to bring the feature into 5.3 SE (sometime roughly mid to end of August). Our EE customers may see these features roughly in the same time line.

Cheers,

-m

My feeling is that web analytics is done and done well by third party tools already.

However if there were a way to look at past logged errors with a search and get stack traces with more info (ie user X clicked URL y), then my work on finding the source of problems reported in the past would be made infinitely easier.

The database connection monitoring sounds super useful. Would it be possible to monitor regardless of whether you're using the new database setup or the old jndi pool method? Would it include connections made by jackrabbit if you put the document library in your db too?