After installation is complete, and the Lamaxu agent has been started, navigate to the logs directory and check the contents of the agent.log file. You should see activity indicating that data is being collected from each of the queue managers that you configured at step 6.
Data collection for a queue manager has started when the following lines can be found in the agent.log file. The example log entries below would normally be preceded by addition information such as date/time and the queue manager the log entries are for.
Example agent.log output
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting CHANNEL_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected CHANNEL_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting COMMAND_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected COMMAND_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting PERFM_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected PERFM_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting QMGR_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected QMGR_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting LOGGER_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected LOGGER_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting TRACE_ACTIVITY data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected TRACE_ACTIVITY data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting PUBSUB_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected PUBSUB_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting CONFIG_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected CONFIG_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting STATISTICS data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected STATISTICS data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting ACCOUNTING data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected ACCOUNTING data
2016-10-12 14:04:39 INFO Sweeper:179 - [MQ9TST data collector] - Finished collecting data from message broker: MQ9TST
If there are multiple queue managers defined then you will see additional repeated messages for each of them.
As the Lamaxu collects data from each configured queue manager in parallel, you may begin querying data as soon as collection is complete for at least one.