You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Himanshu Garg (JIRA)" <ji...@apache.org> on 2019/05/30 11:41:00 UTC
[jira] [Commented] (AIRFLOW-4596) Capture stats for dagrun schedule
delay for adhoc/nonschduled task
[ https://issues.apache.org/jira/browse/AIRFLOW-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851767#comment-16851767 ]
Himanshu Garg commented on AIRFLOW-4596:
----------------------------------------
cc [~vardan]
> Capture stats for dagrun schedule delay for adhoc/nonschduled task
> ------------------------------------------------------------------
>
> Key: AIRFLOW-4596
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4596
> Project: Apache Airflow
> Issue Type: New Feature
> Components: models
> Affects Versions: 1.10.3
> Reporter: Himanshu Garg
> Assignee: Himanshu Garg
> Priority: Major
>
> With respect to the metric we are capturing in airflow version v1-10 - https://github.com/apache/airflow/blob/v1-10-stable/docs/metrics.rst. The Timer merics `dagrun.schedule_delay.<dag_id>` `Seconds of delay between the scheduled DagRun start date and the actual DagRun start date`
> we are capturig the delay of only schduled Dags.
> But we can also include delay in the adhoc/non-scheduled Dags by capturing the difference between `start_date` in `dag_run` table and `start_date` in `task_instance` table keeping the `dag_id` and `excecution` date as the cardinality for performing join.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)