After you start Mongoose you can see output like below:

2016-06-24T07:08:39,506 I LogUtil              main                           Logging subsystem is ↩
   configured successfully
2016-06-24T07:08:39,612 I                      main                           Configuration paramet↩
   ers:
+--------------------------------+----------------------------------------------------------------+
| Key                            | Value                                                          |
+--------------------------------+----------------------------------------------------------------+
| item.type                      | data                                                           |
| load.type                      | create                                                         |
| load.threads                   | 1                                                              |
| load.limit.count               | 0                                                              |
| load.limit.time                | 0s                                                             |
| run.mode                       | standalone                                                     |
| run.version                    | 2.3.0                                                          |
| run.id                         | 2016.06.24.07.08.38.448                                        |
| storage.type                   | http                                                           |
+--------------------------------+----------------------------------------------------------------+
2016-06-24T07:08:39,614 I ScenarioRunner       main                           Using the scenario fr↩
   om the file "/home/kurila/work/mongoose/mongoose-2.3.0/scenario/default.json"
2016-06-24T07:08:39,850 I HttpBucketHelper     main                           Bucket "mongoose-2016↩
   .06.24.07.08.39.730" created
2016-06-24T07:08:39,895 I LoadExecutorBase     main                           0-S3-Create-1x1: will↩
   use "newDataItemSrc<BasicHttpData>" as an item source
2016-06-24T07:08:39,905 I LoadJob              main                           Start the job "0-S3-C↩
   reate-1x1"
2016-06-24T07:08:39,923 I LoadExecutorBase     0-S3-Create-1x1                count=(0/0); duration↩
   [us]=(0/0/0); latency[us]=(0/0/0); TP[op/s]=(0.000/0.000); BW[MB/s]=(0.000/0.000)
2016-06-24T07:08:49,942 I LoadExecutorBase     0-S3-Create-1x1                count=(1980/0); durat↩
   ion[us]=(4391/3901/48705); latency[us]=(1050/151/25281); TP[op/s]=(219.031/184.341); BW[MB/s]=(↩
   219.031/184.341)
2016-06-24T07:08:59,943 I LoadExecutorBase     0-S3-Create-1x1                count=(4391/0); durat↩
   ion[us]=(4226/3876/48705); latency[us]=(977/219/25281); TP[op/s]=(230.412/220.435); BW[MB/s]=(2↩
   30.412/220.435)
2016-06-24T07:09:09,944 I LoadExecutorBase     0-S3-Create-1x1                count=(6841/0); durat↩
   ion[us]=(4162/3870/48705); latency[us]=(907/154/25281); TP[op/s]=(235.291/235.836); BW[MB/s]=(2↩
   35.291/235.836)
2016-06-24T07:09:19,945 I LoadExecutorBase     0-S3-Create-1x1                count=(9344/0); durat↩
   ion[us]=(4112/3844/48705); latency[us]=(851/154/3537); TP[op/s]=(239.031/244.870); BW[MB/s]=(23↩
   9.031/244.870)
...
								

There is a table of some key configuration parameters in the beginning which are loaded from the default configuration file and overriden with CLI arguments:

• item.type: the default item type to use (container/data/token)
• load.type: the default load type to use (create/read/update/delete)
• load.threads: the default concurrency level to use
• load.limit.count: the default maximum count of the items to process (create/read/etc), 0 means no limit
• load.limit.time: the default load job time limit, 0 means no limit
• run.mode: the run mode (standalone/wsmock/server/client/webui)

After several initialization statements Mongoose starts reporting its progress every 10 seconds. Progress information is printed with the following layout:

<TIMESTAMP> <LEVEL> <CLASS> <LOAD_JOB_NAME>↩
count=(<SUCCESS>/<FAIL>);↩
duration[us]=(<AVG>/<MIN>/<MAX>);↩
latency[us]=(<AVG>/<MIN>/<MAX>);↩
TP[op/s]=(<AVG>/<AVG_LAST>);↩
BW[MB/s]=(<AVG>/<AVG_LAST>)
						

<TIMESTAMP> <LEVEL> <CLASS> <LOAD_JOB_NAME>↩
n=(<SUCCESS>/<FAIL>);↩
t[s]=(<JOB_TIME>/<DURATION_SUM>)↩
size=(<SIZE>);↩
TP[op/s]=(<AVG>/<AVG_LAST>);↩
BW[MB/s]=(<AVG>/<AVG_LAST>)↩
dur[us]=(<AVG>/<MIN>/<MAX>);↩
lat[us]=(<AVG>/<MIN>/<MAX>)
						

The summary metrics statement has a bit different metrics layout:

count=(<SUCCESS>/<FAIL>);↩
duration[us]=(<AVG>/<MIN>/<LOQ>/<MED>/<HIQ>/<MAX>);↩
latency[us]=(<AVG>/<MIN>/<LOQ>/<MED>/<HIQ>/<MAX>);↩
TP[op/s]=(<AVG>/<AVG_LAST>);↩
BW[MB/s]=(<AVG>/<AVG_LAST>)
						

n=(<SUCCESS>/<FAIL>);↩
t[s]=(<JOB_TIME>/<DURATION_SUM>)↩
size=(<SIZE>);↩
TP[op/s]=(<AVG>/<AVG_LAST>);↩
BW[MB/s]=(<AVG>/<AVG_LAST>)↩
dur[us]=(<AVG>/<MIN>/<LOQ>/<MED>/<HIQ>/<MAX>);↩
lat[us]=(<AVG>/<MIN>/<LOQ>/<MED>/<HIQ>/<MAX>)
						

The tool saves rich logging information about the events and performance metrics. The particular path for the logs for every run may be determined as log/<RUN_ID>. The directory contains a subset of the following files:

• 3rparty.log (optional, created when needed only)

  Third party libraries logging goes here

• config.log (available since v1.0.0)

  Effective run configuration. In case a run was restarted or resumed several times, the log file contains several configurations

• errors.log

  The file contains error and warning messages

• items.csv

  The file contains information about processed data items with the entries pattern:

  <ITEM_PATH>,<ITEM_RING_OFFSET>,<ITEM_SIZE>,<RING_LAYER_#>/<UPDATED_RANGES_MASK>

  This file is without a header line because some users shuffle it.

• messages.log

  The file contains Mongoose internal log messages.

• perf.avg.csv (optional, created by Mongoose ≥ 0.8)

  The file contains periodic performance metrics dumps. The header line describes the content:

  Version < 2.4.0	Version ≥ 2.4.0
  DateTimeISO8601, LoadId, TypeAPI, TypeLoad, CountConn, CountNode, CountLoadServer, CountSucc, CountFail, DurationAvg[us], DurationMin[us], DurationMax[us], LatencyAvg[us], LatencyMin[us], LatencyMax[us], TPAvg[op/s], TPLast[op/s], BWAvg[MB/s], BWLast[MB/s]	DateTimeISO8601, LoadId, TypeAPI, TypeLoad, CountConn, CountNode, CountLoadServer, CountSucc, CountFail, Size, JobDuration[s], DurationSum[s], TPLast[op/s], TPAvg[op/s], BWAvg[MB/s], BWLast[MB/s], DurationAvg[us], DurationMin[us], DurationMax[us], LatencyAvg[us], LatencyMin[us], LatencyMax[us]

• perf.sum.csv

  The file contains summary performance information calculated at the end of the run. The header line describes the content:

  Version < 2.4.0	Version ≥ 2.4.0
  DateTimeISO8601, LoadId, TypeAPI, TypeLoad, CountConn, CountNode, CountLoadServer, CountSucc, CountFail, DurationAvg[us], DurationMin[us], DurationLoQ[us], DurationMed[us], DurationHiQ[us], DurationMax[us], LatencyAvg[us], LatencyMin[us], LatencyLoQ[us], LatencyMed[us], LatencyHiQ[us], LatencyMax[us], TPAvg[op/s], TPLast[op/s], BWAvg[MB/s], BWLast[MB/s]	DateTimeISO8601, LoadId, TypeAPI, TypeLoad, CountConn, CountNode, CountLoadServer, CountSucc, CountFail, Size, JobDuration[s], DurationSum[s], TPAvg[op/s], TPLast[op/s], BWAvg[MB/s], BWLast[MB/s], DurationAvg[us], DurationMin[us], DurationLoQ[us], DurationMed[us], DurationHiQ[us], DurationMax[us], LatencyAvg[us], LatencyMin[us], LatencyLoQ[us], LatencyMed[us], LatencyHiQ[us], LatencyMax[us]

• perf.trace.csv

  The file contains detailed performance metrics per data item processed. The entry pattern is described by header:

  Thread,
  TargetNode,
  ItemId,
  ItemSize,
  StatusCode,
  ReqTimeStart[us],
  RespLatency[us],
  DataLatency[us],
  Duration[us]

The result code in the perf.trace.csv file may have one of the values below