[
https://issues.apache.org/jira/browse/HBASE-25895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351841#comment-17351841
]
Sean Busbey commented on HBASE-25895:
-------------------------------------
{quote}
Publishes a set of JSON endpoints following a RESTful structure, which expose a
subset of the o.a.h.h.ClusterMetrics’ object tree. The URI structure is as
follows
/api/v1/admin/cluster_metrics
/api/v1/admin/cluster_metrics/live_servers
/api/v1/admin/cluster_metrics/dead_servers
{quote}
How does this API definition square with our downstream facing compatibility
and versioning promises ([ref guide
section|http://hbase.apache.org/book.html#hbase.versioning])?
Is this api entirely meant to be private, for our internal use when building
HBase UI? Is it meant to be covered under “wire compatibility”? Is it meant to
be treated as client api, and if so is all of it public or only some?
This comment in {{...http/api_v1/cluster_metrics/package-info.java}}:
{code}
* Exposes the (@link org.apache.hadoop.hbase.ClusterMetrics) object over HTTP
as a REST
* resource hierarchy. Intended for Master * {@link
org.apache.hadoop.hbase.http.InfoServer) consumption only.
@InterfaceAudience.Private
package org.apache.hadoop.hbase.master.http.api_v1.cluster metrics;
{code}
leads me to believe entirely private. If that’s the case we should note it
somewhere more prominent because I don’t think downstream users are likely to
notice.
> Implement a Cluster Metrics JSON endpoint
> -----------------------------------------
>
> Key: HBASE-25895
> URL: https://issues.apache.org/jira/browse/HBASE-25895
> Project: HBase
> Issue Type: Sub-task
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
>
> In order to build a dynamic visualization functionality, we need access to
> the underlying dataset. I think we can do a lot by exposing the
> ClusterMetrics already available via the {{o.a.h.h.client.Admin}} interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
