Kaspersky IoT Secure Gateway 100

Managing the Kaspersky IoT Secure Gateway 100 health log

Kaspersky IoT Secure Gateway 100 lets you configure the settings of the system health log. Health log settings are configured in the .log configuration file, which is located in the TGW-HW-LOG section of the SD card. The SD card is included in the distribution kit. System health logs are stored in the folder /logs.

To configure the Kaspersky IoT Secure Gateway 100 health log settings, do the following in the .log configuration file:

1. In the LogFileSizeLimit parameter, enter the maximum size (in bytes) of one system health log file. For example, LogFileSizeLimit=100000000.
2. In the DirectorySizeLimit parameter, enter the maximum size (in bytes) of the folder containing all system health log files. For example, DirectorySizeLimit=1500000000.

   Kaspersky IoT Secure Gateway 100 does not process full disk space warning events by default. For this reason, make sure that the configured size settings for the log storage folder are appropriate for the available disk space of the device.

3. Save the changes in the .log file.

If the .log file is absent, the system log will be deemed disabled and the log will not be written to the /logs folder.

The settings defined in the .log file will be applied the next time Kaspersky IoT Secure Gateway 100 is started.

Rules for writing and rotating log files

Log files are written and rotated according to the following rules:

• If the size limit of one log file is exceeded during data write operations, a new file is created and the data is written to the new file.
• If a data string could not be completely written due to the size limit of one log file, a new file is created, the data string is written to this new file, and subsequent data will be written to the new file.
• If the size limits of one log file and all log files are exceeded when writing a data string, the old log file is deleted, a new file is created, and subsequent data will be written to this new file.
• If the limit for all log files is exceeded when writing a data string, the old file is deleted and the data string is written to the current file.
• Old log files are deleted in such a way to ensure that there is sufficient memory for writing a data string.
• A new file for log writing is created at the beginning of each work session (gateway loading/restart).

Logging data

The following information is logged:

• Initialization status of hardware components
• OS load status
• Initialization status of system components
• Initialization and operating status:
  • Network services
  • Data repository
  • System logging service
  • Application component:
    • OPC UA client and manager
    • MindSphere agent and manager
    • Data transfer component
• Transmitted data elements
• Initialization and loading errors