Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Conky vs netdata, the Slant community recommends Conky for most people. In the question“What are the best system monitors for UNIX-like systems?” Conky is ranked 3rd while netdata is ranked 5th. The most important reason people chose Conky is:
Conky is editable to the point that there is almost no limit to the designs one can use to display the type of information one wants. Not only are there thousands of themes available on sites like deviantart and gnome-look, but a user can create any type of look they like with a little bit of know-how and imagination.
Specs
Question Ranking
Pros
Pro Infinitely themeable
Conky is editable to the point that there is almost no limit to the designs one can use to display the type of information one wants. Not only are there thousands of themes available on sites like deviantart and gnome-look, but a user can create any type of look they like with a little bit of know-how and imagination.
Pro Many different sensor stats
Conky has a bunch of sensor stats that the user can choose to display such as CPU usage, memory, uptime, etc. Depending on what the user wants to display, most likely there is a way to display the needed info when using Conky.
Pro Runs on top of X
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 Setup can be difficult
Being text based, the config file for Conky can be intimidating for those unfamiliar. Though there are configuration managers out there such as Conky Manager which can make the setup a bit easier.
Con Is system monitor but can't manage processes
Conky is a great system monitor, but can't e.g. kill (individual) processes like htop can.
Con Requires X
Cannot easily be used on a headless server or remotely (most people and servers support remoting via SSH).
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
