- extensive metrics on the system and JVM
- At minimum the following metrics should be exposed:
- CPU
- RAM
- Disk
- Network core metrics at the core level
- JVM performance
- Garbage collection
- Size of memory pools
- Consumption of memory pools
- Monitoring systems can pull metrics from the node
- The node does not push metrics
- The node does not report on itself
| Metrics emitted on http port 40403. Complete (metrics emitted via API) |
| 2 | Node measures COMM Events | COMM events are a measure of an RChain transaction. The node must report on how many raw comm events are being processed, so we can demonstrate 40K COMM events /second | Must Have | - Create a counter of COMM events as a total count of events in the last hour. Rita Allen to confirm with SRE if the metrics should reset in the past hour.
- COMM events should be measured for Propose (block creation) and Replay RSpace.
| Rita Allen to validate the requirement, see what has been implemented. |
| 3 | Node reports on CPU Utilization | The Node reports on the percentage of CPU that is being consumed. | Must Have | - Report on the percentage of CPU being consumed at the time the request for metrics is being made.
| Rita Allen Please confirm the status |
| 4 | Node reports on total RAM consumed | The node reports on the amount of RAM being consumed | Must Have | - Report on the total amount of RAM being consumed at the time the request for metrics is being made
| Rita Allen Please confirm the status |
| 5 | Deploy Count | The node reports on the total number of deployments received | Must Have | - Report on the total number of times the deploy API receives a request.
| Needs to be implemented. Should have a ticket. Add ticket number here Rita Allen |
| 6 | Blocks proposed | A validating node proposes blocks | Must Have | - Total blocks proposed by the node in the past hour. Metric should reset in the past hour. Rita Allen to confirm.
| Needs to be implemented. Should have a ticket. Add ticket number here Rita Allen. |
| 7 | Fork Choice Tip | For something like Ethstats.net, it would be good to show the current fork choice tip for each node | Nice to have | - Show the hash of the block that is the current fork choice rule.
|
|
| 8 | Blocks being processed? |
|
|
|
|
| 9 | Time since last block? |
|
|
|
|
| 10 | Demonstration of a node operating monitoring system | Node operators will have various needs and expectations for their node monitoring system. The RChain node will not dictate the system they use. However, at launch of test net there will be an example of a node operating system to share as an example, along with documentation in the event a node operator wants to reproduce the example monitoring system. | Must have | - Create a Pyrofex node monitoring system
- Document the system so others can create something similar.
- This system will be created using Prometheus and
|