Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3367C200C3E for ; Tue, 21 Mar 2017 23:03:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3234A160B81; Tue, 21 Mar 2017 22:03:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 82038160B6E for ; Tue, 21 Mar 2017 23:03:46 +0100 (CET) Received: (qmail 51810 invoked by uid 500); 21 Mar 2017 22:03:45 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 51801 invoked by uid 99); 21 Mar 2017 22:03:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Mar 2017 22:03:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 62373C249F for ; Tue, 21 Mar 2017 22:03:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.549 X-Spam-Level: X-Spam-Status: No, score=-98.549 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id nuz2NnxH9qdb for ; Tue, 21 Mar 2017 22:03:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C3B085FB99 for ; Tue, 21 Mar 2017 22:03:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 309C3E08C3 for ; Tue, 21 Mar 2017 22:03:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 98C7E254D7 for ; Tue, 21 Mar 2017 22:03:41 +0000 (UTC) Date: Tue, 21 Mar 2017 22:03:41 +0000 (UTC) From: "Abel Martin (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AIRFLOW-973) Make alert emails more flexible MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Mar 2017 22:03:47 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935412#comment-15935412 ] Abel Martin edited comment on AIRFLOW-973 at 3/21/17 10:03 PM: --------------------------------------------------------------- That'd be great. We have multiple Airflow systems and we'd appreciate the ability to customize these messages. was (Author: abelmartin): That'd would be great. We have multiple Airflow systems and we'd appreciate the ability to customize these messages. > 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 (v6.3.15#6346)