bc28580_.htm |
Last updated Friday, 21 July 2017Information is written to the JSON publication for message flow accounting and statistics data.
Snapshot data is used for performance analysis, and is published as retained and not persistent. Snapshot data is produced every 20 seconds, and you can view it in the web user interface to help you analyze the performance of your message flows. If statistics collection is started through the web user interface, statistics data is emitted in JSON format in addition to any other formats that are already being emitted.
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 is registered anywhere in the network. They can also be collected by more than one subscriber.
One JSON publication is generated for each message flow that is producing data for the time period that you choose. For example, if MessageFlowA and MessageFlowB are both producing archive data over a period of 60 minutes, both MessageFlowA and MessageFlowB produce a JSON 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 JSON publication have the following identifiers:
The tables provided here describe the contents of each of these folders.
The following table describes the general accounting and statistics information, created in folder WMQIStatisticsAccounting.
| Field | Data type | Details |
|---|---|---|
| RecordType | Character | Type of output, one of:
|
| RecordCode | Character | Reason for output, one of:
|
| NumberOfThreads | Numeric | Number of thread statistics subfolders in WMQIStatisticsAccounting folder |
| NumberOfNodes | Numeric | Number of node statistics subfolders in WMQIStatisticsAccounting folder |
The following table describes the message flow statistics information, created in folder MessageFlow.
| Field | Data type | Details |
|---|---|---|
| BrokerLabel | Character |
Broker name |
| BrokerUUID | Character |
Broker universal unique identifier |
| ExecutionGroupName | Character |
Integration server name |
| ExecutionGroupUUID | Character |
Integration server universal unique identifier |
| MessageFlowName | Character |
Message flow name |
| StartDate | Character | Interval start date |
| StartTime | Character | Interval start time |
| EndDate | Character | Interval end date |
| EndTime | Character | Interval end time |
| TotalElapsedTime | Numeric | Total elapsed time spent processing input messages (microseconds) |
| MaximumElapsedTime | Numeric | Maximum elapsed time that is spent processing an input message (microseconds) |
| MinimumElapsedTime | Numeric | Minimum elapsed time that is spent processing an input message (microseconds) |
| TotalCPUTime | Numeric | Total processor time spent processing input messages (microseconds) |
| MaximumCPUTime | Numeric | Maximum processor time that is spent processing an input message (microseconds) |
| MinimumCPUTime | Numeric | Minimum processor time that is spent processing an input message (microseconds) |
| CPUTimeWaitingForInputMessage | Numeric | Total processor time spent waiting for input messages (microseconds) |
| ElapsedTimeWaitingForInputMessage | Numeric | Total elapsed time that is spent waiting for input messages (microseconds) |
| TotalInputMessages | Numeric | Total number of messages processed TotalInputMessages records only those messages that are propagated from input node terminals. |
| 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 |
| TotalNumberOfMQErrors | Numeric | Number of MQGET errors (MQInput node) or web
services errors (HTTPInput node) For example, a conversion error occurs when the message is got from the queue. |
| TotalNumberOfMessagesWithErrors | Numeric | Number of messages that contain errors These errors include exceptions that are thrown downstream of the input node, and errors that are detected by the input node after it successfully retrieves the message from the queue, but before it propagates it to the output terminal (for example, a format error). TotalNumberOfMessagesWithErrors can include messages that are not included in TotalInputMessages. |
| TotalNumberOfErrorsProcessingMessages | Numeric | Number of errors when processing a message |
| TotalNumberOfTimeOutsWaitingForRepliesToAggregateMessages | Numeric | Number of timeouts when processing a message (AggregateReply node only) |
| TotalNumberOfCommits | Numeric | Number of transaction commits |
| TotalNumberOfBackouts | Numeric | Number of transaction backouts |
| AccountingOrigin | Character (maximum 32) | Accounting origin |
The following table describes the thread statistics information for each individual thread, created in folder ThreadStatistics.
| Field | Data type | Details |
|---|---|---|
| Number | Numeric | Relative thread number in pool |
| TotalNumberOfInputMessages | Numeric | Total number of messages that are processed by a thread |
| TotalElapsedTime | Numeric | Total elapsed time spent processing input messages (microseconds) |
| TotalCPUTime | Numeric | Total processor time spent processing input messages (microseconds) |
| CPUTimeWaitingForInputMessage | Numeric | Total processor time spent waiting for input messages (microseconds) |
| ElapsedTimeWaitingForInputMessage | Numeric | Total elapsed time that is 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 following table describes the node statistics information for each individual node, created in folder NodesStatistics.
| 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 processor time spent processing input messages (microseconds) |
| MaximumCPUTime | Numeric | Maximum processor time spent processing input messages (microseconds) |
| MinimumCPUTime | Numeric | Minimum processor time spent processing input messages (microseconds) |
| CountOfInvocations | Numeric | Total number of messages that are processed by this node |
| NumberOfInputTerminals | Numeric | Number of input terminals |
| NumberOfOutputTerminals | Numeric | Number of output terminals |
The following table 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:
|
| CountOfInvocations | Numeric | Total number of invocations |
Last updated Friday, 21 July 2017