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

Hi Michael,

It would be nice to have more monitoring features and capabilities in Liferay 5.3 SE.

add vote ...

Thanks

Jonas Yuan

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?

If you are in Tomcat, you can go after the Tomcat database pools by activating JMX for Tomcat. If you are using C3P0, you can also monitor the pool usage for C3P0.

For Jackrabbit, it would depend on how you configured the database connections. If you had Jackrabbit use a connection pool that's been declared in the JNDI resources of your app server, then yes you can monitor that already.

I have edited the portal-ext.properties to activate monitoring.

##
## Monitoring
##

#
# Set this to true to monitor portal requests.
#
monitoring.portal.request=true

#
# Set this to true to monitor portlet action requests.
#
monitoring.portlet.action.request=true

#
# Set this to true to monitor portlet event requests.
#
monitoring.portlet.event.request=true

#
# Set this to true to monitor portlet render requests.
#
monitoring.portlet.render.request=true

#
# Set this to true to monitor portlet resource requests.
#
monitoring.portlet.resource.request=true


##
## Spring
##

#
# Input a list of comma delimited Spring configurations. These will be
# loaded after the bean definitions specified in the contextConfigLocation
# parameter in web.xml.
#
# Note that there is a special case for hibernate-spring.xml and
# jpa-spring.xml. Even though both files are specified, only one will
# actually load at runtime based on the property "persistence.provider".
#
spring.configs=\
META-INF/base-spring.xml,\
\
META-INF/hibernate-spring.xml,\
META-INF/infrastructure-spring.xml,\
META-INF/management-spring.xml,\
\
META-INF/util-spring.xml,\
\
META-INF/jpa-spring.xml,\
\
META-INF/audit-spring.xml,\
META-INF/cluster-spring.xml,\
META-INF/editor-spring.xml,\
META-INF/jcr-spring.xml,\
META-INF/ldap-spring.xml,\
META-INF/messaging-core-spring.xml,\
META-INF/messaging-misc-spring.xml,\
META-INF/poller-spring.xml,\
META-INF/rules-spring.xml,\
META-INF/scheduler-spring.xml,\
META-INF/scripting-spring.xml,\
META-INF/search-spring.xml,\
META-INF/workflow-spring.xml,\
\
META-INF/counter-spring.xml,\
META-INF/document-library-spring.xml,\
META-INF/mail-spring.xml,\
META-INF/portal-spring.xml,\
META-INF/portlet-container-spring.xml,\
\
#META-INF/dynamic-data-source-spring.xml,\
#META-INF/shard-data-source-spring.xml,\
#META-INF/memcached-spring.xml,\
META-INF/monitoring-spring.xml,\
\
META-INF/ext-spring.xml


And now I can see te portal_statistics JMX MBeans and the portlet_statistics JMX MBeans through jmx-console but I don't know how to analize the information that I see. I mean what information can be useful for me from for example the ActionRequestPortletContainerManager MBean, RenderRequestPortletContainerManager, etc.

What does the names of these beans mean?

Thanks!!