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

Creating JMX Agents

After installing the cartridge file, you must create and configure one or more JMX agents. These agents are responsible for collecting performance and monitoring data from the JMX application servers. JMX agents can be located either on the same machine as the resources they monitor, to collect data locally, or hosted on an Agent Manager on a remote machine, for remote collection. In both cases, an Agent Manager is required to collect the data from the agent.

 
* 
IMPORTANT: The JMX agent properties can also be accessed from the Agent Properties dashboard, but it is strongly recommended that you do not change these settings from this dashboard. All configuration should be done from the Application Servers Administration and JMX Administration dashboards.

You can create JMX Agents using the Connection URL through the Setup agent wizard on the Application Servers Administration dashboard. In this case, do not deploy the agent package or create agents through the Agent Status dashboard. The Setup agent wizard performs these tasks for you as part of the agent creation process. For more information, see Creating JMX Agents Using the Connection URL.

You can also create JMX Agents that use the JMX Discovery Agent to do Local Process Discovery. In order to use local process discovery, you must first create and activate the Discovery Agent through the Agent Status dashboard, then create the JMX Agent through the Setup agent wizard. For more information, see Creating JMX Agents Using Local Process Discovery.

Creating JMX Agents Using the Connection URL

To create a JMX Connection URL agent:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, clickMonitoring Agents > Setup agents...
3
Select JMX (Connection URL).
 
* 
NOTE: To create a group of agents with common configuration, see Creating JMX Agents Using Local Process Discovery .
4
On the Agent Host page of the Setup Agent by Connection URL wizard, select the Agent Manager to host the JMX agent.
 
* 
NOTE: To be eligible, an Agent Manager must be version compatible with the installed version of Foglight for JMX, or must already contain a JMX agent package that is version compatible (for example, a version 5.8.x JMX agent package).
5
Optional — Use the Connection Info Assistant to generate the Service URL needed to connect with the MBean server you want to monitor.
a
Click Connection Info Assistant.
b
In the Connection Info Assistant dialog box, select a connection type from the list.
 
* 
NOTE: The appearance of the dialog box changes depending on the connection type you select from the list.
For example, select JMX RMI (JBoss 7, Glassfish, Tomcat, Resin) to configure a generic platform MBean server connection. The dialog box refreshes. Host and Port appear in the list of properties.
c
Click the Value field for the property you want to edit and type a new value.
d
After updating the property values, click OK to close the dialog box.
The Connection Info Assistant closes, returning you to the MBean Server Connection page. Continue with Step 7.
6
On the MBean Server Connection page, specify the information required by the agent in order for it to connect to the MBean server you want to monitor.
In the Service URL box, type the service URL of the MBean server. For example:
service:jmx:rmi://{hostname}/jndi/rmi://{hostname}:{port}/jmxrmi
where {hostname} and {port} are specific to the MBean server you have chosen.
 
* 
TIP: If you are uncertain of the exact URL, use the Connection Info Assistant to build it for you. See Step 5 for details.
Depending on the properties specified, the Classpath and Environment Variables values may update automatically.
 
* 
NOTE: In some cases, you may need to enable remote access to an application server's MBean Server in order to collect data. For more information about how to change the remote configuration, see “Configuring Remote Access to MBean Servers” on page 7.
7
Optional — Update any of the following parameters:
•
To add any additional classpaths required to connect to the MBean server, type them in the Classpath box.
•
To specify any special environment variables required to allow the JMX agent to connect to the MBean server, type them in the Environment Variables box.
•
If your primary MBean server is not the platform server, type the port number to collect JVM data from the platform server in the JVM Data Port box.
•
To change the length of time the agent should wait before attempting to retry a connection, type a value in the Connection Retry Interval box. The default is 30 seconds.
Click Next.
8
On the Credentials page, select whether the agent requires credentials.
If the MBean server has security enabled and requires credentials to access it, click the Use credentials check box. If you have not already configured credentials for the JMX agent, you are prompted to do so. For more information about credentials, see the topic “Controlling System Access with Credentials” in the Foglight Administration and Configuration guide or help.
 
* 
NOTE: Local connections normally do not require credentials.
Click Next.
9
On the MBean Server Model page, select the server model to be used by this agent from the list provided. The server model specifies the MBean types that the agent collects metrics and attributes for, along with MBean relationship information.
Foglight for JMX includes server model templates for the following application servers: JBoss, Oracle AS, Tomcat, WebLogic, and WebSphere. You can use these server model templates as the basis for creating a server model. For more information, see Server Model Templates.
If no appropriate model exists or if you require a different MBean Server Model configuration, click Create New Model to create an MBean Server Model. For more information, see Creating MBean Server Models.
Click Next.
10
Optional — On the Server Group page, assign the monitored MBean server to a group. A group is typically used to represent the domain, cluster, or any other logical or administrative grouping, to which an MBean server belongs.
Do one of the following:
•
To use the default group, select the Use the default option.
•
To use an existing group, select the Assign the following Server Group option, then select the group from the list.
•
To create a new group, select the Assign the following Server Group option, and select Define new group from the list. In the Name box, type the name of the new group.
Click Next.
11
On the Review page, verify the agent configuration and specify a name for the agent.
In the Specify a name for your agent box at the bottom of the screen, type a name for the agent you are creating.
12
Click Finish.
A task for the agent creation appears in the Task History list. Use this list to track the progress of the task.
Next Steps:
•
After creating an agent, you can manage it from the Application Servers Administration dashboard. For more information, see Managing JMX Agents.
•
To create or manage server models, use the JMX Administration dashboard. For more information, see Managing MBean Server Models.
•
Use the JMX Explorer dashboard to view the MBean data. For more information, see Monitoring and Investigating JMX Data.
•
View data collected by the agent in the Application Servers > Monitor dashboard. See the Monitoring Application Servers User and Reference Guide or help for more information.

Creating JMX Agents Using Local Process Discovery

Before you can create a JMX agent using local process discovery, you must first deploy the JMX Discovery Agent package to create a Discovery Agent on the monitored host. After the Discovery Agent is running and collecting data, you can discover monitored processes on hosts.

Creating a JMX Agent using local process discovery is a three-step process. Complete the procedures in the following sections in order:

1
Deploying the JMX Discovery Agent Package
2
Creating and Activating a JMX Discovery Agent
3
Creating a JMX Agent Using Local Process Discovery .
 
* 
IMPORTANT: Local Process Discovery is supported only for Java processes running in Oracle JDK 1.6 or JRockit JDK 1.6. Earlier versions of the JDK and JDKs from other vendors are incompatible.

Deploying the JMX Discovery Agent Package

In addition to the JMX agent, Foglight for JMX also includes a JMX Discovery Agent that you can use to discover processes on a monitored host. If you intend to use local process discovery, you must first deploy the JMX Discovery Agent to the appropriate hosts.

The process for deploying the JMX Discovery Agent is the same as it was in previous versions.

To deploy a Discovery Agent package:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, click Deploy Agent Package.
3
In the HostSelector box, select the monitored host, and then click Next.
4
In the Agent Packages box, select the JMX Discovery Agent package: JMXDiscoveryAgent.gar, and then click Next.
5
View your selections in Summary, and then click Finish.

Next, create and activate the Discovery Agent.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating