You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/05/19 07:05:12 UTC
[jira] [Commented] (AMBARI-16724) Allow customizing Connection
Timeout for METRIC Alerts
[ https://issues.apache.org/jira/browse/AMBARI-16724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290596#comment-15290596 ]
Hudson commented on AMBARI-16724:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4872 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4872/])
AMBARI-16724 Allow customizing Connection Timeout for METRIC Alerts (zhewang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2344384421465e5dae3ae418bc985f9af60199b2])
* ambari-web/app/controllers/main/alerts/definition_configs_controller.js
* ambari-web/test/controllers/main/alerts/definitions_configs_controller_test.js
> 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)