Collecting Debug Logs
When reaching out for debugging assistance with the Unified SDK, please collect and provide the following logs:
UnifiedSDK Logs
Logs contain information about the Unified SDK service.
Default location: C:\ProgramData\UnifiedSDK.Service\logs\UnifiedSDK.Service.log
Or you can specify where UnifiedSDK service should store log files by options -lf "<path to the log file>"
or -d "<path to the data folder>"
.
Note, that by default UnifiedSDK service writes only Error logs and it can be not enough for investigation. You can configure logging level with -ll
option (Error
, Information
or Debug
) when you installing UnifiedSDK service.
Note, that with Debug level you will take all requests and responses without any encryption. All keys and token will be logged to the log file. So we recommend to use default option settings (only error logging) or Information
(only general data logging) in production.
Protocols Logs
Protocol logs can be enabled via StartVpnRequest
using EnableTunnelLogging
property.
Once enabled, protocol logs will be stored at the following locations:
Hydra
C:\ProgramData\UnifiedSDK.Service\system\logs\hydra.log
WireGuard
C:\Program Files (x86)\%your_app_folder%\Executable\Wireguard\log.bin
Windows Event Logs
Some events, such as unexpected service drops, are logged to Windows Event Logs.
To access these logs:
Open Event Viewer by running:
%windir%\system32\eventvwr.msc /s
Navigate to
Windows Logs
>Application
Look for log entries with the source
UnifiedSDK.Service
Memory Dumps
More information about memory dumps can be found here.
Last updated