Network Status Monitoring Guideline

Working Folder

cd /root/mainnet/ eth-net-intelligence-api/

Configure the Node Monitoring App

We will need to add the app1.json file located in the eth-net-intelligence-api directory by reference app.json:

There are few configurations that need to be changed in this file.

  • "name": The name that will appear for your node app in the pm2 process manager (see next section for more details on pm2)

  • "RPC_HOST": The IP address for the machine hosting your running gethinstance

  • "RPC_PORT": The RPC port that your geth instance is running on

  • "LISTENING_PORT": The network listening port for your geth instance

  • "INSTANCE_NAME": The name that will appear on the dashboard in your browser for this particular node

  • "WS_SERVER": The server address for the frontend UI (i.e. eth-netstats) running in background

  • "WS_SECRET": The secret used to allow the frontend to connect eth-net-intelligence-api. You choose any value to put here.

In app.json, we have to modify three parameters, namely INSTANCE_NAME, WS_SERVER andWS_SECRET.

You can get INSTANCE_NAME from private chain information.

WS_SERVER will point eth-netstats so we use eth-netstats' default url : http://localhost:3000

We set WS_SECRET = "BRISE123!"

Finally app.json

Start The Node App

We execute the backend tool ( eth-net-intelligence-api) run the following command:

/ROOT/MAINNET/eth-net-intelligence-api> pm2 start app1.json

Result

Issues:

You might encounter issue- No action

solution :

My solution is restart eth-net-intelligence-api again

/ROOT/MAINNET/eth-net-intelligence-api> pm2 start app.json app1.json or /ROOT/MAINNET/eth-net-intelligence-api> pm2 restart <App name>

PreviousFor DevelopersNextProxy Contract

Last updated