Batch writes new spans to new or existing traces. You cannot update existing spans.
HTTP request
POST https://cloudtrace.googleapis.com/v2/{name=projects/*}/traces:batchWrite
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Required. The name of the project where the spans belong. The format is Authorization requires the following IAM permission on the specified resource
|
Request body
The request body contains data with the following structure:
JSON representation |
---|
{
"spans": [
{
object ( |
Fields | |
---|---|
spans[] |
Required. A list of new spans. The span names must not match existing spans, otherwise the results are undefined. |
Response body
If successful, the response body is an empty JSON object.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/trace.append
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
Span
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 might be gaps or overlaps between spans in a trace.
JSON representation |
---|
{ "name": string, "spanId": string, "parentSpanId": string, "displayName": { object ( |
Fields | |
---|---|
name |
Required. The resource name of the span in the following format:
|
span |
Required. The |
parent |
The |
display |
Required. A description of the span's operation (up to 128 bytes). Cloud Trace displays the description in the Cloud console. For example, the display name can be a qualified method name or a file name and a line number where the operation is called. A best practice is to use the same display name within an application and at the same call point. This makes it easier to correlate spans in different traces. |
start |
Required. The start time of the span. On the client side, this is the time kept by the local machine where the span execution starts. On the server side, this is the time when the server's application handler starts running. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
end |
Required. The end time of the span. On the client side, this is the time kept by the local machine where the span execution ends. On the server side, this is the time when the server application handler stops running. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
attributes |
A set of attributes on the span. You can have up to 32 attributes per span. |
stack |
Stack trace captured at the start of the span. |
time |
A set of time events. You can have up to 32 annotations and 128 message events per span. |
links |
Links associated with the span. You can have up to 128 links per Span. |
status |
Optional. The final status for this span. |
same |
Optional. Set this parameter to indicate whether this span is in the same process as its parent. If you do not set this parameter, Trace is unable to take advantage of this helpful information. |
child |
Optional. The number of child spans that were generated while this span was active. If set, allows implementation to detect missing child spans. |
span |
Optional. Distinguishes between spans generated in a particular context. For example, two spans with the same name may be distinguished using |