You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yao Lei (JIRA)" <ji...@apache.org> on 2016/09/22 01:08:20 UTC

[jira] [Issue Comment Deleted] (AMBARI-18292) Support dispatching notifications of assigned alert states for script-based alert dispatcher

     [ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yao Lei updated AMBARI-18292:
-----------------------------
    Comment: was deleted

(was: See  https://reviews.apache.org/r/51599/.
Alert states can be set when creating or editing alert target 
)

> Support dispatching notifications of assigned alert states for script-based alert dispatcher
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18292
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18292
>             Project: Ambari
>          Issue Type: Improvement
>          Components: alerts
>    Affects Versions: trunk
>            Reporter: Yao Lei
>         Attachments: AMBARI-18292.1.patch, AMBARI-18292.patch
>
>
> By default, Ambari allow all notifications of all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) to dispatch in script-based alert dispatcher.
> However, sometimes we hope to filter notification of some alert states 
> This patch will resolve this by setting 'notification.dispatch.alert.script.states'  in ambari.properties  as following:
> #Only dispatch WARNING and CRITICAL  state  notification 
> notification.dispatch.alert.script.states=WARNING,CRITICAL 
> If you don't set this property that means all notifications  will be dispatched
> I think  making the desired  notifications  configurable  is useful for Ambari users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)