
http_tpp.monitor - Parallel query http server monitor for mon

Parallel query http server monitor for mon. Logs timing and size results, can use a proxy server, and can incorporate a "Smart Alarm" function via a user supplied Perl module.

http_tpp.monitor -l log_file_YYYYMM.log -T alarm_seconds -t timeout_seconds host [host:/path_to_doc ...]


Note that a proxy will be used to access ot.myweb.com
hostgroup internet_web www.ama-assn.org
www.gartner.com
test.mysite.com:/~meekj/ca_zip.txt
ot.myweb.com/ca_zip.txt@proxy.mysite.com
watch internet_web
service internet_web
interval 5m
monitor http_tpp.monitor -l /usr/local/mon/logs/internet_web_YYYYMM.log -T 10 -t 15
period wd {Sun-Sat}
alert mail.alert firewall_admin
alertevery 1h summary
Command line test examples:
http_tpp.monitor -d www.redhat.com bns.pha.com mytheyw.com/_mem_bin/FormsLogin.asp\?/ nonexist.pha.com www.sun.com/@proxy.labs.theyw.com
http_tpp.monitor -d www.redhat.com@proxy.labs.theyw.com www.sun.com/@proxy.labs.theyw.com www.yahoo.com/@proxy.labs.theyw.com

On some systems, and/or versions of Perl modules, selecting a proxy for any queries will result in the proxy being used for all queries.
The "Smart Alarm" module is not yet documented here.
LWP::Parallel::UserAgent has default values on the number of parallel queries that will be made at once. These values cannot be currently changed via options.
Because LWP::Parallel::UserAgent does not seem to allow a per request setting of the proxy, each proxy, and the no-proxy queries must be done separately.
The previous two issues mean that the time to do all of the queries could often exceed the timeout setting due to the multiple rounds of request batches.
The timing results are not highly accurate due to the parallelization. In the future an option to capture and analyze the actual packet stream might be added.

LWP::Parallel::UserAgent HTTP::Request::Common Time::HiRes

Jon Meek, meekj@ieee.org

phttp.monitor by Gilles LAMIRAL