Rider Debugger Log Verbosity Configuration for Deployment Diagnostics

Rider Debugger Log Verbosity

Goal: capture sufficient IDE‑level diagnostics to diagnose a failed deployment when using Rider’s remote debugging feature.

Constraints: Rider uses a decoupled architecture where the frontend IDE communicates with the ReSharper backend. Log verbosity is controlled via the registry and the Idea.log file is generated by the frontend. Some settings are only available on Windows; macOS/Linux require CLI adjustments. The remote debugger agent must be reachable on a specific port, but the port configuration is not exposed directly in the UI.

Uncertainty: Which registry key or configuration file should be edited to enable the highest level of debug output without impacting performance? How does the chosen verbosity level affect the size of the Idea.log file and the ability to correlate deployment failures?

Questions

• What exact registry entry or configuration setting should be modified to increase Rider’s internal debugger log verbosity to its maximum level?
• Is there a recommended maximum size or rotation policy for Idea.log when running remote debugging sessions?
• Does Rider expose the remote debugger agent’s listening port in the UI, or must it be set manually via a configuration file?