The options that you specify for message flow accounting and statistics collection determine what information is collected. You can configure the collection of snapshot data, archive data, or both.
An interval ends and restarts when any of the following events occur, to preserve the integrity of the data that has been collected prior to the event:
You can modify the statistics properties in the node.conf.yaml or server.conf.yaml files to specify snapshot data collection, archive data collection, or both. When you have updated the .yaml file, you must restart the integration node or server for the changes to take effect. The state of the statistics collection that is configured in the .yaml file is applied to all flows that are deployed when the integration server starts, and also to any additional flows that are deployed afterwards. For information about configuring an integration server or integration node by editing a .yaml file, see Configuring an integration server by using the server.conf.yaml file and Modifying an integration node. You can activate snapshot data collection while archive data collection is active. The data recorded in both reports is the same, but is collected for different intervals. If you activate both snapshot and archive data collection, be careful not to combine information from the two different reports, because you might count information twice.
You can view statistics data as it is generated by selecting the Statistics tab in the web user interface.
For information about how to configure the collection of snapshot or archive statistics, see Configuring the collection of message flow accounting and statistics data.