Reduce Debug Level on CLI console

To limit the log level to only error messages when backtesting locally with Lean, you should ensure the following steps are correctly implemented:

1. Configuring config.json:

   • Make sure your config.json file includes the "debugging" section with the "log-level": "Error" setting. It should look like this:

     {
       "debugging": {
         "log-level": "Error"
       }
     }
     

2. Using ConsoleErrorLogHandler:

   • The ConsoleErrorLogHandler is a subclass of ConsoleLogHandler that only logs error messages. Ensure that your local Lean environment is configured to use this handler. This handler suppresses debug and trace messages by overriding the debug and trace methods to do nothing.

3. Lean Environment Configuration:

   • Verify that your Lean environment is set up to respect the config.json settings. If there are any custom logging configurations or handlers, they might override these settings.

4. Restart Lean Environment:

   • After making changes to the config.json, restart your local Lean environment to apply the new settings.

5. Check for Overrides:

   • Review any custom scripts or configurations that might override the config.json settings. Ensure no other logging handlers are being used that could affect the logging level.

6. Testing:

   • If the issue persists, try testing the configuration on a different machine or environment to rule out local setup issues.

By following these steps, you should be able to limit the log output to only error messages during local backtesting with Lean. If you continue to encounter issues, consider consulting the Lean documentation or community forums for further troubleshooting specific to your setup.

Sources: Debugging Tools - QuantConnect.com, Debugging - QuantConnect.com, Logging - QuantConnect.com