--- title: "Guide to Collecting Debug Logs in StellarProtect and StellarProtect Legacy Mode" slug: "guide-to-collecting-debug-logs-in-stellarprotect-and-stellarprotect-legacy-mode" description: "EndpointProtection/StellarSeries/ready_to_release/HelpCenter" updated: 2025-01-21T10:10:03Z published: 2025-01-21T10:10:03Z canonical: "help.txone.com/guide-to-collecting-debug-logs-in-stellarprotect-and-stellarprotect-legacy-mode" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.txone.com/llms.txt > Use this file to discover all available pages before exploring further. # Guide to Collecting Debug Logs in StellarProtect and StellarProtect Legacy Mode ### **Summary** This guide outlines the steps to collect debug logs in **StellarProtect** and **StellarProtect Legacy Mode**, using both the RDQA console and directly from the agents --- ### **Details** ## Collecting Logs Using RDQA The RDQA system enables administrators to remotely collect debug logs from StellarProtect and StellarProtect Legacy Mode agents via the StellarOne management console. **Step 1: Access the RDQA Page** - Open your web browser and navigate to https:///rdqa. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28307%29.png) **Step 2: Select the Agent** - Click on the StellarProtect or StellarProtect (Legacy Mode) tab to access the list of managed agents. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28308%29.png) **Step 3: Select Debug Logging** - Enable Debug Logging: ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28309%29.png) - The command to enable debug logging is sent to the agent: ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28310%29.png) - It takes a few seconds for it to be enabled. Once done, this will be confirmed in the Debug Logging Status column: ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28311%29.png) **Step 4: Reproduce the Issue** - Perform the actions that recreate the issue on the agent. **Step 5: Collect the Logs** - Click the **Collect Debug Information** button. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28312%29.png) - Wait until it indicates that the logs are ready to be downloaded. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28313%29.png) **Step 6: Disable the Debugging** - Once the logs are downloaded, the logging status automatically reverts to **disabled**. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28314%29.png) --- ## Collecting Logs Directly from StellarProtect Agents When the RDQA console is not an option, it’s possible to collect logs directly from StellarProtect agents. **Step 1: Locate and Execute the op_diagnostic Tool** - Navigate to the agent's installation directory. - Execute op_diagnostic.exe. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28315%29.png) **Step 2: Set the Debug Level** - Select the debug level **Trace** and click **Apply**. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28316%29.png) **Step 3: Reproduce the Issue** - Perform the actions that recreate the issue on the agent. **Step 4: Collect the Logs** - Click the **Collect Debug Log** button. - Wait for the "Troubleshooting data collected" message to appear. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28317%29.png) - Click **Open Folder** to access the archived ZIP file. **Step 5: Restore the Debug Level** - Change the debug level back to Error and click Apply. **Warning:** Ensure you run op_diagnostic.exe from the correct directory to avoid errors. --- ## Collecting Logs Directly from StellarProtect Legacy Agents When the RDQA console is not an option, it’s possible to collect logs directly from StellarProtect Legacy agents. **Step 1: Locate the WKSupportTool ** - Navigate to the agent's installation directory: \WKSupportTool.exe. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28318%29.png) **Step 2: Set the Debug Level** - Run WKSupportTool.exe. - On the **[A] Debug** page, select: - **Output error logs and debug information** (optional). - **Output driver debug information**. - Click **Apply**. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28319%29.png) **Step 3: Reproduce the Issue** - Perform the actions that recreate the issue on the agent. **Step 4: Collect the Logs** - Click the **Collect Debug Log** button. Wait until the "Troubleshooting data collected" message appears. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28320%29.png) - Click **Open Folder** to access the archived ZIP file. **Step 5: Restore the Debug Log Level** - Change the settings back to **Output only errors** and click **Apply**. ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%28321%29.png) **Warning:** Ensure you are in the correct installation directory before running WKSupportTool.exe to avoid issues during log collection. --- For support assistance, please contact us at support@txone.com or your support provider.