# 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: ![mceclip0.png](https://bitgert.zendesk.com/hc/article_attachments/4460583653521/mceclip0.png) 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** and**WS\_SECRET**. You can get **INSTANCE\_NAME** from private chain information. ![mceclip1.png](https://bitgert.zendesk.com/hc/article_attachments/4460584234257/mceclip1.png) **WS\_SERVER** will point **eth-netstats** so we use **eth-netstats'** default url **:** [http://localhost:3000](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 ![mceclip2.png](https://bitgert.zendesk.com/hc/article_attachments/4460564266257/mceclip2.png) 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 \