tencent cloud

Elastic MapReduce

  • Release Notes and Announcements
  • Product Introduction
  • Purchase Guide
    • EMR on CVM Billing Instructions
    • EMR on TKE Billing Instructions
    • EMR Serverless HBase Billing Instructions
    • EMR Serverless TCBase Billing Overview
  • Getting Started
  • EMR on CVM Operation Guide
    • Planning Cluster
    • Administrative rights
    • Configuring Cluster
    • Managing Cluster
    • Managing Service
    • Monitoring and Alarms
    • TCInsight
  • EMR on TKE Operation Guide
  • EMR Serverless HBase Operation Guide
  • EMR Serverless TCBase Operation Guide
  • EMR Development Guide
    • Hadoop Development Guide
    • Spark Development Guide
    • HBase Development Guide
    • Phoenix on Hbase Development Guide
    • Hive Development Guide
    • Presto Development Guide
    • Sqoop Development Guide
    • Hue Development Guide
    • Oozie Development Guide
    • Flume Development Guide
    • Kerberos Development Guide
    • Knox Development Guide
    • Alluxio Development Guide
    • Kylin Development Guide
    • Livy Development Guide
    • Kyuubi Development Guide
    • Zeppelin Development Guide
    • Hudi Development Guide
    • Superset Development Guide
    • Impala Development Guide
    • Druid Development Guide
    • TensorFlow Development Guide
    • Kudu Development Guide
    • Ranger Development Guide
    • Kafka Development Guide
    • StarRocks Development Guide
    • Flink Development Guide
    • JupyterLab Development Guide
    • MLflow Development Guide
  • Practical Tutorial
    • Practice of EMR on CVM Ops
    • Data Migration
    • Practical Tutorial on Custom Scaling
  • API Documentation
    • History
    • Introduction
    • API Category
    • Making API Requests
    • Cluster Resource Management APIs
    • Cluster Service APIs
    • User Management APIs
    • Information Query APIs
    • Information Query APIs
    • Scaling APIs
    • Configuration APIs
    • Other APIs
    • Cluster Lifecycle APIs
    • Serverless HBase APIs
    • YARN Resource Scheduling APIs
    • Data Types
    • Error Codes
  • FAQs
    • EMR on CVM
  • Service Level Agreement
  • Contact Us

DescribeHBaseTableRequestMetric

Baixar
Modo Foco
Tamanho da Fonte
Última atualização: 2026-10-10 14:58:39

1. API Description

Domain name for API request: emr.intl.tencentcloudapi.com.

This API is used to obtain the read/write rate at the HBase table level.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: DescribeHBaseTableRequestMetric.
Version Yes String Common Params. The value used for this API: 2019-01-03.
Region Yes String Common Params. For more information, please see the list of regions supported by the product.
InstanceId Yes String Cluster ID.
TableName Yes String HBase table name.
RegionServer No String HBase RegionServer service.
Downsample No String Specifies the data monitoring granularity to be obtained.
StartTime No Integer Specifies the start timestamp of the monitoring data to be queried.
EndTime No Integer Specifies the end timestamp of the monitoring data to be queried.

3. Output Parameters

Parameter Name Type Description
MetricDataList Array of HBaseMetricData Package structure returned by the HBase monitoring metric.
RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

4. Example

Example1 Obtaining Read/Write Request Metrics at the HBase Table Level

This example shows you how to obtain the read/write request metrics at the HBase table level.

Input Example

POST / HTTP/1.1
Host: emr.intl.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: DescribeHBaseTableRequestMetric
<Common request parameters>

{
    "InstanceId": "emr-lvr4kbpk",
    "TableName": "hbase_meta",
    "StartTime": 1764826199,
    "EndTime": 1764828199
}

Output Example

{
    "Response": {
        "MetricDataList": [
            {
                "MetricDesc": "read request rate",
                "MetricName": "read_request_rate",
                "Timestamps": [
                    1764826200,
                    1764826500,
                    1764826800,
                    1764827100,
                    1764827400,
                    1764827700,
                    1764828000
                ],
                "Values": [
                    0.01,
                    0.01,
                    0.01,
                    0.01,
                    0.01,
                    0.01,
                    0.01
                ]
            },
            {
                "MetricDesc": "write request rate",
                "MetricName": "write_request_rate",
                "Timestamps": [
                    1764826200,
                    1764826500,
                    1764826800,
                    1764827100,
                    1764827400,
                    1764827700,
                    1764828000
                ],
                "Values": [
                    0,
                    0,
                    0,
                    0,
                    0,
                    0,
                    0
                ]
            }
        ],
        "RequestId": "fa272328-a8f8-4b00-ae01-d627d6c597d1"
    }
}

5. Developer Resources

SDK

TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

Command Line Interface

6. Error Code

There is no error code related to the API business logic. For other error codes, please see Common Error Codes.

Ajuda e Suporte

Esta página foi útil?

comentários