Access counter and statistics by DeleGate

Yutaka Sato

May 11, 2006

Basic functionality for access counters and real-time statistics were built-into DeleGate/9.2.0. It is applied not only to access count from clients but also to general counts including Referers, errors, and more, in future. So far, the following counters have been implemented.

count for each requested URL on origin/proxy HTTP DeleGate (example)
count for each Referer URL on origin/proxy HTTP DeleGate (example)
count for each transferred file on origin FTP DeleGate (example)
count for each error or rejection in SMTP DeleGate (example)
count for each session of FTP, SMTP, NNTP DeleGate (example)
count for each packet incoming to DNS DeleGate (example)

This built-in counter is intended to be used to show real-time statistics of DeleGate servers too. It will be convenient to be able to get statistics in real-time and without keeping a large volume of log files.

Basic Usage

Counters are enabled with the COUNTER parameter, as follows in the simplest.

COUNTER=do

A SSI tag "COUNTER" is introduced to show values in counters. The simplest example is the access counter of the SHTML page including the tag.

11

There are three types of counters based on (client's) IP address; the first one is incremented on every hit, the second one is incremented excluding repetitive hit by the same IP address, and the third one is incremented excluding repetitive hit by one of last ten IP addresses. Each counter is represented with %T, %U, and %V respectively in a format string given by the fmt="formatString" attribute.

11 : 5 : 5 hits / 4 nets (since Jun 12 2006)

Yet another count is "network count" which is represented as "%N" in the format string. It is introduced to be a metrics of the coverage or distribution of (client's) IP addresses on the address space. It is not a counter incremented on each hit, but the number of bits in a bit map of network addresses. In the current implementation, the width of the network mask is 10 bits, therefore the logical maximum number of "%N" is 1024. The map of networks can be shown with "%M" as follows.


  0.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
 16.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
 32.0.0.0 -------- -------- -------- -0------ -------- -------- -------- --------
 48.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
 64.0.0.0 -------- ---1-4-- -------- -------- -------- -------- -------- --------
 80.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
 96.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
112.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
128.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
144.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
160.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
176.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------
192.0.0.0 -------- -------- -------- -------- -------- -------- -------- -3------
208.0.0.0 -------- -------- -------- -------- -------- -------- -------- --------

In the map, each true bit is marked with 'X' while false bit is marked with '-'. The recent ten networks are marked with a digit from '0' to '9'. The recent ten IP addresses can be shown with "%L" as follows.


LAST[0][  0] 2660003E  38.B
LAST[1][  1] 42F0008A  66.D
LAST[2][  0] 42F00089  66.D
LAST[3][  0] CE500002 206.B
LAST[4][  5] 43600082  67.B

This table of recent 10 addresses is managed in the LRU order, that is the entry of the least recentry hit is pushed out from the table.

Hits 11 : 0.0/hour, 0.0/day, 0.4/month

PageViews: 5 hits / 4 nets
[ The source of this SHTML file (11 hits) ]