This document lists the quotas and system limits that apply to Eventarc. Quotas specify the amount of a countable, shared resource that you can use, and they are defined by Google Cloud services such as Eventarc. System limits are fixed values that cannot be changed.
Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.
The Cloud Quotas system does the following:
- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a way to request changes to the quota value
In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.
Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.
There are also system limits on Eventarc resources. System limits can't be changed.
Quotas
If your project needs more of a particular resource than your quotas allow, you can request an increase to most quotas in the Google Cloud console. For more information, see About quota increase requests.
Note that as a pre-GA feature, Eventarc Advanced is available "as is" and its quotas can't be increased.
Eventarc Advanced
| Quota | Description | Value | Can be increased | Scope |
|---|---|---|---|---|
| Bus throughput | Publishing throughput 1 | 384 MB per minute 2 | No | Per project per region per minute |
| Enrollments | Number of enrollments | 100 | No | Per project per region |
| Enrollments | Number of enrollments that can be attached to a bus | 100 | No | Per bus |
| Pipelines | Number of pipelines | 100 | No | Per project per region |
| Write requests | Number of management plane 3 writes | 1000 | No | Per project per region per minute |
1 Throughput quota is measured in 64 kB increments. For example, a 1 kB message would use 64 kB of quota.
2 The maximum pipeline throughput is also 384 MB per minute (or 6.4 MB per second average).
3 Resource API operations.
Eventarc Standard
| Quota | Description | Value | Can be increased | Scope |
|---|---|---|---|---|
| Trigger read requests | Number of trigger API reads | 6000 | Yes | Per project per minute |
| Trigger write requests | Number of trigger API writes | 600 | Yes. The global location has a write limit of 10 QPS. | Per project per minute |
Limits
The number of Eventarc resources is limited for a given project. There is no direct limit on the size of the Eventarc API request.
Eventarc Advanced
| Resource | Description | Limit | Can be increased | Scope |
|---|---|---|---|---|
| Bus | Maximum number of MessageBus resources |
1 | No | Per project |
| Bus | Maximum number of MessageBus resources |
5000 | No | Per organization |
| Event | Event size | 1 MB | No | N/A |
| Google API source | Maximum number of GoogleApiSource resources |
1 | No | Per project |
| Pipeline | Maximum queries per second | 100 (1 KB payload) | No | Per pipeline |
| Read requests | Number of management plane 1 reads | 6000 | No | Per project per region per minute |
| Schema | Maximum size of input or output data format schemas when converting the format of an event | 8 KB | No | Per schema per pipeline |
1 Resource API operations.
Eventarc Standard
| Resource | Description | Limit | Can be increased | Scope |
|---|---|---|---|---|
| Event | Event size | 512 KB | No | N/A |
| Published events (third-party and custom events) | The number of third-party and custom events that can be published per project across all channels | 300 | No. To request an exception, contact support. | Per project |
| Trigger | Maximum number of Trigger resources |
500 | No | Per location per project |
| Trigger | Maximum number of triggers for internal HTTP endpoints | 100 | No | Per project |