Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 369A819DB7 for ; Wed, 6 Apr 2016 02:07:26 +0000 (UTC) Received: (qmail 77585 invoked by uid 500); 6 Apr 2016 02:07:25 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 77550 invoked by uid 500); 6 Apr 2016 02:07:25 -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 77533 invoked by uid 99); 6 Apr 2016 02:07:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2016 02:07:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 91C052C1F4E for ; Wed, 6 Apr 2016 02:07:25 +0000 (UTC) Date: Wed, 6 Apr 2016 02:07:25 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-15720) AGGREGATE Alerts Should Not Expose Repeat Tolerance or Tolerance Enabled Settings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227564#comment-15227564 ] Hadoop QA commented on AMBARI-15720: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12797163/AMBARI-15720.v0.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6238//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6238//console This message is automatically generated. > AGGREGATE Alerts Should Not Expose Repeat Tolerance or Tolerance Enabled Settings > --------------------------------------------------------------------------------- > > Key: AMBARI-15720 > URL: https://issues.apache.org/jira/browse/AMBARI-15720 > Project: Ambari > Issue Type: Task > Components: ambari-web > Affects Versions: 2.4.0 > Reporter: Zhe (Joe) Wang > Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-15720.v0.patch > > > {{AGGREGATE}} type alerts should not expose a {{repeat_tolerance}} or {{repeat_tolerance_enabled}} setting in the web client. This is because of the nature of how {{AGGREGATE}} alerts functions. They respond to {{HARD}} alert events and are therefore simply a summary of the known alerts which have already reached their repeat tolerance levels. > These types of alerts will not honor a global repeat tolerance value ({{cluster-env/alerts_repeat_tolerance}} nor will they honor changes to alert definitions of source type {{AGGREGATE}}. > They effectively have a tolerance of 1 always. -- This message was sent by Atlassian JIRA (v6.3.4#6332)