"; for ($i = 0; $i < count($nav); $i++){ if ($dirMax >= $pthSize){ if(($nav[$i][2] != 1) && (getfilepath($nav[$i][1]) == $parsedpath)) echo "Help : ".$nav[$i][0]; if (parsefilepath($nav[$i][1]) == $dirs[$pthSize]){ if ((getfilepath($nav[$i][1]) != $pth) || getfilepath($nav[$i][1]) != $pth."index.php") echo "Help : "; if (getfilepath($nav[$i][1]) == $parsedpath) echo $nav[$i][0]; else { echo "".$nav[$i][0]." : "; for ($j = 0; $j < count($nav[$i][3]); $j++){ if(getfilepath($nav[$i][3][$j][1]) == $parsedpath) echo $nav[$i][3][$j][0]; if(parsefilepath($nav[$i][3][$j][1]) == $dirs[$pthSize + 1]) { if ((getfilepath($nav[$i][3][$j][1]) == $parsedpath));// echo $nav[$i][3][$j][0]; else { echo "".$nav[$i][3][$j][0]." : "; for($k = 0; $k < count($nav[$i][3][$j][3]); $k++) { if(getfilepath($nav[$i][3][$j][3][$k][1]) == $parsedpath) echo $nav[$i][3][$j][3][$k][0]; if (parsefilepath($nav[$i][3][$j][3][$k][1]) == $dirs[$pthSize+2] && getfilebase($nav[$i][3][$j][3][$k][1]) == $path_parts["basename"]) { if (getfilepath($nav[$i][3][$j][3][$k][1]) == $parsedpath) ; //echo $nav[$i][3][$j][3][$k][0]; else if (parsefilepath($nav[$i][3][$j][3][$k][1]) == $dirs[$pthSize+3] && $nav[$i][3][$j][3][$k][2] == 1) { for ($l = 0; $l < count($nav[$i][3][$j][3][$k][3]); $l++){ if (getfilepath($nav[$i][3][$j][3][$k][3][$l][1]) == $parsedpath) echo "".$nav[$i][3][$j][3][$k][0]." : "; echo $nav[$i][3][$j][3][$k][3][$l][0]; } } } } } } } } } } } echo ""; ?>

The Performance page provides key metrics describing the load on the Server. The performance table is updated every minute to show current values of each statistic.


The number of interfaces being monitored.


The rate at which the server is processing traffic samples.


The byte rate of measurement data arriving at the server. In order to prevent data loss, this value must be kept well below the capacity of the link attaching the server to the network.


The number of traffic samples that were lost in the network. If this number is high, it might indicate that there is a problem with overloading at the server. A server can be overloaded if the volume of data arriving exceeds the capacity of its interface card (check Bytes) or if the server is unable to keep up with the processing required to handle the arriving samples (check Samples and CPU).


The number of interfaces that the server wishes to collect data from, but which have become unreachable over the network. Click on the number to get a list of the unreachable interfaces.

Other Manager

The number of interfaces that the server wishes to collect data from, but which are in use by another measurement system, and are thus not available. Click on the number to get a list of interfaces and their owners.


The load average on the CPU. This number indicates the average number of tasks ready to run at any instant. If the number is less than 1 then the CPU has spare capacity. The number may exceed 1 during periods when the server is busy handling queries, running reports or consolidating data, but a persistently high number might indicate that the server is becoming overloaded (check Lost to see if lack of CPU resources might be causing data loss).


Memory utilization will fluctuate as the server handles different tasks, such as responding to a query or processing a sample, but there may be a problem is the memory utilization is consistently high. Excessive memory utilization causes extra processing overhead and slows the server down. If memory utilization is high, check CPU and Lost to see whether this might be causing the server to overload.


Disk space is required to store traffic data. If disk space is low, the server will automatically delete old data in order to make space for new, however, this might result in a shortening of the history below that requested in the configuration file.