[FEATURE] Store logs of UI gekkos

[GuyPaddock]

I know that running via CLI dumps trade advice / debug info to standard out. But, where does this info go (if anywhere) when running in UI mode?

[askmike]

Gekko UI doesn't log the same data unfortunately. How would you like to see it work? If you run 3 gekkos through the UI the logs would all be messed up.

[GuyPaddock]

Hmmm. Well... when debugging an issue I'm seeing with the server while using the UI, it would still be great if I can enable logging temporarily, even if the logs would be very busy. Similar to how you can turn on debug logging for CLI, it'd be great to have an option to toggle it on. If I happen to be stupid and run multiple Gekkos through the UI, that's on me.

[GuyPaddock]

Alternatively, what if a new log file was generated for each Gekko?

[thegamecat]

This is largely why I write backtests and live buy/sells to my own csvs.

I would be attaching a session id to each gekko and either running a different log file for each session, or one log which each activity identified as a session.

[askmike]

More people have been asking for this, we can add logging. What about this?

• We don't allow logging whilst backtesting in the UI
• When starting a live gekko there is an advanced section where people can toggle on "log-debug-output-to-file"?

Though some plugins (like the performance analyzer) either log to stdout OR upstream to parent process, so we would have to change some stuff around.

[thegamecat]

I don't like this approach to not log backtests - it's actually causing me an issue here: #970

We should be writing logs for everything, maybe they go to a different folder for backtests but still, they should happen.

For reference - I write all buy/sell/strategy outputs to a strategy_log folder, for example (rename to csv):

test-all-1-poloniex-USDT-ETH-1502697116356.txt

test-all-1-poloniex-USDT-ETH-2017-08-14T07-51-56.384Z-roundtrips.txt

[askmike]

What about logging trade info to CSV regardless (also an advanced option)? I see this as something different than logs.

…

On 16 Aug 2017 10:04, "thegamecat" ***@***.***> wrote: I don't like this approach to not log backtests - it's actually causing me an issue here: #970 <#970> We should be writing logs for everything, maybe they go to a different folder for backtests but still, they should happen. I write all logs to a strategy_log folder, for example (rename to csv): test-all-1-poloniex-USDT-ETH-1502697116356.txt <https://github.com/askmike/gekko/files/1227640/test-all-1-poloniex-USDT-ETH-1502697116356.txt> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#972 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD-nFvLNbguyT4iY2rSS-PLo-o70Gks5sYrCmgaJpZM4O4H8E> .

[thegamecat]

Totally agree about trades being different to logs.

What I use to eval when not using the GA is:

1. Trades / buys and sells, times, balance etc.
2. Every single tick logged with indicator, price, buys and sells

[askmike]

Can you check out the develop branch? All logging for UI gekkos are stored in the /logs folder. Note that this not include trade and roundtrip information from the performanceAnalyzer (just from the portfolioManager) at the moment.