JMX Active Discovery

JMX Active Discovery is a LogicMonitor feature that automatically detects and monitors Java Management Extensions (JMX) objects on a device.

It can identify the following:

• All instances of a specified MBean.
• Instances filtered by specific attributes of a fully defined MBean.
• Multiple Java instances running on different ports. For each instance, it enumerates the available MBean objects.

This results in a structured array of discovered JMX objects across one or more Java Virtual Machines (JVMs), enabling streamlined monitoring in complex Java environments.

Requirements for Configuring JMX Active Discovery

To configure JMX Active Discovery, toggle the Enable Active Discovery switch. 
This enables LogicMonitor to automatically find the DataSource’s instances and the resources they apply to. For more information, see Active Discovery.

Parameters for JMX Active Discovery

You need to define key parameters that determine how LogicMonitor identifies and connects to JMX objects.

Configuring JMX Active Discovery

1. In LogicMonitor, navigate to More > Modules > My Module Toolbox.
2. Select Add > DataSource.
3. In the Info tab, provide the basic information.
   For more information, see DataSource Configuration.
4. In the Summary section, provide the following information:
   1. Collection Method—Select “JMX” from the dropdown menu. This defines how data is collected for the DataSource.
   2. Collection Schedule—Select an interval based on how frequently the monitored data updates. Use shorter intervals (for example, 1 minute) for rapidly changing or critical metrics. Longer intervals reduce system load on both the monitored resource and the Collector.
   3. Multi-Instance—Toggle the Multi-Instance switch to enable monitoring of multiple instances of an object. For example, multiple disks or volumes on a server.
   4. ERI Discovery—An optional script that runs once for each instance to assign external resource identifiers (ERIs).
   5. Enable Active Discovery—Toggle the Enable Active Discovery switch to enable LogicMonitor to automatically detect instances.
      
      Note: This option is available only when Multi-Instance switch is enabled.
5. Select Access Groups to assign access to the DataSource.
   For more information, see Access Groups for Modules.
6. In the AppliesTo field, enter AppliesTo scripting to determine which resources are associated with this DataSource. For more information, see AppliesTo Scripting Overview. 
7. In the Active Discovery section, provide the following information:
   1. Discovery Schedule—Select an option from the discovery schedule dropdown menu. Configure Active Discovery to run on a set schedule (for example, every 15 minutes, every hour, or once a day), or to run only when the host or DataSource is first applied to a resource or updated.
   2. Group Method—Select how instances are grouped after discovery using the Group Method dropdown menu.
      1. Manual—Manually organize instances into groups after discovery, or leave them permanently ungrouped.
      2. Regular Expression—Group instances based on pattern matching using regular expressions.
      3. Instance level property—Automatically create instance groups based on unique values of the selected instance-level property (ILP).
         For information, see Instance Groups. 
   3. (Optional) Disable Discovered Instances—Toggle the Disable Discovered Instances switch to place newly discovered instances in a disabled state by default. These instances move to the dynamic Unmonitored group and are not monitored until you enable them. This option is useful when you want to fine-tune datapoint thresholds before enabling monitoring to avoid unnecessary alerts.For more information, see Instance Groups.
   4. Automatically Delete Instances—Toggle the Automatically Delete Instances switch to remove instances from monitoring when Active Discovery no longer detects them. You can delete the instance immediately or retain its history for 30 days.
      
      Recommendation: Keep this option disabled if you want to continue receiving alerts for missing instances.
   5. Select “JMX” from the Discovery Method dropdown.
   6. In the JMX Path field, enter the path to the MBean object or attribute you want to discover. 
      The structure and type of the attribute specified in the JMX Path determines how instances are discovered:
      • Primitive type (string or integer) — The attribute’s value is returned as both the alias and the instance value.
      • Array — The array index is used as the alias, and each element is returned as a separate instance.
      • Map — The keys are used as aliases, and the values are returned as instance values.
        For example: To return the serverInfo value from the Catalina:type=Server MBean, use the following format: Catalina:type=Server:serverInfo
        This would return an instance value such as:  Apache Tomcat/5.5.25
        You can use this value in filtering.
   7. (Optional)In the Service URL field, enter the URL of the JMX server.
   8. In the Ports List field, enter a comma-separated list of ports to scan for JMX objects.
      
      
      Note:

      • Use ##WILDVALUE## to represent the discovered MBean object.
      • Use ##WILDVALUE2## to represent the discovered attribute value if port discovery is also in use.
   9. You can filter discovered instances based on ports, MBean paths, or attribute values. To add a filter do the following:
      1. Select Add Filter.
      2. In the Property Name field, enter ##WILDVALUE## or ##WILDVALUE2## if using port-based discovery.
      3. Select an Operator from the dropdown list.
      4. In the Value field, enter the value to filter against.
      5. (Optional) Enter a Comment to describe the filter purpose.
      6. Select Apply to save the filter.
         
   10. Select Save.

LogicMonitor now automatically discovers JMX objects across the specified Java instances, enabling monitoring of key performance metrics without manual setup.