What open source server monitoring for Linux server?

Hi,

we are looking in our company new Linux Server Monitoring - performance, uptime and speed.

We had some open source - Nagios nad Cacti, but this software are very hard on maintenence and hard for end user.

Do you have any experience with open source Server monitoring Bijk.com - http://www.bijk.com?

We test Bijk.com last week, it is looks good, but there isn't all features such in Nagios.

Thanks for your help.

From serverfault Thomas

• hi,

  try zabbix - nagios, cacti and monit combined into one.

  m

  Muhammad : zabbix is becoming more popular ....
  From Martynas

• Give a try to munin at http://munin-monitoring.org

  Very simple configuration within a few mins.

  From Nickman

• Nagios has a steep learning curve but once setup it has nearly 0 maintenance. If you think it is "hard on maintenance" either you have incorrectly configured it or you should be looking for some outsourced monitoring solution.

  If you want to stay in the opensource d-i-y world I'd look at Nagios+Cacti or Zenoss. There are also Zabbix, OpenNMS, Munin, and many other. Nearly every one of these product has one or more companies behind it that could sell you support should the need arise.

  If you choose an opensource solution take a good look at the community behind it, a monitoring system should be a really stable platform that you'll use many years, I'd look for something with a good, thriving community behind.

  Thomas : OK, thanks. We will stay with http://www.bijk.com - it is simply for us, than Nagios or Zabbix. Thanks for your answer.
  From Luke404

• I'm not partial to the nagios/cacti approach in that performance data needs to be linked to fault data to trigger a lot of alarms properly, like in the event of a long term threshold being exceeded. Like Martynas suggested, something like Zabbix is more appropriate in my opinion, although I'm more partial to OpenNMS.

  There are a lot of "open core" products on the market now, but I don't really agree with the principle or the fact that it's entirely possible for you to do something like submit a feature upstream, have it be rejected, and then surprise! it's in the pay version in the next release. It's not to say that one of these options may or may not work for you, but the drawbacks are something to carefully consider when choosing one of these products.

  From Mike Danko