Get your server issues fixed by our experts for a price starting at just 25 USD/Hour. Click here to register and open a ticket with us now!

Author Topic: HTTPing  (Read 3849 times)

0 Members and 1 Guest are viewing this topic.

Vinil

  • Guest
HTTPing
« on: December 27, 2013, 08:11:20 pm »
Httping monitoring tool is like ‘ping’ but for http-requests. Give it an url, and it’ll show you how long it takes to connect, send a request and retrieve the reply (only the headers). Be aware that the transmission across the network also takes time! So it measures the latency of the Webserver + network.

How to install


You can install it through yum

Quote
yum install httping

or try with rpm repository.

Quote
http://pkgs.org/centos-6-rhel-6/repoforge-x86_64/httping-2.0-1.el6.rf.x86_64.rpm.html


Install via source


Code: [Select]
cd /usr/local/src

http://www.vanheusden.com/httping/httping-2.3.3.tgz

tar -zxvf httping-2.3.3.tgz
cd httping-2.3.3

make install

This will first invoke the 'configure'-script and then build the sources.
You can also run 'configure' manually. Then the following switches apply:
--with-tfo      force enable tcp fast open
--with-ncurses  force enable ncurses
--with-openssl  force enable openssl
--with-fftw3    force enable fftw3

Please note that TCP fast open requires a Linux kernel of version 3.7 or more recent.

'fftw3' support is only usefull if you include the ncurses interface.


Now ping your website.

Code: [Select]
root@server1 [~]# httping -g www.example.com
PING www.example.com:80 (/):
connected to 192.168.0.10:80 (228 bytes), seq=0 time=17.44 ms
connected to 192.168.0.10:80 (228 bytes), seq=1 time=2.24 ms
connected to 192.168.0.10:80 (228 bytes), seq=2 time=1.55 ms
connected to 192.168.0.10:80 (228 bytes), seq=3 time=1.92 ms
connected to 192.168.0.10:80 (228 bytes), seq=4 time=4.50 ms

Ping a Webserver and Specify a port: ( specify port 80 )

Code: [Select]
root@server1 [~]#$ httping -c 4 -p 80 -g http://www.example.com

PING www.example.com:80 (/):
connected to 192.168.0.10:80 (486 bytes), seq=0 time=2.65 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=1 time=2.54 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=2 time=1.65 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=3 time=1.59 ms  0KB/s


Ping a Webserver and request complete page/file:

The capital “G” sends a GET request rather then a HEAD request. By receiving the entire page/file you can measure the throughput of the webserver.


Code: [Select]
root@server1 [~]# httping -c 4 -p 80 -G -b -g www.example.com
PING example.com:80 (/):
connected to 192.168.0.10:80 (486 bytes), seq=0 time=2.65 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=1 time=2.54 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=2 time=1.65 ms  0KB/s
connected to 192.168.0.10:80 (486 bytes), seq=3 time=1.59 ms  0KB/s
--- http://example.com/ ping statistics ---
4 connects, 4 ok, 0.00% failed, time 3009ms
round-trip min/avg/max = 1.6/2.1/2.6 ms
Transfer speed: min/avg/max = 0.000000/0.000000/0.000000 KB
« Last Edit: December 27, 2013, 08:16:12 pm by Vinil »