Release Notes and Announcements
- Release Notes
- Announcements
Product Introduction
- Overview
- Features
- Available Regions
- Limits
- Concepts
- Service Regions and Service Providers
Purchase Guide
- Billing Overview
- Product Pricing
- Pay-as-You-Go
- Overdue Payments
- Cleaning up CLS resources
- Cost Optimization
- FAQs
Getting Started
Operation Guide
- Resource Management
- Permission Management
- Log Collection
- Metric Collection
- Log Storage
- Metric Storage
- Search and Analysis (Log Topic)
- Search and Analysis (Metric Topic)
- Dashboard
- Data Processing documents
- Shipping and Consumption
- Configuration Templates
- Monitoring Alarm
- Cloud Insight
- Independent DataSight console
- Historical Documentation
Practical Tutorial
- Log Collection
- Search and Analysis
- Dashboard
- Monitoring Alarm
- Shipping and Consumption
- Cost Optimization
Developer Guide
API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Topic Management APIs
- Log Set Management APIs
- Index APIs
- Topic Partition (Abandoned) APIs
- Machine Group APIs
- Log Collection Configuration APIs
- Log APIs
- Metric Collection Configuration APIs
- Metric APIs
- Service APIs
- Alarm Policy APIs
- Data Processing APIs
- Console Customization APIs
- Kafka Consumption APIs
- CKafka Task APIs
- Kafka Data Subscription APIs
- COS Shipping Task APIs
- Dashboard APIs
- SCF Delivery Task APIs
- Scheduled SQL Analysis APIs
- COS Data Import Task APIs
- RemoteWrite APIs
- Cloud Product Integration APIs
- Unified Consumption APIs
- AI APIs
- DLC Task APIs
- es Data Import Task APIs
- Splunk Delivery APIs
- Query View APIs
- OpenClaw APIs
- Network Application APIs
- Data Types
- Error Codes
FAQs
- Explanation of Health Monitoring Problems
- Collection Related
- Log Search
- Others
CLS Policy
- Kebijakan Privasi
- Perjanjian Pemrosesan dan Keamanan Data

Consume logs to Devo

Download

Mode fokus

Ukuran font

Terakhir diperbarui: 2026-04-22 19:05:16

Diterjemahkan oleh AI

To help users quickly integrate Tencent Cloud (CLS) with the Devo SIEM platform, Devo provides a dedicated collection tool Tencent Cloud Collector that can directly collect log data from specified log topics in CLS and synchronize it to Devo. Below are detailed configuration instructions.
Prerequisites
1. CLS has been activated, a logset and a log topic have been created, and log data has been successfully collected.
2. The target log data has been successfully collected in the log topic (you can verify whether the data is written normally through the "log search" feature in the CLS console).
Configure Tencent Cloud Collector to integrate with CLS
When you use Tencent Cloud Collector in Devo to collect logs from CLS, you need to correctly configure parameters related to CLS, as shown in the table below.
Configuration Parameter
Description
Example
endpoint
Request domain, the domain of the API upload log tags page.
ap-beijing.cls.tencentcs.com
secret_id
User's Secret_id, please go to CAM to view.
AKIDnTXXXXXXXXXXXXXZhbG
secret_key
User's Secret_key, please go to CAM to view.
SfeXXXXXXXXXXXXXXXXXOq3
region
The region where the topic is located. For details, see Regions and Access Domains.
 ap-beijing
logset_id
logset ID, only one logset is supported.
011648f2-8ed5-41ef-a9df-63c4ed152016
topic_ids
log topic ID, multiple topics should be separated by commas.
29ccb4c0-ab2f-47ab-9dcd-31413b057812

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Cloud Log Service

Consume logs to Devo

Prerequisites

Configure Tencent Cloud Collector to integrate with CLS

Bantuan dan Dukungan

Configuration Parameter	Description	Example
endpoint	Request domain, the domain of the API upload log tags page.	ap-beijing.cls.tencentcs.com
secret_id	User's Secret_id, please go to CAM to view.	AKIDnTXXXXXXXXXXXXXZhbG
secret_key	User's Secret_key, please go to CAM to view.	SfeXXXXXXXXXXXXXXXXXOq3
region	The region where the topic is located. For details, see Regions and Access Domains.	ap-beijing
logset_id	logset ID, only one logset is supported.	011648f2-8ed5-41ef-a9df-63c4ed152016
topic_ids	log topic ID, multiple topics should be separated by commas.	29ccb4c0-ab2f-47ab-9dcd-31413b057812