Unnecessary log when trading multiple symbols with multiple grid trade rows

[uhliksk]

Is your proposal related to a problem?

My SSD is wearing pretty fast because of massive log generated by binance-bot docker container. For the last 24 hours more than 650 GB of log has been rotated which extrapolated is about 235 TB per year. The most data is created by Start step and Finish step events even by symbols not actually traded because of max. open trades limit. Those data are repetitive without the changes significant to track.

Describe the solution you'd like

The Start step operation should not save the full data into log and it should just store actual state into temporary variable. Then when Finish step is reached the temporary variable should be compared with the actual data and only a modified values should be written into log. This way a significant portion of the log will be cut off. Full data should be saved just at the start of cycle or even less frequently.

Describe alternatives you've considered

I had to disable logging at all in my production environment which is very bad decision as the ability to track any issues is very limited without the log.

Additional context

Massive log may be responsible for missed sell orders described in #451 as it can cause undesirable delayed writes to database or even unexpected hardware or driver failures.

[uhliksk]

Delayed writes indirectly solved in #562 as events are processed sequentially and thus timing doesn't matter anymore. As intensive logging is solved by logging errors only I don't need this to be fixed anymore.