You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing v2 strategy using multiple controller configs, we observed that the log file is shared and its difficult to read or trace logs for a particular controller without looking into other controller events. This would also cause increase on the size of log files specially when hit by an issue or exchange related problems.
Impact
So when you create a script config with multiple controllers like below:
Instead of sharing all logs inside the script file name v2_generic_with_controllers.log, create log files that point to each of controller yml files, e.g conf_market_making.dman_maker_1.log
Additional context
No response
The text was updated successfully, but these errors were encountered:
Feature Suggestion
When testing v2 strategy using multiple controller configs, we observed that the log file is shared and its difficult to read or trace logs for a particular controller without looking into other controller events. This would also cause increase on the size of log files specially when hit by an issue or exchange related problems.
Impact
So when you create a script config with multiple controllers like below:
Instead of sharing all logs inside the script file name
v2_generic_with_controllers.log
, create log files that point to each of controller yml files, e.gconf_market_making.dman_maker_1.log
Additional context
No response
The text was updated successfully, but these errors were encountered: