- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Permission Management
- Log Collection
- Collection Overview
- Collecting Logs in Self-Built Kubernetes Cluster
- Collecting Syslog
- Collection by LogListener
- Collecting Text Log
- Uploading Log over Kafka
- Uploading Logs via Anonymous Write
- Uploading Logs via Logback Appender
- Uploading Logs via Log4j Appender
- Uploading Log via SDK
- Uploading Log via API
- Importing Data
- Tencent Cloud Service Log Access
- Metric Collection
- Log Storage
- Metric Storage
- Search and Analysis (Log Topic)
- Syntax and Rules
- Statistical Analysis (SQL)
- Quick Analysis
- SQL Syntax
- SQL Functions
- String Function
- Date and Time Functions
- IP Geographic Function
- URL Function
- Mathematical Calculation Functions
- Mathematical Statistical Function
- General Aggregate Function
- Geospatial Function
- Binary String Function
- Estimation Function
- Type Conversion Function
- Logical Function
- Operators
- Bitwise Operation
- Regular Expression Function
- Lambda Function
- Conditional Expressions
- Array Functions
- Interval-Valued Comparison and Periodicity-Valued Comparison Functions
- JSON Functions
- Window Functions
- Sampling Analysis
- Configuring Indexes
- Reindexing
- Context Search and Analysis
- Downloading Log
- Search and Analysis (Metric Topic)
- Dashboard
- Data Processing documents
- Data Processing
- Creating Processing Task
- Viewing Data Processing Details
- Data Processing Functions
- Function Overview
- Key-Value Extraction Functions
- Enrichment Functions
- Flow Control
- Row Processing Functions
- Field Processing Functions
- Value Structuring Functions
- Regular Expression Processing Functions
- Time Value Processing Functions
- String Processing Functions
- Type Conversion Functions
- Logical and Mathematical Functions
- Encoding and Decoding Functions
- IP Parsing Functions
- Processing Cases
- Scheduled SQL Analysis
- SCF
- Data Processing
- Shipping and Consumption
- Monitoring Alarm
- Historical Documentation
- Practical Tutorial
- Developer Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Topic Management APIs
- Log Set Management APIs
- Index APIs
- Topic Partition APIs
- Machine Group APIs
- Collection Configuration APIs
- Log APIs
- Metric APIs
- Alarm Policy APIs
- Data Processing APIs
- Kafka Protocol Consumption APIs
- CKafka Shipping Task APIs
- Kafka Data Subscription APIs
- COS Shipping Task APIs
- SCF Delivery Task APIs
- Scheduled SQL Analysis APIs
- COS Data Import Task APIs
- Data Types
- Error Codes
- FAQs
- CLS Service Level Agreement
- CLS Policy
- Contact Us
- Glossary
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Resource Management
- Permission Management
- Log Collection
- Collection Overview
- Collecting Logs in Self-Built Kubernetes Cluster
- Collecting Syslog
- Collection by LogListener
- Collecting Text Log
- Uploading Log over Kafka
- Uploading Logs via Anonymous Write
- Uploading Logs via Logback Appender
- Uploading Logs via Log4j Appender
- Uploading Log via SDK
- Uploading Log via API
- Importing Data
- Tencent Cloud Service Log Access
- Metric Collection
- Log Storage
- Metric Storage
- Search and Analysis (Log Topic)
- Syntax and Rules
- Statistical Analysis (SQL)
- Quick Analysis
- SQL Syntax
- SQL Functions
- String Function
- Date and Time Functions
- IP Geographic Function
- URL Function
- Mathematical Calculation Functions
- Mathematical Statistical Function
- General Aggregate Function
- Geospatial Function
- Binary String Function
- Estimation Function
- Type Conversion Function
- Logical Function
- Operators
- Bitwise Operation
- Regular Expression Function
- Lambda Function
- Conditional Expressions
- Array Functions
- Interval-Valued Comparison and Periodicity-Valued Comparison Functions
- JSON Functions
- Window Functions
- Sampling Analysis
- Configuring Indexes
- Reindexing
- Context Search and Analysis
- Downloading Log
- Search and Analysis (Metric Topic)
- Dashboard
- Data Processing documents
- Data Processing
- Creating Processing Task
- Viewing Data Processing Details
- Data Processing Functions
- Function Overview
- Key-Value Extraction Functions
- Enrichment Functions
- Flow Control
- Row Processing Functions
- Field Processing Functions
- Value Structuring Functions
- Regular Expression Processing Functions
- Time Value Processing Functions
- String Processing Functions
- Type Conversion Functions
- Logical and Mathematical Functions
- Encoding and Decoding Functions
- IP Parsing Functions
- Processing Cases
- Scheduled SQL Analysis
- SCF
- Data Processing
- Shipping and Consumption
- Monitoring Alarm
- Historical Documentation
- Practical Tutorial
- Developer Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Topic Management APIs
- Log Set Management APIs
- Index APIs
- Topic Partition APIs
- Machine Group APIs
- Collection Configuration APIs
- Log APIs
- Metric APIs
- Alarm Policy APIs
- Data Processing APIs
- Kafka Protocol Consumption APIs
- CKafka Shipping Task APIs
- Kafka Data Subscription APIs
- COS Shipping Task APIs
- SCF Delivery Task APIs
- Scheduled SQL Analysis APIs
- COS Data Import Task APIs
- Data Types
- Error Codes
- FAQs
- CLS Service Level Agreement
- CLS Policy
- Contact Us
- Glossary
Overview
You can create logsets and log topics in different regions when using CLS. Regions are independent geographical areas where IDCs are located. Tencent Cloud regions are completely isolated. You can select the nearest region based on different business scenarios and the location of your targeted users to reduce log access latency and improve user experience.
Available regions
Region | Code |
Beijing | ap-beijing |
Guangzhou | ap-guangzhou |
Shanghai | ap-shanghai |
Chengdu | ap-chengdu |
Nanjing | ap-nanjing |
Chongqing | ap-chongqing |
Hong Kong (China) | ap-hongkong |
Silicon Valley | na-siliconvalley |
Virginia | na-ashburn |
Singapore | ap-singapore |
Bangkok | ap-bangkok |
Frankfurt | eu-frankfurt |
Tokyo | ap-tokyo |
Seoul | ap-seoul |
Jakarta | ap-jakarta |
São Paulo | sa-saopaulo |
Note:
If CLS is integrated into other cloud products, you need to select a logset in the same region as the other cloud products. Cloud products in the same region access each other over a private network, which effectively reduces latency and improves access speed.
Domain name
CLS has different domain names for each of its modules, as described below:
LogListener is a log collection client provided by CLS and can report local logs to CLS. It uses the following domain names:
Region | Code | Private Network Domain Name | Public Network Domain Name |
Beijing | ap-beijing | ap-beijing.cls.tencentyun.com | ap-beijing.cls.tencentcs.com |
Guangzhou | ap-guangzhou | ap-guangzhou.cls.tencentyun.com | ap-guangzhou.cls.tencentcs.com |
Shanghai | ap-shanghai | ap-shanghai.cls.tencentyun.com | ap-shanghai.cls.tencentcs.com |
Chengdu | ap-chengdu | ap-chengdu.cls.tencentyun.com | ap-chengdu.cls.tencentcs.com |
Nanjing | ap-nanjing | ap-nanjing.cls.tencentyun.com | ap-nanjing.cls.tencentcs.com |
Chongqing | ap-chongqing | ap-chongqing.cls.tencentyun.com | ap-chongqing.cls.tencentcs.com |
Hong Kong (China) | ap-hongkong | ap-hongkong.cls.tencentyun.com | ap-hongkong.cls.tencentcs.com |
Silicon Valley | na-siliconvalley | na-siliconvalley.cls.tencentyun.com | na-siliconvalley.cls.tencentcs.com |
Virginia | na-ashburn | na-ashburn.cls.tencentyun.com | na-ashburn.cls.tencentcs.com |
Singapore | ap-singapore | ap-singapore.cls.tencentyun.com | ap-singapore.cls.tencentcs.com |
Bangkok | ap-bangkok | ap-bangkok.cls.tencentyun.com | ap-bangkok.cls.tencentcs.com |
Frankfurt | eu-frankfurt | eu-frankfurt.cls.tencentyun.com | eu-frankfurt.cls.tencentcs.com |
Tokyo | ap-tokyo | ap-tokyo.cls.tencentyun.com | ap-tokyo.cls.tencentcs.com |
Seoul | ap-seoul | ap-seoul.cls.tencentyun.com | ap-seoul.cls.tencentcs.com |
Jakarta | ap-jakarta | ap-jakarta.cls.tencentyun.com | ap-jakarta.cls.tencentcs.com |
São Paulo | sa-saopaulo | sa-saopaulo.cls.tencentyun.com | sa-saopaulo.cls.tencentcs.com |
CLS API 3.0 is the latest version of CLS APIs that complies with the unified API specifications of Tencent Cloud. You can use the APIs to manage resources such as log topics and alarm policies. The APIs use the following domain names:
If you access CLS over the public network, you can also use the unified domain name
cls.tencentcloudapi.com. Your API request will be automatically resolved to a server nearest to the client. For latency-sensitive businesses, we recommend you specify the domain name in a region.Region | Code | Private Network Domain Name | Public Network Domain Name |
Beijing | ap-beijing | cls.internal.tencentcloudapi.com | cls.ap-beijing.tencentcloudapi.com |
Guangzhou | ap-guangzhou | cls.internal.tencentcloudapi.com | cls.ap-guangzhou.tencentcloudapi.com |
Shanghai | ap-shanghai | cls.internal.tencentcloudapi.com | cls.ap-shanghai.tencentcloudapi.com |
Chengdu | ap-chengdu | cls.internal.tencentcloudapi.com | cls.ap-chengdu.tencentcloudapi.com |
Nanjing | ap-nanjing | cls.internal.tencentcloudapi.com | cls.ap-nanjing.tencentcloudapi.com |
Chongqing | ap-chongqing | cls.internal.tencentcloudapi.com | cls.ap-chongqing.tencentcloudapi.com |
Hong Kong (China) | ap-hongkong | cls.internal.tencentcloudapi.com | cls.ap-hongkong.tencentcloudapi.com |
Silicon Valley | na-siliconvalley | cls.internal.tencentcloudapi.com | cls.na-siliconvalley.tencentcloudapi.com |
Virginia | na-ashburn | cls.internal.tencentcloudapi.com | cls.na-ashburn.tencentcloudapi.com |
Singapore | ap-singapore | cls.internal.tencentcloudapi.com | cls.ap-singapore.tencentcloudapi.com |
Bangkok | ap-bangkok | cls.internal.tencentcloudapi.com | cls.ap-bangkok.tencentcloudapi.com |
Frankfurt | eu-frankfurt | cls.internal.tencentcloudapi.com | cls.eu-frankfurt.tencentcloudapi.com |
Tokyo | ap-tokyo | cls.internal.tencentcloudapi.com | cls.ap-tokyo.tencentcloudapi.com |
Seoul | ap-seoul | cls.internal.tencentcloudapi.com | cls.ap-seoul.tencentcloudapi.com |
Jakarta | ap-jakarta | cls.internal.tencentcloudapi.com | cls.ap-jakarta.tencentcloudapi.com |
São Paulo | sa-saopaulo | cls.internal.tencentcloudapi.com | cls.sa-saopaulo.tencentcloudapi.com |
The following domain names apply to APIs for log upload. Update all other APIs to API 3.0.
Region | Code | Private Network Domain Name | Public Network Domain Name |
Beijing | ap-beijing | ap-beijing.cls.tencentyun.com | ap-beijing.cls.tencentcs.com |
Guangzhou | ap-guangzhou | ap-guangzhou.cls.tencentyun.com | ap-guangzhou.cls.tencentcs.com |
Shanghai | ap-shanghai | ap-shanghai.cls.tencentyun.com | ap-shanghai.cls.tencentcs.com |
Chengdu | ap-chengdu | ap-chengdu.cls.tencentyun.com | ap-chengdu.cls.tencentcs.com |
Nanjing | ap-nanjing | ap-nanjing.cls.tencentyun.com | ap-nanjing.cls.tencentcs.com |
Chongqing | ap-chongqing | ap-chongqing.cls.tencentyun.com | ap-chongqing.cls.tencentcs.com |
Hong Kong (China) | ap-hongkong | ap-hongkong.cls.tencentyun.com | ap-hongkong.cls.tencentcs.com |
Silicon Valley | na-siliconvalley | na-siliconvalley.cls.tencentyun.com | na-siliconvalley.cls.tencentcs.com |
Virginia | na-ashburn | na-ashburn.cls.tencentyun.com | na-ashburn.cls.tencentcs.com |
Singapore | ap-singapore | ap-singapore.cls.tencentyun.com | ap-singapore.cls.tencentcs.com |
Bangkok | ap-bangkok | ap-bangkok.cls.tencentyun.com | ap-bangkok.cls.tencentcs.com |
Frankfurt | eu-frankfurt | eu-frankfurt.cls.tencentyun.com | eu-frankfurt.cls.tencentcs.com |
Tokyo | ap-tokyo | ap-tokyo.cls.tencentyun.com | ap-tokyo.cls.tencentcs.com |
Seoul | ap-seoul | ap-seoul.cls.tencentyun.com | ap-seoul.cls.tencentcs.com |
Jakarta | ap-jakarta | ap-jakarta.cls.tencentyun.com | ap-jakarta.cls.tencentcs.com |
São Paulo | sa-saopaulo | sa-saopaulo.cls.tencentyun.com | sa-saopaulo.cls.tencentcs.com |
As described in Uploading Logs via Kafka, you can use Kafka Producer SDKs or other Kafka agents to upload logs to CLS. This feature uses the following domain names:
Region | Code | Private Network Domain Name | Public Network Domain Name |
Beijing | ap-beijing | bj-producer.cls.tencentyun.com | bj-producer.cls.tencentcs.com |
Guangzhou | ap-guangzhou | gz-producer.cls.tencentyun.com | gz-producer.cls.tencentcs.com |
Shanghai | ap-shanghai | sh-producer.cls.tencentyun.com | sh-producer.cls.tencentcs.com |
Chengdu | ap-chengdu | cd-producer.cls.tencentyun.com | cd-producer.cls.tencentcs.com |
Nanjing | ap-nanjing | nj-producer.cls.tencentyun.com | nj-producer.cls.tencentcs.com |
Chongqing | ap-chongqing | cq-producer.cls.tencentyun.com | cq-producer.cls.tencentcs.com |
Hong Kong (China) | ap-hongkong | hk-producer.cls.tencentyun.com | hk-producer.cls.tencentcs.com |
Silicon Valley | na-siliconvalley | usw-producer.cls.tencentyun.com | usw-producer.cls.tencentcs.com |
Virginia | na-ashburn | use-producer.cls.tencentyun.com | use-producer.cls.tencentcs.com |
Singapore | ap-singapore | sg-producer.cls.tencentyun.com | sg-producer.cls.tencentcs.com |
Bangkok | ap-bangkok | th-producer.cls.tencentyun.com | th-producer.cls.tencentcs.com |
Frankfurt | eu-frankfurt | de-producer.cls.tencentyun.com | de-producer.cls.tencentcs.com |
Tokyo | ap-tokyo | jp-producer.cls.tencentyun.com | jp-producer.cls.tencentcs.com |
Seoul | ap-seoul | kr-producer.cls.tencentyun.com | kr-producer.cls.tencentcs.com |
Jakarta | ap-jakarta | jkt-producer.cls.tencentyun.com | jkt-producer.cls.tencentcs.com |
As described in Consumption over Kafka, you can use Kafka Consumer SDKs or other big data components to consume the data to data warehouses. This feature uses the following domain names:
Region | Code | Private Network Domain Name | Public Network Domain Name |
Beijing | ap-beijing | kafkaconsumer-ap-beijing.cls.tencentyun.com | kafkaconsumer-ap-beijing.cls.tencentcs.com |
Guangzhou | ap-guangzhou | kafkaconsumer-ap-guangzhou.cls.tencentyun.com | kafkaconsumer-ap-guangzhou.cls.tencentcs.com |
Shanghai | ap-shanghai | kafkaconsumer-ap-shanghai.cls.tencentyun.com | kafkaconsumer-ap-shanghai.cls.tencentcs.com |
Chengdu | ap-chengdu | kafkaconsumer-ap-chengdu.cls.tencentyun.com | kafkaconsumer-ap-chengdu.cls.tencentcs.com |
Nanjing | ap-nanjing | kafkaconsumer-ap-nanjing.cls.tencentyun.com | kafkaconsumer-ap-nanjing.cls.tencentcs.com |
Chongqing | ap-chongqing | kafkaconsumer-ap-chongqing.cls.tencentyun.com | kafkaconsumer-ap-chongqing.cls.tencentcs.com |
Hong Kong (China) | ap-hongkong | kafkaconsumer-ap-hongkong.cls.tencentyun.com | kafkaconsumer-ap-hongkong.cls.tencentcs.com |
Silicon Valley | na-siliconvalley | kafkaconsumer-na-siliconvalley.cls.tencentyun.com | kafkaconsumer-na-siliconvalley.cls.tencentcs.com |
Virginia | na-ashburn | kafkaconsumer-na-ashburn.cls.tencentyun.com | kafkaconsumer-na-ashburn.cls.tencentcs.com |
Singapore | ap-singapore | kafkaconsumer-ap-singapore.cls.tencentyun.com | kafkaconsumer-ap-singapore.cls.tencentcs.com |
Bangkok | ap-bangkok | kafkaconsumer-ap-bangkok.cls.tencentyun.com | kafkaconsumer-ap-bangkok.cls.tencentcs.com |
Frankfurt | eu-frankfurt | kafkaconsumer-eu-frankfurt.cls.tencentyun.com | kafkaconsumer-eu-frankfurt.cls.tencentcs.com |
Tokyo | ap-tokyo | kafkaconsumer-ap-tokyo.cls.tencentyun.com | kafkaconsumer-ap-tokyo.cls.tencentcs.com |
Seoul | ap-seoul | kafkaconsumer-ap-seoul.cls.tencentyun.com | kafkaconsumer-ap-seoul.cls.tencentcs.com |
Jakarta | ap-jakarta | kafkaconsumer-ap-jakarta.cls.tencentyun.com | kafkaconsumer-ap-jakarta.cls.tencentcs.com |
Ya
Tidak
Apakah halaman ini membantu?