bookmark_borderbookmark
Stay organized with collections
Save and categorize content based on your preferences.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-26 UTC."],[[["Client-side traces offer detailed information on each request, including spans with timestamps for RPC request and response times, as well as network and client system latency."],["Span metadata includes essential details like Span ID, Parent Span ID, Project ID, Start Time, and End Time, enabling effective trace analysis."],["Span attributes encompass a wide range of client properties, such as client version, environment, connection settings, database properties, RPC retry settings, and OpenTelemetry configurations."],["Client-side traces log gRPC events, alongside events for AggregateQuery, BatchGetDocuments, RunQuery, Transaction, and Commit operations, offering insights into various client activities."],["Exceptional events that trigger a Span Status = ERROR are captured with relevant information including the exception message, type, and stacktrace for in depth error analysis."]]],[]]
