Trace transport request/response sizes in APM #94845
Labels
:Distributed Coordination/Network
Http and internode communication implementations
>enhancement
Supportability
Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
With #94543 we expose some stats about transport request/response sizes. We also expose information about tasks to the APM tracer. And every transport request/response pair begets a task. So we should be able to expose information about transport request/response sizes to APM too. This would be awfully useful when digging deeply into network traffic investigations.
It looks like we can add arbitrary attributes to a span via
Tracer#setAttribute
. Getting the request size there isn't too bad (see below) but the response size looks harder becausewe close the task before serialising the response(edit:see below). Also I don't know if there are any standard attribute names we should use here, or whether it works in APM if we invent attribute names likees.transport.request_bytes
.Patch that adds a request size attribute
Edit: #94865 keeps the task alive until after serializing the response, so maybe this is easier to achieve now.
The text was updated successfully, but these errors were encountered: