Improve logging

Right now we’re seeing:

2014-11-28 17:31:53,074 [PID 12] INFO - Running job Every 90 seconds do threaded(<function quoter at 0x7f739e3e00c8>) (last run: 2014-11-28 17:30:22, next run: 2014-11-28 17:31:5$

It’d be nice if this would be slightly more concise. Eg.

2014-11-28 17:31:53,074 [PID 12] INFO - Running every 90 seconds 'threaded(<function quoter at 0x7f739e3e00c8>)' (last run: 17:30:22, next run: 17:31:50)

[DieterKoblenz]

Is there a way to disable logging all together? I use logging in my application and these logs (for example the job I run every 5 seconds) interfere a lot. (I’ve set my log up as a csv file which I can import in an mysql database every day)

[SijmenHuizenga]

Hi all! Thank you all for the good suggestions. Here is an update on the current state:

• Log level for all messages is now DEBUG, by default you won’t see logs. You can control the visibility of logs through the python logger.
• The subject of logging received its own documentation page here: https://schedule.readthedocs.io/en/latest/logging.html I welcome everyone to create PR’s adding more examples to that page
• Thanks to @zcking we now have PR #193, which adds some more log messages

On the subject of hiding sensitive information from log messages as raised by @zspatter; I don’t think we should add a built-in switch for removing args from the logs as only few people need this and we want to keep this library simple. However, I would very much like to add add a good example of how to implement this in the documentation. We can experiment on the best way to do this: overriding some method or adding a decorator as described here, I’m open to suggestions. To track this, I’ve created #402