Pre-requisites for Monitoring Apache Qpid Java Broker

Before attempting to manage and monitor Apache Qpid Java Broker, make sure that the following pre-requisites are fulfilled:

• Determine the correct port using which the target Apache Qpid Java Broker has to be managed in the eG admin interface.

• By default, the eG agent executes REST APIs on the target component to collect the required metrics. For the eG agent to execute the REST APIs, a user with monitoring privilege is required with the respective user credentials. The minimum user role can be “guest” by default.

• To enable the eG agent to collect JVM-related metrics, make sure the requirement for JVM monitoring detailed in the Configuring JVM Monitoring for Windows in Apache Qpid Java Broker and Configuring JVM Monitoring for Linux in Apache Qpid Java Broker topics are satisfied.

• By default, the eG agent cannot perform Java business transaction monitoring on a Apache Qpid Java Broker. For that, you need to enable the eG Java Business Transaction Monitor (BTM) on the Apache Qpid Java Broker. To know how to achieve this, refer to Configuring BTM Monitoring for Windows in Apache Qpid Java Broker and Configuring BTM Monitoring for Linux in Apache Qpid Java Broker topics.