Repository navigation
Polish up logging #157
Description
Activity
Also, a question that comes to mind: do we want to override the default Python logger formatting? considering Crawlee is a library
Also, a question that comes to mind: do we want to override the default Python logger formatting? considering Crawlee is a library
And also a framework... It is not unusual for frameworks to define their own loggers. But if a client wants to override that, we should make it easy.
Reacted by Vlada DusekWe should also review the debug logs to ensure they provide some value. Suppose a user switches from info to debug level. In that case, they should get some meaningful information (e.g., about sending this request, processing this response, storing this item into the dataset, ...) that could help them (currently it is quite random and maybe a bit of spam).
In the current state, we make a new logger in every module that needs to log something. There is
CrawleeLogFormatter, which handles logging in the console.kwargsoflogging.infoand related methods - should we use that?