Trace files of the Integration Server and Integration Server Console

Information about the operation of the Integration Server and the Integration Server Console may be recorded in the following trace files:

• %ProgramData%\Kaspersky Lab\VIISLA\logs\viisla_service_loader.log – Integration Server trace file. The file does not contain personal data.
• %ProgramData%\Kaspersky Lab\VIISLA\logs\service.log – Integration Server trace file.
• %ProgramData%\Kaspersky Lab\VIISLA Console\logs\console.log – the trace file of the Integration Server Console.

Trace files are created only after you have enabled the logging of information on the Integration Server operation. By default, information about the operation of the Integration Server and Integration Server Console is not saved.

You can enable the logging of information to Integration Server and Integration Server Console trace files, and change the verbosity level of information in trace files by using the following configuration files:

• %ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\appsettings.logging.json – for the Integration Server trace file.
• %ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA Console\NLog.config – for the Integration Server Console trace file.

Contact Technical Support representatives for details.

Trace files are moved to an archive folder (%ProgramData%\Kaspersky Lab\VIISLA\logs\archives) when the file size reaches 5 MB. Up to 10 files are stored in the archive folder. Once this number is reached, older files are deleted.

Access to the folder where trace files are saved is restricted by using an ACL. Administrator rights are required to access this folder.

If you change the default folder for storing trace files, Kaspersky Security does not control access to trace files. It is recommended to protect the information from unauthorized access.

The following information may be saved in the Integration Server trace file:

• Diagnostic information about the operation of the Integration Server, its workload, and the results of a data integrity check.
• Headers and contents of HTTP requests that are sent and received by the Integration Server during its operation.
• IP addresses of SVMs and protected virtual machines, and the IP address of the device hosting the Kaspersky Security Center Administration Console if the Kaspersky Security Center Administration Console is installed separately from the Kaspersky Security Center Administration Server.
• Tracing of requests to the Integration Server.
• Description of exclusions and errors that occurred when working with internal subsystems and external services.
• Names of internal Integration Server accounts.
• Names of accounts that are used to connect the Integration Server to virtual infrastructure objects.
• Depending on the type of virtual infrastructure:
  • IP addresses or fully qualified domain names (FQDN) of hypervisors or virtual infrastructure administration servers to which the Integration Server connects.
  • IP addresses or fully qualified domain names (FQDN) of the Keystone microservice or other cloud infrastructure microservices to which the Integration Server connects.
• If Kaspersky Security is used in multitenancy mode:
  • Names and identifiers of the tenants registered in the Integration Server database.
  • Account names of Kaspersky Security Center virtual Administration Servers administrators.
  • Identifiers and IP addresses of the tenant virtual machines.

The following information may be saved in the Integration Server Console trace file:

• Diagnostic information about the operation of the Integration Server Console.
• Tracing of command line parameters and results of checking them.
• Headers and contents of HTTP requests that are sent and received by the Integration Server Console during its operation.
• Information about navigations through sections of the Integration Server Console and working with interface elements.
• IP address of the Kaspersky Security Center Administration Server.
• Port numbers for interaction with the Kaspersky Security Center Administration Server through the Kaspersky Security Center Network Agent.
• Description of exclusions and errors that occurred when working with internal subsystems and external services.
• Names of internal Integration Server accounts.
• Names of accounts that are used to connect the Integration Server to virtual infrastructure objects.
• Depending on the type of virtual infrastructure:
  • IP addresses or fully qualified domain names (FQDN) of hypervisors or virtual infrastructure administration servers to which the Integration Server connects.
  • IP addresses or fully qualified domain names (FQDN) of the Keystone microservice or other cloud infrastructure microservices to which the Integration Server connects.
• If Kaspersky Security is used in multitenancy mode, the names of tenants registered in the Integration Server database are listed.

You can use Integration Server trace files and Integration Server Console trace files when contacting the Technical Support. The information recorded in trace files may be needed for analysis and identification of the causes of errors in the operation of the Integration Server.

Integration Server trace files and Integration Server Console trace files are not automatically sent to Kaspersky.

Page top