[
https://issues.apache.org/jira/browse/AMBARI-15605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225444#comment-15225444
]
Hadoop QA commented on AMBARI-15605:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12796916/AMBARI-15605.v2.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/6190//console
This message is automatically generated.
> UI Changes To Expose Alert Repeat Tolerance Counts
> --------------------------------------------------
>
> Key: AMBARI-15605
> URL: https://issues.apache.org/jira/browse/AMBARI-15605
> 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-15605.v0.patch, AMBARI-15605.v1.patch,
> AMBARI-15605.v2.patch
>
>
> The web client will need to display alerts which have not yet reached their
> retry threshold value differently. This will involve indicating that the
> alert has gone to a non-OK state but has not yet reached the number of
> consecutive instances to be considered a true positive alert.
> The values are exposed off of the alert endpoint:
> {code}
> GET api/v1/clusters/<cluster>/alerts/<id>
> "Alert": {
> "cluster_name": "c1",
> "component_name": "AMBARI_AGENT",
> "definition_id": 3,
> "definition_name": "ambari_agent_disk_usage",
> "state" : CRITICAL,
> …
> "repeat_tolerance" : 3,
> "repeat_tolerance_remaining": 2
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
