- You need to have Lisk installed.
- Install this script only in one server and make sure you whitelist this server's IP in all servers.
- You need to have [fs, http, node-cmd, path] installed in npm, for example: npm install node-cmd
- Make sure to add your new serverport number to your firewall. If you are using UFW maybe this can help you: UFW - First time with a firewall
Code: Select all
git clone https://github.com/mrgrshift/Server-Monitor
You need to edit config.json file with all your proper data. The structure is as follows:
Code: Select all
All data fields are obligatory.
name: It is the name of your delegate.
address: It is the address of your delegate.
serverip: It is the IP of the server where you are installing this software.
serverport: It is the port of your server for which it will be serving the information. Must be different from the ports that Lisk uses.
servers: Is an array of all the servers you will monitor. Make sure you insert the right format. You can add as many servers as you want, but make sure you use the correct sequence always start with "server1" following "server2" and so on.
After you finish and save your changes from config.json, run in a background process (you can use screen): node webserver.js
node webserver.js will start a web server which you can access with http://serverip:serverport/ from a web browser like Chrome.
If you access from a device that you have in your servers whitelist, you will be able to obtain almost realtime data.
If you access from a device that is no in your servers whitelist, you will obtain the data with a delay of 20 seconds maximum.
Optimum method of use. If you are in your office or home computer whitelist that IP's and open chrome on your server's address, you will not need to check everytime how your servers are performing, chrome will alert you if none of your servers are forging. When the page load is complete you will recieve a first alert to test and for you to see how it works.