Backtest logging

Hi Jared, I realise this is 5 years old now, but....

What are the "smarter logging techniques" that you recommend?

Is there a way to delete logs from earlier backtests?

Thanks.

Hi Christopher,

I suggest logging only important events, meaning focusing on the change events rather logging every time loop. In addition, try Charting when dealing with numerical data that makes sense to be plotted. Furthermore, we increase logging limits based on the users' tier. Using the Debugger might be another way to reduce the need for Logging.

Deleting old backtests won't free logging quota because it's not about disk space, rather it's about restricting logging prices to prevent data theft.

Best,
Shile Wen

Shile Wen if we accidentally use up our log quota (e.g. by running a long backtest without commenting out some Debug statements used for debugging with a shorter backtest), is there any recourse?  Or do we just have to wait 24 hours until the quota resets?

Sorry, not at this time =( I can see why you'd want that though. We can add resetting logs as a Friday project for one of the team. 

I dont see any logs when a backtest has an error. The console is all rate-limiting messages so the logs I am looking for arne't there. Where is the link to get the logs from a cloud backtest before an error?

Hey Non Compete,

you can't really access the logs in the cloud if there was an error in your code, try to debug what you're trying to log so that it prints into the console automatically even if there's an error.

In this case you could also debug your code and add some break points to check if there's any information or you could add if statements to check if there's any values available.

Hope it helps ;)