deepak4babu opened a new issue, #54132: URL: https://github.com/apache/airflow/issues/54132
### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.10.3 ### What happened? We have enabled dag processor to route dag_processor_manager logs to stdout using this env - AIRFLOW__LOGGING__DAG_PROCESSOR_MANAGER_LOG_STDOUT. But still the logs are logged inside the container as well. In addition to thsi, the clean-logs script shipped as part of airflow, is not cleaning the rotated logs that ends `.1`, `.2` etc. ### What you think should happen instead? Once the logs are routed to stdout, it should be logged inside the container. ### How to reproduce Enable AIRFLOW__LOGGING__DAG_PROCESSOR_MANAGER_LOG_STDOUT env to "True". Exec into dag-processor container and check the logs path. ### Operating System Debian GNU/Linux ### Versions of Apache Airflow Providers apache-airflow-providers-celery==3.8.3 apache-airflow-providers-cncf-kubernetes==10.1.0 apache-airflow-providers-common-compat==1.2.1 apache-airflow-providers-common-io==1.4.2 apache-airflow-providers-common-sql==1.19.0 apache-airflow-providers-fab==1.5.2 apache-airflow-providers-ftp==3.11.1 apache-airflow-providers-http==4.13.2 apache-airflow-providers-imap==3.7.0 apache-airflow-providers-smtp==1.8.0 apache-airflow-providers-sqlite==3.9.0 ### Deployment Other ### Deployment details We use a slightly modified version of official helm chart ### 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]
