google_api_cloud_trace v0.7.0 API Reference

Modules

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.CloudTrace.V1.

Helper functions for deserializing responses into models.

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 `{}`.

The response message for the `ListTraces` method.

A trace describes how long it takes for an application to perform an operation. It consists of a set of spans, each of which represent a single timed event within the operation.

A span represents a single timed event within a trace. Spans can be nested and form a trace tree. Often, a trace contains a root span that describes the end-to-end latency of an operation and, optionally, one or more subspans for its suboperations. Spans do not need to be contiguous. There may be gaps between spans in a trace.

List of new or updated traces.

Helper functions for building Tesla requests.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.CloudTrace.V2.

Helper functions for deserializing responses into models.

Text annotation with a set of attributes.

The allowed types for [VALUE] in a `[KEY]:[VALUE]` attribute.

A set of attributes, each in the format `[KEY]:[VALUE]`.

The request message for the `BatchWriteSpans` method.

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 `{}`.

A pointer from the current span to another span in the same trace or in a different trace. For example, this can be used in batching operations, where a single batch handler processes multiple requests from different traces or when the handler receives a request from a different project.

A collection of links, which are references from this span to a span in the same or different trace.

An event describing a message sent/received between Spans.

An event describing an RPC message sent or received on the network.

A span represents a single operation within a trace. Spans can be nested to form a trace tree. Often, a trace contains a root span that describes the end-to-end latency, and one or more subspans for its sub-operations. A trace can also contain multiple root spans, or none at all. Spans do not need to be contiguous—there may be gaps or overlaps between spans in a trace.

Represents a single stack frame in a stack trace.

A collection of stack frames, which can be truncated.

A call stack appearing in a trace.

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. 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.

A time-stamped annotation or message event in the Span.

A collection of `TimeEvent`s. A `TimeEvent` is a time-stamped annotation on the span, consisting of either user-supplied key:value pairs, or details of a message sent/received between Spans.

A trace describes how long it takes for an application to perform some operations. It consists of a set of spans, each representing an operation and including time information and operation details.

Represents a string that might be shortened to a specified length.

Helper functions for building Tesla requests.