Describe default Airflow loggers

[codewithdaniel1]

closes: #10593

Why

Airflow has several loggers used across task execution, DAG processing, scheduler activity, and the webserver. Issue #10593 asks for clearer documentation around the default logging configuration and how common Airflow loggers relate to existing logging docs.

Previous closed PRs attempted a larger standalone logging page. This PR keeps the change smaller and adds a concise section to the existing logging architecture documentation instead.

What changed

This PR adds a “Default Airflow loggers” section to the logging and monitoring architecture page.

The new section briefly explains commonly referenced logger names, including:

• root
• airflow.task
• airflow.processor
• airflow.processor_manager
• flask_appbuilder

It also links readers to the existing task logging and advanced logging configuration documentation for more detailed setup and customization guidance.

Testing

Documentation-only change.

Local checks:

git diff --check
git diff --stat

Result:

1 file changed, 30 insertions(+)

---

Was generative AI tooling used to co-author this PR?

• Yes: ChatGPT

Generated-by: ChatGPT following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack