|
|
|
@ -1,4 +1,4 @@ |
|
|
|
|
// Copyright (c) 2015, Google Inc. |
|
|
|
|
// Copyright 2016 Google Inc. |
|
|
|
|
// |
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License"); |
|
|
|
|
// you may not use this file except in compliance with the License. |
|
|
|
@ -41,8 +41,8 @@ service TraceService { |
|
|
|
|
option (google.api.http) = { get: "/v1/projects/{project_id}/traces/{trace_id}" }; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// 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 |
|
|
|
|
// 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. |
|
|
|
@ -93,7 +93,8 @@ message TraceSpan { |
|
|
|
|
RPC_CLIENT = 2; |
|
|
|
|
} |
|
|
|
|
|
|
|
|
|
// Identifier for the span. This identifier must be unique within a trace. |
|
|
|
|
// Identifier for the span. Must be a 64-bit integer other than 0 and |
|
|
|
|
// unique within a trace. |
|
|
|
|
fixed64 span_id = 1; |
|
|
|
|
|
|
|
|
|
// Distinguishes between spans generated in a particular context. For example, |
|
|
|
@ -102,10 +103,11 @@ message TraceSpan { |
|
|
|
|
SpanKind kind = 2; |
|
|
|
|
|
|
|
|
|
// Name of the trace. The trace name is sanitized and displayed in the |
|
|
|
|
// Cloud Trace tool in the Google Developers 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. |
|
|
|
|
// Stackdriver Trace tool in the Google Developers 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. |
|
|
|
|
string name = 3; |
|
|
|
|
|
|
|
|
|
// Start time of the span in nanoseconds from the UNIX epoch. |
|
|
|
|