The service associated with the operation. The service
name is specific to each service implementation and should be
chosen to avoid conflicts with other service implementations. These
service names correspond to the service definition in the admin
console.
The network resource logical name. This name is
used to uniquely identify a network resource specification.
Service implementations may be configured to use their own
network resource logical names or may share logical
names.
The exceeded rate limit. This limit need not match
the configured sustained traffic rate limit if the component
implementation uses an allocation scheme across the
cluster.
The resource burst size. This limit need not match
the configured burst limit for the resource if the component
implementation uses an allocation scheme across the
cluster.
<xhtml:p>The service associated with the operation. The service
name is specific to each service implementation and should be
chosen to avoid conflicts with other service implementations. These
service names correspond to the service definition in the admin
console.</xhtml:p>
<xhtml:p>The network resource logical name. This name is
used to uniquely identify a network resource specification.
Service implementations may be configured to use their own
network resource logical names or may share logical
names.</xhtml:p>
<xhtml:p>The exceeded rate limit. This limit need not match
the configured sustained traffic rate limit if the component
implementation uses an allocation scheme across the
cluster.</xhtml:p>
<xhtml:p>The resource burst size. This limit need not match
the configured burst limit for the resource if the component
implementation uses an allocation scheme across the
cluster.</xhtml:p>