You can use integration node and integration server configuration files (node.conf.yaml and server.conf.yaml) to view and modify the settings that control the collection of message flow accounting and statistics data.
You can modify the properties that have been set for message flow accounting and statistics data collection. For example, you can start collecting data for a new message flow that you have deployed to an integration server for which you are already collecting data. When you restart the integration server, the new settings that you have defined in the .yaml configuration file will come into effect.
You can configure the collection of snapshot data, archive data, or both, by setting properties in the Statistics section of the configuration file (node.conf.yaml or server.conf.yaml), as shown in the following example:Statistics:
# Application message flows will by default inherit Snapshot and Archive values set here
Snapshot:
#publicationOn: 'inactive' # choose 1 of : active|inactive, default inactive
# Also set Events.OperationalEvents.MQ|MQTT for outputFormat json,xml to be published to MQ/MQTT
#accountingOrigin: 'none' # choose 1 of : none|basic
#nodeDataLevel: 'none' # choose 1 of : none|basic|advanced
#outputFormat: 'usertrace' # comma separated list of : csv,bluemix,json,xml,usertrace
#threadDataLevel: 'none' # choose 1 of : none|basic
Archive:
#archivalOn: 'inactive' # choose 1 of : active|inactive, default inactive
# Also set Events.OperationalEvents.MQ|MQTT for outputFormat xml to be published to MQ/MQTT
#accountingOrigin: 'none' # choose 1 of : none|basic
#majorInterval: 60 # Sets the interval in minutes at which archive statistics are published
#nodeDataLevel: 'none' # choose 1 of : none|basic|advanced
#outputFormat: 'usertrace' # comma separated list of : csv,xml,usertrace
#threadDataLevel: 'none' # choose 1 of : none|basic
Configure the collection of accounting and statistics data for one or more active message flows by setting the statistics properties in the configuration file for your integration node or integration server: