Configuring target burst capacity

If a traffic burst is too large for the application to handle, the Activator service will be placed in the request path to protect the revision and optimize request load balancing.

Target burst capacity can be configured using a combination of the following parameters:

• Setting the targeted concurrency limits for the revision. For more information, see the documentation on concurrency.
• Setting the target burst capacity per revision.

• Global key: No global key.
• Possible values: float
• Default:

Example: