Simulator: json output representation of the event statistics? #4670
Description
Should we consider printing out a json representation of the event statistics? like e.g.:
Simulation stopped early as all validators have been unbonded; nobody left to propose a block!
Event statistics:
/no-operation/failure => 1582
auth/deduct_fee/failure => 15
auth/deduct_fee/ok => 159
bank/multisend/failure => 22
bank/multisend/ok => 217
bank/send/failure => 242
bank/send/ok => 2379
beginblock/evidence => 151
beginblock/signing/missed => 565
beginblock/signing/signed => 2768
distr/set_withdraw_address/failure => 1312
distr/withdraw_delegator_reward/failure => 1190
distr/withdraw_delegator_reward/ok => 140
distr/withdraw_validator_commission/failure => 299
distr/withdraw_validator_commission/ok => 994
endblock/validatorupdates/added => 106
endblock/validatorupdates/kicked => 113
endblock/validatorupdates/updated => 842
gov/deposit/failure => 802
gov/deposit/ok => 1741
gov/submit_proposal/failure => 60
gov/submit_proposal/ok => 300
slashing/unjail/failure => 2483
staking/begin_redelegate/failure => 1944
staking/begin_redelegate/ok => 148
staking/create_validator/failure => 2018
staking/create_validator/ok => 106
staking/delegate/failure => 1479
staking/delegate/ok => 2910
staking/edit_validator/failure => 60
staking/edit_validator/ok => 63
GoLevelDB Stats
Compactions
Level | Tables | Size(MB) | Time(sec) | Read(MB) | Write(MB)
-------+------------+---------------+---------------+---------------+---------------
0 | 0 | 0.00000 | 0.06395 | 0.00000 | 5.99821
1 | 1 | 0.84860 | 0.02618 | 5.99821 | 0.84860
GoLevelDB cached block size 1273211
--- PASS: TestFullAppSimulation (30.89s)
PASS
ok github.com/cosmos/cosmos-sdk/simapp 30.936s
It might then be easier to parse them out if they need to be analyzed/optimized.