You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/09/01 09:34:20 UTC
[jira] [Commented] (AMBARI-18292) Support dispatching assigned
alert states notification for script-based alert dispatcher
[ https://issues.apache.org/jira/browse/AMBARI-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454896#comment-15454896 ]
Hadoop QA commented on AMBARI-18292:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12826584/AMBARI-18292.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8549//console
This message is automatically generated.
> Support dispatching assigned alert states notification 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
> Fix For: 2.5.0
>
> Attachments: AMBARI-18292.patch
>
>
> By default, Ambari allow all kinds of alert states (OK,WARNING,CRITICAL,UNKNOWN) notification to dispatch in script-based alert dispatcher.
> However, sometimes we hope to filter some alert states notification
> This patch will resolve this by setting 'notification.dispatch.alert.script.states' in ambari.properties as following:
> #Only dispatch WARNING and CRITICAL alert notification
> notification.dispatch.alert.script.states=WARNING,CRITICAL
> If you don't set this property that means all notification will be dispatched
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)