Using JMX Beans to Obtain Metrics

Each broker in the domain subscribes to events and statistics updates from every other broker and every agent in the domain. Each broker evaluates these events and statistics against its alarm definitions. If an alarm is fired, any connected NuoDB management client application (such as the REST service and NuoDB Manager) can receive notifications.

Even though alarm definitions are stored in the durable domain configuration and are therefore shared by all brokers, each broker observes statistics and event changes, and evaluates whether alarms should fire. It does so on its own, because under failure, other brokers may no longer be available.

Each broker maintains an MBean for the domain, for each database, for each process in the domain and for each peer.

This section describes the MBeans available in the broker and how to start a broker so that you can use a JMX client application such as JConsole or some other tool to access the information provided by those MBeans.

JMX MBeans is a preview feature.

Caution: NuoDB encourages you to use preview features in your development projects. However, the use of preview features in production is not supported.

See the following topics:

Description of NuoDB MBean Objects

Description of MBean Object Names

Viewing Notifications in JConsole

Viewing Metrics in JConsole

Specifying Java JMX Options for Starting Brokers