Apply suggestions from code review of branch no-uvicorn.error-logs-without-error
Co-authored-by: Richard Bowman <richard.bowman@cantab.net>
This commit is contained in:
parent
95969c5daa
commit
353d311c1e
2 changed files with 2 additions and 4 deletions
|
|
@ -106,10 +106,8 @@ class OFMLogFileFormatter(logging.Formatter):
|
|||
def format(self, record: logging.LogRecord):
|
||||
"""Adjust the logging formatting for uvicorn logs.
|
||||
|
||||
Any ``uvicorn.error`` logs that are at a lower
|
||||
|
||||
uvicorn has two loggers. Each API access is ``uvicorn.access`` which we filter
|
||||
due to the noise the other is ``uvicorn.error`` for more important messages.
|
||||
due to the noise. The other is ``uvicorn.error`` for more important messages.
|
||||
However, ``uvicorn.error`` is used for expected messages that are not errors,
|
||||
such as server start up. This can lead to people erroneously thinking that
|
||||
there is an error with their miroscope.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue