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 D502519455 for ; Fri, 1 Apr 2016 13:43:25 +0000 (UTC) Received: (qmail 87312 invoked by uid 500); 1 Apr 2016 13:43:25 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 87269 invoked by uid 500); 1 Apr 2016 13:43: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 87258 invoked by uid 99); 1 Apr 2016 13:43:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 13:43:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 766442C14F6 for ; Fri, 1 Apr 2016 13:43:25 +0000 (UTC) Date: Fri, 1 Apr 2016 13:43:25 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15656) Record and Expose Alert Occurrence Values 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-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15656: ------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > Record and Expose Alert Occurrence Values > ----------------------------------------- > > Key: AMBARI-15656 > URL: https://issues.apache.org/jira/browse/AMBARI-15656 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15656.patch > > > Alert repeat tolerance values should be captured and exposed via the API. The rules for capturing the occurrences of an alert are: > - Alert instances always start at 1 > - Alerts with an {{OK}} state always reset the counter > - When transitioning from {{OK}} to non-{{OK}}, the counter is reset > - When transitioning within non-{{OK}} states (such as back and forth between {{WARNING}} and {{CRITICAL}}, the counter is merely incremented. > {code} > GET api/v1/clusters/c1/alerts/1 > { > "href": "http://localhost:8080/api/v1/clusters/c1/alerts/1", > "Alert": { > "cluster_name": "c1", > ... > "repeat_tolerance": 1, > "repeat_tolerance_remaining": 0, > "occurrences": 8, > .... > {code} > - {{OK}} alert instances will *always* have a value of {{0}} for {{repeat_tolerance_remaining}} since they do not honor repeat tolerance. An {{OK}} alert is considered to be correct always. -- This message was sent by Atlassian JIRA (v6.3.4#6332)