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

Posted to commits@airflow.apache.org by "James Meickle (JIRA)" <ji...@apache.org> on 2018/03/12 18:55:00 UTC

[jira] [Commented] (AIRFLOW-973) Make alert emails more flexible

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

James Meickle commented on AIRFLOW-973:
---------------------------------------

+1 on this. We have the same DAG code running in stg/prd environments and can't differentiate emails except by looking at the domain in the sender.

I suggest allowing a "cluster name" in the config file, and defaulting it to "airflow". Then use that cluster name as the [tag] at the start of the email, rather than hardcoding it to 'airflow'.

> Make alert emails more flexible
> -------------------------------
>
>                 Key: AIRFLOW-973
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-973
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Peter Sujan
>            Priority: Minor
>
> For email filing/organization purposes, it would be useful to be able to customize the alert emails. As a start, the ability to add a custom prefix to the subject line should be pretty simple to add - it could be read from the config file. I think it could be interesting to format the email body as well, though I don't have a good design for this (perhaps the user could supply a format string or jinja template?). I'm happy to attempt the change myself, but would like to hear others' input first.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)