IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Message flow statistics and accounting data

Message flow statistics and accounting data can be collected to record performance and operating details of one or more message flows.

Message flow statistics and accounting data captures dynamic information about the runtime behavior of a message flow. For example, it indicates how many messages are processed and how large those messages are, as well as processor usage and elapsed processing times. The statistical data is collected and recorded in a specified location when an event occurs, such as when a snapshot interval expires or when the integration server that you are collecting information about stops. You can configure the data to be published in a number of formats including JSON, XML, and csv (Comma Separated Values) format for use in spread sheets, or you can choose to have it reported to user trace.

You can publish statistics and accounting data to one of more of the following destinations:
You can use the statistics generated for the following purposes:

The integration server takes information about statistics and accounting from the operating system. On some operating systems, such as Windows and Linux, rounding can occur because the system calls that are used to determine the processor times are not sufficiently granular. This rounding might affect the accuracy of the data.

Data relating to the size of messages is not collected for WebSphere® Adapters nodes (for example, the SAPInput node), the FileInput node, the JMSInput node, or any user-defined input node that does not create a message tree from a bit stream.

You can start and stop data collection by modifying the statistics collection properties in the server.conf.yaml configuration file for the integration server. By default, data collection is turned off. For more information, see Starting and stopping the collection of message flow statistics and accounting data and Configuring an integration server by using the server.conf.yaml file.

You can activate data collection on your production and test systems. If you collect the default level of statistics (message flow), the effect on performance is minimal. However, collecting more data than the default message flow statistics can generate high volumes of report data that might affect performance slightly.

The information in the following topics will help you when you are planning your data collection:

The following topic contains reference information that you might find helpful when analyzing and tuning the performance of your message flows: Message flow accounting and statistics records.

Publishing data to MQ and MQTT

If you want to publish data to MQ or MQTT, ensure that the publication of events has been enabled and that the pub/sub broker has been configured before you start data collection. For more information, see Configuring the publication of event messages and Configuring the built-in MQTT pub/sub broker.

The topic for each message has the following structure:
  • For XML format:
    • For an MQ pub/sub broker:
      $SYS/Broker/integrationNodeName/StatisticsAccounting/integration_server_name
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/integrationNodeName/StatisticsAccounting/integration_server_name
  • For JSON format:
    • For an MQ pub/sub broker:
      $SYS/Broker/integrationNodeName/Statistics/JSON/integration_server_name
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/integrationNodeName/Statistics/JSON/integration_server_name
You can set up subscriptions for a specific integration server on a specific integration node. For example:
  • For XML format:
    • For an MQ pub/sub broker:
      $SYS/Broker/INODE/StatisticsAccounting/default
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/INODE/StatisticsAccounting/default
  • For JSON format:
    • For an MQ pub/sub broker:
      $SYS/Broker/INODE/Statistics/JSON/default
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/INODE/Statistics/JSON/default
You can also use wildcards in the subscriptions to broaden the scope of what is returned. For example, to subscribe to reports for all integration servers on all integration nodes, use the following values:
  • For XML format:
    • For an MQ pub/sub broker:
      $SYS/Broker/+/StatisticsAccounting/#
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/+/StatisticsAccounting/#
  • For JSON format:
    • For an MQ pub/sub broker:
      $SYS/Broker/+/Statistics/JSON/#
    • For an MQTT pub/sub broker:
      IBM/IntegrationBus/+/Statistics/JSON/#

ac19100_.htm | Last updated 2018-11-02 14:45:17