blocks|key|112972|text|https://github.com/jedie/django-tools/blob/master/django_tools/middlewares/ThreadLocal.py上有一个ThreadLocal中间件，它可以帮助您解决当前请求随处可用的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|112973|因此，您需要做的是将中间件添加到您的MIDDLEWARE_CLASSES设置中，并在某个地方创建一个函数，如下所示：|112974|+from+django_tools.middlewares+import+ThreadLocal
+def+log_something(levelname,+module,+funcname,+message):
+++++user+=+ThreadLocal.get_current_user()
+++++#+do+your+logging+here.+"user"+is+the+user+object+and+the+user+id+is+in+user.pk|code-block|syntax|javascript|112975|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jedie/django-tools/blob/master/django_tools/middlewares/ThreadLocal.py^0|0|2H|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]]]]

There exists a ThreadLocal middleware on <a href="https://github.com/jedie/django-tools/blob/master/django_tools/middlewares/ThreadLocal.py">https://github.com/jedie/django-tools/blob/master/django_tools/middlewares/ThreadLocal.py</a> which helps you with your issue in making the current request available everywhere.

So what you need to do is add the middleware to your MIDDLEWARE_CLASSES setting, and create a function somewhere like this:

<pre><code> from django_tools.middlewares import ThreadLocal
 def log_something(levelname, module, funcname, message):
 user = ThreadLocal.get_current_user()
 # do your logging here. "user" is the user object and the user id is in user.pk
</code></pre>

blocks|key|330477|text|这里有一种不需要线程本地变量或中间件的可行方法:在views.py中，假设有一个将线程映射到请求的字典，以及一个用于序列化对它的访问的锁：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|330478|from+threading+import+RLock
shared_data_lock+=+RLock()
request_map+=+{}

def+set_request(request):
++++with+shared_data_lock:
++++++++request_map[threading.current_thread()]+=+request|code-block|syntax|javascript|330479|创建以下过滤器并附加到需要输出特定于请求的信息的处理程序：|330480|import+logging
class+RequestFilter(logging.Filter):
++++def+filter(self,+record):
++++++++with+shared_data_lock:
++++++++++++request+=+request_map.get(threading.current_thread())
++++++++if+request:
++++++++++++#+Set+data+from+the+request+into+the+record,+e.g.
++++++++++++record.user_id+=+request.user.id
++++++++return+True|330481|然后，作为每个视图的第一个语句，在映射中设置请求：|330482|def+my_view(request,+...):
++++set_request(request)
++++#+do+your+other+view+stuff+here|330483|使用此设置，您会发现日志输出包含特定于请求的相关信息。|330484|entityMap^0|P|8|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|14|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|V|$]]

Here's a possible approach without thread locals or middleware: in your <code>views.py</code>, say, have a dict mapping threads to requests, and a lock to serialise access to it:

<pre><code>from threading import RLock
shared_data_lock = RLock()
request_map = {}

def set_request(request):
 with shared_data_lock:
 request_map[threading.current_thread()] = request
</code></pre>

Create the following filter and attach to the handlers which need to output request-specific info:

<pre><code>import logging
class RequestFilter(logging.Filter):
 def filter(self, record):
 with shared_data_lock:
 request = request_map.get(threading.current_thread())
 if request:
 # Set data from the request into the record, e.g.
 record.user_id = request.user.id
 return True
</code></pre>

Then, as the first statement of each view, set the request in the map:

<pre><code>def my_view(request, ...):
 set_request(request)
 # do your other view stuff here
</code></pre>

With this setup, you should find that your log output contains the relevant request-specific info.

blocks|key|113061|text|我想你要找的是一个custom+log+formatter。与mawimawi的答案结合使用以包含线程本地信息，您的format方法可以自动获取该信息并将其添加到每个记录的消息中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|113062|有几件事需要考虑:首先，线程局部变量可能是危险的，更糟糕的是，如果您以使用线程池的方式进行部署，还会泄漏信息。其次，您需要谨慎编写格式化程序，以防它在没有线程本地信息的上下文中被调用。|113063|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.python.org/2/library/logging.html#formatter-objects^0|9|K|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I think you are looking for a <a href="http://docs.python.org/2/library/logging.html#formatter-objects" rel="nofollow">custom log formatter</a>. Taken in conjunction with mawimawi's answer to include the threadlocal information, your format method could automatically take the information and add it to each logged message.

There are a couple of things to think about: First, threadlocal variables can be dangerous and, worse, leak information, if you deploy in a way that uses a threadpool. Second, you need to be cautious how you write your formatter in case it gets called in a context that doesn't have the threadlocal information.

Lets say I want to log like this formatting string :

<pre><code>%(levelname)s %(asctime)s %(module)s %(funcName)s %(message)s %(user_id)
</code></pre>

It can be done using this type of logging command :

<code>logging.error('Error fetching information', extra = { 'user_id': 22 } )</code>

This will add the current userid to logging messages for current request.

But the extra dict needs to be added to every logging call.

Is there a good way to add this context in a common function in django (eg Middleware, or index function of a view ), so that the extra dictionary with user id is set, and all further logging calls in the current request also log the current user.

django logging set context globally per request?

中间件

假设我想像这样记录格式化字符串：%(levelname)s %(asctime)s %(module)s %(funcName)s %(message)s %(user_id)可以使用以下类型的日志记录命令完成此操作：logging.error('Error fetching information', extra =...

问django日志为每个请求全局设置上下文？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问django日志为每个请求全局设置上下文？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问django日志为每个请求全局设置上下文？
EN