Skip to content

[v3-3-test] Fix missing HTTP access logs when api-server omits the core app (#72026) - #72808

Merged
vatsrahul1001 merged 1 commit into
v3-3-testfrom
backport-860233f-v3-3-test
Sep 10, 2026
Merged

vatsrahul1001 merged 1 commit into
v3-3-testfrom
backport-860233f-v3-3-test

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor
  • Fix missing HTTP access logs when api-server omits the core app

An api-server started without the core app -- for example --apps execution,
the shape used to run the Task Execution API as its own deployment -- served
requests but recorded none of them. That leaves the component every running task
depends on for heartbeats, state transitions and XComs with no per-request
telemetry, which is the primary signal for diagnosing heartbeat stalls.

Both server backends disable their own access logger, and the built-in access
loggers are muted in the logging config, all on the premise that
HttpAccessLogMiddleware handles access logging. That premise only held while the
middleware was installed by the core app branch, so no configuration could
recover the records. Installing it for every apps selection makes the premise
true again instead of adding a fourth conditional that would give execution-only
deployments a different log format from every other deployment.

  • Lock in HttpAccessLog outermost ordering with a positional assertion

  • Trim redundant caveat from init_middlewares ordering note


(cherry picked from commit 860233f)

Co-authored-by: manish1337 78193094+manish1337@users.noreply.github.com
Co-authored-by: pierrejeambrun pierre.jeambrun@astronomer.io

…re app (#72026)

* Fix missing HTTP access logs when api-server omits the core app

An api-server started without the core app -- for example `--apps execution`,
the shape used to run the Task Execution API as its own deployment -- served
requests but recorded none of them. That leaves the component every running task
depends on for heartbeats, state transitions and XComs with no per-request
telemetry, which is the primary signal for diagnosing heartbeat stalls.

Both server backends disable their own access logger, and the built-in access
loggers are muted in the logging config, all on the premise that
HttpAccessLogMiddleware handles access logging. That premise only held while the
middleware was installed by the core app branch, so no configuration could
recover the records. Installing it for every apps selection makes the premise
true again instead of adding a fourth conditional that would give execution-only
deployments a different log format from every other deployment.

* Lock in HttpAccessLog outermost ordering with a positional assertion

* Trim redundant caveat from init_middlewares ordering note

---------
(cherry picked from commit 860233f)

Co-authored-by: manish1337 <78193094+manish1337@users.noreply.github.com>
Co-authored-by: pierrejeambrun <pierre.jeambrun@astronomer.io>
@boring-cyborg boring-cyborg Bot added the area:API Airflow's REST/HTTP API label Sep 9, 2026
@pierrejeambrun
pierrejeambrun marked this pull request as ready for review September 9, 2026 16:21
@vatsrahul1001 vatsrahul1001 added the type:bug-fix Changelog: Bug Fixes label Sep 10, 2026
@vatsrahul1001 vatsrahul1001 added this to the Airflow 3.3.2 milestone Sep 10, 2026
@vatsrahul1001
vatsrahul1001 merged commit 7e13aaa into v3-3-test Sep 10, 2026
134 of 135 checks passed
@vatsrahul1001
vatsrahul1001 deleted the backport-860233f-v3-3-test branch September 10, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:API Airflow's REST/HTTP API type:bug-fix Changelog: Bug Fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants