Chat now with support
Chat with Support

Foglight for JMX 5.9.8 - User Guide

Foglight for JMX System Requirements Installing Foglight for JMX Managing JMX Agents Managing MBean Server Models Monitoring and Investigating JMX Data

Selecting MBean Attributes for Collection

After adding a Root Type and specifying the monitored instances, you can select and configure individual attributes for collection. You can reduce the amount of data collected by reducing the number of attributes selected for collection for each MBean type. The collection of available attributes depends on the instance availability (for example, All by root query).

To select and configure attributes for collection:
1
On the Server Model Editor dashboard, click the value displayed in the Collected Attributes column (for example, 4/11) for the root type you want to configure.
2
In the Collected Attributes dialog box that opens, select the check boxes for the attributes you want to collect.
3
Optional — If necessary, you can edit the attribute to change its storage type. Click Edit in the row for the attribute that you want to edit. For more information, see Step 7 of the procedure Adding a Root Type to an MBean Server Model .
4
Click OK.
The table updates to reflect any changes you have made to the attributes collected.

Exposing MBean Relationships

In addition to specifying the MBean attributes to collect, an MBean Server Model also gives structure to the MBeans you monitor. MBeans have implicit relationships to other MBeans, and the server model can be configured to make these relationships explicit. Exposing the relationship structure has two advantages: it defines a relationship structure that allows you to easily navigate between related MBeans in the dashboard, and it allows you to define parent/child relationships, where the health of a child affects the health of a parent.

An MBean relationship can be ignored, exposed as a reference relationship, or exposed as a containment relationship. References are usually made between objects that are siblings. Containing relationships are usually made between parent and child objects. Containment is useful when the health of the children impacts the health of the parent.

To expose MBean relationships:
1
On the Server Model Editor dashboard, click the value in the Relationships column (for example, 0/1) for the root type you want to configure.
2
In the Exposed Relationships dialog box that opens, click the text in the Relationship column of the attribute for which you want to expose a relationship.
3
In the list that opens, select one of the following options:
•
Ignore relationship
•
Expose as containment relationship
•
Expose as reference relationship
4
Click OK.
The table updates to reflect any changes you have made to the relationships.

Changing the Display Name of an MBean Type

The default display name for an MBean type is equivalent to its ObjectName. You can change the display name of the MBean type using groovy scripts. A groovy script can reference any collected property or ObjectName property.

To change the display name:
1
On the Server Model Editor dashboard, click the text Display Name column for a selected MBean type.
2
In the Display Name dialog box that opens, select the Use a groovy script to customize the display name as follows option.
3
Type the script in the box. For example:
•
To access a collected property with the name MyPropertyName, use the following: scope.get('_MyPropertyName', null).
•
To access an ObjectName property with the key ObjectNameKey, use the following: scope.get('ON_ObjectNameKey', null)
4
Optional — Click Property Reference List to display a list of available properties that can be referenced in the script.
5
Click OK.

Removing an MBean Type

By removing an MBean type, you are reducing the amount of data collected. When you remove an MBean Type, the following occurs:

•
All collected instances of the selected type are deleted
•
All exposed relationships that contain the selected type are set to ignore
To remove an MBean type:
1
On the Server Model Editor dashboard, click the name of an MBean type that you want to remove.
2
In the list that opens, click Remove.
3
Read the warning. If you agree, click Remove.
 
* 
TIP: If you need to stop monitoring temporarily, you may want to set the monitored instances to “Do not monitor” instead of removing the type entirely. For more information, see “Define Server Model Instance Overrides for a JMX Agent” on page 8.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating