[
https://issues.apache.org/jira/browse/AMBARI-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221930#comment-15221930
]
Hudson commented on AMBARI-15656:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4582 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4582/])
AMBARI-15656 - Record and Expose Alert Occurrence Values (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b8b7436631b7e32b95676c80b5fb5afe683d70a])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
*
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertCurrentEntity.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertResourceProvider.java
> 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)
