-
Notifications
You must be signed in to change notification settings - Fork 10.8k
Add flag to disable Scraped debug messages #3984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Seems like a valid request, I have seen my logs flooded with those messages as well. |
Thanks @elacuesta, that's what I thought as well, I'd be happy to pick this up when I have a bit of time. |
krisztian-toth
pushed a commit
to krisztian-toth/scrapy
that referenced
this issue
Aug 29, 2019
krisztian-toth
pushed a commit
to krisztian-toth/scrapy
that referenced
this issue
Aug 30, 2019
…crapy#3984)" This reverts commit c34dd26
krisztian-toth
pushed a commit
to krisztian-toth/scrapy
that referenced
this issue
Aug 30, 2019
…e to omit logging actions (scrapy#3984)
krisztian-toth
pushed a commit
to krisztian-toth/scrapy
that referenced
this issue
Sep 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Add a flag to settings (e.g.
LOG_SCRAPED_ENABLED
) to be able to disable the logging of each scraped Item onDEBUG
level.Motivation
Crawling with Scrapy on log level
DEBUG
provides a lot of useful context during development. The only problem is the "scraped" message (constructed inscrapy.logformatter.LogFormatter.scraped
) - it obfuscates the log entirely in the command line and can be really frustrating in general. Adding a flag to disable this log message (with a default value so that the current behaviour doesn't change) would be really useful.Describe alternatives you've considered
Right now you either put up with it or use
INFO
level instead which makes you lose a lot of useful log entries available inDEBUG
level.The text was updated successfully, but these errors were encountered: