Default request referring to version v1 of the Service Control API. This contains the host and root path used as a starting point for constructing service requests.

Manage your Google Service Control data

View and manage your data across Google Cloud Platform services

Represents the entirety of the methods and resources available for the Service Control API service.

Deprecated, use `metadata` field instead. Other service-specific data about the request, response, and other activities.

See: auditLogServiceData smart constructor.

Creates a value of AuditLogServiceData with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• alsdAddtional

Properties of the object. Contains field 'type with type URL.

Other service-specific data about the request, response, and other information associated with the current audited event.

See: auditLogMetadata smart constructor.

Creates a value of AuditLogMetadata with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• almAddtional

Properties of the object.

The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. The error model is designed to be: - Simple to use and understand for most users - Flexible enough to meet unexpected needs # Overview The `Status` message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers *understand* and *resolve* the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package `google.rpc` that can be used for common error conditions. # Language mapping The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the `Status` message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client, it may embed the `Status` in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting. - Batch operations. If a client uses batch request and batch response, the `Status` message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the `Status` message. - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons.

See: status smart constructor.

Creates a value of Status with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• sDetails
• sCode
• sMessage

A list of messages that carry the error details. There is a common set of message types for APIs to use.

The status code, which should be an enum value of google.rpc.Code.

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.

Metadata about the request.

See: requestMetadata smart constructor.

Creates a value of RequestMetadata with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• rmCallerSuppliedUserAgent
• rmCallerIP
• rmDestinationAttributes
• rmCallerNetwork
• rmRequestAttributes

The user agent of the caller. This information is not authenticated and should be treated accordingly. For example: + `google-api-python-client/1.4.0`: The request was made by the Google API client for Python. + `Cloud SDK Command Line Tool apitools-client/1.0 gcloud/0.9.62`: The request was made by the Google Cloud SDK CLI (gcloud). + `AppEngine-Google; (+http://code.google.com/appengine; appid: s~my-project`: The request was made from the `my-project` App Engine app. NOLINT

The IP address of the caller. For caller from internet, this will be public IPv4 or IPv6 address. For caller from a Compute Engine VM with external IP address, this will be the VM's external IP address. For caller from a Compute Engine VM without external IP address, if the VM is in the same organization (or project) as the accessed resource, `caller_ip` will be the VM's internal IPv4 address, otherwise the `caller_ip` will be redacted to "gce-internal-ip". See https://cloud.google.com/compute/docs/vpc/ for more information.

The destination of a network activity, such as accepting a TCP connection. In a multi hop network activity, the destination represents the receiver of the last hop. Only two fields are used in this message, Peer.port and Peer.ip. These fields are optionally populated by those services utilizing the IAM condition feature.

The network of the caller. Set only if the network host project is part of the same GCP organization (or project) as the accessed resource. See https://cloud.google.com/compute/docs/vpc/ for more information. This is a scheme-less URI full resource name. For example: "//compute.googleapis.com/projects/PROJECT_ID/global/networks/NETWORK_ID"

Request attributes used in IAM condition evaluation. This field contains request attributes like request time and access levels associated with the request. To get the whole view of the attributes used in IAM condition evaluation, the user must also look into `AuditLog.authentication_info.resource_attributes`.

The labels or tags on the resource, such as AWS resource tags and Kubernetes resource labels.

See: resourceLabels smart constructor.

Creates a value of ResourceLabels with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• rlAddtional

Request message for the Report method.

See: reportRequest smart constructor.

Creates a value of ReportRequest with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• rrServiceConfigId
• rrOperations

Specifies which version of service config should be used to process the request. If unspecified or no matching version can be found, the latest one will be used.

Operations to be reported. Typically the service should report one operation per request. Putting multiple operations into a single request is allowed, but should be used only when multiple operations are natually available at the time of the report. If multiple operations are in a single request, the total request size should be no larger than 1MB. See ReportResponse.report_errors for partial failure behavior.

Request message for the Check method.

See: checkRequest smart constructor.

Creates a value of CheckRequest with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• crOperation
• crRequestProjectSettings
• crServiceConfigId
• crSkipActivationCheck

The operation to be checked.

Requests the project settings to be returned as part of the check response.

Specifies which version of service configuration should be used to process the request. If unspecified or no matching version can be found, the latest one will be used.

Indicates if service activation check should be skipped for this request. Default behavior is to perform the check and apply relevant quota.

The labels describing the metric value. See comments on google.api.servicecontrol.v1.Operation.labels for the overriding relationship.

See: metricValueLabels smart constructor.

Creates a value of MetricValueLabels with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• mvlAddtional

Distribution represents a frequency distribution of double-valued sample points. It contains the size of the population of sample points plus additional optional information: - the arithmetic mean of the samples - the minimum and maximum of the samples - the sum-squared-deviation of the samples, used to compute variance - a histogram of the values of the sample points

See: distribution smart constructor.

Creates a value of Distribution with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• dSumOfSquaredDeviation
• dMean
• dExponentialBuckets
• dMaximum
• dLinearBuckets
• dCount
• dMinimum
• dBucketCounts
• dExplicitBuckets

The sum of squared deviations from the mean: Sum[i=1..count]((x_i - mean)^2) where each x_i is a sample values. If `count` is zero then this field must be zero, otherwise validation of the request fails.

The arithmetic mean of the samples in the distribution. If `count` is zero then this field must be zero.

Buckets with exponentially growing width.

The maximum of the population of values. Ignored if `count` is zero.

Buckets with constant width.

The total number of samples in the distribution. Must be >= 0.

The minimum of the population of values. Ignored if `count` is zero.

The number of samples in each histogram bucket. `bucket_counts` are optional. If present, they must sum to the `count` value. The buckets are defined below in `bucket_option`. There are N buckets. `bucket_counts[0]` is the number of samples in the underflow bucket. `bucket_counts[1]` to `bucket_counts[N-1]` are the numbers of samples in each of the finite buckets. And `bucket_counts[N] is the number of samples in the overflow bucket. See the comments of `bucket_option` below for more details. Any suffix of trailing zeros may be omitted.

Buckets with arbitrary user-provided width.

Quota mode for this operation.

Describing buckets with exponentially growing width.

See: exponentialBuckets smart constructor.

Creates a value of ExponentialBuckets with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• ebGrowthFactor
• ebScale
• ebNumFiniteBuckets

The i'th exponential bucket covers the interval [scale * growth_factor^(i-1), scale * growth_factor^i) where i ranges from 1 to num_finite_buckets inclusive. Must be larger than 1.0.

The i'th exponential bucket covers the interval [scale * growth_factor^(i-1), scale * growth_factor^i) where i ranges from 1 to num_finite_buckets inclusive. Must be > 0.

The number of finite buckets. With the underflow and overflow buckets, the total number of buckets is `num_finite_buckets` + 2. See comments on `bucket_options` for details.

This message defines attributes for a node that handles a network request. The node can be either a service or an application that sends, forwards, or receives the request. Service peers should fill in the `service`, `principal`, and `labels` as appropriate.

See: peer smart constructor.

Creates a value of Peer with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• pRegionCode
• pService
• pIP
• pPrincipal
• pLabels
• pPort

The CLDR country/region code associated with the above IP address. If the IP address is private, the `region_code` should reflect the physical location where this peer is running.

The canonical service name of the peer. NOTE: different systems may have different service naming schemes.

The IP address of the peer.

The identity of this peer. Similar to `Request.auth.principal`, but relative to the peer instead of the request. For example, the idenity associated with a load balancer that forwared the request.

The labels associated with the peer.

The network port of the peer.

Authorization information for the operation.

See: authorizationInfo smart constructor.

Creates a value of AuthorizationInfo with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• aiGranted
• aiResourceAttributes
• aiResource
• aiPermission

Whether or not authorization for `resource` and `permission` was granted.

Resource attributes used in IAM condition evaluation. This field contains resource attributes like resource type and resource name. To get the whole view of the attributes used in IAM condition evaluation, the user must also look into `AuditLog.request_metadata.request_attributes`.

The resource being accessed, as a REST-style string. For example: bigquery.googleapis.com/projects/PROJECTID/datasets/DATASETID

The required IAM permission.

Represents information regarding an operation.

See: operation smart constructor.