Regen docs (#364)
diff --git a/docs/dyn/cloudtrace_v1.projects.html b/docs/dyn/cloudtrace_v1.projects.html
index 71e5176..3c1086c 100644
--- a/docs/dyn/cloudtrace_v1.projects.html
+++ b/docs/dyn/cloudtrace_v1.projects.html
@@ -72,7 +72,7 @@
</style>
-<h1><a href="cloudtrace_v1.html">Google Cloud Trace API</a> . <a href="cloudtrace_v1.projects.html">projects</a></h1>
+<h1><a href="cloudtrace_v1.html">Stackdriver Trace API</a> . <a href="cloudtrace_v1.projects.html">projects</a></h1>
<h2>Instance Methods</h2>
<p class="toc_element">
<code><a href="cloudtrace_v1.projects.traces.html">traces()</a></code>
@@ -81,11 +81,15 @@
<p class="toc_element">
<code><a href="#patchTraces">patchTraces(projectId, body, x__xgafv=None)</a></code></p>
-<p class="firstline">Sends new traces to Stackdriver 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>
+<p class="firstline">Sends new traces to Stackdriver Trace or updates existing traces. If the ID</p>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="patchTraces">patchTraces(projectId, body, x__xgafv=None)</code>
- <pre>Sends new traces to Stackdriver 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 Stackdriver 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, ID of the Cloud project where the trace data is stored. (required)
@@ -94,19 +98,36 @@
{ # 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.
+ "traceId": "A String", # Globally unique identifier for the trace. This identifier is a 128-bit
+ # numeric value formatted as a 32-byte hex string.
"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.
- "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.
- "name": "A String", # Name of the trace. The trace name is sanitized and displayed in the Stackdriver Trace tool in the {% dynamic print site_values.console_name %}. 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.
- "labels": { # Collection of labels 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.
+ "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.
+ "name": "A String", # Name of the span. Must be less than 128 bytes. The span name is sanitized
+ # and displayed in the Stackdriver Trace tool in the
+ # {% dynamic print site_values.console_name %}.
+ # 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.
+ "labels": { # Collection of labels associated with the span. Label keys must be less than
+ # 128 bytes. Label values must be less than 16 kilobytes.
"a_key": "A String",
},
"parentSpanId": "A String", # ID of the parent span, if any. Optional.
"startTime": "A String", # Start time of the span in nanoseconds from the UNIX epoch.
- "spanId": "A String", # Identifier for the span. This identifier must be unique within a trace.
+ "spanId": "A String", # Identifier for the span. Must be a 64-bit integer other than 0 and
+ # unique within a trace.
"endTime": "A String", # End time of the span in nanoseconds from the UNIX epoch.
},
],
@@ -115,11 +136,22 @@
}
x__xgafv: string, V1 error format.
+ Allowed values
+ 1 - v1 error format
+ 2 - v2 error format
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>