gergely/flask-logging-extras
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Celery task logging in place of blueprints

Browse Source 
When inside a celery task, this allows you to use the task name rather than a blueprint
This commit is contained in:
Omer Yampel 2017-06-28 09:56:12 -04:00 committed by GitHub
parent 583dfdd941
commit b39619bb3e
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
flask_logging_extras/__init__.py
View File

@ -32,6 +32,11 @@ no value is present in the message record.
import logging
try:
from celery import current_task:
except ImportError:
current_task = None
from flask import has_request_context, request
__version_info__ = ('0', '0', '1')
@ -134,7 +139,9 @@ class FlaskExtraLogger(logging.getLoggerClass()):
# If we were asked to log the blueprint name, add it to the extra list
if self._blueprint_var is not None:
if has_request_context():
if current_task:
kwargs['extra'][self._blueprint_var] = current_task.name
elif has_request_context():
kwargs['extra'][self._blueprint_var] = request.blueprint or self._blueprint_app
else:
kwargs['extra'][self._blueprint_var] = self._blueprint_norequest