Notes from meeting with Nash: https://rchain.atlassian.net/wiki/spaces/OP/pages/562036959/2018-10-01+Meeting+notes+production+engineering+tutorial

Establishing a mindset for backward compatibility

Plan to start testing protobuf schema after Mercury

Deliverable from the SRE team

Test the plan

Gather metrics to the health of the cluster

Prerequisite

• Metrics for what good node performance looks like

  • Health of clique

Memory consumption

• How do we establish the baselines?

• What processes do we put in place to monitor change in baselines?

Resilience to errors on the network

Discussion about how we monitor

• Do we offer a centralized system?

  • Becomes difficult as the network grows

• Do we offer a monitoring module with node software?

  • Achieving buy-in from node operators may be difficult or at best inconsistent

• Do we use the Casper protocol to help bubble up metrics on the network?

Do we need to support monitoring beyond the clique?

• Measure things on a single node

• Aggregate metrics for nodes on the clique

What does it mean that the network supports 40K transactions/second?

• The business requirement is to measure 40K COMM events/second

• This means COMM events

  • There is a misunderstanding in the community between COOM events and TRANSACTIONS

  • COMM events are a join

  • Deploys aren’t a good metric because the platform is computational and not token transfer

• What tools do we need to monitor a network to understand it’s transaction speed?

What does it mean to be secure?

• What tools do we need to monitor a network to understand it’s security?

What does it mean to be scalable?

• What

DOS attack is the priority for Mercury

• Ability to detect the number of deploys a node receives

• Ability to detect the number of proposes a node makes

Trust infrastructure

• Proof of stake

• What is the trust between two nodes? Does proof of stake

What does it mean to be reliable

Idea to test with a testnet crash