Detecting long-running tasks

[dominic-lcw]

Description

In the current overview, we can easily spot out dag runs that are long running. But it is not that convenient to debug into it.

Use case/motivation

I think it would be nice to have the below UI features:

• In the overview page, user is able to click on the long-running dagrun bar and go to specific page.

Another thoughts on API:

• Would it be useful to have an api endpoint that take in (dag_id, look_back_range, algorithm) and return the dag_id's that are detected to be long-running outliers based on certain algorithm?

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[bbovenzi]

The duration graphs need some love in 3.1.

• +1 on clicking on a bar to select
• We should also remove the animation during auto refresh
• The labels need some reworking too. They add a lot of noise and whitespace, shrinking the usable area of the graph

[dominic-lcw]

Thanks Roy!

[pierrejeambrun]

Closing as main functionality has been implemented in #50416 (link from duration graph).

Creating an other issues for labels and refresh.

[pierrejeambrun]

#54786