Joffreybvn opened a new pull request, #34964:
URL: https://github.com/apache/airflow/pull/34964
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
Hello,
This PR implements a new parameter for each Operators and Hooks:
`logger_name`. Goal is to make the logging configuration more granular.
*Example*: having one task to show all DEBUG, while the others are on
WARNING. I can configure two loggers, and assign them on my dags.
*Example* of SQLExecuteQueryOperator:
```python
SQLExecuteQueryOperator(
...,
logger_name="my.custom.logger",
hook_params={"logger_name": "my.custom.logger"}
)
```
#### Use case:
I am passing data between tasks (typically from APIs to a datawarehouse). I
use the SQLOperators and templated jinja to do the inserts. But, huge inserts
clogs up the logging view on the UI. Sometimes, the webserver crashes because
of it.
I would like to be able to:
- Enable INFO logging for some tasks, while having it on WARNING for others.
- For the INFO tasks, I would like multiple handlers:
- One that keeps only warning and error locally (for the webserver)
- One that throw everything into Elastic, so that the user can visit
Kibana to see everything
This is doable with an [advanced logging
configuration](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/advanced-logging-configuration.html),
and the ability to configure the name of the logger at task-level.
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
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: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
