XML publication for message flow accounting and statistics data

This topic describe the information that is written to the XML publication for message flow accounting and statistics data. The data is created within the folder WMQIStatisticsAccounting, which contains subfolders that provide more detailed information. All folders are present within the publication even if you set current data collection parameters to specify that the relevant data is not collected.

Snapshot data is used for performance analysis, and is published as retained and non-persistent. Archive data is used for accounting where an audit trail might be required, and is published as retained and persistent. All publications are global and can be collected by a subscriber that has registered anywhere in the network. They can also be collected by more than one subscriber.

One XML publication is generated for each message flow that is producing data for the time period you have chosen. For example, if MessageFlowA and MessageFlowB, are both producing archive data over a period of 60 minutes, both MessageFlowA and MessageFlowB will produce an XML publication every 60 minutes.

If you are concerned about the safe delivery of these messages, for example for charging purposes, use a secure delivery mechanism such as WebSphere MQ.

The folders and subfolders in the XML publication have the following identifiers:

The tables provided here describe the contents of each of these folders in the order listed above.

The table below describes the general accounting and statistics information, created in folder WMQIStatisticsAccounting.

Field Data type Details
RecordType Character Type of output, one of:
  • Archive
  • Snapshot
RecordCode Character Reason for output, one of:
  • MajorInterval
  • Snapshot
  • Shutdown
  • ReDeploy
  • StatsSettingsModified

The table below describes the message flow statistics information, created in folder MessageFlow.

Field Data type Details
BrokerLabel

Character
(maximum 32)

Broker name
BrokerUUID

Character
(maximum 32)

Broker universal unique identifier
ExecutionGroupName

Character
(maximum 32)

Execution group name
ExecutionGroupUUID

Character
(maximum 32)

Execution group universal unique identifier
MessageFlowName

Character
(maximum 32)

Message flow name
StartDate Character

Interval start date
(YYYY-MM-DD)

StartTime Character

Interval start time
(HH:MM:SS:NNNNNN)

EndDate Character

Interval end date
(YYYY-MM-DD)

EndTime Character

Interval end time
(HH:MM:SS:NNNNNN)

TotalElapsedTime Numeric Total elapsed time spent processing input messages (microseconds)
MaximumElapsedTime Numeric Maximum elapsed time spent processing an input message (microseconds)
MinimumElapsedTime Numeric Minimum elapsed time spent processing an input message (microseconds)
TotalCPUTime Numeric Total CPU time spent processing input messages (microseconds)
MaximumCPUTime Numeric Maximum CPU time spent processing an input message (microseconds)
MinimumCPUTime Numeric Minimum CPU time spent processing an input message (microseconds)
CPUTimeWaitingForInputMessage Numeric Total CPU time spent waiting for input messages (microseconds)
ElapsedTimeWaitingForInputMessage Numeric Total elapsed time spent waiting for input messages (microseconds)
TotalInputMessages Numeric Total number of messages processed
TotalSizeOfInputMessages Numeric Total size of input messages (bytes)
MaximumSizeOfInputMessages Numeric Maximum input message size (bytes)
MinimumSizeOfInputMessages Numeric Minimum message input size (bytes)
NumberOfThreadsInPool Numeric Number of threads in pool
TimesMaximumNumberofThreadsReached Numeric Number of times the maximum number of threads is reached
TotalNumberOfMQErrors1 Numeric Number of MQGET errors (MQInput node)
TotalNumberOfMessagesWithErrors2 Numeric Number of messages that contain errors
TotalNumberOfErrorsProcessingMessages Numeric Number of errors processing a message
TotalNumberOfTimeOutsWaitingForRepliesToAggregateMessages Numeric Number of timeouts processing a message (AggregateReply node only)
TotalNumberOfCommits Numeric Number of transaction commits
TotalNumberOfBackouts Numeric Number of transaction backouts
AccountingOrigin Character (maximum 32) Accounting origin
Notes:
  1. For example, a conversion error occurs when the message is got from the queue.
  2. These include exceptions that are thrown downstream of the input node, and errors detected by the input node after it has successfully retrieved the message from the queue but before it has propagated it to the out terminal (for example, a format error).

The table below describes the thread statistics information, created in folder Threads.

Field Data type Details
Number Numeric Number of thread statistics subfolders within Threads folder

The table below describes the thread statistics information for each individual thread, created in folder ThreadStatistics, a subfolder of Threads.

Field Data type Details
Number Numeric Relative thread number in pool
TotalNumberOfInputMessages Numeric Total number of messages processed by thread
TotalElapsedTime Numeric Total elapsed time spent processing input messages (microseconds)
TotalCUPTime Numeric Total CPU time spent processing input messages (microseconds)
CPUTimeWaitingForInputMessage Numeric Total CPU time spent waiting for input messages (microseconds)
ElapsedTimeWaitingForInputMessage Numeric Total elapsed time spent waiting for input messages (microseconds)
TotalSizeOfInputMessages Numeric Total size of input messages (bytes)
MaximumSizeOfInputMessages Numeric Maximum size of input messages (bytes)
MinimumSizeOfInputMessages Numeric Minimum size of input messages (bytes)

The table below describes the node statistics information, created in folder Nodes.

Field Data type Details
Number Numeric Number of node statistics subfolders within Nodes folder

The table below describes the node statistics information for each individual node, created in folder NodesStatistics, a subfolder of Nodes.

Field Data type Details
Label Character Name of node (Label)
Type Character Type of node
TotalElapsedTime Numeric Total elapsed time spent processing input messages (microseconds)
MaximumElapsedTime Numeric Maximum elapsed time spent processing input messages (microseconds)
MinimumElapsedTime Numeric Minimum elapsed time spent processing input messages (microseconds)
TotalCPUTime Numeric Total CPU time spent processing input messages (microseconds)
MaximumCPUTime Numeric Maximum CPU time spent processing input messages (microseconds)
MinimumCPUTime Numeric Minimum CPU time spent processing input messages (microseconds)
CountOfInvocations Numeric Total number of messages processed by this node
NumberOfInputTerminals Numeric Number of input terminals
NumberOfOutputTerminals Numeric Number of output terminals

The table below describes the terminal statistics information, created in folder TerminalStatistics.

Field Data type Details
Label Character Name of terminal
Type Character Type of terminal, one of:
  • Input
  • Output
CountOfInvocations Numeric Total number of invocations
Related concepts
Message flows overview
Message flow accounting and statistics data
Related tasks
Developing message flows
Collecting message flow accounting and statistics data
Related reference
Message flow accounting and statistics details
Example of an XML publication for message flow accounting and statistics