You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ace Haidrey (JIRA)" <ji...@apache.org> on 2017/12/14 01:27:00 UTC

[jira] [Commented] (AIRFLOW-511) DagRun Failure: Retry, Email, Callbacks

    [ https://issues.apache.org/jira/browse/AIRFLOW-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290191#comment-16290191 ] 

Ace Haidrey commented on AIRFLOW-511:
-------------------------------------

[~aoen] [~bolke] [~Fokko] etc.

Can one of you take a look at this request and give thoughts on how to best implement this. I can make the PR, testing, etc. if no one else will but I think this is quite an important feature. Airflow's pillars to visualize, maintain, and monitor pipelines, and not getting messages on dagrun timeouts has no solution to monitoring. 

> DagRun Failure: Retry, Email, Callbacks
> ---------------------------------------
>
>                 Key: AIRFLOW-511
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-511
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Rob Froetscher
>            Priority: Minor
>
> Are there any plans to have retry, email, or callbacks on failure of a DAG run? Would you guys be open to someone implementing that? Right now particularly with dagrun_timeout, there is not much insight that the dag actually stopped.
> Pseudocode: https://github.com/apache/incubator-airflow/compare/master...rfroetscher:dagrun_failure



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)