You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Christian (JIRA)" <ji...@apache.org> on 2019/08/08 15:18:00 UTC
[jira] [Updated] (AIRFLOW-5146) Add ability to monitor queueing
duration of DAG runs
[ https://issues.apache.org/jira/browse/AIRFLOW-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian updated AIRFLOW-5146:
-------------------------------
Description:
As a system administrator I would like to monitor the system load based on the duration tasks reside in the {{QUEUED}} state. With this information it is possible to see potential bottlenecks which may be caused by ,e.g., {{schedule_intervals}} that fall together.
Right now this information cannot be retrieved easily from the database without writing additional lines of code, to extract that information.
was:
As a system administrator I would like to monitor the system load based on the duration tasks reside in the `QUEUED` state. With this information it is possible to see potential bottlenecks which may be caused by ,e.g., `schedule_intervals` that fall together.
Right now this information cannot be retrieved easily from the database without writing additional lines of code, to extract that information.
> Add ability to monitor queueing duration of DAG runs
> ----------------------------------------------------
>
> Key: AIRFLOW-5146
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5146
> Project: Apache Airflow
> Issue Type: Wish
> Components: DagRun, database
> Affects Versions: 2.0.0, 1.10.5
> Reporter: Christian
> Priority: Minor
>
> As a system administrator I would like to monitor the system load based on the duration tasks reside in the {{QUEUED}} state. With this information it is possible to see potential bottlenecks which may be caused by ,e.g., {{schedule_intervals}} that fall together.
> Right now this information cannot be retrieved easily from the database without writing additional lines of code, to extract that information.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)