[
https://issues.apache.org/jira/browse/HIVE-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255520#comment-15255520
]
Lefty Leverenz commented on HIVE-13480:
---------------------------------------
Doc note: This adds *hive.service.metrics.hadoop2.frequency* and
*hive.service.metrics.hadoop2.component* to HiveConf.java and adds HADOOP2 to
the description of *hive.service.metrics.reporter*. They need to be documented
in the Metrics section of Configuration Properties for release 2.1.0.
* [Configuration Properties -- Metrics |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-Metrics]
> Add hadoop2 metrics reporter for Codahale metrics
> -------------------------------------------------
>
> Key: HIVE-13480
> URL: https://issues.apache.org/jira/browse/HIVE-13480
> Project: Hive
> Issue Type: Bug
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Labels: TODOC2.1
> Fix For: 2.1.0
>
> Attachments: HIVE-13480.2.patch, HIVE-13480.3.patch,
> HIVE-13480.4.patch, HIVE-13480.5.patch, HIVE-13480.patch
>
>
> Multiple other apache components allow sending metrics over to Hadoop2
> metrics, which allow for monitoring solutions like Ambari Metrics Server to
> work against that to show metrics for components in one place. Our Codahale
> metrics works very well, so ideally, we would like to bridge the two, to
> allow Codahale to add a Hadoop2 reporter that enables us to continue to use
> Codahale metrics (i.e. not write another custom metrics impl) but report
> using Hadoop2.
> Apache Phoenix also had such a recent usecase and were in the process of
> adding in a stub piece that allows this forwarding. We should use the same
> reporter to minimize redundancy while pushing metrics to a centralized
> solution like Hadoop2 Metrics/AMS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
