munin

I prefer Munin over Cacti because Munin's config is in simple text-based config files which can be scripted.

I hope this means I don't have to ever configure Nagios or Munin or Monit again.

Pingdom for site uptime & paging, munin for capacity planning and performance monitoring, and monit for process monitoring.

Site Reliability -- one for nagios alerts, one for site testing, one for munin, and one for github PRs 5.

Seriously I'd like to know what they do since I'm still looking for monitoring solution (currently testing munin).

With Cloudwatch I don't have to manage munin, cacti, and a server to run them on.

I had nagios, cacti, munin, graphite all running and had two ops guys pretty much 80% of their time managing it.

Give munin another chance, I find it's the easiest to setup from the list.

I've gotten a lot of mileage out of `ssh dbserver mysql -b -e \'select * from pants where...\'` in nagios and munin scripts.

I ran into this recently, backing up munin data to s3.

Other than being kind of small, tracking only 3 things, and costing $10 month what do these have over munin, cacti, or other RDD graphers?

Took me a moment to realise I was doing it on a 5-minute boundary, and munin fires on a 5-minute boundary - the data was being updated as I was copying it...

I am admittedly not a good sysadmin, but I keep an eye on my own "pirate" server (that is, outside the realm of the corporate network) and I have already ordered additional storage because Munin shows that, at present consumption rates, we will run out of storage in about 4 months, crossing the 70% mark in three.

Graphite + Grafana are like Cacti or Munin, but orders of magnitude smarter and more powerful.

Could anyone who tried this monitoring tool compare it to Munin?

Yes, I know about Nagios, Zabbix, Munin, etc.