Release Notes and Announcements

Release Notes

Announcements

User Guide

Product Introduction

Overview

Features

Available Regions

Limits

Concepts

Service Regions and Service Providers

Purchase Guide

Billing Overview

Product Pricing

Pay-as-You-Go

Billing

Cleaning up CLS resources

Cost Optimization

FAQs

Getting Started

Getting Started in 1 Minute

Getting Started Guide

Quickly Trying out CLS with Demo

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

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

Embedding CLS Console

CLS Connection to Grafana

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

Health Check

Collection

Log Search

Others

CLS Service Level Agreement

CLS Policy

Data Processing And Security Agreement

Glossary

Log Upload

PDF

Focus Mode

Font Size

Last updated: 2024-01-20 17:11:57

What should I do if a message indicating a parameter error is displayed?
This error indicates that Request Parameters were specified incorrectly for log uploading via the API or SDK. Ensure that the parameters are specified correctly.
What are the possible causes for an authentication failure?
Authentication will fail when there is an authentication error during log uploading. The possible causes are as follows:
Cause
Solution
The key does not exist
Check whether the key has been deleted or disabled in the console.
If its status is normal, check whether the key is entered correctly. Note that there must be no leading or trailing spaces. You can click here to view the key.
The signature is incorrect
Check the signature calculation process against the signature document under "Making API Requests".
The signature expire
Re-calculate the signature against the signature document under "Making API Requests".
The request is not authorized
There is no log upload permission. Go to the CAM console to add the CLS load upload permission for your account.
The key is invalid
The key format is incorrect. You can click here to view the key.
Others
If the error persists after you have checked the above causes, contact us.
What should I do if the logs to upload exceed the size limit?
Adjust the log size according to the following limits:
Limit
Description
Log upload
The number of logGroups in a .pb package cannot exceed 10.
﻿
A logGroup in a .pb package can contain 1 to 10,000 log entries.
﻿
A single value in log cannot exceed 1 MB.
﻿
All values in the logGroup of a .pb package cannot exceed 5 MB.
﻿
The package for a single upload request cannot exceed 6 MB before compression.
Why is throttling or frequency control triggered?
The following limits may be exceeded:
Limit
Description
Frequency limit on writes
For a single log topic partition: 500 QPS.
Bandwidth limit on writes
For a single log topic partition: 5 MB/s.
You are advised to reduce the frequency and traffic of log uploads. If you do not want to do so, enable auto-split for the log topic.
How do I handle an upload request error?
Contact us.

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

tencent cloud

Cloud Log Service

Log Upload

What should I do if a message indicating a parameter error is displayed?

What are the possible causes for an authentication failure?

What should I do if the logs to upload exceed the size limit?

Why is throttling or frequency control triggered?

How do I handle an upload request error?

Help and Support

Cause	Solution
The key does not exist	Check whether the key has been deleted or disabled in the console. If its status is normal, check whether the key is entered correctly. Note that there must be no leading or trailing spaces. You can click here to view the key.
The signature is incorrect	Check the signature calculation process against the signature document under "Making API Requests".
The signature expire	Re-calculate the signature against the signature document under "Making API Requests".
The request is not authorized	There is no log upload permission. Go to the CAM console to add the CLS load upload permission for your account.
The key is invalid	The key format is incorrect. You can click here to view the key.
Others	If the error persists after you have checked the above causes, contact us.

Limit	Description
Log upload	The number of logGroups in a .pb package cannot exceed 10.
		A logGroup in a .pb package can contain 1 to 10,000 log entries.
		A single value in log cannot exceed 1 MB.
		All values in the logGroup of a .pb package cannot exceed 5 MB.
		The package for a single upload request cannot exceed 6 MB before compression.

Limit	Description
Frequency limit on writes	For a single log topic partition: 500 QPS.
Bandwidth limit on writes	For a single log topic partition: 5 MB/s.