Balancer logging

April 11, 2024

ID 214599

Balancer uses the logging parameters specified in kl_balancer_log.conf.

When deploying Balancer to a computer without Kaspersky CyberTrace, copy kl_balancer_log.conf from the bin directory to the same directory as the Balancer binary file.

Log files name format

Balancer writes messages to files named "kl_balancer-<pid>-<date_time>.log".

Log file contents

If the err logging level is used, Balancer writes the following information to the log:

  • Errors occurred during Balancer initialization.
  • Errors occurred while establishing connections with Kaspersky CyberTrace instances.
  • Errors occurred while establishing connection with a REST API client.
  • Errors occurred while receiving the results of events matching.
  • Service alerts from Kaspersky CyberTrace.

If the inf logging level is used, Balancer writes the following information to the log:

  • Balancer version, OS version, and PID of Balancer process.
  • Information to be written at the err logging level.
  • Establishing or closing connections with Kaspersky CyberTrace instances.
  • Establishing or closing connection with a REST API client.
  • Receiving and sending requests and responses to and from Kaspersky CyberTrace instances.
  • Receiving and sending requests and responses to and from a REST API client.
  • Switching Balancer to ReplyBack mode.
  • Switching Balancer to operation within the EPS limit.
  • Switching Balancer to operation without the EPS limit.
  • Average EPS per hour.
  • Changes in the Kaspersky CyberTrace licensing level.

If the dbg logging level is used, Balancer writes the following information to the log:

  • Information to be written at the inf logging level.
  • The values of Balancer configuration file parameters.

    This information is logged on Balancer initialization.

  • Incoming events processed by Balancer.

If there is no kl_balancer_log.conf file in the directory of Balancer binary file, Balancer will not write logs.

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.