Author: Markus Hinrichs
Editor: Randall Roland
The ENF engineers have now switched their attention to CDT and DUNE following Leap 3.2 release, with upcoming updates. The very technical discussion about the aspirations for the Prometheus Exporter capabilities in Leap 4.0 to shed light on the enigmatic nodEOS and give a dynamic overview tool that gathers various types of data continues in this week's Node Operator Roundtable. This time, the Roundtable included 12 people.
The major subject of conversation during the weekly EOS Node Operator Round Table sessions is software development. Developers, block producers, blockchain engineers, and community members who want to learn more about the EOS development process might benefit from the knowledge it offers.
Click here for the video recording of the meeting (Passcode: +q0S.ZLx)
Summary of the Antelope Leap Updates on the way from Stephen Diesel (ENF, Product Manager of Leap)
UPDATES | RELEASE TIMEFRAME |
Leap 3.2.1 potential patch release | still needs more discussion to give a clear timeline |
CDT 3.1 | Release likely next Monday December 12th, 2022 |
DUNE | following CDT release (Update on release next week) |
System contract updates | in the pipeline |
Prometheus Exporter Discussion Part 2/2
RECAP: What to add to the Prometheus Exporter in Leap 4.0 (from last meeting)
ability to control the depth of your monitoring
minimizing node impact when collecting statistics (run it on a different thread)
everything that is presently being logged
get info on head block, LIB, etc.
node configurations: runtime, if OC is enabled, whether console logging is enabled, and features
block logs: trimmed or full nodes
In the future, a different get info endpoint may be used to format the data as JSON.
This week's conversation concentrated on Matthew Darwin's wish list's low-hanging fruit.
The following list only contains the node-related metrics that were regarded to be "low-hanging fruit," as the participants expanded and updated Matthew Darwin's list as a starting point for the discussion. (quote):
what is returned from /v1/chain/get_info (head block number, lib)
unapplied transaction queue sizes
Unapplied transaction queue sizes - number of transactions
Unapplied transaction queue sizes - byte size
Unapplied transaction queue sizes - speculative CPU time
blacklisted transactions size
Blacklisted transactions size - by account
Blacklisted transactions size - by key
Blacklisted transactions size - by contract
subjective billing sizes
New get subjective bill account info Github issue feature request
scheduled transaction size
total count
number of forks
number of unapplied blocks
number of dropped blocks
number of transactions received per peer/API
number of unique transactions received
number of connections on wrong chain
number of new connections
uptime
cpu usage by thread
disk space used, by volume (blocks, ship, state, trace)
disk space available
current block number
Chain related metrics (not covered in depth in this call, quoted)
number of missed blocks (missed in a round) by producer
number of missing producers (missed 12 blocks in a round) by producer
number of double production (more than 12 blocks in a round) by producer
average (and last) block arrival time by producer
number of transactions per block by producer
amount of blockchain cpu used per block by producer
number of bytes per block by producer
replay status (when starting from snapshot and replaying blocks)
Agenda for the next Roundtable (December 14)
Michael from EOSUSA has suggested discussing the Antelope resource model for the coming week.
There are chances to enhance the resource model on Antelope chains, as seen from the current WAX congestion difficulties.
Participants (12) of this round table:
Randall Roland | EOS Support
Ted Cahall | ENF
Michael | EOSUSA
Virginia Glass
Denis Carriere
Kevin Heifner | OCI
Brian Hazzard
Max Cho | KOREOS
Daniel Keyes | EOS Nation
Stephen Diesel | ENF
Matthew Darwin | EOS Nation
Jeff Werner
Sources & References
Video Recording of the Meeting (Passcode: +q0S.ZLx)