[jira] [Updated] (AMBARI-15656) Record and Expose Alert Occurrence Values

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

     [ 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)