[
https://issues.apache.org/jira/browse/CALCITE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471323#comment-16471323
]
Karan Mehta commented on CALCITE-2307:
--------------------------------------
{{Np, [~elserj]}}
{{Http2Server}} is an example class from
https://github.com/eclipse/jetty.project I used to find how to integrate
jetty-jmx and worked my way backwards.
[https://www.eclipse.org/jetty/documentation/current/jmx-chapter.html] is an
relevant link too from their documentation.
[https://www.eclipse.org/jetty/documentation/current/jetty-jmx-annotations.html]
shows they decide the MBeans that needs to be exposed.
I did a quick POC in {{HTTPServer}} class from avatica and determined that it
works. Let me know if you need anything else.
> Expose Jetty server metrics via Avatica-server
> ----------------------------------------------
>
> Key: CALCITE-2307
> URL: https://issues.apache.org/jira/browse/CALCITE-2307
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Karan Mehta
> Priority: Major
>
> To know how the jetty server is performing, we need to know its metrics.
> Eclipse Jetty already provides a way to publish its internal metrics to JMX.
> However we need to enable it. This involves adding an additional dependency
> on the jetty-jmx project and adding the MBeanContainter in the server beans.
> We can customize this via a config parameter if required.
> This is essential for PHOENIX-3655
> [~elserj] [~apurtell]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
