[
https://issues.apache.org/jira/browse/HIVE-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412162#comment-16412162
]
Sergey Shelukhin edited comment on HIVE-18971 at 3/23/18 9:58 PM:
------------------------------------------------------------------
Hmm... I'm not sure actually I can easily access those right now as I'm running
custom built HS2, so it's probably not aggregating anywhere. But it should be
the same logic right?
In codahale it looks like this:
{noformat}
{
"name" : "metrics:name=WM_llap_numExecutors",
"modelerType" : "com.codahale.metrics.JmxReporter$JmxGauge",
"Value" : 72
{noformat}
I'll test separately after committing and deploying on Ambari, in process of
making dashboards.
was (Author: sershe):
Hmm... I'm not sure actually I can easily access those right now as I'm running
custom built HS2, so it's probably not aggregating anywhere.
In codahale it looks like this:
{noformat}
{
"name" : "metrics:name=WM_llap_numExecutors",
"modelerType" : "com.codahale.metrics.JmxReporter$JmxGauge",
"Value" : 72
{noformat}
I'll test separately after committing and deploying on Ambari, in process of
making dashboards.
> add HS2 WM metrics for use in Grafana and such
> ----------------------------------------------
>
> Key: HIVE-18971
> URL: https://issues.apache.org/jira/browse/HIVE-18971
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: HIVE-18971.01.patch, HIVE-18971.patch
>
>
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2
> even sets up metrics right now...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
