Description
Add a built-in UI view that visualizes the typical (mean / median) start and end time of each Dag over a 24-hour timeline, aggregated from recent successful Dag runs.
This is not the existing Gantt view. The current Gantt is per Dag run — it shows when each task started/ended within a single run.
The proposed view operates at a different level: it aggregates across all Dags to answer "across my whole deployment, when during the day does each Dag usually run?"
DEMO
Use case/motivation
Operators running many Dags currently have no at-a-glance way to see how scheduled load is distributed across the day. To understand it today you have to open each Dag's runs one by one.
This view makes the whole schedule visible at once, which helps to:
- spot overlapping heavy windows where many Dags pile up at the same hour,
- find quiet windows for maintenance / deploys / resource-intensive jobs,
- notice drift when a Dag's typical run time shifts over recent runs,
- plan capacity and SLAs across the fleet.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
Add a built-in UI view that visualizes the typical (mean / median) start and end time of each Dag over a 24-hour timeline, aggregated from recent successful Dag runs.
This is not the existing Gantt view. The current Gantt is per Dag run — it shows when each task started/ended within a single run.
The proposed view operates at a different level: it aggregates across all Dags to answer "across my whole deployment, when during the day does each Dag usually run?"
DEMO
Use case/motivation
Operators running many Dags currently have no at-a-glance way to see how scheduled load is distributed across the day. To understand it today you have to open each Dag's runs one by one.
This view makes the whole schedule visible at once, which helps to:
Related issues
No response
Are you willing to submit a PR?
Code of Conduct