Monitor ActiveMQ Message Broker
Activemq sfAgent plugin provides metrics related to message traffic distribution and other internal transactions among the brokers.
Metrics collected by the plugin are organized across the following categories
- Broker stats: contain transactional data and metrics related to broker state
- Topic stats: provide metrics for analyzing internal transactions associated with each topic
- Queue stats: provide metrics for analyzing internal transactions associated with each queue
- JVM stats: contain all JVM related metrics like garbage collection details, memory pools, loaded/unloaded classes etc.
Activemq logger plugin collects general logs comprising state change and broker specific information generated by the activemq message broker.
The configurations given below apply only to the ActiveMQ message broker running on an instance.
Activemq Metric Plugin is based on Jolokia agent which requires JMX monitoring to be enable locally. Following property needs to be included during the start of activemq process
JCMD command must be installed in the machine
sfAgent section provides steps to install and automatically generate plugin configurations. User can also manually add the configuration shown below to
- name: activemq
- name: activemq-log
log_path: <..activemq logpath..>
Parameters required in metrics plugin
process: Activemq process name (It should be part of java main class)
port: Broker Port
documentTypes: User can either leave this empty to collect all
documentTypes or mention specific
documentTypes to collect. Available options for plugin type activemq are
Logger plugin requires log path to be specified. Wildcard characters are supported
Viewing data and dashboards
Data collected by plugins can be viewed in SnappyFlow’s browse data section