[ https://issues.apache.org/jira/browse/AIRFLOW-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
t oo updated AIRFLOW-6419: -------------------------- Description: dag level logs are written under separate date folders. This is great because the old dates are not 'modified/accessed' so they can be easily purged by utilities like tmpwatch This JIRA is about making other logs (such as dag_processor_manager/webserver/scheduler.etc) go under separate date folders to allow easy purging. the log from redirecting 'airflow scheduler' to stdout grows over 100mb a day in my env was: scheduler logs are written under separate date folders. This is great because the old dates are not 'modified/accessed' so they can be easily purged by utilities like tmpwatch This JIRA is about making other logs (such as dag_processor_manager/webserver.etc) go under separate date folders to allow easy purging Summary: dag_processor_manager/webserver/scheduler logs should be created under date folder (was: dag_processor_manager/webserver logs should be created under date folder) > dag_processor_manager/webserver/scheduler logs should be created under date > folder > ---------------------------------------------------------------------------------- > > Key: AIRFLOW-6419 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6419 > Project: Apache Airflow > Issue Type: Improvement > Components: logging > Affects Versions: 1.10.7 > Reporter: t oo > Priority: Major > > dag level logs are written under separate date folders. This is great because > the old dates are not 'modified/accessed' so they can be easily purged by > utilities like tmpwatch > This JIRA is about making other logs (such as > dag_processor_manager/webserver/scheduler.etc) go under separate date folders > to allow easy purging. the log from redirecting 'airflow scheduler' to stdout > grows over 100mb a day in my env -- This message was sent by Atlassian Jira (v8.3.4#803005)