8.9. AMQ Broker の監視

手順

1. 実行中の Pod のリストを取得します。

   $ oc get pods
   
   NAME                 READY     STATUS    RESTARTS   AGE
   broker-amq-1-ftqmk   1/1       Running   0          14d

2. oclogsコマンドを実行します。

   $ oc logs -f broker-amq-1-ftqmk
   
   Running /amq-broker-71-openshift image, version 1.3-5
   INFO: Loading '/opt/amq/bin/env'
   INFO: Using java '/usr/lib/jvm/java-1.8.0/bin/java'
   INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)
   ...
   INFO | Listening for connections at: tcp://broker-amq-1-ftqmk:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
   INFO | Connector openwire started
   INFO | Starting OpenShift discovery agent for service broker-amq-tcp transport type tcp
   INFO | Network Connector DiscoveryNetworkConnector:NC:BrokerService[broker-amq-1-ftqmk] started
   INFO | Apache ActiveMQ 5.11.0.redhat-621084 (broker-amq-1-ftqmk, ID:broker-amq-1-ftqmk-41433-1491445582960-0:1) started
   INFO | For help or more information please see: http://activemq.apache.org
   WARN | Store limit is 102400 mb (current store usage is 0 mb). The data directory: /opt/amq/data/kahadb only has 9684 mb of usable space - resetting to maximum available disk space: 9684 mb
   WARN | Temporary Store limit is 51200 mb, whilst the temporary data directory: /opt/amq/data/broker-amq-1-ftqmk/tmp_storage only has 9684 mb of usable space - resetting to maximum available 9684 mb.

3. クエリーを実行して、ブローカーのMax Consumersを監視します。

   $ curl -k -u admin:admin http://console-broker.amq-demo.apps.example.com/console/jolokia/read/org.apache.activemq.artemis:broker=%22broker%22,component=addresses,address=%22TESTQUEUE%22,subcomponent=queues,routing-type=%22anycast%22,queue=%22TESTQUEUE%22/MaxConsumers
   
   {"request":{"mbean":"org.apache.activemq.artemis:address=\"TESTQUEUE\",broker=\"broker\",component=addresses,queue=\"TESTQUEUE\",routing-type=\"anycast\",subcomponent=queues","attribute":"MaxConsumers","type":"read"},"value":-1,"timestamp":1528297825,"status":200}