venkatamandavilli-code commented on issue #53040: URL: https://github.com/apache/airflow/issues/53040#issuecomment-4724920255
@cmarteepants Thanks for opening this meta issue. I can see strong operational value in improving filtering support across the Airflow 3.x UI, especially for organizations running Airflow at enterprise scale. In environments with large DAG inventories, high-volume DAG runs, many task instances, and multiple teams using the same platform, filtering is not just a convenience feature — it directly affects troubleshooting, monitoring, governance, and day-to-day support. Filters such as DAG owner, DAG version, duration range, operator type, logical date range, queue, pool, mapped index, and asset-related filters would help users narrow down issues much faster. This would be especially useful during incident analysis, SLA reviews, post-run troubleshooting, and platform operations. I also agree that consistency across views is important. Having similar filtering behavior across DAGs, DAG Runs, Task Instances, Assets, Audit Logs, and XComs would make the new UI easier to use and reduce the learning curve for users migrating from the older UI. This would be a valuable improvement for shared Airflow platforms used by multiple business and technical teams. -- 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]
