Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Glances vs netdata, the Slant community recommends Glances for most people. In the question“What are the best system monitors for UNIX-like systems?” Glances is ranked 2nd while netdata is ranked 5th. The most important reason people chose Glances is:
Unlike the default system monitors found in Ubuntu or Gnome Shell, Glances shows a lot of information all in one place instead of having to click through tab after tab. This makes cursory glances at one's stats a lot easier and less time-consuming.
Specs
Question Ranking
Pros
Pro Important information all in one place
Unlike the default system monitors found in Ubuntu or Gnome Shell, Glances shows a lot of information all in one place instead of having to click through tab after tab. This makes cursory glances at one's stats a lot easier and less time-consuming.
Pro Includes network bandwidth
Pro Works in a terminal
Works perfectly well even if you remote access a server via SSH.
Pro A lot of information
Much more information than htop.
Pro Easily installed
Glances is a popular system monitor and in being so is often found in most distros repositories, so it is easily installed.
Pro Web interface and remote monitoring features
A Web interface based on a Restful JSON API is also available and allows remote monitoring.
Pro Shows only necessary details
Most performance monitors overwhelm you with too much detail. Glances almost always shows exactly what you were interested in immediately.
Pro Pleasant UI
Very nice UI with a good overview and nice colours.
Pro Plug and play
No need to configure anything to get started.
Pro Access via web
NetData is accessible via the web. So even remote hosts can be monitored.
Pro Smooth installation and setup
Cons
Con Lack of colors can make it confusing.
Con High cpu usage (on RPi), broken after a few hours of running
It's based on Python.
Con Only in browser (if you use it together with atop, you can do without though)
The application is only accessible via the web browser. So if it's not running it has to be started and then accessed via the browser.
Con Takes up a significant portion of cpu and memory in smaller server instances
