API Reference google_api_logging v0.41.2


API client metadata for GoogleApi.Logging.V2.

API calls for all endpoints tagged BillingAccounts.

API calls for all endpoints tagged Entries.

API calls for all endpoints tagged Exclusions.

API calls for all endpoints tagged Folders.

API calls for all endpoints tagged Locations.

API calls for all endpoints tagged Logs.

API calls for all endpoints tagged MonitoredResourceDescriptors.

API calls for all endpoints tagged Organizations.

API calls for all endpoints tagged Projects.

API calls for all endpoints tagged Sinks.

API calls for all endpoints tagged V2.

Handle Tesla connections for GoogleApi.Logging.V2.

Options that change functionality of a sink exporting data to BigQuery.

BucketOptions describes the bucket boundaries used to create a histogram for the distribution. The buckets can be in a linear sequence, an exponential sequence, or each bucket can be specified explicitly. BucketOptions does not include the number of values in each bucket.A bucket has an inclusive lower bound and exclusive upper bound for the values that are counted for that bucket. The upper bound of a bucket must be strictly greater than the lower bound. The sequence of N buckets for a distribution consists of an underflow bucket (number 0), zero or more finite buckets (number 1 through N - 2) and an overflow bucket (number N - 1). The buckets are contiguous: the lower bound of bucket i (i > 0) is the same as the upper bound of bucket i - 1. The buckets span the whole range of finite values: lower bound of the underflow bucket is -infinity and the upper bound of the overflow bucket is +infinity. The finite buckets are so-called because both bounds are finite.

The request message for Operations.CancelOperation.

Describes the customer-managed encryption key (CMEK) settings associated with a project, folder, organization, billing account, or flexible resource.Note: CMEK for the Log Router can currently only be configured for Google Cloud organizations. Once configured, it applies to all projects and folders in the Google Cloud organization.See Enabling CMEK for Log Router (https://cloud.google.com/logging/docs/routing/managed-encryption) for more information.

Metadata for CopyLogEntries long running operations.

The parameters to CopyLogEntries.

Response type for CopyLogEntries long running operations.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for Empty is empty JSON object {}.

Specifies a set of buckets with arbitrary widths.There are size(bounds) + 1 (= N) buckets. Bucket i has the following boundaries:Upper bound (0 <= i < N-1): boundsi Lower bound (1 <= i < N); boundsi - 1The bounds field must contain at least one element. If bounds has only one element, then there are no finite buckets, and that single element is the common boundary of the overflow and underflow buckets.

Specifies an exponential sequence of buckets that have a width that is proportional to the value of the lower bound. Each bucket represents a constant relative uncertainty on a specific value in the bucket.There are num_finite_buckets + 2 (= N) buckets. Bucket i has the following boundaries:Upper bound (0 <= i < N-1): scale (growth_factor ^ i). Lower bound (1 <= i < N): scale (growth_factor ^ (i - 1)).

A common proto for logging HTTP requests. Only contains semantics defined by the HTTP specification. Product-specific logging information MUST be defined in a separate message.

A description of a label.

Specifies a linear sequence of buckets that all have the same width (except overflow and underflow). Each bucket represents a constant absolute uncertainty on the specific value in the bucket.There are num_finite_buckets + 2 (= N) buckets. Bucket i has the following boundaries:Upper bound (0 <= i < N-1): offset + (width i). Lower bound (1 <= i < N): offset + (width (i - 1)).

The response from ListBuckets.

Result returned from ListExclusions.

The response message for Locations.ListLocations.

The parameters to ListLogEntries.

Result returned from ListLogEntries.

Result returned from ListLogMetrics.

Result returned from ListLogs.

Result returned from ListMonitoredResourceDescriptors.

The response message for Operations.ListOperations.

Result returned from ListSinks.

The response from ListViews.

A resource that represents Google Cloud Platform location.

Describes a repository in which log entries are stored.

An individual entry in a log.

Additional information about a potentially long-running operation with which a log entry is associated.

Additional information about the source code location that produced the log entry.

Specifies a set of log entries that are filtered out by a sink. If your Google Cloud resource receives a large volume of log entries, you can use exclusions to reduce your chargeable logs. Note that exclusions on organization-level and folder-level sinks don't apply to child resources. Note also that you cannot modify the _Required sink or exclude logs from it.

Application log line emitted while processing a request.

Describes a logs-based metric. The value of the metric is the number of log entries that match a logs filter in a given time interval.Logs-based metrics can also be used to extract values from logs and create a distribution of the values. The distribution records the statistics of the extracted values along with an optional histogram of the values as specified by the bucket options.

Describes a sink used to export log entries to one of the following destinations in any project: a Cloud Storage bucket, a BigQuery dataset, a Pub/Sub topic or a Cloud Logging log bucket. A logs filter controls which log entries are exported. The sink must be created within a project, organization, billing account, or folder.

Describes a view over log entries in a bucket.

Defines a metric type and its schema. Once a metric descriptor is created, deleting or altering it stops data collection and makes the metric type's existing data unusable.

Additional annotations that can be used to guide the usage of a metric.

An object representing a resource that can be used for monitoring, logging, billing, or other purposes. Examples include virtual machine instances, databases, and storage devices such as disks. The type field identifies a MonitoredResourceDescriptor object that describes the resource's schema. Information in the labels field identifies the actual resource and its attributes according to the schema. For example, a particular Compute Engine VM instance could be represented by the following object, because the MonitoredResourceDescriptor for "gce_instance" has labels "instance_id" and "zone": { "type": "gce_instance", "labels": { "instance_id": "12345678901234", "zone": "us-central1-a" }}

An object that describes the schema of a MonitoredResource object using a type name and a set of labels. For example, the monitored resource descriptor for Google Compute Engine VM instances has a type of "gce_instance" and specifies the use of the labels "instance_id" and "zone" to identify particular VM instances.Different APIs can support different monitored resource types. APIs generally provide a list method that returns the monitored resource descriptors used by the API.

Auxiliary metadata for a MonitoredResource object. MonitoredResource objects contain the minimum set of information to uniquely identify a monitored resource instance. There is some other useful auxiliary metadata. Monitoring and Logging use an ingestion pipeline to extract metadata for cloud resources of all types, and store the metadata in this message.

This resource represents a long-running operation that is the result of a network API call.

Complete log information about a single HTTP request to an App Engine application.

Specifies a location in a source code file.

A reference to a particular snapshot of the source tree used to build and deploy an application.

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 (https://github.com/grpc). Each Status message contains three pieces of data: error code, error message, and error details.You can find out more about this error model and how to work with it in the API Design Guide (https://cloud.google.com/apis/design/errors).

Information about entries that were omitted from the session.

The parameters to TailLogEntries.

Result returned from TailLogEntries.

The parameters to UndeleteBucket.

The parameters to WriteLogEntries.

Result returned from WriteLogEntries.