Checking a Full Node

Procedure

1. Log in to the NES console.
2. Choose Dedicated > Network Management.
3. Click a node ID.
   Figure 1 Checking a full node
   

4. Check the node details, including the data of Basic Settings, Monitoring, APIs, and Alarms.
   Figure 2 Node details
   

Basic Settings

Here shows the node ID, public blockchain name, node status, mainnet and testnet types, node type, HTTP endpoint, WebSocket endpoint, blockchain instance flavor, creation time, availability zone (AZ), execution client, execution client version, consensus client, consensus client version, and so on.

Figure 3 Basic settings

An AZ is a physical region where resources use independent power supplies and networks. Your public blockchain nodes are automatically allocated to different AZs. To ensure application availability when deleting nodes, it is recommended to avoid leaving the remaining nodes in the same AZ. Currently, AZ1 and AZ3 are supported.

Monitoring

Here shows the CPU usage, physical memory usage, network traffic, and disk usage.

Figure 4 Monitoring

APIs

Here shows the total number of API calls and the top 5 most called APIs.

Figure 5 APIs

Alarms

Here shows the active and history alarms of the current node.

Figure 6 Alarms