Configuring BTM Monitoring for Linux in Apache Qpid Java Broker

eG Enterprise's Java Business Transaction Monitor (BTM) tracks individual transactions to Apache Qpid Java Broker in real-time, captures the time taken by each transaction, traces the journey of each transaction and the path it takes, and accurately pinpoints where and why a transaction slowed down. To collect BTM-related metrics, the eG agent connects to the Apache Qpid Java Broker via BTM.

To enable BTM metrics for Apache Qpid Java Broker component, first we need to specify the path of the BTM jar file location and then add the below line to the QPID_OPTS parameter where this parameter exists in installation location/bin/qpid-serverfile.

QPID_OPTS="-javaagent:<BTM jar location>”

For example, it should be

export JAVA=java \
JAVA_VM=-server \
JAVA_MEM="-Xmx512m -XX:MaxDirectMemorySize=1536m" \
JAVA_GC="-XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError" \
QPID_CLASSPATH="${QPID_LIBS}" \
QPID_RUN_LOG=2
QPID_OPTS="-Dcom.sun.management.jmxremote.port=16666
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.rmi.server.hostname=192.168.8.137
-javaagent:/opt/eGurkha/lib/javaagent_btmqpid_8080/eg_btm.jar"

Then restart the server with the command as

installation location/bin/qpid-server