Alexey Zavalskiy
09/01/2022, 5:42 PMpython_logs:
python_log_level: DEBUG
managed_python_loggers:
- scrapy.core.engine
- scrapy.utils.log
In attachment example of .stderr file from job.jamie
09/01/2022, 6:30 PMscrapy.core.engine
and scrapy.utils.log
eg
2022-09-01 17:28:34 [scrapy.utils.log] INFO: Scrapy 2.6.2 started (bot: scrapybot)
and
2022-09-01 17:28:34 [scrapy.core.engine] INFO: Spider opened
is the issue that the log you attached isn't showing up in dagit?Alexey Zavalskiy
09/02/2022, 6:11 AMjamie
09/13/2022, 2:57 PMowen
09/13/2022, 5:02 PMmanaged_python_loggers
to just - root
in your dagster.yaml, does that end up capturing logs?Alexey Zavalskiy
09/15/2022, 9:51 AMroot
in managed_python_loggers
lead to capturing logsowen
09/15/2022, 8:20 PMcontext.log._managed_loggers
, which should be the actual python logger objects that Dagster is expecting to capture messages from. With your original config, I'd expect that to contain two loggers, <Logger scrapy.core.engine (INFO)>, <Logger scrapy.utils.log (INFO)>
logging.getLogger("a.b.c") != logging.getLogger("a.b.c ")
, which is something to watch out for (not sure if spaces get stripped out in the yaml config or not)Alexey Zavalskiy
09/16/2022, 4:02 PMcontext.log._managed_loggers
from my op and get [<Logger dagster.builtin (DEBUG)>, <Logger scrapy.core.engine (DEBUG)>, <Logger scrapy.utils.log (DEBUG)>]
, but still don’t have these logs in dagit if root
logger isn’t set.
Checked for some typos or spaces, didn’t help