Rider Debugger Log Verbosity Configuration for Deployment Diagnostics

Rider Debugger Log Configuration

To increase Rider's internal debugger log verbosity to the maximum level, you must use the Debug Log Settings menu rather than a single registry key. Because Rider's architecture splits the IDE frontend from the ReSharper backend, diagnostics for remote deployment failures are distributed across multiple files.

Configuration Steps

1. Navigate to Help | Diagnostic Tools | Debug Log Settings...
2. Enter the following categories to enable trace-level logging for the debugger and the remote client protocol:

   #com.jetbrains.rider:trace
   #com.jetbrains.rdclient:trace

3. Alternatively, use Help | Diagnostic Tools | Choose Log Scenarios and select the Debugger scenario for a predefined set of trace categories.
4. Reproduce the deployment failure, then immediately remove these settings or select Disable All in the Log Scenarios menu to avoid significant performance degradation and disk space exhaustion.

Log Rotation and Correlation

Rider does not expose a user-configurable maximum size or rotation policy for idea.log; the platform utilizes a built-in rolling appender that rotates logs into numbered files automatically. Due to the high volume of data generated by trace verbosity, it is recommended to capture only the specific window of the failure.

To correlate deployment failures, idea.log alone is insufficient. You must use Help | Collect Logs and Diagnostic Data. This generates a ZIP archive containing both the frontend idea.log and the backend.log (ReSharper host log). Correlation is achieved by matching timestamps of the deployment action across both files to determine if the failure occurred during the protocol handshake or the agent execution.

Remote Debugger Agent Port

Rider does not expose the remote debugger agent's listening port in the UI. In standard remote debugging workflows, the port is negotiated automatically via the SSH/SFTP deployment connection. Manual port specification is typically only required for custom agent launch scenarios via external configuration files or environment variables, which vary by runtime version.

Assumptions and Verification

These instructions assume a recent version of Rider (2023.x or newer). To verify the settings are active, check the idea.log file after applying the changes to confirm the log level for the specified categories has shifted to TRACE.

Missing Diagnostic Detail: Please provide the operating system of the remote target (e.g., Linux, Windows, or a specific container), as this determines whether the failure is likely a port-binding restriction or a filesystem permission issue during agent deployment.