The Database tab is intended for setting the parameters for storing the acquired data.
- Statistics keeping time
The maximum time which will be the statistics — the volume of transferred data in total and for particular defined services — kept for. The optimal setting depends both on the requirement how long should be the measured data stored, as well as on the size of available disk space and on the intensity of the network traffic (during the time of no communication, nothing is stored).
The time for keeping of the data is determined by the two following parameters:
Data for the high resolution — data with the high resolution (3 seconds sampling rate). The time for keeping is given in weeks. This data represents the majority of the stored data.
Low resolution data — data with low resolution (1 hour sampling rate). This data occupies much less space than the data with high resolution but its accuracy is sufficient for observing longer time period (e.g. 1 week and more).
Thanks to their small size, the data with small resolution can be kept for longer time — time is given in months.
- Log keeping time
Time of storing (respectively maximum age) of the log files Error Log, Connection Log, HTTP Log, Mail Log and ICQ Log. Given in days.
- Captured objects maximal age
Time for storing of the captures objects (i.e. information, which is displayed in the window Scanned data — see chapter 7.4). Given in days.
Keep captured WWW pages — time for storing the captured WWW pages. WWW pages can contain big amount of graphics and other objects, therefore it deals with high volume data.
Keep captured FTP sessions — time for storing the information about connections to the FTP servers. Only information about the relations is stored (server, user, downloaded or uploaded files), not the transferred files. The volume of the data is therefore small.
Keep captured e-mails — time for storing the captured E-mail messages. The messages are stored also with the attachment and can therefore represent high amount of data.
- Daily cleaning should be started at
Startup time for automatic database maintenance (performed once a day). The main goal of this action is to remove the data, which is older than the set values (see the options described above).
This maintenance can take a long time (in the worst case even several tens of minutes — depends on the size of the stored data and speed of the used computer). During the maintenance time it is not possible to view the currently processed log (in the appropriate window a message saying the maintenance is running, will appear). For this reason, the maintenance should be scheduled to the time, when there is low or even no traffic in the network (e.g. during the night).
Note: If the computer with Kerio Network Monitor is turned off in the given time, maintenance will be performed on the next start of the Kerio Network Monitor Daemon service.
- (Last cleaning took ... seconds)
The time which took the last database maintenance (in seconds).