Glances is a free open source, modern, cross-platform, real-time top and htop like system monitoring tool. It offers advanced features compared to its counterparts, and can run in different modes: as a standalone, in client/server mode and in web server mode.
Considering the web server mode, you do not necessarily need to log into your remote server via SSH to run glances, you can run it in web server mode and access it via a web browser to remotely monitor your Linux server, as explained below.
To run glances in web server mode, you need to install it together with the Python bottle module, a fast, simple and lightweight WSGI micro web-framework, using the appropriate command for your Linux distribution.
$ sudo apt install glances python-bottle #Debian/Ubuntu $ sudo yum install glances python-bottle #RHEL/CentOS $ sudo dnf install glancespython-bottle #Fedora 22+
Alternatively, install it using PIP command like shown.
$ sudo pip install bottle
Once you have installed the above packages, launch glances with the
-w flag to run it in web server mode. By default, it will listen on port 61208.
$ glances -w OR $ glances -w &
If you are running firewalld services, then you should open port 61208 to allow inbound traffic to that port.
$ sudo firewall-cmd --permanent --add-port=61208/tcp $ sudo firewall-cmd --reload
For UFW firewall, run these commands.
$ sudo ufw allow 61208/tcp $ sudo ufw reload
After that, from a web browser, use the URL
http://SERVER_IP:61208/ to access the glances UI.
If you are using systemd system and services manager, you can run glances in web server mode as a service for efficient management, as explained in the next section. I actually prefer this method to running it as a background process.
Run Glances in Web Server Mode as a Service
Start by creating your service unit file (which I have preferred to name as glancesweb.service) under /usr/lib/systemd/system/glancesweb.service.
$ sudo vim /usr/lib/systemd/system/glancesweb.service
Then copy and paste the unit file configuration below in it.
[Unit] Description = Glances in Web Server Mode After = network.target [Service] ExecStart = /usr/bin/glances -w -t 5 [Install] WantedBy = multi-user.target
The above configuration tells systemd that this is a unit of type service, it should be loaded after the network.target.
And once the system is in the network target, systemd will invoke the command “/usr/bin/glances -w -t 5” as a service. The
-t specifies an interval for live updates in seconds.
[install] section informs systemd that this service is wanted by “multi-user.target”. Therefore, when you enable it, a symbolic link is created from the /etc/systemd/system/multi-user.target.wants/glancesweb.service to /usr/lib/systemd/system/glancesweb.service. Disabling it will delete this symbolic link.
Next, enable your new systemd service, start and view its status as follows.
$ sudo systemctl enable connection.service $ sudo systemctl start connection.service $ sudo systemctl status connection.service
Finally, from your web browser, use the URL
http://SERVER_IP:61208/ to remotely monitor your Linux servers via the glances UI, on any device (smart phone, tablet or computer).
You can change the refresh rate of the page, simply add the period in seconds at the end of the URL, this sets the refresh rate to 8 seconds.
One downside of running glances in web server mode is that, if the Internet connection is poor the client tends to easily disconnect from the server.
You can learn how to create new systemd services from this guide:
That’s all! If you have any questions or additional information to add, use the comment from below.
10 thoughts on “Use Glances to Monitor Remote Linux in Web Server Mode”
Does anyone know how to change default port 61208?
Reload of ufw shouldn’t have “allow” in it. How do I know….because I copy-pasted code from the internet into my terminal of course.
True, we will correct it in the article as soon as possible. Many thanks for the useful feedback.
@Aaron and @Guido,
Corrected the command in the article.
Hi, is it any way to make Glances trigger actions without client connection? I’ve tried but couldn’t so I created a task or cron to issue an http request to make actions being triggered. I’ve tested in Windows but I think in Linux it should be the same.
Yes, Glances trigger actions without client connection. You need to run it as a service as described above.
In “$ sudo systemctl enable connection.service
$ sudo systemctl start connection.service
$ sudo systemctl status connection.service”,
“connection.service” Shouldn’t be glancesweb.service ?
Remember you can give a custom systemd service unit any name of your choice, here for example we named our unit file: glancesweb.service.
I meant he meant how you refer to it as ‘connection.service’ inconsistently in part of the tutorial. Or do I misunderstand something?
Oh i get it, sorry for the misunderstanding. It was an editing problem during publishing, we will correct it as soon as possible.
Thanks so much and to @Hussein as well.