Output formats for message flow accounting and statistics data

When you collect message flow statistics, you can choose the output destination for the data:

Statistics data is written to the specified output location in the following circumstances:

User trace

You can specify that the data collected is written to the user trace log. The data is written even if trace is currently switched off. The default output destination for accounting and statistics data is the user trace log. The data is written to one of the following locations:
  • On Windows systems, if the broker workpath has been set using the -w option of the mqsicreatebroker command, data is written to workpath\log. If the broker workpath has not been specified, data is written to install_dir\log, where install_dir is the directory in which WebSphere Event Broker is installed.

  • On UNIX systems, data is written to /var/wmqi/log.

  • On Linux systems, data is written to /var/wmqi/log.

  • On z/OS systems, data is written to /component_filesystem/log.

XML publication

You can specify that the data collected is published. The publication message is created in XML format and is available to subscribers registered in the broker network that subscribe to the correct topic.

The topic on which the data is published has the following structure:

$SYS/Broker/brokerName/StatisticsAccounting/recordType/executionGroupLabel/messageFlowLabel
The variables correspond to the following values:
brokerName
The name of the broker for which statistics are collected.
recordType
Set to Snapshot or Archive, depending on the type of data to which you are subscribing. Alternatively, use # to register for both snapshot and archive data if it is being produced.
executionGroupLabel
The name of the execution group for which statistics are collected.
messageFlowLabel
The label on the message flow for which statistics are collected.

Subscribers can include filter expressions to limit the publications that they receive. For example, they can choose to see only snapshot data, or to see data collected for a single broker. Subscribers can specify wild cards (+ and #) to receive publications that refer to multiple resources.

The following examples show the topic with which a subscriber should register to receive different sorts of data:
  • Register the following topic for the subscriber to receive data for all message flows running on BrokerA:

    $SYS/Broker/BrokerA/StatisticsAccounting/#

  • Register the following topic for the subscriber to receive only archive statistics relating to a message flow Flow1 running on execution group Execution on broker BrokerA:

    $SYS/Broker/BrokerA/StatisticsAccounting/Archive/Execution/Flow1

  • Register the following topic for the subscriber to receive both snapshot and archive data for message flow Flow1 running on execution group Execution on broker BrokerA

    $SYS/Broker/BrokerA/StatisticsAccouting/#/Execution/Flow1

Message display, test and performance utilities SupportPac (IH03) can help you with registering your subscriber.

SMF

On z/OS, you can specify that the data collected is written to SMF. SMF supports the collection of data from multiple subsystems, and you might therefore be able to synchronize the information recorded. When you want to interpret the information recorded, you can use any utility program that processes SMF records. Accounting and statistics data uses SMF type 117 records.

Related concepts
Message flows overview
Related tasks
Collecting message flow accounting and statistics data
Developing message flows
Related reference
mqsichangeflowstats command
Message flow accounting and statistics data