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 7E970200C81 for ; Fri, 26 May 2017 09:04:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7D37F160BC8; Fri, 26 May 2017 07:04:09 +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 BF8B9160BB8 for ; Fri, 26 May 2017 09:04:08 +0200 (CEST) Received: (qmail 75626 invoked by uid 500); 26 May 2017 07:04:08 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 75617 invoked by uid 99); 26 May 2017 07:04:07 -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; Fri, 26 May 2017 07:04:07 +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 918E1C0A53 for ; Fri, 26 May 2017 07:04:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Yi_FhESjDTod for ; Fri, 26 May 2017 07:04:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D86D55F297 for ; Fri, 26 May 2017 07:04:05 +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 DF367E0D50 for ; Fri, 26 May 2017 07:04:04 +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 3C88F21B5A for ; Fri, 26 May 2017 07:04:04 +0000 (UTC) Date: Fri, 26 May 2017 07:04:04 +0000 (UTC) From: "Yao Lei (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 26 May 2017 07:04:09 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: ----------------------------- Description: Although we can create the alert target of type ALERT_SCRIPT by web ui (AMBARI-18423), we still need access to ambari.properties to add the new script and then restart ambari server to make this function take effect.It is better specify the script directly in alert target rather than in ambari.properties.In this way,we also don't need to restart ambari server. So now on web ui we can offer two ways to configure the script location for script-based alert dispatchers: 1.By script dispatch property (*ambari.dispatch-property.script*).This is already supported in previous ambari release. Please see https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 2.By script filename(*ambari.dispatch-property.script.filename*). This new way will lookup the script by filename in script directory,default in /var/lib/ambari-server/resources/scripts. We can change the directory in ambari.properties by *notification.dispatch.alert.script.directory* property. was: Although we can create the alert target of type ALERT_SCRIPT by web ui (AMBARI-18423), we still need access to ambari.properties to add the new script and then restart ambari server to make this function take effect.It is better specify the script directly in alert target rather than in ambari.properties.In this way,we also don't need to restart ambari server. So now on web ui we can offer two ways to configure the script location for script-based alert dispatchers: 1.By script dispatch property (*ambari.dispatch-property.script*).This is already supported in previous ambari release. Please see https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 2.By script filename(*ambari.dispatch-property.script.filename*). This new way will lookup the script by filename in script directory,default in /var/lib/ambari-server/resources/scripts. We can change the directory in ambari.properties by notification.dispatch.alert.script.directory property. > Specify the script directly in alert target for script-based alert dispatchers > ------------------------------------------------------------------------------ > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web > Affects Versions: trunk > Reporter: Yao Lei > Assignee: Yao Lei > Fix For: 3.0.0 > > > Although we can create the alert target of type ALERT_SCRIPT by web ui (AMBARI-18423), we still need access to ambari.properties to add the new script and then restart ambari server to make this function take effect.It is better specify the script directly in alert target rather than in ambari.properties.In this way,we also don't need to restart ambari server. > So now on web ui we can offer two ways to configure the script location for script-based alert dispatchers: > 1.By script dispatch property (*ambari.dispatch-property.script*).This is already supported in previous ambari release. > Please see https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(*ambari.dispatch-property.script.filename*). > This new way will lookup the script by filename in script directory,default in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by *notification.dispatch.alert.script.directory* property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)