[Filters] Add filters to Task View - Task Instances Tab

[cmarteepants]

View

Task View – Task Instances Tab

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

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[mkkubins]

Hi,

I am looking on this issue, any examples in the UI somewhere how it should look like?

[mkkubins]

I would like to take this issue. Can you assign it to me?

[Lee-W]

Sure :)

[vatsrahul1001]

@mkkubins i , how are we progressing on this?