Ask the Community
Groups
Enabling Debug Logging for Network Monitor - Connect IT Community | Kaseya
<main> <article class="userContent"> <p>There are various issues in Network Monitor when enabling debug logging will provide more information about an issue, especially when there isn't a clear indication of a root cause from other logging, like Event Viewer and System Log. </p> <p> </p> <p><strong>On the KServer</strong></p> <p>To enable debug logging, please navigate to <Windows Drive>\Kaseya\knm, open the init.cfg file and add the following lines:</p> <div>vsa_debug_log=1<br>msmq_eventmessage_log=all<br>msmq_responsemessage_log=all<br>log_level=2</div> <div> </div> <div>In Kaseya 7.0, the debug logs will be written to <Windows Drive>\Kaseya\knm\logs. The debug files are:</div> <div> <ul><li>debug.txt</li> <li>response_message_type_log.txt</li> <li>websocket_debug.txt</li> </ul><p> </p> </div> <div>In Kaseya 8.0 and above, the debug logs will be written to <Windows Drive>\Kaseya\Logs\Services. The debug files are:</div> <div> <ul><li>KaseyaNetworkMonitor.txt</li> <li>KaseyaNetworkMonitor.response_message_type_log.txt</li> <li>KaseyaNetworkMonitor.websocket_debug.txt</li> </ul><p><strong>On the Gateways</strong></p> <p>To enable debug logging for the KNM gateway, the init.cfg file is located in the <Windows Drive>\[Program Files|Program Files (x86)]\Kaseya\<Agent>\knm_gateway directory on the agent machine where the gateway is installed. Add the line:</p> <p>log_level=2</p> <p>For KNM gateways on the agent machines, the debug logs will be written to <Windows Drive>\[Program Files|Program Files (x86)]\Kaseya\<Agent>\knm_gateway\logs.</p> <p><strong>The Network Monitor services do not need to be restarted and should start writing immediately.</strong></p> <p><strong>Please note that these steps for the KServer are only applicable to On-Premise customers.</strong></p> <p> </p> </div> </article> </main>