Cloud Log Service
- Release Notes and Announcements
- Announcements
- Product Introduction
- Limits
- Log Collection
- Purchase Guide
- Pay-as-You-Go
- Getting Started
- Operation Guide
- Resource Management
- Permission Management
- Log Collection
- Collection by LogListener
- LogListener Installation and Deployment
- Collecting Text Log
- Collecting Logs in Self-Built Kubernetes Cluster
- Importing Data
- Metric Collection
- Log Storage
- Search and Analysis (Log Topic)
- Statistical Analysis (SQL)
- SQL Syntax
- SQL Functions
- Search and Analysis (Metric Topic)
- Dashboard
- Creating Statistical Charts
- Data Processing documents
- Data Processing
- Data Processing Functions
- Scheduled SQL Analysis
- Shipping and Consumption
- Shipping to COS
- Shipping to CKafka
- Shipping to ES
- Log Shipping
- Consumption over Kafka
- Monitoring Alarm
- Managing Alarm Policies
- Channels to Receive Alarm Notifications
- Cloud Insight
- Historical Documentation
- Practical Tutorial
- Search and Analysis
- Monitoring Alarm
- Shipping and Consumption
- Developer Guide
- API Documentation
- Making API Requests
- Topic Management APIs
- Log Set Management 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
- FAQs
- Health Check
- Collection
- Log Search
Log Upload
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 | |
Others |
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?
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No