Skip to main content

Quotas & Limits

OmniCore limits resource allocation and use and enforces appropriate quotas on a per-tenant basis. Specific policies vary depending on resource availability, user profile, service usage history, and other factors, and are subject to change without notice.

Limits

This section lists the quotas for OmniCore in three categories: tenant/device/telemetry, rate, and time.

Tenant, device, and telemetry limits

QuotaLimitCan be increased
Devices per tenant, per regionUnlimited, but the default is 100,000Yes
Device registries per project, per region100Yes
Devices bound to a gateway10,000Yes
Devices attached to a gateway10,000Yes
Gateways bound to a device10No
Device ID length256 bytesNo
Device registry ID length256 bytesNo
Combined size of metadata key-value pairs256 KBNo
Credentials per device3No
Configuration versions per device10No
Device configuration data64 KBNo
Maximum page size for list request500No
Telemetry event notification configurations10No
Telemetry event payload256 KBNo

Rate limits

For all Cloud to Device Communication the following Limits apply

  • Rate Limit: 100 per sec
  • Burst Limit: 100 per sec
  • Quota: 10,000 per day

These include

  • Cloud-to-device throughput, per device
  • Configuration updates per device
  • Attribute updates per device
  • Attribute updates per registry
  • Device manager API read calls per tenant
  • Device manager API create and delete calls per tenant
  • Device manager API update calls per tenant(see the exception in the next row)
  • Device manager API modifyCloudToDeviceConfig calls per tenant
  • State updates per device
  • State updates per tenant
  • Commands per registry
  • Commands per tenant

For all Cloud to Device Communication the following Limits apply

RateLimitCan be increased
HTTP device telemetry publishes per device6,00 per minNo
Device telemetry publishes per tenantUnlimited, but the default is 60,000 per minYes
Device-to-cloud throughput, per device512 KB/sNo
State updates per device1 per sec*No
State updates per tenant6,000 per min*Yes
Number of logged events per tenant1,000 per secYes
Size of logged events per tenant1 MB per sec (each log entry is roughly 1 KB)Yes
Commands per registry1,000 per secYes
Commands per tenant1,000 per secYes

Quota enforcement

The consequences of exceeding quota are different for tenants and resources, such as a registries and devices:

  • tenant exceeds quota: tenant is blocked until usage is back under the limit. In rare cases, a quota enforcement period can continue even when your usage is no longer over the limit. If your tenant is still being blocked even though you're no longer exceeding any quotas, wait a while and try again.
  • Device using the TCP bridge exceeds quota: Device is disconnected.

For example, if you attempt to update a device's configuration more than once per second over the TCP/UDP bridge, OmniCore disconnects the device. To fix the problem, ensure you publish device configurations no more than once per second, ideally once per 10 seconds, then reconnect the device. See Configuring Devices for more information.

Quota increases

Contact us