Skip to content

Improve logs

I have some difficulties to understand the logs (on the server side).

Below is just an example, when fetching the operations for my main bank, but there are probably a lot of places where the logs could be more precise.

[2017-04-26 15:07:26:725] info - sources/weboob | Calling weboob: command test...
[2017-04-26 15:07:27:103] info - sources/weboob | exited with code 0
[2017-04-26 15:07:27:104] info - sources/weboob | Calling weboob: command transactions...
[2017-04-26 15:09:07:362] info - sources/weboob | exited with code 0
[2017-04-26 15:09:07:411] info - sources/weboob | OK: weboob exited normally with non-empty JSON content.
[2017-04-26 15:10:13:169] info - accounts-manager | Updating 'last checked' for linked accounts...
[2017-04-26 15:10:13:436] info - accounts-manager | Informing user new operations have been imported...
[2017-04-26 15:10:13:436] info - accounts-manager | Checking alerts for accounts balance...
[2017-04-26 15:10:13:437] info - accounts-manager | Checking alerts for operations amount...
[2017-04-26 15:10:13:689] info - accounts-manager | Post process: done.
  • The dates should probably be in UTC ?
  • Calling weboob: command test... should explain what it does : testing that the weboob version is correct and that the python module is available
  • What happens between the time weboob returned the result and Updating 'last checked' for linked accounts... ? We should log that once the have the results from weboob we will now check if they do no already exist in database
  • Informing user new operations have been imported... we should add something like "if there are new operations" (or even tell right now if there were new operations if we know it)
  • Add the name of backend and modules in logs at the beginning of poll