(split task from #22 )
Now that nodeos maps it's warning to zap level, it's annoying to have them by default.
Previous suggestion: We should probably try to tweak it to have ERROR only
New suggestion: What if we took the most common "warning" logs and (in a nice hard-coded regex fashion), toned them down to "info" ?
This is open for discussion..
$ ./dfuseeos start
Starting dfuse for EOSIO with config file './dfuse.yaml'
Launching applications: abicodec,apiproxy,blockmeta,dashboard,dgraphql,eosq,eosws,fluxdb,merger,mindreader,node-manager,relayer,search-archive,search-indexer,search-live,search-router,trxdb-loader
Your instance should be ready in a few seconds, here some relevant links:
Dashboard: http://localhost:8081
Explorer & APIs: http://localhost:8080
GraphiQL: http://localhost:8080/graphiql
warn 2020-05-08T21:58:27.856 thread-0 controller.cpp:583 startup ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database (log_plugin/to_zap_log_plugin.go:53)
warn 2020-05-08T21:58:27.857 thread-0 controller.cpp:452 initialize_blockchai ] Initializing new blockchain with genesis state (log_plugin/to_zap_log_plugin.go:53)
Cannot find latest snapshot, will replay from blocks.log (nodeos/snapshot.go:153)
warn 2020-05-08T21:58:28.699 thread-0 platform_timer_accurac:64 compute_and_print_ti ] Checktime timer accuracy on this platform and hardware combination is poor; accuracy of subjective transaction deadline enforcement will suffer (log_plugin/to_zap_log_plugin.go:53)
warn 2020-05-08T21:58:28.706 thread-0 controller.cpp:583 startup ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database (log_plugin/to_zap_log_plugin.go:53)
warn 2020-05-08T21:58:28.706 thread-0 controller.cpp:452 initialize_blockchai ] Initializing new blockchain with genesis state (log_plugin/to_zap_log_plugin.go:53)
(split task from #22 ) Now that nodeos maps it's warning to zap level, it's annoying to have them by default.
This is open for discussion..