Selecting the Docker container log verbosity

Kaspersky SD-WAN automatically keeps logs of Docker containers, which are used to deploy and support solution components. You can select the level of detail of these logs for monitoring containers and quickly recovering from faults.

To select Docker container log verbosity:

1. In the lower part of the menu, click the settings icon → Log settings.

   This opens a page displaying a table of Docker containers. Information about Docker containers is displayed in the following columns of the table:

   • Module name is the name of the Docker container.
   • Logging level is the Docker container log verbosity:
2. Select the Docker container verbosity level in one of the following ways:
   • If you want to select the verbosity level of all Docker containers, click the corresponding button in the General logging level section.
   • If you want to select the verbosity level for an individual Docker container, click the corresponding button next to it.

   You can select the following verbosity levels for Docker containers:

   • TRACE to have the log include the most complete information about the operation and condition of the module and its variables. You can use this level of detail for observing code execution, as well as for diagnostics and detailed analysis of errors that occur during development.
   • DEBUG to have the log include the information necessary for debugging the module, such as the status of operations and values of variables. You can use this level of detail to diagnose errors and analyze module behavior.
   • INFO to have the log include general information necessary for understanding the functioning of the module, for example, confirmations of operations. You can use this level of detail to track the progress of the execution of the module. This level of detail is selected by default for all containers.
   • WARN to have the log include information about incidents that are not errors, but may compromise the operation of the container and require your intervention, such as problems with settings and deprecated functions. You can use this level of detail to prevent potential errors.
   • ERROR to have the log include information about errors that occur during the execution of the code and require your intervention. An error message can contain information about the part of the container in which the error occurred, as well as detailed information about the error. You can use this level of detail to resolve occurring errors.