IBM Cloud Logs limits

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.

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.

IBM Cloud Logs limits the data ingested by a service instance per day.

• If a user sends data too fast, ingestion is throttled.
• If user uses all of the allowed daily ingestion limit, data that is received after that point is blocked and the data is dropped.

For example, data is ingested by IBM Cloud Logs as it is received. When the rate of data ingestion reaches 3 MiB per second, data is ingested at a slower rate. Data is dropped when data reaches 0.25 TB per day. Warnings are sent to the configured email address when the rate reaches the limit. Users also receive an email when data is dropped.

Data in OpenSearch is calculated based on index size after compression.

For a single ingestion request IBM Cloud Logs, these limitations exist:

• request_timeout: 30 seconds
• request_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.