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

Posted to dev@airflow.apache.org by Lance Norskog <la...@gmail.com> on 2016/05/16 19:07:07 UTC

About alarms

How do you folks handle notifications and alarms when tasks fail?

We have hourly and daily tasks, and use Hipchat, email and Nagios for
notification.

-- 
Lance Norskog
lance.norskog@gmail.com
Redwood City, CA

Re: About alarms

Posted by Maxime Beauchemin <ma...@gmail.com>.

Note that you can use tasks through operators (SlackOperator,
EmailOperator, PythonOperator, ...) along with trigger_rule, but you can
also use your own callbacks by passing a callable to any operators's
`on_failure_callback`, `on_retry_callback` and/or `on_success_callback`.

More about these callbacks here:
http://pythonhosted.org/airflow/code.html?highlight=on_failure_callback#baseoperator

Max

On Mon, May 16, 2016 at 1:19 PM, Chris Riccomini <cr...@apache.org>
wrote:

> Right now, we're just using email. Planning to use Slack shortly.
>
> On Mon, May 16, 2016 at 12:07 PM, Lance Norskog <la...@gmail.com>
> wrote:
>
> > How do you folks handle notifications and alarms when tasks fail?
> >
> > We have hourly and daily tasks, and use Hipchat, email and Nagios for
> > notification.
> >
> > --
> > Lance Norskog
> > lance.norskog@gmail.com
> > Redwood City, CA
> >
>

Re: About alarms

Posted by Chris Riccomini <cr...@apache.org>.

Right now, we're just using email. Planning to use Slack shortly.

On Mon, May 16, 2016 at 12:07 PM, Lance Norskog <la...@gmail.com>
wrote:

> How do you folks handle notifications and alarms when tasks fail?
>
> We have hourly and daily tasks, and use Hipchat, email and Nagios for
> notification.
>
> --
> Lance Norskog
> lance.norskog@gmail.com
> Redwood City, CA
>