[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377161#comment-14377161
]
Nick Dimiduk commented on CALCITE-642:
--------------------------------------
I have two minds on this. On the one side, I think Avatica should support
metrics out of the box. That means deploying something based on a
light-weight/minimal metrics library such as Dropwizard Metrics. On the other
hand, consuming projects probably already have a metrics system available --
notably Hadoop having it's own Hadoop metrics (for Hive and Phoenix).
Maybe the right approach is to build an internal API for emitting metrics,
allowing the implementation they feed to be pluggable. I don't know how complex
this might be.
> Avatica server metrics
> ----------------------
>
> Key: CALCITE-642
> URL: https://issues.apache.org/jira/browse/CALCITE-642
> Project: Calcite
> Issue Type: Improvement
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: next
>
>
> Along the same lines as CALCITE-641, avatica server should track some basic
> metrics. We can expose them through a "standard" API (such as Hadoop metrics,
> or Dropwizard metrics), and include them on some interval in the service log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
