You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ruanhui (Jira)" <ji...@apache.org> on 2025/08/31 14:51:00 UTC

[jira] [Commented] (HBASE-27890) Expose a getter on Connection/AsyncConnection for getting public access to connection metrics

    [ https://issues.apache.org/jira/browse/HBASE-27890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017290#comment-18017290 ] 

ruanhui commented on HBASE-27890:
---------------------------------

ok. Thanks Duo.

> Expose a getter on Connection/AsyncConnection for getting public access to connection metrics
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27890
>                 URL: https://issues.apache.org/jira/browse/HBASE-27890
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Priority: Major
>              Labels: pull-request-available
>
> Currently the MetricsConnection metrics are only exposed via jmx. This is not very easy to deal with on the client side. In our environment we have 10s of thousands of client instances and we do not expose a jmx port. If we did, it'd be painful to try fetching from so many (and constantly changing) instances. 
> Many environments have their own monitoring stack and their own way of shipping deployables metrics to their monitoring. We should provide a way to get access to these metrics within the process. It's possible (but extremely cumbersome) to query jmx beans from within the process. We did this in my environment and I would recommend against it. Let's provide direct access to the metrics.
> I think we probably want to keep MetricsConnection IA.Private, but maybe we can create a new MetricsConnectionSnapshot and provide a getter on the Connection/AsyncConnection.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)