Event log and statistics

March 25, 2022

ID 49312

This section describes how to configure the Event log and statistics settings and how to view the Event log and statistics database (information for one server and general information about all servers).

Kaspersky Anti-Virus can store information about application events and statistical information about threats detected as a result of anti-virus scanning and actions taken on them in the Event log and statistics database.

The Event log and statistics database is distributed as a replica and stored on each one of the protected servers. It contains the cumulative statistics of all events on all protected servers. All modifications are distributed through the standard replication mechanism in accordance with their schedule and topology. By default, information is saved in the Event log and statistics database kaveventslog.nsf.

If Kaspersky Anti-Virus uses a distributed deployment scheme, information on all protected servers is saved in the kaveventslog.nsf database.

The database kavquarantine.nsf is created in the Kaspersky Anti-Virus database catalog when the application is installed (the default catalog is kavdatabases). Information stored in the Event log and statistics database can only be accessed using the Control Center database user interface. You can view and delete records in the Event log and statistics database.

The Event log records information about the activity of Kaspersky Anti-Virus modules at the server task level of the Lotus Domino server. The scope of information recorded in the Event log is specified in the Detailing level section. By default, the most important information about the operation of all Kaspersky Anti-Virus modules involves events of critical importance pointing to problems in the application or vulnerability in the server's protection.

The Event log settings also define the location where event information is displayed and the period for storing records in the kaveventslog.nsf database. You can configure the Event log settings both for a group of servers using a profile and for each server individually. The file to be used to save the Event log can only be specified in the server settings. This setting cannot be changed using the profile.

Statistical information is recorded about objects scanned for viruses, threats detected and actions taken on them. Statistical information is kept separately for each protection component. You can specify what type of information should be saved in statistics while configuring the profile settings for the mail protection, replication protection, and database scanning tasks. By default, the application stores information obtained from scanning infected, protected, and not scanned objects with the reasons why they could not be scanned.

By default, records in the Event log and statistics database are stored for 30 days. You can change the storage time of event records and statistics using both profile and server settings (see sections "Configuring the Event log", "Configuring statistics"). Records are deleted automatically on expiry of the specified time period.

Information from the Event log and statistics database can be deleted manually for each protected server.

Events recorded on the protected server during the current application session can be displayed on the Lotus Domino server console and saved in a text file. By default, five cyclically rewritable log files are used with the name server(N).log, where N is the sequential number of the log. The log files are located on the protected server in logs service directory only for this server.

You can change the number of log files in use and their names and maximum size using the settings in the notes.ini configuration file.

In this Help section

Configuring the Event log

Configuring the statistics settings

Viewing the Event log and statistics database

Deleting information from the Event log and statistics

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.