Discussion: do we need logging at the domain API layer?

[saurabhnanda]

No description provided.

[jfoutz]

the handlers run in IO. i'm pretty sure logging is just a fancier form of lift.lift.putStrLn there are some questions to answer about how to pass the file handle around, to ensure everything can log to the same file. also perhaps log rotation.

In a production system sometimes logging is necessary. For example, access logs for advertising tracking. In general, if the logs should be automatically be processed for reporting, or whatever they're needed for.

If there's something you specifically need tracked, can't that just be put in the database directly?

I understand putStrLn debugging, I don't think it's a good idea to leave those print statements in production, because it'll fill up disks with not much use.

I see the value in it, if others have strong feelings about it, but i vote no.