Sign inSign up

vegaprotocol/vaguer

By vegaprotocol

•Updated almost 2 years ago

Image
0

1.5K

vegaprotocol/vaguer repository overview

⁠Vaguer (formerly Grade, formerly Vaguer)

Scores data nodes against peers over time

⁠Run it

npm install
# Get the status of all data nodes on fairground
npm start fairground
# Get the status of all data nodes on mainnet1
npm start mainnet1
# Get the status of all data nodes in a given network configuration file
npm start https://raw.githubusercontent.com/vegaprotocol/networks/master/fairground/fairground.toml
# JSON output
JSON=true npm start fairground --silent
# Prometheus output
PROMETHEUS=true npm start fairground --silent

⁠What am I seeing?

The hash columns are a shortened sha256 hash of some data fetched from the server, so that the consistency across nodes can be compared. A difference in hashes between two nodes means that some part of the data returned is different.

  • host is the reported name of the node, as configured in the network.toml for the selected network
  • blockHeight is shown, as only nodes with the same block height are relevant. Some of the hashed data can change between blocks
  • totalPeers is show, but is not hashed - it's just an indicator of node health
  • steakHash is a hash of all of the validators and their staking amounts. Nodes on the same block should have the same data.
  • marketsHash hashes some basic information about the markets live on the network
  • assetsHash hashes some basic information about the active assets on the network
  • governanceHash hashes some basic information about governance proposals on the network
  • hashHash is a hash of the above hashes, plus a hash of network information and genesis information

The final result is that the set of nodes that are on the same height and agree on the final hashHash are considered to be 'correct', and the nodes that differ will display some debugging information above the table that points to where the hashes diverge. Divergent hashes of nodes on the same block height suggest a problem with the node, and aren't necessarily critical errors.

⁠Sample output

hostblockHeighttotalPeerssteakHashmarketsHashassetsHashgovernanceHashhashHash🥇
api.n06--------
api.n076847449eee0fc79af09dce206c9018905cc52-
api.n086847459eee0fc2c5ee0dce206c90189d2b604🥇
api.n096847449eee0fc2c5ee0dce206c90189d69503-
api.n106847459eee0fc2c5ee0dce206c90189d2b604🥇
api.n11--------
api.n126847449eee0fc2c5ee0dce206c90189d69503-

⁠Alternate output formats

For most cases, the table in the console is sufficient. JSON and Prometheus formats are available via environment variables, see above for how to use them

⁠LICENSE⁠

MIT

Tag summary

Content type

Image

Digest

sha256:ad467d6f5…

Size

23.4 MB

Last updated

over 3 years ago

docker pull vegaprotocol/vaguer