We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original issue: EOSIO/eos#8477
To ease troubleshooting it would be very helpful to log more information about the size of the block in nodeos standard output
Today it looks like this:
Received block 2804890f34cb6cd3... #101125076 @ 2020-01-20T16:11:58.500 signed by eoseouldotio [trxs: 8, lib: 101124757, conf: 0, latency: 265 ms]
Request is to add things like:
If computing this information will take additional CPU, the probably it should be optionally controlled by either a configuration or logging option.
The text was updated successfully, but these errors were encountered:
GH-292 Add additional logging to Produced and Received block log mess…
a7cc626
…ages.
heifner
Successfully merging a pull request may close this issue.
Original issue: EOSIO/eos#8477
To ease troubleshooting it would be very helpful to log more information about the size of the block in nodeos standard output
Today it looks like this:
Received block 2804890f34cb6cd3... #101125076 @ 2020-01-20T16:11:58.500 signed by eoseouldotio [trxs: 8, lib: 101124757, conf: 0, latency: 265 ms]
Request is to add things like:
If computing this information will take additional CPU, the probably it should be optionally controlled by either a configuration or logging option.
The text was updated successfully, but these errors were encountered: