BUG: Uvicorn startup logs confusingly labeled as [error]

[rohan-pandeyy]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

When starting the backend and sync-microservices services using fastapi dev commands, the startup logs from Uvicorn (e.g., "Started server process") are prefixed with [error]. This is misleading as these are standard informational logs, not errors.

Steps to Reproduce

1. Start the backend service: fastapi dev --port 52123.
2. Observe the console output during startup.
3. Start the sync-microservices service: fastapi dev --port 52124.
4. Observe the console output during startup.

Expected Behavior

The logs should be labeled with [uvicorn] or a similar neutral tag, indicating the source of the log without implying an error severity.

Example:

[BACKEND] | [uvicorn] | INFO | Started server process [12345]

This issue appears to be a regression introduced in PR #940. Previously, the InterceptHandler explicitly prepended [uvicorn] to the log messages:

logger.log(record.levelno, f"[uvicorn] {msg}")

The refactoring to avoid recursion changed this logic to derive the tag from the logger name (uvicorn.error -> error), causing the misleading [error] tag.

Record

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[rohan-pandeyy]

Hi @rahulharpal1603, could you please assign me this issue? The fix is simple, we explicitly map uvicorn.error to
uvicorn in the handler.

A mere 7 line change