This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new eb81f33235e docs: describe default Airflow loggers (#70842)
eb81f33235e is described below
commit eb81f33235e0ea4adbc59b350ea666a60ae70329
Author: Daniel <[email protected]>
AuthorDate: Thu Aug 13 09:56:30 2026 -0400
docs: describe default Airflow loggers (#70842)
Signed-off-by: codewithdaniel1
<[email protected]>
---
.../logging-monitoring/logging-architecture.rst | 30 ++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git
a/airflow-core/docs/administration-and-deployment/logging-monitoring/logging-architecture.rst
b/airflow-core/docs/administration-and-deployment/logging-monitoring/logging-architecture.rst
index ae000ddfe0b..21c35e1d82c 100644
---
a/airflow-core/docs/administration-and-deployment/logging-monitoring/logging-architecture.rst
+++
b/airflow-core/docs/administration-and-deployment/logging-monitoring/logging-architecture.rst
@@ -32,6 +32,36 @@ logging to cloud storage such as AWS, Google Cloud, and
Azure.
The logging settings and options can be specified in the Airflow Configuration
file,
which as usual needs to be available to all the Airflow process: Web server,
Scheduler, and Workers.
+Default Airflow loggers
+-----------------------
+
+Airflow uses Python's standard logging framework, and most loggers follow the
+Python package and module naming convention. A few logger names are useful to
+know when reading logs or customizing logging behavior:
+
+* ``root``: the root Python logger. During task execution, Airflow configures
+ the root logger so standard Python loggers that propagate to it can write to
+ the task log.
+* ``airflow.task``: the parent logger for task logs. Operators and hooks use
+ child loggers under this namespace, such as ``airflow.task.operators`` and
+ ``airflow.task.hooks``.
+* ``airflow.processor``: used by Dag file processing code, including messages
+ emitted while parsing Dag files.
+* ``airflow.processor_manager``: used by the scheduler's Dag processor manager
+ to report Dag processing activity.
+* ``flask_appbuilder``: used by Flask-AppBuilder in the webserver. Airflow's
+ default logging configuration keeps this logger less verbose than Airflow's
+ own component loggers.
+
+Task logs are configured separately from other component logs because they must
+be grouped by task instance and made available in the Airflow UI. For task log
+file layout and remote task logging settings, see
+:doc:`/administration-and-deployment/logging-monitoring/logging-tasks`.
+
+For custom handlers, custom logger levels, or per-operator and per-task logger
+configuration, see
+:doc:`/administration-and-deployment/logging-monitoring/advanced-logging-configuration`.
+
You can customize the logging settings for each of the Airflow components by
specifying the logging settings
in the Airflow Configuration file, or for advanced configuration by using
:doc:`advanced features
</administration-and-deployment/logging-monitoring/advanced-logging-configuration>`.
