SSProbe is a server status monitor, it provides a visual interface, real-time for you to display server status, such as CPU usage, memory usage, network speed and so on.
- Low CPU and memory usage.📉
- The client is very easy to deploy.🚀
- Super fast ⚡ and responsive 💦
- Takes less than 10 minutes to setup ⏱️
- After the server restarts, the client automatically reconnects to the server.⚒️
Live demo at Zolo's SSProbe.
On the release page, find the zip file corresponding to the system version, unzip it and upload the files ssprobe-server and config.yaml to your server, upload ssprobe-client to the machine you need to monitor.
The config.yaml contains some of your configuration, which is described below.
server:
token: 123456 # Used to verify the identity of the client (the monitored machine) when connecting to the server.
port: 3384 # The port the server is listening on.
web:
title: Zolo's Probe # The page's site title.
github: "" # Your github url(optional)
telegram: "" # Your telegram url(optional)
notifier:
telegram:
enable: true # Enable Telegram Bot to send notifications.
useEmbed: false # Whether to use the Bot created by yourself.
language: chinese # Language of Bot notifications
botToken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx # Bot token.(This is valid when useEmbed is true)
userId: 1953745499 # Telegram's user ID
⚠️ useEmbed: Do you use a Bot you created?If you deploy this server-side application on a server in mainland China, you will not be able to use Bot to send notifications due to network reasons. When
useEmbedis set tofalse, you can specify a UserID, using the Bot we've already created.
Use Telegram to search for @BotFather, send him /newbot,follow the steps to complete the creation, then send him /mybots to select your bot and get the token.
Use Telegram to search for @ssprobe_bot, Send /me to him to get your UserID. (@ssprobe_bot is the bot we have created. If you have enabled the Telegram bot and set useEmbed: false, then subsequent notifications will be sent to you via this bot.)
(1) 🖥️ Server-side program
Make sure that config.yaml and ssprobe-server are in the same directory, and start your program with the following command:
chmod a+x ./ssprobe-server && ./ssprobe-serverAt this moment，Open http://ip:10240 and you will see the monitoring page if you set web.enable: true
(2) 💻 Client program
chmod a+x ./ssprobe-client
./ssprobe-client --name=ClientName --server=ServerAddress --token=YourServerToken
⚠️ If you modify the server's listening port, you need to specify an additional `--port' parameter.(the default server port is: 3384)
Such as ./ssprobe-client --name=ClientA --server=110.42.133.216 --port=3384 --token=123456
Once the command is executed, you can see the data on the monitoring page.
Take nginx as an example and add the following to nginx.conf:
server {
listen 443 ssl;
server_name test.onezol.com;
ssl_certificate /home/zolo/ssprobe/test.onezol.com_chain.crt; # SSL Certificate Address
ssl_certificate_key /home/zolo/ssprobe/test.onezol.com_key.key;
ssl_session_cache shared:SSL:1m;
ssl_session_timeout 5m;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
location / {
proxy_pass http://127.0.0.1:10240/; # 10240 is the port of the program ssprobe-server
}
location /wss/ { # Here /wss/ cannot be modified
proxy_pass http://127.0.0.1:10240/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-real-ip $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
}
}If you need to deploy the front-end and back-end separately, you need to download the files in the server/static/ directory and create a config.json file in the index.html directory with the following contents:
{
"site_title":"your_site_title",
"websocket_url": "ws://server_address:10240",
"github": "your_github_url",
"telegram": "your_telegram_url"
}