tencent cloud

Cloud Log Service

문서Cloud Log ServiceOperation GuideShipping and ConsumptionDelivering Azure Logs

Delivering Azure Logs

Download
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-08-25 12:05:46
AI 번역
After logs are collected to CLS, you can ship log data to Azure Monitor Analytics Log for unified storage, query, and analysis on Azure, and use it as a data source for upper-layer services such as Microsoft Sentinel and Azure Monitor. This feature is billed based on public network read traffic.

Prerequisites

CLS has been activated, a logset and a log topic have been created, and log data has been successfully collected.
Sub-accounts/collaborators require authorization from the root account. For the authorization steps, see Managing Permissions Based on CAM. For the authorization policy, see CLS Access Policy Templates.
The following preparations have been completed on Azure to receive data shipped from CLS:
A Log Analytics workspace has been created, and a target Custom table (such as MyCLSLog_CL) has been created in the workspace.
A Data Collection Endpoint (DCE) has been created.
A Data Collection Rule (DCR) has been created, and the target table (Custom table) and Stream have been defined in the DCR.
App Registration has been completed in Azure AD, and the Tenant ID, Client ID, and Client Secret have been obtained. The following role authorizations have also been completed:
Grant the Monitoring Metrics Publisher role on the DCR to write log data to the DCE.
Grant the Log Analytics Reader role on the target Log Analytics workspace (or its resource group/subscription) to read the target table Schema in the field mapping step. If this permission is not granted, Get Azure Fields and Auto-Map will fail. You need to manually verify the fields on the Azure side and fill them in on this page.

Operation Steps

1. Log in to the CLS console.
2. Select Log Topic in the left sidebar.
3. Click the ID or name of the log topic to be shipped to go to the log topic management page.
4. Click the Data Shipping & Consumption > Ship to Azure Log tab to go to the Deliver to Azure Log configuration page. Click Create to go to Basic Configuration.
Basic Configuration Item
Required
Description
Example
Shipping Task Name
Yes
Name of a shipping task.
cls-to-analytics-log-prod
Log Topic
Yes
Source log topic selected for delivery to Analytics Log.
Guangzhou/test123.
Log Prefiltering
No
Add conditions: Configure filter conditions in interactive mode/statement mode, and send the filtered results to Azure Analytics Log.
Interaction mode (Default):
Retain logs: Logs that meet the conditions will be retained.
Discard logs: Logs that meet the conditions will be discarded.
Statement mode: See Pre-filter Functions.
-
Service log
No
Write the monitoring metrics of the shipping task to the free log topic cls_service_log.
Enable the switch.
Shipping log preview
No
Preview the logs you need to ship.
{"a":123,"b":123,"c":-123,"d":123.45,"e":{"e1":123,"f1":"123"}}
5. Click Next to go to the Target Configuration page.
Configuration Item
Required
Description
Data collection endpoint URI (DCE)
Yes
Data Collection Endpoint URL, the HTTP entry point for log ingestion. Obtain it from Azure portal "Monitor → Data Collection Endpoints", such as https://my-dce-xyz.eastus-1.ingest.monitor.azure.com.
Data collection rule ID (DCR Immutable ID)
Yes
Immutable ID of the Data Collection Rule, which defines the destination Workspace/table for logs and the KQL transformation rules. Obtain it from DCR details page → JSON view → immutableId, in the format of dcr-a1b2c3d4....
Table Name
Yes
Name of the target table, for example, MyCLSLog. The system automatically assembles it into the stream name defined in the DCR (Custom-<table name>).
Tenant ID
Yes
Azure AD tenant ID, used to assemble the login URL for obtaining a Token.
Client ID
Yes
Application (client) ID of the App Registration.
Client Secret
Yes
Client Secret of the App Registration. The secret is used only by the server to obtain an AccessToken and is not displayed in plaintext in the console.
After the connectivity check passes, you can configure field mappings. Click Map Filed, and the system will read the Schema of the target table and automatically fill in the log field name column with log fields of the same name.
Azure App Authentication Configuration Item
Required
Description
Rule
Log Field Name
Yes
Field name in CLS logs. Map it to an Azure target table field. Only the key of a first-layer node in JSON (such as app_name) is supported. Nested nodes such as details.request_id are not supported.
-
Azure Field
No
The system reads it from the Schema of the Azure DCR Stream. Modification is not supported here. Go to the Azure side to adjust the target table/DCR.
-
Field Type
No
Type of the Azure field (such as Datetime, String, and Int). The system reads it from the Schema. Modification is not supported here.

Assignment Information returned uponon resolution Failed
No
When a field value fails to parse, use this value to write to Azure. You can select Empty (empty string), null, or Custom value.
If the field does not exist in the log, the Azure side writes null. If the value assigned on parsing failure is null, the Azure side writes null. If the value assigned on parsing failure is not null, the system tries to parse the field again based on the assigned value, writes the value if parsing succeeds, or writes null if parsing fails.
Empty/null/custom value
Enable Mapping
No
Whether to map this field to an Azure table. If mapping is not required, disable the switch. Fields marked as "Required" in Azure (such as TimeGenerated) cannot be disabled.
-
6. Click Submit to complete the new task configuration.


이전 주제: Consume Demo - Stream Processing다음 주제: Consume logs to Devo

도움말 및 지원

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

피드백