[
https://issues.apache.org/jira/browse/HIVE-14752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492934#comment-15492934
]
Barna Zsombor Klara commented on HIVE-14752:
--------------------------------------------
I was actually planning to make use of the Metrics API we have in place.
Codahale metrics is already part of Hive (we only use it in HS2 AFAIK) and has
a decent API to track most of the things I need.
While it is not persisted anywhere, we do dump it out on the HS2 webui, and we
can see it over JMX too.
I agree that the format in the webui is not very readable right now, but a
separate jira could make it a bit prettier.
The thing I like about codahale is that it could give an at a glance look at
what is going on in the server/metastore. While the logs would need to be post
processed a bit.
> New metrics should be introduced to more easily monitor the workload of
> HS2/HMS
> -------------------------------------------------------------------------------
>
> Key: HIVE-14752
> URL: https://issues.apache.org/jira/browse/HIVE-14752
> Project: Hive
> Issue Type: Task
> Components: Hive, HiveServer2, Metastore
> Reporter: Barna Zsombor Klara
> Assignee: Barna Zsombor Klara
>
> Currently we have no way to easily track the number of sessions/queries in a
> HS2 instance.
> It would be great if we could tell the number of queries being run, which
> lifecycle phase they are in (submitted, compilation, execution), and how much
> time was spent executing/compiling them.
> This Jira will be an umbrella to track the subtasks for each potentially
> useful metric we can think of.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
