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 Services APIs
    • User Management 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

Health Inspection

Download
フォーカスモード
フォントサイズ
最終更新日: 2025-09-02 17:19:50

Feature Introduction

The cluster health inspection feature automatically generates an inspection report every hour by default, thoroughly monitoring the cluster health status. Based on the health score model, it performs a percentage-based weight assessment across 5 levels: basic diagnosis, computing insights, storage insights, resource insights, and event diagnosis, providing quantified data for cluster stability and efficiency. The inspection report clearly annotates deduction dimensions and root cause information to help users quickly locate issues. It also supports the one-time inspection feature to meet users’ inspection needs in the temporary scenario.

Operation Steps

1. Log in to EMR TCInsight > Exception Center, select TCInsight > Root Cause Analysis in the left sidebar on the console, and go to the Health Inspection page.
2. Health inspection provides an intuitive observation of the health score trend of the cluster. You can adjust the observation time to view the historical health trend of the cluster.
3. Click One-Time Inspection, select the inspection dimension and time range as needed to customize the inspection.
4. You can hover over the trend chart line to view the cluster inspection report details.
Note:
1. The health report performs automatic inspection on the data from the previous 1 hour by default at an hourly granularity, generating continuous data for cluster health scores. You can also set a custom time range and inspection coverage for a one-time inspection. Generation of the inspection report takes 3-30 minutes.
2. Currently, the correlation analysis report is an allowlist feature. If you need this feature, submit a ticket to request activation. The correlation analysis function requires proactively selecting the time range, main analysis item, and related information to perform root cause analysis and tracking of exceptions. Output of the real-time analysis report takes 5-30 minutes.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック