[
https://issues.apache.org/jira/browse/AMBARI-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221210#comment-15221210
]
Hadoop QA commented on AMBARI-15656:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12796395/AMBARI-15656.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6140//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6140//console
This message is automatically generated.
> 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)
