JAMON
JAMON
has been added to the Commutineer project to gather statistics on the running of the application.
It is presently available to all application environments, but only defaults to gathering monitoring data on the dev-postgres environment profile.
This article (despite being old) says its feasible to utilise this in a production context - however the performance degradation stats provided suggest that enabling JAMON in the app server will reduce its processing throughput to 1/60th of normal.
Enabling JAMON via Fixture
Even if the default setting for your environment is to disable monitoring, you can enable/disable it at anytime no matter what environment by simply visiting the URIs below
- http//{host}:{port}/fixture/monitoring?enable=true
or
- http//{host}:{port}/fixture/monitoring?disable=true
Viewing monitoring statistics
In order to view the statistics being gathered you would want to visit
- http//{host}:{port}/jamon/jamonadmin.jsp
The following monitors have been enabled:
NB: {JP, 20/10/2008} This monitoring view is NOT presently available to BETA or any deployment which uses the WAR. All grails command line started environments wire in the jamon.war file dynamically (see ${PROJECT_HOME}/scripts/Events.groovy). In a WAR based deployment we need to add to those deployments the
- Installing the jamon.war into ${JETTY_HOME}/webapps
- Updating the ${JETTY_HOME}/etc/jetty.xml as per here
I should also point out that in spite of the jamon.war not being present JAMON can still be enabled in those WAR'd environments and would collect data if enabled. Its just there isn't any way to view the data gathered.
Menu
Visiting the JAMON menu will give you links to the different monitoring views presenting the above data
- http//{host}:{port}/jamon/menu.jsp