IBM Cloud Logs limits
IBM® Cloud Logs has limits that need to be considered when using the service.
Character support
IBM Cloud Logs does not provide full Unicode support for multibyte characters.
Limits per instance
IBM Cloud Logs has limits for each provisioned instance.
| Item | Limit |
|---|---|
| Alerts | 500 |
| Parsing rules | 70 |
| Enrichments | 10 |
| Events to Metrics labels | 8 |
| Ingestion log size | 32 K |
| Largest log size processed by the pipeline | 33 K |
| Branches | 1500 |
| Query time range | 8 days |
| Maximum number of fields | 1500 |
Log ingestion limits
When you send data to an IBM Cloud Logs instance:
- Logs cannot be older than 24 hours.
- Logs cannot be more than 4 hours into the future.
For a single ingestion request IBM Cloud Logs, these limitations exist:
request_timeout: 30 secondsrequest_body_limit_bytes: 10 MiB
Log query limits for Direct HTTP API Archive Query
Results returned
The maximum number of rows that are returned from a query depends if you are querying from Priority insights or data that is stored in IBM Cloud Object Storage.
- The maximum number of results that are returned from Priority insights is 12 K.
- The maximum number of results that are returned from IBM Cloud Object Storageis 50 K.
Bytes scanned
A maximum of 100 MB is scanned for Priority insights data. No limit exists when data stored in IBM Cloud Object Storage is scanned.
Rate limiting
A maximum of 10 queries per minute can be submitted.
When the rate limit is exceeded, an HTTP 429 is returned.