Repository navigation
Missing docs for logging #10593
Description
Hello,
The configuration of the Airflow logger is not easy, as in most applications. We have many loggers, some loggers generate multiple streams. This is very confusing for end-users, and the lack of documentation doesn't make it any easier.
We have following loggers
root loggerairflow.processorairflow.taskflask_appbuilderairflow.processor_manager
airflow.task creates a new log file for each pair of task instances and try numbers. These entries are accessible via the Web UI.
airflow.processor creates a new log file for each DAG File.
flask_appbuilder is only used to filter logs records because the FAB is too verbose, so in most cases, we don't have to configure it specially.
Webserver writes logs to root logger.
Worker writes logs to airflow.processor and root logger
Scheduler writes logs to airflow.processor, airflow.processor_manager and root logger
I would be happy if we had a description of the default configuration and the methods on how to influence these configurations were described. Currently, the documentation only describes configurations for airflow.task.
Best regards,
Kamil Breguła
Activity
kaxil commentedon Dec 30, 2021
cc @blag
AshutoshSrivastavaDev commentedon May 2, 2025
can I take this up
Hasanen99 commentedon Jun 19, 2025
It's unbelievable how this horrible issue requires a complete custom class and building new things to print the logs to stdout. Seriously!
sanchalitorpe13 commentedon Jan 29, 2026
Hi @kaxil, I’d like to work on documenting the default logging configuration for Airflow components (root, airflow.task, airflow.processor, etc.), as well as instructions for modifying them. I will make sure to add examples and follow the current docs style.
potiuk commentedon Mar 2, 2026
@sanchalitorpe-source We are unassigning you from this issue as part of our updated assignment policy.
This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.
We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.
dhariskhan1275 commentedon Jul 24, 2026
can I take this up
shahar1 commentedon Jul 24, 2026
Sure, feel free to raise a PR (we don't officialy assign to GitHub issues by current policy)
dhariskhan1275 commentedon Jul 24, 2026
ok
codewithdaniel1 commentedon Jul 31, 2026
Hi, I’m going to work on a small documentation update for this.
I reviewed the previous closed PRs and plan to keep this version narrowly scoped by adding a concise “Default Airflow loggers” section to the existing logging architecture documentation, rather than creating a new standalone page.
I’ll avoid unrelated file changes and will link to the existing task logging and advanced logging configuration docs for details.