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

   ### Description
   
   Currently, the Airflow UI displays DAGs as independent entities, without 
preserving the folder structure in which DAGs are organized on the filesystem.
   
   ### Use case/motivation
   
   ### Motivation
   In many real-world projects, DAGs are organized into folders by domain 
(e.g.,`sales/` , `marketing/` , `finance/`). It would be very useful to see 
aggregated monitoring at the folder level in the Airflow UI. For example:
   
   - Show all DAGs from the folder `sales/`  grouped together.
   - Provide a “Recent Tasks” style view at the folder level (similar to how we 
currently see for each DAG).
   - Quickly see if any DAG in a folder had recent failures.
   
   This would allow teams to monitor business-domain pipelines more effectively 
and would reduce the need to open multiple DAG pages.
   
   
   ### Proposed behavior (high-level):
   - Display DAG folders in the UI tree, alongside individual DAGs.
   - For each folder, show aggregate DAG health (number of failed/success tasks 
in the last N runs).
   - Allow filtering/search by folder in addition to existing DAG tags.
   
   ### Alternatives considered:
   - DAG tags (already supported), but they do not provide aggregated “recent 
tasks” views, only filtering.
   - External dashboards (Grafana/Prometheus), but it would be more convenient 
to have this directly in Airflow UI.
   
   ### Impact:
   This feature would improve observability and usability for teams managing 
dozens or hundreds of DAGs across multiple business domains.
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to