You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/04/06 04:36:16 UTC

[GitHub] [airflow] milton0825 edited a comment on issue #5050: [AIRFLOW-4251] Instrument DagRun schedule delay

milton0825 edited a comment on issue #5050: [AIRFLOW-4251] Instrument DagRun schedule delay
URL: https://github.com/apache/airflow/pull/5050#issuecomment-480473472
 
 
   I think this metric is useful to track the schedule delay per `DAG`. We can use the metric to tell how behind a `DAG` is to its schedule and can quickly check the historic trend on a dashboard like Grafana.
   
   Canary monitoring serves for the purpose of tracking the delay from DAG schedule to first task execution, which may or may not represents the schedule delay for each DAG.
   
   What do you think?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services