What's the canonically "proper" way to check an external website (that I don't
control) within Nagios? WHat I've done historically has been to define a dummy
"urlhost" that I then hang various check_http checks off of, but that seems
wrong somehow.
In talking to other folks in #nagios on freenode, another approach is defining
it as:
define host{
use web-server
host_name s3.amazonaws.com
hostgroups prod-URL
address s3.amazonaws.com
check_command check_http!-f follow
contact_groups admins-email
}
works, but then there's a warning thrown during pre-flight due to the lack of
services affiliated with this "host."
What's the "correct" way to pull this off?
-- Corey / KB1JWQ
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
