[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Unexpected result on port response time on the web interface
From: |
Marcus Mülbüsch |
Subject: |
Unexpected result on port response time on the web interface |
Date: |
Fri, 24 Apr 2015 11:44:07 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
Hello all,
using monit 5.12.2 on gentoo with the following test
check host example.com with address www.example.com
if failed
port 443 protocol https
with content = "Example Domain"
with timeout 2 seconds
then alert
when used on a large php-page it takes some time to parse for the
content. Thus the web interface shows
Port Response time 4.819s to
<localserver>:443/path/to/scrip.php?param=nothing type TCPSSL/IP protocol HTTP
Port If failed [<localserver>]:443/path/to/scrip.php?param=nothing type
TCPSSL/IP protocol HTTP with timeout 2 seconds then alert
theoug the response time shown is much larger than the allowed
timeout, no alert is raised. The response itself is much faster (as I
tested when the content check is left out, getting times of 0.060s or
thereabaouts), and thus no error should be raised.
However, it seems that the 4.819s listed above include the parse time?
Marcus
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Unexpected result on port response time on the web interface,
Marcus Mülbüsch <=