[I] Support DEBUG logging by component [airflow]

["RNHTTR (via GitHub)" <gi...@apache.org>]

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

   ### Description
   
   Currently, users can only enable debug logging across all Airflow components. So, if you want to enable debug logging in the worker or triggerer, you have to also enable debug logging in the scheduler, which produces a ton of noise and writes a ton of data to disk.
   
   ### Use case/motivation
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a 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: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Support DEBUG logging by component [airflow]

["RNHTTR (via GitHub)" <gi...@apache.org>]

RNHTTR closed issue #40840: Support DEBUG logging by component
URL: https://github.com/apache/airflow/issues/40840


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Support DEBUG logging by component [airflow]

["jedcunningham (via GitHub)" <gi...@apache.org>]

jedcunningham commented on issue #40840:
URL: https://github.com/apache/airflow/issues/40840#issuecomment-2236705594

   I do this fairly regularly already with an env var override for the config. `AIRFLOW__LOGGING__LOGGING_LEVEL=DEBUG airflow scheduler` for example. Is that not sufficient? I feel like getting more granular for the config is a slippery slope - not _that_ worker, just this one, or not _that_ KE task, just this one type thing.


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org