tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Basic Concepts

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-27 17:33:16
This document describes key terms and concepts for Tencent Cloud Observability Platform.

Metric

Metric is a fundamental concept in Tencent Cloud Observability Platform. A metric represents a time-ordered set of data points sent to Tencent Cloud Observability Platform. You can retrieve the statistics of those data points in time series. A metric can be seen as a variable to monitor, and the data points represent the values of that variable over time. For example, the CPU utilization of a CVM instance is a metric, and the capacity utilization of a TencentDB instance is another metric.
Metric data can come from any product, application, or service. For example, a metric can be the CPU utilization of a CVM instance or the process latency of a user service. The metric is uniquely defined by a name, a namespace, and one or more dimensions. Each data point has a timestamp and an optional unit of measure. When a request is made for metric data stored in Tencent Cloud Observability Platform, the returned data stream will be identified by namespace, metric name, and dimension.

Namespace

A namespace is a container for metrics. Metrics in different namespaces are isolated from each other, so metrics from different applications will not be mistakenly aggregated.

Dimension

A dimension is a key-value pair that uniquely identifies a monitored object. A metric is meaningful only after the dimension value is determined. Dimensions are useful for designing the aggregate structure for statistics. For example, two dimension values of server IP and proc_name (process name) can identify monitored object A (IP=1.1.1.1&proc_name=test). You need to specify the appropriate dimensions when you input the metric data of a Tencent Cloud product into Tencent Cloud Observability Platform (dimensions are preset for metrics preset by the system). An error may occur if an undefined dimension is used for retrieval.

Timestamp

Each metric data point in Tencent Cloud Observability Platform must have a timestamp, which indicates the time when the raw data is collected. The timestamp used in a request must be a dateTime object and contain the complete date, hour, minute, and second, such as 2000-01-31 23:59:59. We recommend you provide timestamps based on Beijing time (GMT+8).

Unit

A unit refers to the unit of measure for raw metric data, and an application can derive useful semantic information based on the unit. For example, the unit of CVM's outbound bandwidth is Mbps, because network bandwidth often measures current network speed in Mbps. Common units supported by Tencent Cloud Observability Platform are listed below:
Unit
Description
Second
Time unit
Byte
Data size. 1 byte = 8 bits
bit
The smallest unit of data
%
Percentage
Number of times
Quantity
Bps
Bytes per second
bps
Bits per second

Time granularity

A time granularity refers to a statistical period in Tencent Cloud Observability Platform. Timestamp data represents the result of aggregating all data collected in the specified time granularity. Time granularity is defined in seconds. Tencent Cloud Observability Platform currently supports time granularities of 10 seconds, 60 seconds, and 300 seconds. When calling a Tencent Cloud Observability Platform API, you can specify the time granularity through the period parameter. When the GetMonitorData API is called to get monitoring data, the values of period, startTime, and endTime parameters determine the amount of data to be returned. For example, calling this API with the default values of all parameters will return the statistics for every 300 seconds in the last hour, i.e., a total of 12 data points. Time granularities are also important for alarms. When creating an alarm trigger condition, you need to set the time granularity and period for the alarm rule. Different granularities and periods indicate different alarm judgment durations.

Alarm

Alarm management is a feature in Tencent Cloud's monitoring and alarm services. It triggers an alarm if Tencent Cloud resources have an exception, while allowing you to view alarm information, customize alarm thresholds, and subscribe to alarms. Checks will be performed at set intervals according to your custom thresholds. Once an alarm is triggered, you will receive a notification.

Alarm policy type

Alarm policy type identifies the policy category and corresponds to specific Tencent Cloud products. For example, if you choose the CVM policy, you can customize metric alarms for CPU utilization, disk utilization, and more.

Alarm policy

An alarm policy is a set of alarm trigger conditions, and is related to the project and alarm policy type. Up to 15 alarm policies can be created in each alarm policy type for each project.
An alarm policy includes the following components: alarm trigger condition, alarm object, and alarm recipient group. After an alarm policy is successfully configured, alarm notifications will be sent to users through SMS, email, and other channels as configured when an alarm is triggered.

Alarm recipient group

An alarm recipient group can include one or more users. Alarm notifications are sent through "alarm recipient group." For each alarm policy, notifications will be sent to users in the configured alarm recipient group when the alarm threshold is met. You can go to "Account Center" > "Message Subscription" to add user information and alarm receipt methods.

Alarm receipt method

This refers to the way users will be notified when an exception occurs, such as via SMS and email.

Alarm rule

This refers to the action performed when the monitoring data of a metric meets the configured alarm trigger condition.

Alarm trigger condition

An alarm trigger is a semantic condition consisting of metric, comparison relationship, threshold, statistical period, and duration.

ヘルプとサポート

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

フィードバック