SLS resource throttling errors and solutions - Simple Log Service

Simple Log Service enforces throttling limits on projects, Logstores, and shards for multi-tenant QoS. Exceeding Simple Log Service resource limits may cause API errors, resource creation failures, or data upload failures. Common Simple Log Service throttling errors and solutions are listed below.

Detect throttling

Use Simple Log Service CloudLens for SLS to monitor resource usage and throttling. Address triggered alerts promptly.

Solutions

The following table lists common throttling errors and solutions.

Category		Exceeding limits	Solution
Write limit exceeded	WriteQuotaExceed (Project-level limit exceeded)	Project write traffic: Project write quota exceeded: inflow: xxx Project writes: Project write quota exceeded: qps: xxx	Adjust resource quotas in theSimple Log Service console. For more information, see Adjust resource quotas.
Write limit exceeded	ShardWriteQuotaExceed (Shard-level limit exceeded)	Shard writes: shard write quota exceeded, please split shard (The write operations on all active shards exceed the limit) Shard writes: shard write quota exceeded, shard: xxx	Add shards by splitting them manually or automatically. For more information, see Manage shards.
Read limit exceeded	ShardReadQuotaExceed (Shard-level limit exceeded. No read limit is imposed at the project level.)	Shard reads: Shard read QPS exceeded quota limits. Shard read traffic: Shard read bytes exceeded quota limits.	Add shards by splitting them manually or automatically. For more information, see Manage shards.
Resource creation limit exceeded	ProjectQuotaExceed	Number of Logstores: project xxx logstore count quota exceeded Number of projects: Account <aliuid> can have at most <project quota> projects Number of shards: project <project name>, shard count quota exceeded	Adjust resource quotas in theSimple Log Service console. For more information, see Adjust resource quotas.
Request limit exceeded	Dashboard count limit exceeded	dashboard quota exceeded	Adjust resource quotas in theSimple Log Service console. For more information, see Adjust resource quotas.
Request limit exceeded	Concurrent SQL analysis request limit exceeded	user can only run 15 queries concurrently Too many queued queries	Check for abnormal service pressure or invalid requests caused by your application logic. If you require higher concurrency, you can submit a ticket to request a quota increase. SLS will then increase your SQL concurrency limit.
Other configuration resource creation limit exceeded	QuotaExceed	Number of Logtail collection configurations: project config count exceeded quota Number of machine groups: project machine group count exceeded quota Number of alerts: Alert count exceeds the maximum limit	Adjust resource quotas in theSimple Log Service console. For more information, see Adjust resource quotas.