Skip to content

Application and Access Logging#

FastStream uses two previously configured loggers:

  • faststream - used by FastStream app
  • faststream.access - used by the broker

Logging Requests#

To log requests, it is strongly recommended to use the access_logger of your broker, as it is available from the Context of your application.

from faststream import Logger
from faststream.rabbit import RabbitBroker

broker = RabbitBroker()

async def func(logger: Logger):"message received")

This approach offers several advantages:

  • The logger already contains the request context, including the message ID and broker-based parameters.
  • By replacing the logger when initializing the broker, you will automatically replace all loggers inside your functions.

Logging Levels#

If you use the FastStream CLI, you can change the current logging level of the entire application directly from the command line.

The --log-level flag sets the current logging level for both the broker and the FastStream app. This allows you to configure the levels of not only the default loggers but also your custom loggers, if you use them inside FastStream.

faststream run serve:app --log-level debug

If you want to completely disable the default logging of FastStream, you can set logger=None

from faststream import FastStream
from faststream.rabbit import RabbitBroker

broker = RabbitBroker(logger=None)  # Disables broker logs
app = FastStream(broker, logger=None)  # Disables application logs


Be careful: the logger that you get from the context will also have the value None if you turn off broker logging.

If you don't want to lose access to the `logger' inside your context but want to disable the default logs of FastStream, you can lower the level of logs that the broker publishes itself.

import logging
from faststream.rabbit import RabbitBroker

# Sets the broker logs to the DEBUG level
broker = RabbitBroker(log_level=logging.DEBUG)

Formatting Logs#

If you are not satisfied with the current format of your application logs, you can change it directly in your broker's constructor.

from faststream.rabbit import RabbitBroker
broker = RabbitBroker(log_fmt="%(asctime)s %(levelname)s - %(message)s")

Logger Access#

If you want to override default logger's behavior, you can access them directly via logging.

import logging
logger = logging.getLogger("faststream")
access_logger = logging.getLogger("faststream.access")

Or you can import them from FastStream.

from faststream.log import access_logger, logger

Using Your Own Loggers#

Since FastStream works with the standard logging.Logger object, you can initiate an application and a broker using your own logger.

import logging
from faststream import FastStream
from faststream.rabbit import RabbitBroker

logger = logging.getLogger("my_logger")

broker = RabbitBroker(logger=logger)
app = FastStream(broker, logger=logger)


Doing this, you doesn't change the CLI logs behavior (multiprocessing and hot reload logs). This was done to keep your log storage clear of unnecessary stuff.

This logger will be used only for FastStream and StreamBroker service messages and will be passed to your function through the Context.

By doing this, you will lose information about the context of the current request. However, you can retrieve it directly from the context anywhere in your code.

from faststream import context
log_context: dict[str, str] = context.get_local("log_context")

This way, all broker handlers can get access to your broker logger right from the context:

from faststream import Logger

async def handler(
    logger: Logger,  # <-- YOUR logger here

Structlog Example#

Structlog is a production-ready logging solution for Python. It can be easely integrated with any log storage system, making it suitable for use in production projects.

Here is a quick tutorial on integrating Structlog with FastStream:

Start with the Structlog guide example:

import sys
import structlog

shared_processors = [

if sys.stderr.isatty():
    # terminal session
    processors = shared_processors + [
    # Docker container session
    processors = shared_processors + [


logger = structlog.get_logger()

We created a logger that prints messages to the console in a user-friendly format during development and uses JSON-formatted logs in production.

To integrate this logger with our FastStream application, we just need to access it through context information and pass it to our objects:

import logging

import structlog

from faststream import FastStream, context
from faststream.kafka import KafkaBroker

def merge_contextvars(
    logger: structlog.types.WrappedLogger,
    method_name: str,
    event_dict: structlog.types.EventDict,
) -> structlog.types.EventDict:
    event_dict["extra"] = event_dict.get(
        context.get("log_context", {}),
    return event_dict

shared_processors = [


broker = KafkaBroker(logger=logger, log_level=logging.DEBUG)
app = FastStream(broker, logger=logger)

And the job is done! Now you have a perfectly structured logs using Structlog.

TIMESPAMP [info     ] FastStream app starting...     extra={}
TIMESPAMP [debug    ] `Handler` waiting for messages extra={'topic': 'topic', 'group_id': 'group', 'message_id': ''}
TIMESPAMP [debug    ] `Handler` waiting for messages extra={'topic': 'topic', 'group_id': 'group2', 'message_id': ''}
TIMESPAMP [info     ] FastStream app started successfully! To exit, press CTRL+C extra={'topic': '', 'group_id': '', 'message_id': ''}

Last update: 2023-10-02