Christopher May - Nagios Exchange

With the updated readme, this is a doddle to get working. Ben was most helpful with the heads up regarding ruby 1.8. The only feature I would ask for at this point (if you're interested) is being able to pass the username and password from a file so I dont have the auth details in the nagios command! Thanks for this. Much appreciated.

Reviewed 13 years ago

Does most of the job

I needed this more for ELB checking then ec2 checking, does the ec2 checking quite well from what I've seen and relatively easy to set up. However I will ask, is there a way of finegraining elb metrics? At the moment it just uses the entire region, can the -I flag be used for the elb dns entry? Cheers.

Reviewed 13 years ago

Effective check

Does exactly what it says on the tin, does a couple of things very well. My only gripe would be that if a box doesn't allow the plugin to talk to the server-status page, it should give a nice error, not the Python traceback you get at the moment. Otherwise, very very happy. Thanks for this.

Reviewed 12 years ago

Works well... when it works

Great plugin, but I do have a fairly big problem I've just noticed, we use a .my.cnf file for all username and password (Which is common across the company for the nagios mysql user), however we need to specify hostname in the command for obvious reasons. However, when you run the script with the mycnf option, it doesn't parse the hostname and goes to localhost instead. So I ended up with 20machines all with the same mysql health values! If you use --hostname --user and --pass as normal, the script works great hence the good rating, but if I can submit a bug report somewhere that would be ace. Cheers, Chris

Reviewed 13 years ago

No Favorites Found