arjunanan6 opened a new issue, #33255:
URL: https://github.com/apache/airflow/issues/33255

   ### Apache Airflow version
   
   2.6.3
   
   ### What happened
   
   I've set up Azure keyvaults as a 
[backend](https://airflow.apache.org/docs/apache-airflow-providers-microsoft-azure/stable/secrets-backends/azure-key-vault.html)
 for fetching connections, and it works fine. However, there's just too much 
logging and it's causing issues for our users to read logs. For example:
   
   Is there any way to suppress it to only errors/warnings ? Changing airflow 
logging_level to WARNING/ERROR is one way, but then the task logs don't have 
sufficient information. Is it possible to influence just the logging level on 
SecretClient? 
   
   ### What you think should happen instead
   
   Ideally, it should be possible to set logging level specifically for the 
keyvault backend in the backend_kwargs:
   
   ```
   backend_kwargs = {"connections_prefix": "airflow-connections", 
"variables_prefix": "airflow-variables", "vault_url": 
"https://example-akv-resource-name.vault.azure.net/";, "logging_level": 
"WARNING"}
   ```
   
   
   
   ### How to reproduce
   
   Set up KV backend as described 
[here](https://airflow.apache.org/docs/apache-airflow-providers-microsoft-azure/stable/secrets-backends/azure-key-vault.html).
 
   
   ### Operating System
   
   Debian GNU/Linux
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Deployed with Helm chart on AKS.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to