Aug 012012
 

Be aware this is a joke. ๐Ÿ˜€

I had alert from a memcached service that mentioning for all the time that hit rate was too low, after checking it I found it was actually because the traffic was too low (the site was not in production yet), so how to solve this problem?

After thinking of various “serious” solutions, I finally turned to running a script, keep hitting the entries (actually, only one specific entry) in the cache, so to raise the hit rate to a level that makes Nagios stop alerting me.

OK, OK, I know this is bad, but fun, isn’t it?

Actually this causes another thinking – if there is a particular key having high miss rate, do we care? If we do then the monitoring mechanism won’t work for that case …

Jul 312012
 

Trying to setup Nagios to play with monitoring facilities, turned out there are way too many things are NOT running out of the box. I’m trying to write as much as I can remember, so that I don’t have to Google again next time I step into the setup task again. Sure, others may be befinited from this as well.

A brief intro about the environment – I have my monitoring node in EC2 in east coast, another 3 servers to be monitored in EC2 west cost, all four are running Ubuntu 12.04, plus another physical box sitting in a IDC in Beijing, China, running Fedora 14 (the owner does not want to upgrade for some reason). Almost all servers are running classic applications for Web, such as Nginx, mysql, etc. Other than those public services I also need to monitor system status like disk space, memory utilization, ssh liveness, etc. Continue reading »