Improve printer/print logging
peteruithoven opened this issue · 0 comments
peteruithoven commented
Per print part we're logging:
03-09 15:32:54 [ENTR] (info) : POST request for printer/print (remote IP/port: 192.168.10.179/52586)
03-09 15:32:54 [APRN] (info) : API:printer/print
03-09 15:32:54 [APRN] (info) : hasControl: true
09-03 15:32:54 [COMM] (info) : starting transmit of 89179 bytes of gcode data, maximum packet size is 1016
09-03 15:32:56 [COMM] (info) : gcode data sent in 90 packets (2672 msecs)
We can probably remove the API:printer/print
.
When there isn't control a error is probably logged, or the response, so we could also remove the hasControl logging.
I would move those COMM logs to a higher log level, like debug
.
It might however be insightful to log print sequence numbers.