Nov 6, 2017

Getting logging right is very important to make sure you have enough insight to be able to diagnose issues, but not too much that it might cause problems

In production, it is often advisable to limit the amount of logging to WARNING level for most packages, and INFO only for those which have been determined to be important enough, or for your own application code.

Excessive logging can take CPU cycles away from your application, or cause issues with disk space. It is also worth configuring your logs to rotate every day, rather than by file size. Excessive logging can cause the file to rotate too often to be useful.