tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us
문서Tencent Cloud Distributed Cache (Redis OSS-Compatible)Operation GuideGlobal Replication for Redis EditionMonitoring Metrics

Monitoring Metrics

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-17 18:10:57
Tencent Cloud Distributed Cache Redis protocol supports graphical monitoring of number of commands deviation and synchronization delay during global replication between primary and disaster recovery instances.

Monitoring Metrics

Monitoring Metric
Metric meaning
Unit
delayed number of commands
number of commands deviation during remote synchronization between the primary and disaster recovery instances in global replication
Count
Delay Time
synchronization latency between primary and disaster recovery instances during global replication
ms

View Monitor View

1. Log in to the Tencent Cloud Distributed Cache console.
2. In the left sidebar, select Global Replication.
3. In the Global Replication list on the right-hand side, locate the row of the replication group you need to view.
4. In the Replication Group Status column, click

to slide out the monitoring view of the metrics on the right-hand side, as shown below.


Configure Monitoring and Alerts

1. Log in to the TCOP alarm management page.
2. Click Create Policy and configure the alarm rules on the New Alarm Policy page.
Parameter Name
Parameter Description
Policy Name
Customize the name of an alarm policy for easy identification.
Remarks
Provide a brief description of the alarm policy for easy identification.
Monitoring Type
Select Cloud Service Monitoring.
Policy type
Select Cloud Database / Redis / Memory Edition (5-second granularity) / Global Replication.
Tag of the Policy
Assign tags to the alarm policy.
Alarm object
Select the instances to be monitored and their regions.
Trigger Condition
By default, it is the manual configuration method. You need to configure the threshold conditions for triggering alarms for each metric one by one in the metric alarm section below.
Metric Alarm section, Threshold Type: Select Static: Manually set a constant threshold, and send alarms when the triggering conditions are met.
Click Add Metric to add multiple alarm metrics.
For more information, see Create Alarm Policies.
3. Click Next: Configure Alarm Notification. You can select system preset notification templates or custom notification templates. Each alarm policy can be bound to a maximum of three notification templates. For details, see Notification Templates.
4. Confirm that the configuration is correct, click Complete. For more information on alarms, see Alarm Overview.

Related APIs

API Interface Name
API Feature Description
Create TCOP alarm policy
이전 주제: Managing Global Replication Group다음 주제: Audit Introduction

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백