Logging Celery Tasks in the Same Console as Django

What You Will Learn

In this tutorial, you will master the art of setting up distinct logging configurations for Django and Celery tasks within a Django project. By doing so, you will be able to display logs from both components separately in the same console, making it easier to track and troubleshoot issues effectively.

Introduction to the Problem and Solution

When working on a Django project that utilizes Celery for background task processing, managing logging messages from both Django and Celery in the same console can become confusing. To address this challenge, it is essential to establish separate logging setups for each component. This segregation allows you to differentiate between log messages originating from Django and those produced by Celery tasks.

To achieve this separation of logs effectively: – Create custom handlers for Django and Celery. – Direct their log outputs to distinct streams or files. – Configure specific logger instances with dedicated handlers attached for each component.

By implementing these steps, you ensure that logs from Django and Celery remain independent of each other, providing clarity and ease of debugging during development or production stages.


# In settings.py of your Django project

    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'console_django': {
            'level': 'DEBUG',
            'class': 'logging.StreamHandler',
    # Define formatters, loggers, etc.

# Configure Celery logging separately
import logging.config

celery_logger = logging.getLogger('celery')

# Copyright PHD

Note: For more detailed code examples and explanations, visit PythonHelpDesk.com.


By customizing the LOGGING dictionary in your settings.py, you create a unique handler named ‘console_django’ using a StreamHandler. This handler ensures that log records from Django are displayed on the console output distinctly.

For handling Celery logs separately, access the root logger created by Celery (‘celery’) using Python’s built-in logging module. Add an additional StreamHandler instance directly to this logger object. As a result, all log messages generated by Celery tasks will be visible on the console but clearly differentiated from those produced by Django.

This approach enhances visibility into logged events during development or debugging sessions by enabling developers to distinguish between logs coming from different parts of their application stack efficiently.

    1. How do I enable DEBUG level logs for my entire application? Set your root logger level as DEBUG:

    2. LOGGING = {
          'root': {
              'level': 'DEBUG',
    3. # Copyright PHD
    4. Can I send my logs to multiple destinations concurrently? Yes! Define multiple handlers under ‘handlers’ key in your LOGGING configuration with distinct targets like file output or email notifications.

    5. Is it possible to format my log messages differently based on severity? Absolutely! Utilize formatter classes within your LOGGING setup such as ‘formatter’.

    6. How do I silence certain overly verbose modules or libraries? Adjust levels at per-logger granularity inside LOGGING dict instead of globally setting ‘level.

    7. What if I want asynchronous/non-blocking behavior for my logging operations? Explore alternative handler options like QueueHandler/QueueListener combination provided by Python’s standard library.

    8. Can I rotate log files automatically based on size or time intervals? Implement specialized rotating file handlers available through popular third-party packages such as RotatingFileHandler from logging.handlers.


Implementing separate logging configurations for your main application (Django) and asynchronous task processor (Celery) enhances visibility into system behaviors during development or production phases. By organizing log outputs through tailored handlers and formatters according to component-specific needs, you improve maintainability and troubleshooting capabilities across complex Python projects involving diverse modules or frameworks interactions.

Leave a Comment