blocks|key|546035|text|import+logging
urllib3_logger+=+logging.getLogger('urllib3')
urllib3_logger.setLevel(logging.CRITICAL)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|546036|这样，来自urllib3的所有level=INFO消息都不会出现在日志文件中。|unstyled|546037|因此，您可以继续使用日志messages...just的level=INFO，为您正在使用的库修改此are。|546038|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>import logging
urllib3_logger = logging.getLogger('urllib3')
urllib3_logger.setLevel(logging.CRITICAL)
</code></pre>

In this way all the messages of level=INFO from urllib3 won't be present in the logfile.

So you can continue to use the level=INFO for your log messages...just modify this for the library you are using.

blocks|key|546099|text|对于使用logging.config.dictConfig的任何人，您可以更改字典中的请求库日志级别，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|546100|'loggers':+{
++++'':+{
++++++++'handlers':+['file'],
++++++++'level':+level,
++++++++'propagate':+False
++++},
++++'requests.packages.urllib3':+{
++++++++'handlers':+['file'],
++++++++'level':+logging.WARNING
++++}
}|code-block|syntax|javascript|546101|entityMap^0|4|P|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

For anybody using <code>logging.config.dictConfig</code> you can alter the requests library log level in the dictionary like this:

<pre><code>'loggers': {
 '': {
 'handlers': ['file'],
 'level': level,
 'propagate': False
 },
 'requests.packages.urllib3': {
 'handlers': ['file'],
 'level': logging.WARNING
 }
}
</code></pre>

blocks|key|545982|text|在遇到与您类似的问题后，让我复制/粘贴我在一两周前写的文档部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|545983|import+requests
import+logging

#+these+two+lines+enable+debugging+at+httplib+level+(requests->urllib3->httplib)
#+you+will+see+the+REQUEST,+including+HEADERS+and+DATA,+and+RESPONSE+with+HEADERS+but+without+DATA.
#+the+only+thing+missing+will+be+the+response.body+which+is+not+logged.
import+httplib
httplib.HTTPConnection.debuglevel+=+1

logging.basicConfig()+#+you+need+to+initialize+logging,+otherwise+you+will+not+see+anything+from+requests
logging.getLogger().setLevel(logging.DEBUG)
requests_log+=+logging.getLogger("requests.packages.urllib3")
requests_log.setLevel(logging.DEBUG)
requests_log.propagate+=+True

requests.get('http://httpbin.org/headers')|code-block|syntax|javascript|545984|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Let me copy/paste the documentation section which it I wrote about week or two ago, after having a problem similar to yours:

<pre><code>import requests
import logging

# these two lines enable debugging at httplib level (requests-&gt;urllib3-&gt;httplib)
# you will see the REQUEST, including HEADERS and DATA, and RESPONSE with HEADERS but without DATA.
# the only thing missing will be the response.body which is not logged.
import httplib
httplib.HTTPConnection.debuglevel = 1

logging.basicConfig() # you need to initialize logging, otherwise you will not see anything from requests
logging.getLogger().setLevel(logging.DEBUG)
requests_log = logging.getLogger("requests.packages.urllib3")
requests_log.setLevel(logging.DEBUG)
requests_log.propagate = True

requests.get('http://httpbin.org/headers')
</code></pre>

blocks|key|329591|text|import+logging

#+Only+show+warnings
logging.getLogger("urllib3").setLevel(logging.WARNING)

#+Disable+all+child+loggers+of+urllib3,+e.g.+urllib3.connectionpool
logging.getLogger("urllib3").propagate+=+False|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|329592|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>import logging

# Only show warnings
logging.getLogger("urllib3").setLevel(logging.WARNING)

# Disable all child loggers of urllib3, e.g. urllib3.connectionpool
logging.getLogger("urllib3").propagate = False
</code></pre>

blocks|key|546344|text|将记录器名称设置为requests或requests.urllib3对我不起作用。我必须指定确切的记录器名称才能更改日志记录级别。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|546345|首先查看您定义了哪些记录器，以确定要删除哪些记录器|546346|print(logging.Logger.manager.loggerDict)|code-block|syntax|javascript|546347|你会看到类似这样的东西：|546348|{...'urllib3.poolmanager':+<logging.Logger+object+at+0x1070a6e10>,+'django.request':+<logging.Logger+object+at+0x106d61290>,+'django.template':+<logging.Logger+object+at+0x10630dcd0>,+'django.server':+<logging.Logger+object+at+0x106dd6a50>,+'urllib3.connection':+<logging.Logger+object+at+0x10710a350>,'urllib3.connectionpool':+<logging.Logger+object+at+0x106e09690>+...}|546349|然后为确切的记录器配置级别：|546350|+++'loggers':+{
++++'':+{
++++++++'handlers':+['default'],
++++++++'level':+'DEBUG',
++++++++'propagate':+True
++++},
++++'urllib3.connectionpool':+{
++++++++'handlers':+['default'],
++++++++'level':+'WARNING',
++++++++'propagate'+:+False
++++},|546351|entityMap^0|9|8|I|G|0|0|0|0|0|AB|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|U|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|V|$]]

Setting the logger name as <code>requests</code> or <code>requests.urllib3</code> did not work for me. I had to specify the exact logger name to change the logging level.

First See which loggers you have defined, to see which ones you want to remove

<pre><code>print(logging.Logger.manager.loggerDict)
</code></pre>

And you will see something like this:

<code>{...'urllib3.poolmanager': &lt;logging.Logger object at 0x1070a6e10&gt;, 'django.request': &lt;logging.Logger object at 0x106d61290&gt;, 'django.template': &lt;logging.Logger object at 0x10630dcd0&gt;, 'django.server': &lt;logging.Logger object at 0x106dd6a50&gt;, 'urllib3.connection': &lt;logging.Logger object at 0x10710a350&gt;,'urllib3.connectionpool': &lt;logging.Logger object at 0x106e09690&gt; ...}</code>

Then configure the level for the exact logger:

<pre><code> 'loggers': {
 '': {
 'handlers': ['default'],
 'level': 'DEBUG',
 'propagate': True
 },
 'urllib3.connectionpool': {
 'handlers': ['default'],
 'level': 'WARNING',
 'propagate' : False
 },
</code></pre>

blocks|key|546263|text|如果您有配置文件，可以对其进行配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|546264|在记录器部分添加urllib3：|546265|[loggers]
keys+=+root,+urllib3|code-block|syntax|javascript|546266|添加logger_urllib3部分：|546267|[logger_urllib3]
level+=+WARNING
handlers+=
qualname+=+requests.packages.urllib3.connectionpool|546268|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If You have configuration file, You can configure it.

Add urllib3 in loggers section:

<pre><code>[loggers]
keys = root, urllib3
</code></pre>

Add logger_urllib3 section:

<pre><code>[logger_urllib3]
level = WARNING
handlers =
qualname = requests.packages.urllib3.connectionpool
</code></pre>

blocks|key|329586|text|答案在这里：Python:+how+to+suppress+logging+statements+from+third+party+libraries?|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|329587|您可以将默认日志记录级别保留为basicConfig，然后在获取模块的记录器时设置调试级别。|329588|logging.basicConfig(format='%25(asctime)s+%25(module)s+%25(filename)s:%25(lineno)s+-+%25(message)s')
logger+=+logging.getLogger(__name__)
logger.setLevel(logging.DEBUG)

logger.debug("my+debug+message")|code-block|syntax|javascript|329589|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/21944445/python-how-to-suppress-logging-statements-from-third-party-libraries^0|6|1Y|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

This answer is here: <a href="https://stackoverflow.com/questions/21944445/python-how-to-suppress-logging-statements-from-third-party-libraries">Python: how to suppress logging statements from third party libraries?</a>

You can leave the default logging level for basicConfig, and then you set the DEBUG level when you get the logger for your module.

<pre><code>logging.basicConfig(format='%(asctime)s %(module)s %(filename)s:%(lineno)s - %(message)s')
logger = logging.getLogger(__name__)
logger.setLevel(logging.DEBUG)

logger.debug("my debug message")
</code></pre>

blocks|key|329511|text|Kbrose关于哪个日志记录器正在生成日志消息的指导非常有用。对于我的Django项目，我不得不整理120个不同的记录器，直到我发现是elasticsearch+Python库给我带来了问题。根据大多数问题中的指导，我通过在我的记录器中添加以下内容来禁用它：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|329512|++++++...
++++++'elasticsearch':+{
++++++++++'handlers':+['console'],
++++++++++'level':+logging.WARNING,
++++++},+++++
++++++...|code-block|syntax|javascript|329513|在这里发帖，以防其他人在运行Elasticsearch查询时看到无用的日志消息。|329514|entityMap^0|1V|D|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Kbrose's guidance on finding which logger was generating log messages was immensely useful. For my Django project, I had to sort through 120 different loggers until I found that it was the <code>elasticsearch</code> Python library that was causing issues for me. As per the guidance in most of the questions, I disabled it by adding this to my loggers:

<pre><code> ...
 'elasticsearch': {
 'handlers': ['console'],
 'level': logging.WARNING,
 }, 
 ...
</code></pre>

Posting here in case someone else is seeing the unhelpful log messages come through whenever they run an Elasticsearch query.

blocks|key|546147|text|简单:只需在import+requests之后添加requests.packages.urllib3.disable_warnings()|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|546148|entityMap^0|6|F|P|18|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

simple: just add <code>requests.packages.urllib3.disable_warnings()</code> after <code>import requests</code>

blocks|key|546194|text|我不确定之前的方法是否已经停止工作，但无论如何，这里有另一种消除警告的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|546195|PYTHONWARNINGS="ignore:Unverified+HTTPS+request"+./do-insecure-request.py|code-block|syntax|javascript|546196|基本上，在脚本执行的上下文中添加一个环境变量。|546197|来自文档：https://urllib3.readthedocs.org/en/latest/security.html#disabling-warnings|offset|length|546198|entityMap|0|LINK|mutability|MUTABLE|url|https://urllib3.readthedocs.org/en/latest/security.html#disabling-warnings^0|0|0|0|5|22|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I'm not sure if the previous approaches have stopped working, but in any case, here's another way of removing the warnings:

<pre><code>PYTHONWARNINGS="ignore:Unverified HTTPS request" ./do-insecure-request.py
</code></pre>

Basically, adding an environment variable in the context of the script execution.

From the documentation: <a href="https://urllib3.readthedocs.org/en/latest/security.html#disabling-warnings" rel="nofollow noreferrer">https://urllib3.readthedocs.org/en/latest/security.html#disabling-warnings</a>

By default, the <a href="https://requests.readthedocs.io/" rel="noreferrer">Requests</a> python library writes log messages to the console, along the lines of:

<pre><code>Starting new HTTP connection (1): example.com
http://example.com:80 "GET / HTTP/1.1" 200 606
</code></pre>

I'm usually not interested in these messages, and would like to disable them. What would be the best way to silence those messages or decrease Requests' verbosity?

How do I disable log messages from the Requests library?

Elasticsearch 

日志文件

Django

Python

默认情况下， python库将日志消息写入控制台，如下所示：Starting new HTTP connection (1): example.comhttp://example.com:80 "GET / HTTP/1.1" 200 606我通常对这些消息不感兴趣，并想禁用它们。让这些消息静默或减少请求冗长的最好方法是什么？

问如何禁用请求库中的日志消息？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何禁用请求库中的日志消息？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何禁用请求库中的日志消息？
EN