Skip to content

Accessing the logs

Linux

Info

This section refers to clients running version 3.2 or above. For older supported clients, see the deprecated Linux Logs documentation.

Client logs are written to /var/log/cyberhive-connect.log.

The log file is rotated when it reaches 64MB in size. Therefore the /var/log/cyberhive-connect.log.0 file might contain relevant log output if the log has been recently rotated.

Some limited information about the application can also be found in /var/log/syslog.

Windows (Desktop)

Info

This section refers to clients running version 3.2 or above. For older supported clients, see the deprecated Windows Logs documentation.

Save log file

In order to access the Connect logs, you can use the Save Log File... button in the Advanced section of the ConnectUI program:

Save Log File...

The Save Log File... button is only available when Connect is activated.

Setting the logging level

The logging level defines the verbosity of the logging generated by the Connect client; when a log message is logged at a lower level than the defined logging level, it is discarded and not written to the Event Log.

The logging levels are defined as:

  • error
  • warn
  • info
  • debug
  • trace

The logging level is read from the Registry when the Service starts. To change the values you will need to use the Windows Registry Editor:

  • Press Win+R and type regedit into the text field.
  • Navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\CyberHive\Connect.
  • Add or edit the string value called LoggingLevel and set the level as defined in the list above. The case of string is unimportant, so you can use either info or Info. When an invalid value is set, the default level of info will be used.

Windows Server 2012 R2

Info

This section refers to clients running version 3.2 or above. For older supported clients, see the deprecated Windows Logs documentation.

A "Save Logs" option is available via the Connect UI, which is not supported on Windows Server 2012 R2.

To access the logs from within an Admin Command Prompt, change to the directory where the client logs are stored.

> cd C\Windows\System32\config\systemprofile\AppData\Local\CyberHive\Connect
> dir cyberhive-connect.log*
 Volume in drive C has no label.
 Volume Serial Number is 8AC8-8161

 Directory of C:\Windows\System32\config\systemprofile\AppData\Local\CyberHive\Connect

09/04/2024  10:23        61,442,588 cyberhive-connect.log
09/04/2024  03:31        67,109,247 cyberhive-connect.log.0
08/04/2024  21:20        67,109,387 cyberhive-connect.log.1
08/04/2024  15:11        67,109,494 cyberhive-connect.log.2
               4 File(s)    262,770,716 bytes
               0 Dir(s)  126,104,592,384 bytes free

Setting the logging level

The logging level defines the verbosity of the logging generated by the Connect client; when a log message is logged at a lower level than the defined logging level, it is discarded and not written to the Event Log.

The logging levels are defined as:

  • error
  • warn
  • info
  • debug
  • trace

The logging level is read from the Registry when the Service starts. To change the values you will need to use the Windows Registry Editor:

  • Press Win+R and type regedit into the text field.
  • Navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\CyberHive\Connect.
  • Add or edit the string value called LoggingLevel and set the level as defined in the list above. The case of string is unimportant, so you can use either info or Info. When an invalid value is set, the default level of info will be used.