You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With regards to stats measured, we use WithStatsHandler options to capture call stats. Specifically we only capture the End event which contains stats when an RPC ends. My understanding is that this should include the download of the payload and deserializing of the data. Basically, for unary calls for example, the order of call stats events is:
Begin
OutHeader
OutPayload
InHeader
InPayload
InTrailer
End
This measurement was chosen as it more accurately represents the total lag clients would experience until they can use the call response, so I thought it was a more meaningful data point.
Right now, no there is no mechanism of logging the data from the server. This may be possible with some kind of debug option where we can log to a debug file events and data received.
Thanks!
The text was updated successfully, but these errors were encountered: