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 26D93200C2C for ; Fri, 3 Mar 2017 07:33:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 25742160B57; Fri, 3 Mar 2017 06:33:59 +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 6CD40160B6D for ; Fri, 3 Mar 2017 07:33:58 +0100 (CET) Received: (qmail 32993 invoked by uid 500); 3 Mar 2017 06:33:57 -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 32982 invoked by uid 99); 3 Mar 2017 06:33:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2017 06:33:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3B9F4C0096 for ; Fri, 3 Mar 2017 06:33:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id TO3Mw_0fQ4C2 for ; Fri, 3 Mar 2017 06:33:56 +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 411ED5FD84 for ; Fri, 3 Mar 2017 06:33:56 +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 5952DE0652 for ; Fri, 3 Mar 2017 06:33:55 +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 437AA2417A for ; Fri, 3 Mar 2017 06:33:54 +0000 (UTC) Date: Fri, 3 Mar 2017 06:33:54 +0000 (UTC) From: "Yao Lei (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20291) Script-Based Alert Dispathers support passing more parameters to script MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 03 Mar 2017 06:33:59 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20291: ----------------------------- Affects Version/s: trunk Status: Patch Available (was: Open) > Script-Based Alert Dispathers support passing more parameters to script > ----------------------------------------------------------------------- > > Key: AMBARI-20291 > URL: https://issues.apache.org/jira/browse/AMBARI-20291 > Project: Ambari > Issue Type: Improvement > Affects Versions: trunk > Reporter: Yao Lei > Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20291.patch > > > Script-Based Alert Dispatcher now pass five parameters to script,including alert definition name, definition label,service name, alert state, and alert text. > But if script can receive other two parameters from dispather,it will be better. > 1.hostname. > Because hostname the alert for is not always included in alert text,although it may be null like aggregate alerts. > With it we can more quick to find the related host that occured alert. > 2.alert timestamp. > We may need to know the alert occurrence time ( state change time) more exactly. After the alert happened,it will spend some time to schedule the script to run. > Without it,we can only regard the script start time as the alert occurrence time. > We now use this feature to send alert information to mobile phone and suggest also passing hostname and alert timestamp. -- This message was sent by Atlassian JIRA (v6.3.15#6346)