[
https://issues.apache.org/jira/browse/CALCITE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107613#comment-15107613
]
Josh Elser commented on CALCITE-642:
------------------------------------
I was pondering on this one today and am extremely glad to see Julian and Nick
had came to the same conclusion I did :)
* Metrics2 is nice in that it's auto-magically integrate-able with some others
systems, but the API leaves a bit to be desired; Dropwizard's API is much nicer
to work with
* We probably don't want to pull in all of hadoop-common to Avatica anyways
* We can do runtime wiring of Avatica to lots of systems -- maybe automagically
publish to a metrics2 sink like Nick said
* Could also investigate integration with other systems via a well-documented
JSON or JMX endpoint (some tools like Ambari can already reach out and scrape
data)
> Avatica server metrics
> ----------------------
>
> Key: CALCITE-642
> URL: https://issues.apache.org/jira/browse/CALCITE-642
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> 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)
