Configure logging for API server

[Abdulrehman-PIAIC80387]

The API server did not respect logging.colored_console_log. Setting AIRFLOW__LOGGING__COLORED_CONSOLE_LOG=False left the API server emitting ANSI color escape sequences, which are hard to read in log aggregators that don't render colors.

The root cause is the same one #54992 fixed for the Triggerer: the process never called configure_logging(), so structlog fell back to its default (colors=True) and ignored the colored_console_log config. #54992 fixed the Triggerer but left the API server (the second process named in #54962) unaddressed.

Fix

Call configure_logging() in airflow.api_fastapi.main, the module that both uvicorn and gunicorn import in every worker process (uvicorn runs main:app; gunicorn's worker load() does from airflow.api_fastapi.main import app). configure_logging() reads logging.colored_console_log from config, so the API server now honors it.

Design notes

• The call is placed in the per-worker entrypoint rather than the CLI master process (_run_api_server) on purpose: uvicorn/gunicorn load the app independently in each worker, so configuring logging only in the master would not reach the worker processes that actually emit the request/app logs.
• This mirrors the approach merged in Configure logging for Triggerer #54992 for the Triggerer.

Tests

Added test_main.py asserting configure_logging() is invoked when the worker entrypoint is loaded.

closes: #54962

---

Important

🛠️ Maintainer triage note for @Abdulrehman-PIAIC80387 · by @potiuk · 2026-07-02 17:46 UTC

Some review feedback from @pierrejeambrun is waiting on you:

• 1 unresolved review thread(s) from @pierrejeambrun need a reply or a fix.

The ball is in your court — you've been assigned to this PR. Reply or push a fix in each thread, then mark them resolved.

_{Automated triage — may be imperfect; a maintainer takes the next look.}

[SameerMesiah97]

This seems reasonable but since this PR targets user-facing observability, I think it would be best if you provided screenshots (or log snippets) illustrating the issue you described i.e. 'API server emitting ANSI color escape sequences'. As well as what the logs look like after your fix.

[pierrejeambrun]

One blocker bellow.

Also screenshot of before / after of the tmux session would be welcome.

[pierrejeambrun]

To remove

[potiuk]

@Abdulrehman-PIAIC80387 I've removed the ready for maintainer review label because the next step here is yours: unresolved review thread(s) from @pierrejeambrun awaiting your reply. It'll go back into the maintainer queue automatically once that's done — no need to re-add the label by hand. Next move: address the unresolved threads and reply to @pierrejeambrun. There is no rush.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. If you have questions, an Apache Airflow maintainer — a real person — is happy to help. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.