[jira] [Commented] (AMBARI-15647) Alerts Using the SKIPPED State Cause Stale Alert Notification

["Kristopher Kane (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219891#comment-15219891 ] 

Kristopher Kane commented on AMBARI-15647:
------------------------------------------

[~jonathan.hurley] Do you have a list of all the alerts this affects or where can I see which implement the SKIPPED state? 

> Alerts Using the SKIPPED State Cause Stale Alert Notification
> -------------------------------------------------------------
>
>                 Key: AMBARI-15647
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15647
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.4.0
>
>
> SCRIPT alerts which use the {{SKIPPED}} state as a way of preventing processing are causing instances of the Ambari Stale Alert to trigger. This is because the agents do not return these alerts in the heartbeat causing their timestamps not to update.
> STR:
> - Create a SCRIPT alert which returns {{SKIPPED}} as it's state.
> - Wait for the stale alert to trigger.
> {code}
> There are 1 stale alerts from 1 host(s): c6401.ambari.apache.org[NameNode Service RPC Queue Latency (Hourly) (2h 18m), NameNode Service RPC Processing Latency (Hourly) (2h 18m)]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)