ashb commented on code in PR #55850:
URL: https://github.com/apache/airflow/pull/55850#discussion_r2360633376
##########
airflow-core/src/airflow/config_templates/config.yml:
##########
@@ -788,11 +788,34 @@ logging:
description: |
Logging level.
+ Individual loggers can be set at a different level with the
:ref:`config:logging__namespace_levels`
+ option.
+
Supported values: ``CRITICAL``, ``ERROR``, ``WARNING``, ``INFO``,
``DEBUG``.
version_added: 2.0.0
type: string
example: ~
default: "INFO"
+ namespace_levels:
+ description: |
+ Set the log level for individual named loggers.
+
+ A very common convention in Python is to use the module name as the
name of the logger from which log
+ messages originate. This config option gives us the ability to set log
levels for those loggers
+ easily.
+
+ The format of this variable is a series of ``<logger>=<level>`` pairs,
separated by whitespace or
+ commas.
+
+ Each level is one of the possible values to ``logging_level``.
+
+ The logger names are veiewable in task logs (as the "source"
attribute), or in server components by
+ including ``%(name)s`` in your format string, or in the between ``[]``
after the message in the
+ default format.
+ version_added: 3.1.0
+ type: string
+ example: "sqlalchemy=INFO sqlalchemy.engine=DEBUG, botocor"
Review Comment:
Whoops yes!
```suggestion
example: "sqlalchemy=INFO sqlalchemy.engine=DEBUG, botocore=debug"
```
LC to show case doesn't matter too
##########
airflow-core/src/airflow/config_templates/config.yml:
##########
@@ -788,11 +788,34 @@ logging:
description: |
Logging level.
+ Individual loggers can be set at a different level with the
:ref:`config:logging__namespace_levels`
+ option.
+
Supported values: ``CRITICAL``, ``ERROR``, ``WARNING``, ``INFO``,
``DEBUG``.
version_added: 2.0.0
type: string
example: ~
default: "INFO"
+ namespace_levels:
+ description: |
+ Set the log level for individual named loggers.
+
+ A very common convention in Python is to use the module name as the
name of the logger from which log
+ messages originate. This config option gives us the ability to set log
levels for those loggers
+ easily.
+
+ The format of this variable is a series of ``<logger>=<level>`` pairs,
separated by whitespace or
+ commas.
+
+ Each level is one of the possible values to ``logging_level``.
+
+ The logger names are veiewable in task logs (as the "source"
attribute), or in server components by
+ including ``%(name)s`` in your format string, or in the between ``[]``
after the message in the
+ default format.
+ version_added: 3.1.0
+ type: string
+ example: "sqlalchemy=INFO sqlalchemy.engine=DEBUG, botocor"
Review Comment:
Whoops yes!
```suggestion
example: "sqlalchemy=INFO sqlalchemy.engine=DEBUG, botocore=warning"
```
LC to show case doesn't matter too
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
