tencent cloud

Feedback

Last updated: 2022-08-29 16:59:13

    Notes

    This document is only applicable to the DescribeStatisticData API. For all the following metrics, the tke_cluster_instance_id dimension is required, while other dimensions are optional.

    Namespace

    Namespace = QCE/TKE2

    Monitoring Metrics

    Parameter Metric Unit Dimension Statistical Period
    K8sNodeCpuUsage CPU utilization % Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeStatusReady Node status - Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeLanIntraffic Private inbound bandwidth MB/s Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeTcpCurrEstab Number of TCP connections - Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeLanOuttraffic Private outbound bandwidth MB/s Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeWanIntraffic Public inbound bandwidth MB/s Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeMemUsage Memory utilization % Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodePod
    RestartTotal
    Number of pod restarts on the node - Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeCpu
    CoreRequestTotal
    Number of allocated CPU cores - Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeGpu
    MemoryUsedBytes
    GPU memory usage B Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeGpuUsed GPU utilization % Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeRateGpu
    MemoryUsed
    GPU memory utilization % Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeWan

    Outtraffic
    Public outbound bandwidth MB/s Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeRate
    GpuUsed
    GPU utilization % Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s
    K8sNodeMemory
    RequestBytesTotal
    Memory allocation MB Required dimensions: tke_cluster_instance_id
    Optional dimensions: node_role, node, un_instance_id
    60s,
    300s,
    3600s,
    86400s

    Statistical Granularity and Time Span

    The supported time span varies by statistical granularity. When pulling monitoring data, you should pay attention to the time span restrictions as detailed below:

    Statistical Granularity Maximum Time Span (End Time - Start Time)
    60s 12 hours
    300s 3 days
    3600s 30 days
    86400s 186 days

    Overview of Parameters in Each Dimension

    Parameter Name Type Dimension Name Description Format
    Conditions.N.Dimensions.N.Name Required tke_cluster_instance_id Dimension name of the cluster Enter a string-type dimension name, such as `tke_cluster_instance_id`
    Conditions.N.Dimensions.N.Value tke_cluster_instance_id Specific cluster ID Enter a specific cluster ID, such as cls-fvkxp123
    Conditions.N.Dimensions.N.Name Optional (zero, one, or multiple of which can be passed in optionally) node_role Dimension name of the cluster Enter a string-type dimension name, such as `node_role`
    Conditions.N.Dimensions.N.Value node_role Specific node role Enter a specific node role, such as node
    Conditions.N.Dimensions.N.Name node Dimension name of the node name Enter a string-type dimension name, such as `node`
    Conditions.N.Dimensions.N.Value node Specific node name Enter a specific node name, such as node
    Conditions.N.Dimensions.N.Name un_instance_id Dimension name of the node ID Enter a string-type dimension name, such as `un_instance_id`
    Conditions.N.Dimensions.N.Value un_instance_id Specific node ID Enter a specific node ID, such as ins-nwjhh123

    Input Parameter Description

    In the cluster dimension, use the following input parameters:
    &Namespace=QCE/TKE2
    &Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
    &Conditions.N.Dimensions.0.Value=cls-fvkxp123

    In the node role dimension, use the following input parameters:
    &Namespace=QCE/TKE2
    &Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
    &Conditions.N.Dimensions.0.Value=cls-fvkxp123
    &Conditions.N.Dimensions.1.Name=node_role
    &Conditions.N.Dimensions.1.Value=node

    In the node ID dimension, use the following input parameters:
    &Namespace=QCE/TKE2
    &Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
    &Conditions.N.Dimensions.0.Value=cls-fvkxp123
    &Conditions.N.Dimensions.1.Name=un_instance_id
    &Conditions.N.Dimensions.1.Value=ins-nwjhh123

    In the node name dimension, use the following input parameters:
    &Namespace=QCE/TKE2
    &Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
    &Conditions.N.Dimensions.0.Value=cls-fvkxp123
    &Conditions.N.Dimensions.1.Name=node
    &Conditions.N.Dimensions.1.Value=node

    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support