Closes stackabletech#650. The task handler is what feeds the log view in the Airflow web UI, and its level was pinned to INFO. Setting the airflow.task logger level was the only knob available, but a logger threshold applies to every destination at once, so the UI could not be quietened on its own. Take the level configured for the airflow.task logger and apply it to the task handler instead. No CRD change is needed, and the key is the one the docs already point people at. The two levels are not symmetric, which is the part worth knowing about. At or above INFO only the handler moves, so the UI goes quiet while the console and file handlers keep receiving the records it drops. Below INFO the logger has to be opened up as well, because a logger discards records before any of its handlers can filter them, and that means the extra records reach every destination rather than only the UI. Lowering the UI alone is therefore not possible, whichever way this is implemented. This does change behaviour for anyone raising the level today: it now quietens only the UI rather than every destination. The airflow.task entry is also excluded from the generic loggers block, so it cannot overwrite the level that block would otherwise assign directly. Both templates are covered, the stdlib one used by 2.x and 3.0.x and the structlog one used by 3.1 and later, with a table per template that lists the handler and logger level for every configurable level side by side.

Commits

Commits on Jul 31, 2026

feat: Drive the task handler log level from the airflow.task logger