How would you monitor a large list of URLs?

[Aaron Segura]

Write a simple shell script wrapper for check_http to iterate over a
list of URLs and report any errors. 

-----Original Message-----
From: Sean Carolan [mailto:scarolan at gmail.com] 
Sent: Wednesday, October 15, 2008 1:29 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] How would you monitor a large list of URLs?

I'm sure at least one of you may have been down this path before, so
here's my question:

I have a large list of URLs that I'd like to monitor with Nagios.  At
some point I may break them into groups but for the time being I'd be
happy to have a simple check_url monitor with the same options for all
URLs.  How would you tackle this problem?

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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