Client-side traces , which are collected by executing RPCs, provide several pieces of information for every request from a client, including spans with timestamps of when the client sent the RPC request and when the client received the RPC response. The spans include latency introduced by the network and client system.
Client-side traces can include the following information:
Span metadata
| Span ID | Unique ID of this span |
| Parent Span ID | ID of the parent span, not set for root span |
| Project ID | Google Cloud project ID that ingested the trace |
| Start Time | Span start time |
| End Time | Span end time |
Span attributes
Google Cloud project ID that contains the Datastore database
Database external ID (name)
Duration in seconds Ex. 0.01s
Duration in seconds Ex. 0.1s
Duration in seconds
Logs and events
Client-side traces provide the following logs and events.
Lookup events
| Event: "Lookup complete" "Transaction.Lookup complete" |
|
|---|---|
| Received | Integer |
| Missing | Integer |
| Deferred | Integer |
| transactional | Boolean |
| transaction_id | String |
Commit Events
| Event: "Commit complete" "Transaction.Commit complete" |
|
|---|---|
| doc_count | Integer |
| transactional | Boolean |
| transaction_id | String |
RunQuery Events
"RunQuery complete"
"Transaction.RunQuery complete"
STRONG
or EVENTUAL
-
NOT_FINISHED -
MORE_RESULTS_AFTER_LIMIT -
MORE_RESULTS_AFTER_CURSOR -
NO_MORE_RESULTS

