need logging; check that logging is on for live instance

[dcloud]

Are we using LoggingAdapter to track activity? Looks like no. I guess this is an alternative to tracking via the MongoAdapter, but needs review, imo.

[jcarbaugh]

MongoDBAdapter is now configured.

[jcarbaugh]

We can turn LoggingAdapter on too, it's just not in the default list. It would write to the Heroku logs so we couldn't use it as a persistent store, but good enough for watching stuff live on the server.

[dcloud]

Okay, let's have both!

[dcloud]

I'm seeing a few lines in the log like INFO running BillService at 2014-01-29T15:35:16.567259, so I guess this is working. Ultimately we need some ways of seeing if objects weren't properly processed or processed multiple times or whatever. I don't know if that should be just in logs or if we can generate some reports for such things.

[jcarbaugh]

Right now it is only logging on successful sends. Feel free to add whatever
logging statements you want earlier in the process to see what's going on.

On Wed, Jan 29, 2014 at 11:07 AM, Daniel Cloud notifications@github.comwrote:

I'm seeing a few lines in the log like INFO running BillService at
2014-01-29T15:35:16.567259, so I guess this is working. Ultimately we
need some ways of seeing if objects weren't properly processed or processed
multiple times or whatever. I don't know if that should be just in logs or
if we can generate some reports for such things.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-33598641
.

[jcarbaugh]

Actually, that won't be as easy as I first thought since the current logging is at the adapter level, so it will only ever see things that are actually being sent out.

[jcarbaugh]

There is a logger in services.py that can be used. It just needs to have the log level set to logging.INFO in order to see it in the logs.