- 4 minutes to read

Configuring the Nodinite JMX Monitoring Agent

Note

This guide explains how to use Remote Configuration to add a JMX Gateway, configure Application Hosts, and set CPU threshold and Heap Size monitoring for the Nodinite JMX Monitoring Agent.

Note

Before any monitoring and Remote Configuration can be performed, you must first install the Nodinite JMX Monitoring Agent and create a Monitoring Agent Configuration.

Remote Configuration

As a Nodinite Administrator, click the Configuration button to open the Remote Configuration dialog for the agent.

Remote Configuration button
Example of the Configuration button in the Monitoring Agent Configuration administration page.

Many specific changes can also be made directly on the Resource by using the Action button if the Monitor View has Remote Actions enabled.

Resources per host are grouped by Application and then by Category using the value from the Name field. Read more about Applications here:

Application filter
Example of the Application filter used to group JMX resources by Application.

Step 1: Configure JMX Monitoring

There is a graphical user interface to remotely configure the agent. When you finish, click Save to apply the changes.

JMX tab

In the JMX tab, add the Nodinite Spring Boot JMX Gateway and the JVM Application Hosts to monitor.

You can add one or more JMX Gateways. Each instance to use is one entry in the list.

Add JMX Gateway
Example of adding a JMX Gateway entry.

  • Enabled - When checked, JMX monitoring for this JMX Gateway is active.
  • Name - The name of this Nodinite JMX Gateway.
  • Address - The address to the JMX Gateway.
  • Application Hosts - The list of JVM Application Hosts to monitor.

Add Application Host
Example of adding an Application Host for monitoring.

Basic tab

In the Basic tab, set the essential properties required to monitor the JVM Application.

Basic Tab
Example of the Basic tab for a JVM Application Host.

  • Display Name - The name of this JMX monitoring configuration.
  • Address - The address of the host.
  • Port - The JMX Remote port.

Heap Size tab

In the Heap Size tab, set the Heap Size threshold values used for monitoring memory.

Heap Size Tab
Example of Heap Size threshold settings.

  • Enabled - Whether the Heap Size threshold should be used.
  • Error Threshold % - The minimum amount of free heap in percent before an Error alert is raised.
  • Warning Threshold % - The minimum amount of free heap in percent before a Warning alert is raised.
  • Duration - The time in seconds for the monitoring state before triggering the alert.

CPU tab

In the CPU tab, set the CPU threshold values used for monitoring.

CPU Tab
Example of CPU threshold settings.

  • Enabled - When checked, CPU monitoring is enabled.
  • Error Threshold % - When the CPU usage has been over this threshold, an Error is raised.
  • Warning Threshold % - When the CPU usage has been over this threshold, a Warning is raised.
  • Duration - The time in seconds for the monitoring state before triggering the alert.

Settings tab

In the Settings tab, configure Environment, Debug, and Culture Information for the JMX Gateway.

Settings tab
Example of the Settings tab for configuring Environment, Debug, and Culture Information.

  • Environment - Set the name of the target environment, for example DEV, TEST, QA, or PROD.
  • Debug - Enable additional logging for troubleshooting when required.
  • Culture Information - Set how date and time values are returned by the agent.

Step 2: Add Agent to Nodinite Instance

  1. In the Nodinite Administration, add a new Monitoring Agent Configuration. For detailed guidance, see Add or Manage Monitoring Agent.
  2. Name the configuration.
  3. Set the Service URI to: http://localhost:51010/api
  4. Set the X-API-KEY to 71B32996-908E-4690-B63E-E5018FD4A3B4
  5. Click Save.

Enable JMX monitoring in Boomi

If you intend to monitor a Boomi Atom, follow the steps below.

On each Atom, repeat: Properties > Advanced.

  • Add JMX Remote Authentication.
  • Add and configure JMX Remote Port - 5002.
  • Configure JMX Remote SSL as required.

Restart the Atom after applying the changes.

Save

When done, make sure to click Save to save pending changes.

Save buttons
Example of the Save button used to apply JMX configuration changes.

Add JMX Monitoring Agent Configuration

After the successful installation of the Nodinite JMX Monitoring Agent, you must provide Nodinite with connection details so the Monitoring Service knows there is a new agent available.

No monitoring or other configuration of the Nodinite JMX Monitoring Agent can be performed before the steps outlined below have been executed.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration. Connection information is available in the README.txt file in the installation folder.
  2. Use the Remote Configuration feature to configure the agent. This is detailed at the beginning of this user guide.
  3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Nodinite JMX Monitoring Agent according to business needs. To learn more, see Add or manage Monitor View.
  4. Fine-tune specific settings directly on Resources using Remote Actions.

Frequently asked questions

For additional troubleshooting help, refer to the Troubleshooting guide.

Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
JMX Monitoring Agent

Update
Monitoring Agents
Applications