ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-5640) Ambari-SCOM : HISTORYSERVER metrics
Date Wed, 30 Apr 2014 19:00:16 GMT

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

Tom Beerbower updated AMBARI-5640:
----------------------------------

    Description: 
Make sure that HISTORYSERVER metrics are available and names are consistent with existing
metric names for other services.

Note : we have a lot of inconsistencies between metric names (underscrore, camel case, etc).
 We can't fix this in API v1, but for new services we should make sure that the names are
consistent with other services (i.e. we should be consistently inconsistent).  For example,
in all existing services we have a metric named RpcQueueTime_avg_time.  We shouldn't call
it RpcQueueTimeAvgTime in HISTORYSERVER.



  was:
Make sure that HISTORYSERVER metrics are available and names are consistent with existing
metric names for other services.




> Ambari-SCOM : HISTORYSERVER metrics
> -----------------------------------
>
>                 Key: AMBARI-5640
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5640
>             Project: Ambari
>          Issue Type: Bug
>          Components: Ambari-SCOM
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>
> Make sure that HISTORYSERVER metrics are available and names are consistent with existing
metric names for other services.
> Note : we have a lot of inconsistencies between metric names (underscrore, camel case,
etc).  We can't fix this in API v1, but for new services we should make sure that the names
are consistent with other services (i.e. we should be consistently inconsistent).  For example,
in all existing services we have a metric named RpcQueueTime_avg_time.  We shouldn't call
it RpcQueueTimeAvgTime in HISTORYSERVER.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message