From 0c28c16910ad41a439a03a037f6b2601cf3635b8 Mon Sep 17 00:00:00 2001 From: Rishabh Chauhan Date: Tue, 17 Dec 2024 01:49:08 +0530 Subject: [PATCH] Remove reference of "faststream.access" from docs --- docs/docs/en/getting-started/logging.md | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/docs/docs/en/getting-started/logging.md b/docs/docs/en/getting-started/logging.md index 4c4b9e77b2..d893aed248 100644 --- a/docs/docs/en/getting-started/logging.md +++ b/docs/docs/en/getting-started/logging.md @@ -10,11 +10,6 @@ search: # Application and Access Logging -**FastStream** uses two already 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](../getting-started/context/existed.md){.internal-link} of your application. @@ -77,22 +72,6 @@ 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`. - -```python -import logging -logger = logging.getLogger("faststream") -access_logger = logging.getLogger("faststream.access") -``` - -Or you can import them from **FastStream**. - -```python -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