The EOS Node Operator Roundtable meets every Wednesday at 14:00 UTC to prepare for the next EOS consensus upgrade and share feedback on opportunities to improve the Antelope protocol for node operators.
There are some items on the wish list that need to be monitored at the chain level, which is a higher level of effort to implement and not discussed in detail during the call.
Node (low hanging fruit):
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 gitbub 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 (out of scope for this call):
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)
Next week
For next week, Matthew has proposed a conversation on the Antelope resource model
As can be seen with the current congestion issues on WAX, there are opportunities to improve the resource model on Antelope chains
The EOS Node Operator Roundtable meets every Wednesday at 14:00 UTC to prepare for the next EOS consensus upgrade and share feedback on opportunities to improve the Antelope protocol for node operators.
💬 Join us in Telegram 🗂 See all meeting summaries
🗓 December 7 - 14:00 UTC
🎥 Watch the recording
Summary
🟢 Leap Software Status
41
Technical roundtable for EOS Node Operators
This week was a continuation of last week's discussion on what statistics should be added to the prometheus exporter in Leap 4.0. We had a productive discussion that will continue next week.
The problem:
An original draft for architecture (updates have likely happened since this)
Another historical list requested by Matthew
Example nodeos monitoring dashboard leveraging prometheus data
This week's discussion was focused on the low hanging fruit that could be monitored at the node level from Matthew's wish list: https://github.com/eosnetworkfoundation/mandel/issues/67
There are some items on the wish list that need to be monitored at the chain level, which is a higher level of effort to implement and not discussed in detail during the call.
Node (low hanging fruit):
Chain (out of scope for this call):
Next week
Participants (12)