cmarteepants opened a new issue, #53051: URL: https://github.com/apache/airflow/issues/53051
### Body ### View Task View – Task Instances Tab <img width="1794" height="757" alt="Image" src="https://github.com/user-attachments/assets/4e102832-79fb-47b4-9453-72d08de60164"; /> ### Filters to Add - Filter by **Run ID** ↪ Allows users to locate a specific run of interest for this task - Filter by **Operator Type** ↪ Helpful for identifying runtime behavior across operator classes (e.g., all `PythonOperator` vs. `BranchOperator`) - Filter by **Duration Range** ↪ Surface long-running task instances that may require optimization - Filter by **Logical Date** (from DAG Level) ↪ Aligns with data intervals and scheduling logic - Filter by **Try Number** ↪ Identify retries or flaky task runs - Filter by **Queue** ↪ Investigate issues related to worker routing or prioritization - Filter by **Pool** ↪ Debug resource contention or pool-based throttling - Filter by **Mapped Index** ↪ Useful for triaging issues in mapped tasks, especially outlier indices - Filter by **DAG Version** and / or **Bundle Version** ↪ Correlate issues with DAG-level code changes ### API Support ⚠️ Partial - `/taskInstances` API supports filtering by: - `dag_id`, `dag_run_id`, `task_id`, `map_index`, `execution_date`, `state`, `try_number`, `queue`, `pool` - Missing support for: - `duration` range - `operator` type - `dag_version` ### UI Impact - Extend the table filter panel with these fields (some already present in the table) - Consider grouping filters into metadata (queue/pool), execution details (duration/try), and versioning ### Notes - These filters help narrow down problematic or anomalous task instances in large DAGs - Especially valuable in cases with dynamic task mapping or retry-heavy operators ### Committer - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project. -- 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]
