docs: update generated docs (#1053)
Updates for both discovery docs and epydoc API Documentation
Fixes: #1049
diff --git a/docs/dyn/cloudtrace_v1.projects.html b/docs/dyn/cloudtrace_v1.projects.html
index fba8f4a..05dabb1 100644
--- a/docs/dyn/cloudtrace_v1.projects.html
+++ b/docs/dyn/cloudtrace_v1.projects.html
@@ -80,16 +80,20 @@
<p class="firstline">Returns the traces Resource.</p>
<p class="toc_element">
+ <code><a href="#close">close()</a></code></p>
+<p class="firstline">Close httplib2 connections.</p>
+<p class="toc_element">
<code><a href="#patchTraces">patchTraces(projectId, body=None, x__xgafv=None)</a></code></p>
-<p class="firstline">Sends new traces to Cloud Trace or updates existing traces. If the ID</p>
+<p class="firstline">Sends new traces to Cloud Trace or updates existing traces. If the ID of a trace that you send matches that of an existing trace, any fields in the existing trace and its spans are overwritten by the provided values, and any new fields provided are merged with the existing trace data. If the ID does not match, a new trace is created.</p>
<h3>Method Details</h3>
<div class="method">
+ <code class="details" id="close">close()</code>
+ <pre>Close httplib2 connections.</pre>
+</div>
+
+<div class="method">
<code class="details" id="patchTraces">patchTraces(projectId, body=None, x__xgafv=None)</code>
- <pre>Sends new traces to Cloud Trace or updates existing traces. If the ID
-of a trace that you send matches that of an existing trace, any fields
-in the existing trace and its spans are overwritten by the provided values,
-and any new fields provided are merged with the existing trace data. If the
-ID does not match, a new trace is created.
+ <pre>Sends new traces to Cloud Trace or updates existing traces. If the ID of a trace that you send matches that of an existing trace, any fields in the existing trace and its spans are overwritten by the provided values, and any new fields provided are merged with the existing trace data. If the ID does not match, a new trace is created.
Args:
projectId: string, Required. ID of the Cloud project where the trace data is stored. (required)
@@ -98,70 +102,20 @@
{ # List of new or updated traces.
"traces": [ # List of traces.
- { # 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 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.
"projectId": "A String", # Project ID of the Cloud project where the trace data is stored.
- "traceId": "A String", # Globally unique identifier for the trace. This identifier is a 128-bit
- # numeric value formatted as a 32-byte hex string. For example,
- # `382d4f4c6b7bb2f4a972559d9085001d`. The numeric value should not be zero.
+ "traceId": "A String", # Globally unique identifier for the trace. This identifier is a 128-bit numeric value formatted as a 32-byte hex string. For example, `382d4f4c6b7bb2f4a972559d9085001d`. The numeric value should not be zero.
"spans": [ # Collection of spans in the trace.
- { # 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.
- "spanId": "A String", # Identifier for the span. Must be a 64-bit integer other than 0 and
- # unique within a trace. For example, `2205310701640571284`.
- "kind": "A String", # Distinguishes between spans generated in a particular context. For example,
- # two spans with the same name may be distinguished using `RPC_CLIENT`
- # and `RPC_SERVER` to identify queueing latency associated with the span.
+ { # 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.
"startTime": "A String", # Start time of the span in nanoseconds from the UNIX epoch.
- "name": "A String", # Name of the span. Must be less than 128 bytes. The span name is sanitized
- # and displayed in the Trace tool in the Google Cloud Platform Console.
- # The name may be a method name or some other per-call site name.
- # For the same executable and the same call point, a best practice is
- # to use a consistent name, which makes it easier to correlate
- # cross-trace spans.
- "endTime": "A String", # End time of the span in nanoseconds from the UNIX epoch.
+ "spanId": "A String", # Identifier for the span. Must be a 64-bit integer other than 0 and unique within a trace. For example, `2205310701640571284`.
+ "name": "A String", # Name of the span. Must be less than 128 bytes. The span name is sanitized and displayed in the Trace tool in the Google Cloud Platform Console. The name may be a method name or some other per-call site name. For the same executable and the same call point, a best practice is to use a consistent name, which makes it easier to correlate cross-trace spans.
"parentSpanId": "A String", # Optional. ID of the parent span, if any.
- "labels": { # Collection of labels associated with the span. Label keys must be less than
- # 128 bytes. Label values must be less than 16 kilobytes (10MB for
- # `/stacktrace` values).
- #
- # Some predefined label keys exist, or you may create your own. When creating
- # your own, we recommend the following formats:
- #
- # * `/category/product/key` for agents of well-known products (e.g.
- # `/db/mongodb/read_size`).
- # * `short_host/path/key` for domain-specific keys (e.g.
- # `foo.com/myproduct/bar`)
- #
- # Predefined labels include:
- #
- # * `/agent`
- # * `/component`
- # * `/error/message`
- # * `/error/name`
- # * `/http/client_city`
- # * `/http/client_country`
- # * `/http/client_protocol`
- # * `/http/client_region`
- # * `/http/host`
- # * `/http/method`
- # * `/http/path`
- # * `/http/redirected_url`
- # * `/http/request/size`
- # * `/http/response/size`
- # * `/http/route`
- # * `/http/status_code`
- # * `/http/url`
- # * `/http/user_agent`
- # * `/pid`
- # * `/stacktrace`
- # * `/tid`
+ "labels": { # Collection of labels associated with the span. Label keys must be less than 128 bytes. Label values must be less than 16 kilobytes (10MB for `/stacktrace` values). Some predefined label keys exist, or you may create your own. When creating your own, we recommend the following formats: * `/category/product/key` for agents of well-known products (e.g. `/db/mongodb/read_size`). * `short_host/path/key` for domain-specific keys (e.g. `foo.com/myproduct/bar`) Predefined labels include: * `/agent` * `/component` * `/error/message` * `/error/name` * `/http/client_city` * `/http/client_country` * `/http/client_protocol` * `/http/client_region` * `/http/host` * `/http/method` * `/http/path` * `/http/redirected_url` * `/http/request/size` * `/http/response/size` * `/http/route` * `/http/status_code` * `/http/url` * `/http/user_agent` * `/pid` * `/stacktrace` * `/tid`
"a_key": "A String",
},
+ "kind": "A String", # Distinguishes between spans generated in a particular context. For example, two spans with the same name may be distinguished using `RPC_CLIENT` and `RPC_SERVER` to identify queueing latency associated with the span.
+ "endTime": "A String", # End time of the span in nanoseconds from the UNIX epoch.
},
],
},
@@ -176,15 +130,7 @@
Returns:
An object of the form:
- { # 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 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 `{}`.
}</pre>
</div>