Checking a Staking Node

Procedure

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

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

Basic Settings

Here shows the node ID, public blockchain name, node status, mainnet and testnet types, node type, gRPC endpoint, node TLS certificate, blockchain instance flavor, creation time, AZ, APIs for full nodes, WebSocket endpoint, HTTP endpoint (for validators), gRPC endpoint (for validators), execution client, execution client version, consensus client, and consensus client version. If Display APIs for Full Node is enabled, HTTP and WebSocket endpoints are displayed. If VPC Endpoint (VPCEP) is enabled, the VPC endpoint is displayed.

Figure 3 Basic settings

• Connect to MEV-Boost Relays is displayed only if you enabled this function when creating staking nodes.
• 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

Node Status

Here shows the trends of the peer quantity and block height.

Figure 5 Node status

Alarms

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

Figure 6 Alarms