Configuring JBoss monitoring

The Monitoring Agent for JBoss offers a central point of management for your JBoss environment or application. The software provides a comprehensive means for gathering the information that is required to detect problems early and to prevent them. Information is standardized across the system. You can monitor multiple servers from a single console. By using the JBoss agent you can easily collect and analyze JBoss specific information.

Before you begin

Make sure that the system requirements for the JBoss agent are met in your environment. For the up-to-date system requirement information, see the Software Product Compatibility Reports (SPCR) for the JBoss agent .
Before you configure the JBoss agent , the JBoss server first must be configured by completing the following tasks.
1. Enable JMX MBean Server Connections .
2. Add a JBoss Server Management User .
3. Enabling Web/HTTP Statistic Collection . This procedure is for JBoss EAP version 7.x and WildFly versions 8.x, 9.x and 10.x.

About this task

The Managed System Name includes the instance name that you specify, for example,


instance_name : host_name : pc

, where pc is your two character product code. The Managed System Name is limited to 32 characters.

The instance name that you specify is limited to 28 characters minus the length of your host name. For example, if you specify JBoss as your instance name, your managed system name is JBoss:hostname:JE .

Note: If you specify a long instance name, the Managed System name is truncated and the agent code does not display correctly.

The JBoss agent is a multiple-instance agent. You must create an agent instance for each JBoss server you monitor, and start each agent instance manually.

Procedure

Configure the agent on Windows systems by using the IBM Performance Management window or by using the silent response file.
- Configuring the agent on Windows systems .
- Configuring the agent by using the silent response file .
Configure the agent on Linux systems by running command line script and responding to prompts, or by using the silent response file.
- Configuring the agent by responding to prompts .
- Configuring the agent by using the silent response file .

What to do next

Log in to the Cloud App Management user interface to view monitoring data. For more information, see Starting the Cloud App Management UI.

If you are unable to view the data in the agent dashboards, first check the server connection logs and then the data provider logs. The default paths to these logs are as follows.

/opt/ibm/apm/agent/logs
C:\IBM\APM\TMAITM6_x64\logs