[jira] [Updated] (AMBARI-16724) Allow customizing Connection Timeout for METRIC Alerts

["Zhe (Joe) Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-16724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhe (Joe) Wang updated AMBARI-16724:
------------------------------------
    Attachment: AMBARI-16724.v0.patch

Modified unit test.
Local ambari-web test passed.
27819 tests complete (24 seconds)
  154 tests pending
Manual testing done.

> Allow customizing Connection Timeout for METRIC Alerts 
> -------------------------------------------------------
>
>                 Key: AMBARI-16724
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16724
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Zhe (Joe) Wang
>            Assignee: Zhe (Joe) Wang
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16724.v0.patch
>
>
> METRIC alert types have a connection timeout in their definition but that value is not exposed in the Ambari Web UI (like WEB alerts are).
> {code}
>      "uri" : {
>         "http" : "{{ams-hbase-site/hbase.master.info.port}}",
>         "default_port" : 61310.0,
>         "connection_timeout" : 5.0
>       }
>  {code}
> Include exposing the *Connection Timeout* critical threshold in Ambari Web for METRIC alert types.



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