Database Reference
In-Depth Information
Monitoring
We discussed the Neo4j browser in
Chapter1
,
Installation and the First Query.
Neo4j
browser exposes the basic configuration of our server and database, but that is not enough
for the enterprise class systems, where we need detail monitoring, statistics, and options to
modify certain configurations at runtime without restarting the server.
Neo4j exposes JMX beans for advanced level of monitoring and management, which not
only exposes the overall health of our Neo4j server and database, but also provides certain
operations that can be invoked over live Neo4j instances and that too without restarting the
server. Most of the monitoring options exposed through JMX beans are only available with
the Enterprise version of Neo4j.
Note
For more information on JMX, refer to
http://www.oracle.com/technetwork/java/javase/
Java provides JConsole—
http://docs.oracle.com/javase/7/docs/technotes/guides/manage-
ment/jconsole.html
—which is packaged with standard JDK 7 distribution for viewing/
modifying/invoking the attributes or operations exposed by JMX beans. JConsole is also
leveraged for viewing the overall health of our system where it exposes the various
memory statistics such as heap/non-heap, threads JVM configurations, classes loaded in
VM, and active threads along with their current state.
Let's move forward and discuss the configurations required for enabling JMX beans via
JConsole for viewing the various monitoring attributes exposed by Neo4j in local and re-
mote mode.
