tencent cloud

APIs

DescribeEmrOverviewMetrics

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

1. API Description

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

This API is used to query metric data on the monitoring overview page.

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: DescribeEmrOverviewMetrics.
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.
End Yes Integer End time.
Metric Yes String Metric name. Valid values: NODE.CPU (average CPU utilization and number of cores of the node), NODE.CPU.SLHBASE (average CPU utilization and total number of CPU cores of the Serverless instance), and HDFS.NN.CAPACITY (storage capacity utilization and total capacity).
InstanceId Yes String Cluster ID.
Downsample Yes String Granularity, for example, 30s-max, 1m-max, and 1h-max.
Start No Integer Start time, which is not required for pie charts.
Aggregator No String Aggregation method, which is reserved for scale-out purposes. Currently, this parameter does not need to be passed.
Tags No String Specific type of metrics to be queried, for example, "{"type":"CapacityTotal|CapacityRemaining"}".

3. Output Parameters

Parameter Name Type Description
Result Array of OverviewMetricData Metric data details.
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 Querying the Metric Data on the Monitoring Overview Page

Input Example

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

{
    "End": 1730753724,
    "Metric": "NODE.CPU",
    "InstanceId": "emr-hvijzo6n",
    "Downsample": "30s-min"
}

Output Example

{
    "Response": {
        "RequestId": "a16d3814-3b85-498a-97a7-15e7b0f0f0bd",
        "Result": [
            {
                "Metric": "EMR.19003289.NODE.CPU",
                "Tags": {
                    "Type": "CPUUsedPercent"
                },
                "First": 1730148930,
                "Last": 1730753700,
                "Interval": 30,
                "DataPoints": [
                    "2.3",
                    "2.4",
                    "2.6",
                    "3.8",
                    "2.8",
                    "3.1",
                    "3.4",
                    "3.3",
                    "3.6",
                    "4.3",
                    "3",
                    "3.1",
                    "2.3",
                    "2.9",
                    "2.5",
                    "2.4",
                    "2.2",
                    "4.1",
                    "3.3",
                    "2.5",
                    "4.5",
                    "4.7",
                    "2.5",
                    "3.6",
                    "2.2",
                    "2.3",
                    "2.5",
                    "2.9",
                    "2.2"
                ]
            },
            {
                "Metric": "EMR.19003289.NODE.CPU",
                "Tags": {
                    "Type": "CPUCoresTotal",
                    "Unit": "Cores"
                },
                "First": 1730148930,
                "Last": 1730753700,
                "Interval": 30,
                "DataPoints": [
                    "118"
                ]
            }
        ]
    }
}

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

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

Error Code Description
ResourceNotFound.ClusterNotFound The instance cannot be found.
ResourceNotFound.ResourceNotFound The monitoring metadata cannot be found.
UnauthorizedOperation.AppIdMismatched APPID mismatch.

Ajuda e Suporte

Esta página foi útil?

comentários