Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2 strategy - support for creating separate controller log files #6981

Open
rapcmia opened this issue Apr 24, 2024 · 0 comments
Open

V2 strategy - support for creating separate controller log files #6981

rapcmia opened this issue Apr 24, 2024 · 0 comments
Labels
enhancement Upgrade or improvement to an existing hummingbot feature v2_strategies

Comments

@rapcmia
Copy link
Contributor

rapcmia commented Apr 24, 2024

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:

markets: {}
candles_config: []
controllers_config:
# - conf_directional_trading.bollinger_v1_1.yml
- conf_directional_trading.trend_follower_v1_1.yml
- conf_directional_trading.dman_v3_1.yml
- conf_market_making.dman_maker_1.yml
config_update_interval: 60
script_file_name: v2_generic_with_controllers.py

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

@rapcmia rapcmia added enhancement Upgrade or improvement to an existing hummingbot feature v2_strategies labels Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Upgrade or improvement to an existing hummingbot feature v2_strategies
Projects
Status: No status
Development

No branches or pull requests

1 participant