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 EF349200C72 for ; Fri, 7 Apr 2017 04:17:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EDB66160B91; Fri, 7 Apr 2017 02:17:45 +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 3FCEC160B9F for ; Fri, 7 Apr 2017 04:17:45 +0200 (CEST) Received: (qmail 56791 invoked by uid 500); 7 Apr 2017 02:17:44 -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 56782 invoked by uid 99); 7 Apr 2017 02:17:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Apr 2017 02:17:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F3D4B189F88 for ; Fri, 7 Apr 2017 02:17:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id GecI4x93uexO for ; Fri, 7 Apr 2017 02:17:43 +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 7D4365F1E9 for ; Fri, 7 Apr 2017 02:17:42 +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 CD939E00B4 for ; Fri, 7 Apr 2017 02:17:41 +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 89B8924065 for ; Fri, 7 Apr 2017 02:17:41 +0000 (UTC) Date: Fri, 7 Apr 2017 02:17:41 +0000 (UTC) From: "Yao Lei (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (AMBARI-18423) Support creating/editing alert dispatch targets for script-based alert dispatchers by web wizard instead of command line MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 07 Apr 2017 02:17:46 -0000 [ https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei reassigned AMBARI-18423: -------------------------------- Assignee: Yao Lei > Support creating/editing alert dispatch targets for script-based alert dispatchers by web wizard instead of command line > ------------------------------------------------------------------------------------------------------------------------ > > Key: AMBARI-18423 > URL: https://issues.apache.org/jira/browse/AMBARI-18423 > Project: Ambari > Issue Type: Improvement > Components: alerts, ambari-web > Affects Versions: trunk > Reporter: Yao Lei > Assignee: Yao Lei > Priority: Minor > Fix For: trunk > > Attachments: alert_script_target_1.png, alert_script_target_2.png, alert_script_target_3.png, AMBARI-18423_1.patch, AMBARI-18423.patch > > > Ambari now support creating/editing three kinds of alert dispatch targets by web wizard, including EMAIL,SNMP,Custom SNMP. > If we want to create another kind of alert dispatch target ALERT_SCRIPT for script-based alert dispatcher,we have to execute a command manually like following: > {code} > POST api/v1/alert_targets > > { > "AlertTarget": { > "name": "syslogger", > "description": "Syslog Target", > "notification_type": "ALERT_SCRIPT", > "global": true > } > } > {code} > or > {code} > POST api/v1/alert_targets > { > "AlertTarget": { > "name": "syslogger", > "description": "Syslog Target", > "notification_type": "ALERT_SCRIPT", > "global": false, > "groups":[1,3] > "alert_states":["WARNING","CRITICAL","UNKNOWN"], > "properties": { > "ambari.dispatch-property.script": "com.mycompany.dispatch.syslog.script" > } > } > } > {code} > More details, please see https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > We should do this by web wizard rather than command line, which will lead to more convenience > We think it is really helpeful for us when using script-based alert dispatcher. -- This message was sent by Atlassian JIRA (v6.3.15#6346)