Monitoring
The escenic-admin
web application contains a number of
functions for monitoring various aspects of
Content Engine
performance:
-
Performance summary (see Performance Summary)
-
Top (see Top)
-
View JSP statistics (see View JSP Statistics)
The Content Engine also provides support for monitoring via the Java Monitoring and Management Console.
In addition, all the
Content Engine's
cache components are now JMX-enabled (JMX stands for Java
Management Extensions). This means that you can use any JMX
client (such as jconsole
, the Java Monitoring and
Management Console bundled with the Java runtime) to monitor cache
activity.
If you use the /usr/local/bin/ece
script to start and
stop the
Content Engine
(recommended, see
Install
the ece Script), then you can enable and configure JMX support
by setting the following parameters in
/etc/escenic/engine/ece.conf
:
enable_remote_monitoring
-
Set to 1 to enable JMX.
remote_monitoring_port
-
Specify the number of the port you want to use for monitoring the Content Engine.
If you do not use the /usr/local/bin/ece
script, then
you should set the corresponding Java system parameters
(com.sun.management.jmxremote
and
com.sun.management.jmxremote.port
). On Java 6 JMX is
enabled by default, so com.sun.management.jmxremote
can
be omitted.
When you run the JMX client you will need to enter the name or IP address
of the host on which the
Content Engine
is running and the number of the remote monitoring port you are using. If
you use jconsole
, then you will find two
Content Engine-related
namespaces on the MBeans tab:
com.escenic.cache
-
This contains attributes and statistics for all Content Engine caches.
com.escenic.jvm
-
This contains Content Engine-related JVM statistics.