10

I am working on FastAPI - Uvicorn. I want to disable the logging by uvicorn. I need only the logs which are logged by the server.

Log file

I referred to this blog and implemented the logging.

funnydman
  • 9,083
  • 4
  • 40
  • 55
Sivakumar A
  • 601
  • 1
  • 6
  • 16

3 Answers3

12

You could change log level for getting only needed messages, there are a bunch of possible options:

uvicorn main:app --log-level critical
funnydman
  • 9,083
  • 4
  • 40
  • 55
4

I think I had the same issue.

To disable the logger one must first find the loggers, that shall be disabled. I did this by following this stackoverflow post and this GitHub-Issue.

For me it works to disable just two loggers from uvicorn:

import logging
# ....CODE....
uvicorn_error = logging.getLogger("uvicorn.error")
uvicorn_error.disabled = True
uvicorn_access = logging.getLogger("uvicorn.access")
uvicorn_access.disabled = True

At first I tried the answer provided by @Sanchouz, but this didn't work out for me - Further setting propagate = false is by some regarded as a bad practice (see this) . As I wanted to do it programmatically I couldn't test the answer provided by @funnydman.

Hope this helps anyone, thinklex.

Thinklex
  • 83
  • 6
3

Problem definition

I had a similar problem and I found a solution. In my case, I created a small website with FastAPI to launch web scrappers in separate processes. I also created class-wrapper for loggers from logging module. My problem was: when I started my app inside Docker container with uvicorn ... command, which includes some settings for logging into file, all logging from any web scrapper would go into both scrapper's separate log file and server's log file. I have a lot of stuff to log, so it's quite a problem.

Short answer

When you get your logger, just set it's propagate property to False like this:

logger = logging.getLogger(logger_name)
logger.propagate = False

Long answer

At first I spent some time debugging insides of a logging module and I found a function called callHandlers, which loops through handlers of current logger and it's parents. I wrongly assumed, that root logger was responsible for that problem, but after some more testing it turned out, that actually root logger didn't have any handlers. It means, that some of uvicorn's logger was responsible for that, which makes sense, also considering Thinklex's solution. I tried his solution too, but it doesn't fit me, because it disabled uvicorn's logging completely, and I don't want that, so I'll stick with preventing propagation on my loggers.

Sanchouz
  • 31
  • 3