MQ Configuration, Status, Event, Statistics and Trace
Queue manager metrics are collected using a combination of PCF commands for object configuration, and standard MQ messaging API’s for event, accounting, statistics and activity trace messages.
The following table is a list of all the data items that are regularly collected from a queue manager:
Object Type | Information Collected |
---|---|
Alias queue | All attributes |
Local queue | All attributes |
Remote queue | All attributes |
Model queue | All attributes |
Server connection channels | All attributes |
Sender channels | All attributes |
Receiver channels | All attributes |
Cluster sender channels | All attributes |
Cluster receiver channels | All attributes |
Requester channels | All attributes |
Server channels | All attributes |
Channel events 1, 2 | All attributes |
Command events 1, 2 | All attributes |
Performance events 1, 2 | All attributes |
Pubsub events 1, 2 | All attributes |
Queue manager events 1, 2 | All attributes |
Logger events 1, 2 | All attributes |
Accounting events 1, 2 | All attributes |
Config events 1, 2 | All attributes |
Statistics events 1, 2 | All attributes |
Activity Trace 1, 2 | All attributes |
Table 1: Object types
1 The queue manager must be configured to generate these before they can be collected.
2 A maximum of 5000 events per queue .manager are stored in memory in a FIFO manner. This data can be archived as it’s pushed out of the cache for longer periods when coupled with the archiving product extension.